Task UI, Pause and Resume Behavior
(Doc ID 2298804.1)
Last updated on SEPTEMBER 28, 2018
Applies to:Siebel Financial Services CRM - Version 15.13 [IP2015] and later
Information in this document applies to any platform.
1) Task Events: Is there any behavior difference for Workflows called via Task Events ?
- WF1 called by Task event “Post Cancel”.
- WF2 called by Task event “Pause”.
Both WF1 and WF2 update data by Siebel operation step on the Contact record.
The update from WF1 (called by post cancel) is committed immediately to the database, but the update from WF2 (called by Task event Pause) is not committed.
Is it the expected behavior? Can the update be forced from WF2?
2) Based on the documentation:
Creating an Association That Allows the User to Resume or Transfer a Paused Task UI
A step should be added to call a business service “Task Administration” method “Associate”.
Is this required for suspend and resume ? Or just required for transfer ?
Please provide details regarding the business service (i.e., how it works, why it is needed?).
What if user does not use it and pause/resume a task is used?
3) For tasks not requiring an inbox record to be created, a task property was changed:
Inbox deposition from value “Do Not Care (Fastest)” to value “Discard Record”.
How this can affect the performance of ending the tasks ( delete operation can be slow in Siebel) ?
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document