Imprimir      Abrir versão PDF da ajuda online


Previous Topic

Next Topic

Creating Scheduled Events for Analytics

You can create one or more scheduled events for the Analytics record type and configure one or more Send Email actions on the event to perform the following tasks:

  • Execute an Analytics object on behalf of one or more specified users. The Analytics object can be an analysis, a dashboard, or a dashboard page.
  • Send the results that are generated for a user to that user as an email attachment.

The specified user's access rights determine the results that are generated for that user.

A scheduled event for the Analytics record type is different from a scheduled event for other record types in the following ways:

  • You do not select a list of records for the scheduled event.
  • Only the Send Email action is supported.
  • On the scheduled event, you add a list of the users on whose behalf the Analytics object is to be executed.
  • The Hourly interval type is not available.

A Send Email workflow action for a scheduled event for the Analytics record type is different from a Send Email action for other record types in the following ways:

  • You do not specify a recipient for the email that you configure on the action. The emails are sent to the users who are selected on the workflow rule.
  • The Send Email action executes an Analytics object, as well as sending the emails with the results to the users.
  • You must select the Analytics object that is to be executed, and select the format for the output.

You can create up to a maximum of five Send Email actions on a scheduled event for Analytics. When an instance of the event is executed, all of the actions are performed in sequence for the first user in the list, then all of the actions are performed for the next user, and so on through the list of users.

NOTE: The operations that are performed by workflow actions on scheduled events for the Analytics record type, and the requests and data that are processed by the actions, are counted towards your company's usage against the report services allotments. For information about service allotments, see About Service Allotments. The files that are generated by the workflow actions might also be included in the calculation of the amount of storage used by your company, depending on how long email attachments are retained for your company. The retention period for email attachments is specified in the Email Attachment Expiry (Days) field on the company profile. For more information, see Configuring Company Settings.

Workflow Action Failures

If a workflow action on a scheduled event for the Analytics record type fails for one or more users, then the failure is reported in the Workflow Error Monitor. For more information about what happens when a workflow action on a scheduled event for the Analytics record type fails, see About Workflow Rule and Workflow Action Failures.

Considerations When Scheduling an Event

Aplicam-se as seguintes considerações ao agendar um evento:

  • Não pode especificar uma condição num evento agendado. As instâncias agendadas do evento e as ações de fluxo de trabalho sobre o evento são sempre executadas, salvo se ocorrer um erro.

    NOTA: Depois de selecionar o evento acionador Evento Agendado na página Nova Regra de Fluxo de Trabalho, a página é renovada. A secção Condição de Regras de Fluxo de Trabalho da página é retirada e a secção Detalhes de Agendamento, onde especifica o agendamento do evento, fica disponível.

  • Por questões de desempenho, é recomendado que evite a configuração de vários eventos agendados para executarem ao mesmo tempo.
  • Deve especificar uma data e hora de início para o evento agendado e uma data e hora de fim ou o número de vezes que o evento deve ser executado.

    NOTA: o Oracle CRM On Demand não gera instâncias para datas e horas no passado mesmo que especifique uma data e hora de início no passado. Por exemplo, se especificar uma data de início de 15 de janeiro de 2018 para um evento agendado que deve repetir-se 10 vezes em intervalos de um mês e a data atual fosse 30 de maio de 2018, a primeira instância do evento estaria agendada para 15 de junho de 2018. Apenas serão executadas as instâncias das cinco ocorrências no futuro.

  • Se especificar que o evento agendado deve ser executado em determinada data do mês e se essa data não existir em determinado mês, o evento não será executado nesse mês. Por exemplo, se selecionar o dia 29 de um mês, o evento não será executado em fevereiro, exceto se for um ano bissexto.
  • You can specify that no email is to be sent to a user if the analysis selected on a Send Email action returns no results for that user. By default, the Send Email if No Results check box is selected on the Send Email action, and the email is sent to all of the users selected on the workflow rule, even if the analysis returns no results for a user. If you deselect the check box, then the email will be sent only to those users for whom the analysis returns results.

    NOTE: The Send Email if No Results check box is available only if an analysis is selected on the Send Email action. It is not available if a dashboard or dashboard page is selected on the Send Email action.

    If no email is sent to a user because the analysis returned no results for that user, then the workflow action is considered to have failed for that user, and the failure is reported in the workflow error monitor.

    TIP: If you want the email to be sent to some users even if the analysis returns no results for those users, but you do not want the email to be sent to other users if the analysis returns no results for them, then you can create two separate scheduled events with Send Email actions to execute the same analysis, but with different sets of users. On the scheduled event with the users to whom you do not want the email to be sent if the analysis returns no results, deselect the Send Email if No Results check box.

The following procedure describes how to create a scheduled event for the Analytics record type.

Before you begin. To perform the following procedure, your user role must have the following privileges:

  • Manage Data Rules - Manage Workflow Rules
  • Access V3 Analytics

To create a scheduled event for the Analytics record type

  1. No canto superior direito de qualquer página, clique na ligação global Admin.
  2. Na secção Gestão do processo empresarial, clique em Configuração do fluxo de trabalho.
  3. Na página Lista de Regras de Fluxo de Trabalho, execute um dos seguintes procedimentos:
    • Para criar um novo evento agendado através da cópia de um evento existente, clique em Copiar no evento agendado que pretende copiar.
    • Para criar um novo evento agendado que não se baseie num evento existente, clique em Novo na barra de título.
  4. Na página Detalhe da Regra de Fluxo de Trabalho, na secção Detalhes de Regras de Fluxo de Trabalho Chave, preencha as informações do evento agendado.

    A tabela seguinte descreve os campos.

    Field

    Description

    Workflow Name

    Enter a unique name, up to 50 characters.

    Active

    Use the Active check box to activate or deactivate the scheduled event.

    Up to the time that a scheduled event is made active, the Initiated By field on the scheduled event record shows the name of the user who created the scheduled event. The Initiated By field is shown in the Detail page for the scheduled event after the record is saved.

    After the Active check box is selected on the scheduled event and the record is saved, the Initiated By field on the record is updated to show the name of the user who selected the Active check box.

    The Initiated By field in all pending instances and all error instances for the scheduled event also shows the name of the user who selected the Active check box on the scheduled event.

    NOTE: When you make the scheduled event active, an instance is immediately generated for the first scheduled occurrence of the event. As a best practice, set up all of the workflow actions on the scheduled event before you make the event active. Otherwise, if the start time for the scheduled event is near, the first instance might be executed before you have finished setting up the workflow actions.

    For more information about what happens when you activate or deactivate a scheduled event, see About Scheduled Events.

    Description

    (Optional) Enter additional information about the scheduled event, such as the purpose of the event.

    Record Type

    Select Analytics.

    Trigger Event

    Only the Scheduled Event trigger event is supported for the Analytics record type.

    Enable Notification

    Select this check box if you want Oracle CRM On Demand to send email notifications to the user who made the scheduled event active. If this check box is selected, an email is sent each time an instance of the scheduled event completes successfully, each time an instance of the event fails, and each time a pending instance of the event is deleted.

  5. No campo Data de Início, selecione a data e hora a que pretende que a primeira instância do evento agendado seja executada.
  6. No campo Recorrente, selecione o intervalo a que pretende que o evento agendado se repita, por exemplo, Semanalmente.
  7. No campo Intervalo de, configure o período do intervalo para as instâncias de repetição. Por exemplo, se tiver selecionado Semanalmente no campo Recorrente e se pretender que as instâncias se repitam em intervalos de duas semanas, introduza 2 no campo Intervalo de. O valor mínimo que pode introduzir é 1.
  8. Se tiver selecionado Mensalmente no campo Recorrente, pode agendar opcionalmente o evento para executar no último dia de cada mês em que o evento é executado, selecionando a caixa Último dia do mês.

    Por exemplo, se tiver configurado um evento agendado para iniciar a 23 de abril e repetir em intervalos de dois meses, a primeira instância do evento será executada a 23 de abril. A segunda instância será executada a 23 de junho, a terceira a 23 de agosto e assim sucessivamente. Contudo, se selecionar a caixa Último dia do mês, a primeira instância do evento será executada a 30 de abril, a segunda instância a 30 de junho, a terceira instância a 31 de agosto e assim sucessivamente.

  9. Especifique o número de vezes que pretende que o evento agendado seja executado ou especifique a data e hora de fim, através de uma das seguintes opções:
    • Selecione a opção Após e especifique o número de vezes que o evento agendado deve ser executado. O valor que introduzir deve ser superior a 0 (zero).
    • Selecione a opção Por Hora/Data e selecione a data e hora de fim do evento agendado. A data e hora de fim deve ser posterior à data e hora de início.
  10. Grave as alterações.

Adding Users to Scheduled Events for Analytics

The following procedure describes how to add the list of users on whose behalf the workflow actions on the scheduled event will be executed.

To add a list of users to a scheduled event for Analytics

  1. On the Workflow Rule Detail page, in the Execute As related information section, click Add.
  2. In the Lookup window, search for the users for whom you want the workflow rule to execute the workflow actions.
  3. When you finish selecting users, click OK to close the lookup window.

Creating Send Email Actions for Scheduled Events for Analytics

The following procedure describes how to create a Send Email action for a scheduled event for the Analytics record type.

Before you begin:

  • If you want the Send Email action to execute an analysis, then the analysis must be saved in the catalog, in a folder under Shared Folders, and you must have access to the folder. For the action to complete successfully at runtime for a user specified on the scheduled event, that user must also have access to the folder.
  • If you want the Send Email action to execute a dashboard or dashboard page:
    • The dashboard or dashboard page must be saved in the system-generated Dashboards subfolder directly under /Shared Folders/Company Wide Shared Folder or in the system-generated Dashboards subfolder directly under /Shared Folders/Migrated Company Wide Shared Folder, and you must have access to the dashboard. If the dashboard or dashboard page is stored in the system-generated Dashboards subfolder directly under /Shared Folders/Migrated Company Wide Shared Folder, then you must have the Access Migrated Company Wide Shared Folder privilege.
    • For the action to complete successfully at runtime for a user specified on the scheduled event, that user must have access to the dashboard or dashboard page. If the dashboard or dashboard page is stored in the system-generated Dashboards subfolder directly under /Shared Folders/Migrated Company Wide Shared Folder, then the user must have the Access Migrated Company Wide Shared Folder privilege.
  • If the name of the analysis, dashboard, or dashboard page that you select on the Send Email action contains any of the following special characters, then the character is replaced with an underscore (_) in the name of the file that is sent to the specified user:
    • Asterisk (*)
    • Backslash (\)
    • Colon (:)
    • Comma (,)
    • Double quotation marks (")
    • Greater than symbol (>)
    • Less than symbol (<)
    • Question mark (?)
    • Slash (/)
    • Vertical bar (|)

To create a Send Email action for a scheduled event for the Analytics record type

  1. In the Workflow Rule Detail page, in the Actions related information section, click Menu and select Send Email.
  2. In the Workflow Action Edit page, in the Key Action Details section, complete the detail fields for the workflow action.

    For information about the Mark for Translation check box, see Creating Workflow Actions: Send Email.

  3. In the Analytics Content Details section, do the following:
    1. In the Content Type field, select the type of Analytics object that you want the action to execute.
    2. In the Content Format field, select the type of output that you want the action to generate.
    3. (Optional) If the selected Analytics object is an analysis, and if you do not want the email to be sent to a user if the analysis returns no results for that user, then deselect the Send Email if No Results check box.
    4. Click the Lookup icon for the Content Name Path field to open a pop-up window that displays the catalog.
    5. Browse to the Analytics object that you want and select it, and then click OK.
    6. (Optional) In the Parameters field, enter the parameters for the Analytics object.

      Specifying the parameters for an Analytics object in a workflow action is similar to specifying the parameters for an analysis or dashboard in a Web applet or Web tab. For more information, see About Specifying Filters for Embedded Reports and Dashboards.

  4. In the Email Message section, fill in the From, Reply To, Subject, Email Format, and Message Body fields.

    For information about these fields, see Creating Workflow Actions: Send Email.

    NOTE: If you include fields from the User record type in the email subject or message body, then the fields are populated with the values from the user record of the user on whose behalf the Analytics object is executed.

  5. Save the workflow action.

NOTE: If the size of a file that is to be attached to an outbound email is not greater than 2 MB, then Oracle CRM On Demand attaches the file to the email. If the size of the file is greater than 2 MB, then Oracle CRM On Demand zips the file. If the size of the zipped file is not greater than 2 MB, then the zipped file is attached to the email. Otherwise, the file is not attached to the email. The users on whose behalf the scheduled event was executed can access the unzipped files, as well as the emails, through their personal email monitor, regardless of whether or not the files were sent with the emails. For information about accessing the personal email monitor, see Accessing Your Pending and Sent Emails. If your user role has the Access Master Audit Trail and Admin Configuration Audit privilege, then you can also access the emails and attachments for all users through the company email monitor. For more information, see Reviewing Your Company's Pending and Sent Emails.


Publicado em Agosto 2021 Copyright © 2005, 2021, Oracle e/ou respetivas associadas. Legal Notices.