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; } } }

activation time

DavidMusser

Ok, as you may have seen I'm parsing the workflows contents after the workflow finishes... I have this working now :-) But I've noticed somehting that I did not before...

It seems that if I have a workflow..

Author - Editor 1 - Editor Two - Submit

And if Editor Two rejects back to the author the activation time for the Author Task is after the Editor Two rejects... The only way to track when the task really was finished each time is the time of the comment...

Is there an easier way to get this information?

-D

David R. Musser
MCSE & MCP+I
Eye Street Software

Phone: 540-542-5257
Email: dmusser@eyestreet.com

Find more posts tagged with

Comments

Migrateduser

You could store each Author task's activation time as a job variable. I say "each" because the author could see it 5 times, let's say, and AuthorActivation1..5 could be stated to capture the activation time of each iteration.

Dave

Current Environment(s):
(1) TS 6.1 SP2 on W2K3
(2) TS 6.1 SP2 on W2K
(2) TS 6.1 on W2K

iwovGraduate

The XML you get out of querying the job, should contain a section something like -


<events>
    ...
    <event date="1108677126" name="TaskGoActive" user="domain\me" role="1" task="156439" taskname="external_task_name" other="-1" othername=""/>
    ...
    <event date="1108677142" name="TaskCalledBack" user="SYSTEM" role="1" task="156439" taskname="external_task_name" other="-1" othername="">
    ...
</events>

In the above, an external task with name "external_task_name" and taskid "156439" was started at epoch time 1108677126 and finished at epoch time 1108677142
For user/group task you will have "ChooseTransition" instead of callback event.

If a task was called multiple times you will see multiple entries. Would that help ?

DavidMusser

Thank you both!..... ahhh either more variables, or more regx's...mmmmm...mmm... I think my brain's gonna explode...

:-D

David R. Musser
MCSE & MCP+I
Eye Street Software

Phone: 540-542-5257
Email: dmusser@eyestreet.com

Adam Stoller

Well - you could use a single variable and just append values to it - as opposed to a unique variable for each activation.
You could do this with wfvarstartop / wfvarfinishop to help automate the process.
It may be easier to make use of the existing XML data for the event history information.

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com