Transactions
The Transaction allows customers to map a business process and:
• Build a configurable screen for user input
• Setup smart lookup filters
• Create Object Mappings to map data from a source object or set default values
• Filter records to be loaded on configurable screen
• Set up custom buttons to call apex services
Key Benefits of Transactions
The following list details the key benefits of Transactions.
• Improves adoption by focused user experience
• Eases of maintenance
• Reduces customization
• Reduces clicks and contextual screen switching
• Eliminates duplicate data entry
• Provides access to the right data at the right time
• Provides relevant data to the users by lookup filters and contextual lookups
• Enables parent-child associations to expand or collapse sections
 |
You can invoke Transactions directly from a Wizard or embedded in the flow.
|
There are following types of transactions:
1. Create Header and Child Records: To create a record from an existing record.
2. Edit Header and Child Records: To edit an existing record. This is applicable for a particular item in the object. For example, only on a particular WO.
Use Cases
The following list explains the use cases for different types of transactions.
• From source object to create new child records only: This type of transaction is used to create one or more new child records per target child type.
• From source object to create new header and child records: This type of transaction is used in the following scenarios:
◦ To create a header record from an existing header record. Examples:
▪ Create Child Asset
▪ Create Case from Asset
◦ To create a header record and a new child record from an existing header record. Examples:
▪ Create Return Order from Case
▪ Create Shipment from Case
◦ Create a header record and one or more child records from an existing header record and one or more child records. Examples:
▪ Create Shipment from Work Order
• As standalone to create a new header record: This type of transaction is used to create a header record along with one or more new child records.
• As standalone to edit an existing record: This type of transaction is used to edit an existing header record with some fields optionally defaulted to specific values. Another variation of this scenario is where editing the header record is required along with creating, editing, and deleting child records. Examples:
◦ Cancel Shipment Order
◦ Manage Work Order Line Items
Related Topics