Connector syncs create a new Task
When the CC Connector Syncs a folder which has changes, it creates a new Task. If you have many components which are constantly changing and syncs are running every couple of hours, won't that create a huge number of new, open tasks in short amount of time thus significantly skewing the number of Open WI's?
Would it be possible to have these Sync tasks automatically transition to the Closed state once the sync is complete?
Would it be possible to have these Sync tasks automatically transition to the Closed state once the sync is complete?
One answer
In general, we don't know what the "closed" state is, because process
may have customized the state diagram. What you can do though is create
a "canonical" task, whose state you have transitioned to "closed", and
we'll use that as the template when we create any new sync tasks. Store
the id of that task in the TEMPLATE_ID property on the Jazz Provider
property page of the sync stream.
Cheers,
Geoff
pravesh wrote:
may have customized the state diagram. What you can do though is create
a "canonical" task, whose state you have transitioned to "closed", and
we'll use that as the template when we create any new sync tasks. Store
the id of that task in the TEMPLATE_ID property on the Jazz Provider
property page of the sync stream.
Cheers,
Geoff
pravesh wrote:
When the CC Connector Syncs a folder which has changes, it creates a
new Task. If you have many components which are constantly changing
and syncs are running every couple of hours, won't that create a huge
number of new, open tasks in short amount of time thus significantly
skewing the number of Open WI's?
Would it be possible to have these Sync tasks automatically transition
to the Closed state once the sync is complete?