Pause And Previous Are Not Working When Required Fields Are Not Populated in Task UI
Last updated on MAY 02, 2016
Applies to:Siebel Call Center - Version 126.96.36.199 [IP2013] and later
Information in this document applies to any platform.
On : 188.8.131.52 SIA  version, Task Based UI
Transactional property is set to TRUE on the Task
When executing Task UI in Open UI, if a required field is not entered and a user attempts to Pause the Task or presses the Previous button, a message is presented telling the user that field 'xxx' is required.
Normally (based on how users can undo records) the process would allow users to cancel the Task.
This is the correct message for the Next or Finish button, but this is not the expected message when pressing Pause or Previous.
'xxx' is a required field.
Please enter a value for the field. (SBL-DAT-00498)
1. Go to Agreements.
2. Press the Task icon.
3. Go to Asset to Agreement.
4. Select option: Create New Agreement > Press "Next".
5. Clear (Null) Name, Type, Revision, Status.
6. Press the "Pause" or "Previous" button.
Transactional = TRUE means hold all data in shadow storage until a commit is called or until the task ends.
Transactional = FALSE means commit all data immediately and do all data validations immediately.
The default is TRUE.
If the Task Transactional property is set to FALSE, the application will perform data validations and try to commit the data: the task transaction is off, and updates on business components within Task UI are immediately committed to the base tables.
When the Task Transactional property is set to FALSE, Task UI works similarly to Immediate Commit Property = TRUE.
See Siebel Business Process Framework: Task UI Guide Version 8.1/8.2 > Testing, Troubleshooting, Deploying, and Administering a Task UI.
In the Business Component User Properties list, query the Name property for Immediate Commit In Task.
If the Value property for the Immediate Commit In Task user property is TRUE, then Siebel CRM turns off task transaction: it immediately saves to the base tables any updates that occur on
the business components that the Task UI references.
For a business component to be part of the Task Transaction, the Task Transaction must be turned on at the business component level and at the task level.
For more information, see “Using the Defer Write Record Property When You Disable Task Transaction" in Siebel Business Process Framework: Task UI Guide Version 8.1/8.2 > Testing, Troubleshooting, Deploying, and Administering a Task UI > Process of Testing a Task UI.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms