Task UI , Pause Resume Behavior
Last updated on AUGUST 21, 2017
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 for an example.
We noticed that the update from WF1 (called by post cancel) is committed immediately to the data base but the update from WF2 (called by Task event Pause) is not committed.
Is it the expected behavior? Can we force the update from WF2?
2) Based on the documentation:
Creating an Association That Allows the User to Resume or Transfer a Paused Task UI
We should add a step and call a business service “Task Administration” method “Associate”.
Is this must for suspend & resume ? or just for transfer ?
Could you please provide details regarding the business service i.e how it works, why it is needed?
What if we do not use it and pause/resume a task is used?
3) For tasks we do not want an inbox record to be created , we changed a task property
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) ?
How the performance can change by percentage ?
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