Receiving TWO Task Ready events for first two tasks in Job.
Article ID: KB0091958
Updated On:
| Products | Versions |
|---|---|
| TIBCO BusinessWorks Collaborator | - |
| Not Applicable | - |
Description
Resolution:
TWO Task Ready event is fired in a job incase the Job is Suspended and Resumed.
In such scenario, first the task ready event is fired and on a Resume of a Job, all of the tasks are re-evaluated to see if they should be switched from ‘Waiting’ mode to ‘Ready’.
If you see at the database TASKS table, which has two fields FIRST_READY_TIME and READY_TIME. The field READY_TIME column of the Task table changes every time the task is acquired and released. Whereas FIRST_READY_TIME column in the database table that represents the time the task first switch to a ready state.
This is the user error problem and it depends on the design of the process, logic and implementation. Following are the steps to avoid duplicate task notification->
1. You could acquire the task BEFORE the Job Suspend then the task will not become Ready again.
2. Incase you do not want to Suspend the Job, then you might need to place a perform condition on the task to avoid task to became Ready. But in this case, you would not see as a task to acquire. Please refer to document for more details about the perform condition.
TIBCO BusinessWorks Collaborator Process Design Guide -> Chapter 2 Designing Workflows -> Specifying Conditions -> Using the Perform/Iterate Condition Wizard and More About Conditions part.
TWO Task Ready event is fired in a job incase the Job is Suspended and Resumed.
In such scenario, first the task ready event is fired and on a Resume of a Job, all of the tasks are re-evaluated to see if they should be switched from ‘Waiting’ mode to ‘Ready’.
If you see at the database TASKS table, which has two fields FIRST_READY_TIME and READY_TIME. The field READY_TIME column of the Task table changes every time the task is acquired and released. Whereas FIRST_READY_TIME column in the database table that represents the time the task first switch to a ready state.
This is the user error problem and it depends on the design of the process, logic and implementation. Following are the steps to avoid duplicate task notification->
1. You could acquire the task BEFORE the Job Suspend then the task will not become Ready again.
2. Incase you do not want to Suspend the Job, then you might need to place a perform condition on the task to avoid task to became Ready. But in this case, you would not see as a task to acquire. Please refer to document for more details about the perform condition.
TIBCO BusinessWorks Collaborator Process Design Guide -> Chapter 2 Designing Workflows -> Specifying Conditions -> Using the Perform/Iterate Condition Wizard and More About Conditions part.
Issue/Introduction
Receiving TWO Task Ready events for first two tasks in Job.
Feedback
Yes
No
Powered by
