nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Difference between successive taskids

sheetalpolaris

Hi,

I noticed that whenever we initiate a workflow job, the difference between the succesive taskids of the workflow tasks is always 4. Does this pattern occurs all the time. Was just curious to know. Can anyone please let me know if this happens all the time.

Kind Regards,
sheetal

Find more posts tagged with

Comments

ISCBorisB

The difference between the succesive taskids of the workflow tasks is always 4 [...] Can anyone please let me know if this happens all the time

No. TS has several independent Object ID Sequences. ID assignment is dynamic, sequential
(next available) and is not rolled back on aborted transactions. It means that you'll routinely
have gaps in Objects' IDs, it's normal.

Any observation of the nature you've provided is a coincidence, possibly prompted by particular
WF Model design (Task+3 other Objects and the like). Even if that's indeed the case, try to
instantiate several of these WFs simultaneously. Chances are, you'll have mixed IDs in them.

That said, why would you care one way or another? Yes, no - what of it?

Rick Poulin

That said, why would you care one way or another? Yes, no - what of it?

I'd surmise that a lazy programmer might assume that wfobj.getTasks()[4] might return a consistent result.

To add to Boris' reply, the assignment of IDs to tasks is sequential but not necessarily in the same order as your workflow implies. Open up your job in the UI, go Actions > Change Properties > Advanced. At the bottom, you'll see all tasks created for the job, and the number assigned to them in ascending order.

Still, there's no real use for this information as far as I'm aware.

Adam Stoller

Just to add to what's already been noted...couldn't resist...:

What does all this mean? Pretty much what was stated before - don't assume anything about the id value of one task with respect to the id value of any other task. It's handled internally by the system, was never published as a supported mechanism for customizations to utilize, and can change at any time without any notice.Instead, use the name of the task for accessing it - either the TeamSite::WFtask method of GetTaskByName() in Perl, or the CSWorkflow interface's getTasks() with a loop using the CSTask interface's getName() methods in Java.