Print      Open PDF Version of Online Help

Administering Oracle CRM On Demand > Life Sciences Management > Setting Up the Automatic Submission of Sample Transactions

Setting Up the Automatic Submission of Sample Transactions

This topic describes how to use the workflow functionality in Oracle CRM On Demand to automatically submit sample transactions for processing.

Before you begin. Review the information in About the Automatic Submission of Sample Transactions.

To set up the automatic submission of sample transactions

1. Determine which fields on the sample transactions that you will use in the condition on the workflow rules.

   For example, you might decide to use the setting in a check box field on the sample transaction record type as the criterion for determining whether a record must be submitted. In the workflow rule, you can specify that if the check box is selected on a record, then the workflow submits the record. You can use an existing check box field, or you might want to set up a custom check box field and give it a name, such as Mark for Submit. For more information on setting up custom fields, see the sections on Field Management and Page Layout Management in the table in Record Type Application Customization Page.

2. Set up the necessary workflow rules for the Sample Transaction record type.

   You can set up as many workflow rules as you want. It is likely that you will want to set up a workflow rule with the When Modified Record Saved trigger event to automatically submit the sample transaction records that are modified.

   NOTE: While configuring the workflow rule, you must also include a condition to check whether the Status field is set to a value of In Progress. This condition is required so that when the Submit action runs successfully, the action changes the Status field of the Sample Transaction record, which is a modification action that calls this workflow again.

   The following is an example of a minimal rule condition:

   [<bMark_for_Submit_ITAG>]="Y" AND [<TransactionStatus>]="In Progress" AND ExcludeChannel("Online")

   In this example, Mark for Submit is a custom field, and ExcludeChannel is an optional condition that allows you to restrict the trigger so that the workflow becomes active only for an import, and not when the Submit Call button is used in the UI. If you receive any errors when this workflow action is triggered, see Viewing Error Instances in the Workflow Error Monitor.

   For information about setting up workflow rules, see Creating Workflow Rules.

3. In each of the workflow rules, specify the condition that must be met for the actions on the workflow to be performed.

   For example, you can specify that if a certain check box field on the record is selected, then the actions on the workflow rule must be performed.

   NOTE: If you want to prevent the workflow rules from submitting records that are created or updated through the user interface, then set up the necessary restriction in the conditions on your workflow rules. For more information, see Restricting Workflow Rules to Specific Channels or Roles.

4. Create the necessary Submit workflow action on each of your workflow rules.

   For more information on the Submit workflow action, see the information on workflow actions for Oracle CRM On Demand Life Sciences Edition in About Workflow Actions.

   NOTE: The Submit action must be preceded by a Wait action with a non-zero wait value. Using a non-zero wait renders the workflow action as an asynchronous action. An asynchronous action is recommended for overall application performance, especially if you are importing and submitting a large set of sample transaction records.

NOTE: The language-independent field names and the field-name syntax used in any example expressions in this topic are the field names and the field-name syntax that were used in Expression Builder in releases earlier than Release 29 Service Pack 1. These examples are still valid. However, if you select the corresponding fields for an expression from the Fields list in Expression Builder in Release 29 Service Pack 1 or later, then the field names and the field-name syntax will be different from those shown in the examples. It is recommended that you always select the fields for your expressions from the Fields list in Expression Builder, so that the field names and the field-name syntax are always correct. For more information about the field names and the field-name syntax in expressions, see About Expressions.