| Print Open PDF Version of Online Help

2. #### Example of Using Processes to Lock Records This topic gives an example of creating a process to support the scenario described in Scenario for Locking Activity Records. You might use this feature differently, depending on your business model. You create a process that limits the actions that users can perform, as follows: When the status of the record is Completed, users cannot delete the record. When the status of the record is Submitted, the following happens: Users cannot update or delete the record, or link other records to the call activity record. All fields on the call activity record are read-only. The process applies to account calls and professional calls but not to general calls. To set up a process to lock call activity records In Oracle CRM On Demand, create a process as follows: In the Process Name field, enter a unique name for the process. In the Object Name field, select Activity. When you select Activity in the Object Name field, the value in the Primary Field is automatically set to Call Type. The Transition Field is automatically set to Status. For more information about creating processes, see Creating Processes. Add the transition states shown in the following table to the process that you created in Step 1 of this procedure. For more information about adding transition states to processes, see Adding Transition States to Processes.
   State | Disable Update Check Box | Disable Delete/Remove Check Box
   --- | --- | ---
   Not Started | Deselected | Deselected
   In Progress | Deselected | Deselected
   Completed | Deselected | Selected
   Committed | Selected | Selected
5. Restrict the process so that it applies to account calls and professional calls but not to general calls, by adding the Account Calls and Professional Calls primary values to the process. For more information about restricting processes, see Restricting Processes. On the Submitted transition state, configure the field setup, and select the Read-Only check box for all fields. For more information about configuring the field setup for transition states, see Configuring the Field Setup for Transition States. On the Completed and Submitted transition states, enable the appropriate access controls for the related record types. The settings for the check boxes are shown in the following table. For more information about enabling access controls for related record types, see Enabling Access Controls for Related Record Types.
   Transition State | Related Record Type | Disable Create/Add | Disable Update | Disable Delete/Remove
   --- | --- | --- | --- | ---
   Completed | Message Responses | Deselected | Deselected | Selected
   Products Detailed | Deselected | Deselected | Selected
   Promotional Item Dropped | Deselected | Deselected | Selected
   Samples Dropped | Deselected | Deselected | Selected
   Sample Requests | Deselected | Deselected | Selected
   Sample Transactions | Deselected | Deselected | Selected
   Signatures | Deselected | Deselected | Selected
   Solutions | Deselected | Deselected | Selected
   Submitted | Attachments | Selected | Selected | Selected
   Books | Selected | Selected | Selected
   Contacts (M:M) | Selected | Selected | Selected
   Custom Objects 01 through 03 | Selected | Selected | Selected
   Message Responses | Selected | Selected | Selected
   Products Detailed | Selected | Selected | Selected
   Samples Dropped | Selected | Selected | Selected
   Sample Requests | Selected | Selected | Selected
   Sample Transactions | Selected | Selected | Selected
   Signatures | Selected | Selected | Selected
   Solutions (M:M) | Selected | Selected | Selected
NOTE: Sample request records have sample request item records linked to them that must also be locked when the parent record is locked. To lock the sample request item records, you must set up a separate process that is based on the Sample Request record type. Similarly, sample transaction records have transaction item records linked to them. To lock the transaction item records, you must set up a separate process that is based on the Sample Transaction record type. The process that you set up for a record type locks the parent records of that record type and their child records, but the process does not lock any records that are linked to the child records.

Published 5/23/2022 | Copyright © 2005, 2022, Oracle and/or its affiliates. Legal Notices.