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

task transitions in workflow

cute_guy

Is there a way to check whether task transitions have occured and the workflow has advanced to next task, thro' some command or some script and without the CC GUI.

Regards,
Ganesh

TS 6.5 and Solaris 8

Find more posts tagged with

Comments

ravio

Is there a way to check whether task transitions have occured and the workflow has advanced to next task, thro' some command or some script and without the CC GUI.

TS 6.5 and Solaris 8

Yes,
1. Commandline:iwgetwfobj
2. You can check the workflow tab from the GUI

cute_guy

how do i do that with iwgetwfobj?

ravio

how do i do that with iwgetwfobj?

This should be in the CLT manual.
The syntax is
$iw-home/bin/iwgetwfobj -c YourWFid

You will get an XML output from this which has all the details,

If you want, you could write it into a scipt and also transform it into a more readable (maybe an html) report.

cute_guy

In the Big XML file which variable/value will say that transition has not occured.

On what basis should the script determine that particular task has not moved over to next task.

kaalraa

In that Big XML... there are values such as ACTIVE TASK ... You have to read out that ID .. convert that to task name and checks whether it is a transitioned task... or still waiting. A bit tricky Smiley Happy

Also just curious to know.... as for what need or requirement you have to check for transition?

In the Big XML file which variable/value will say that transition has not occured.

On what basis should the script determine that particular task has not moved over to next task.

cute_guy

Scenario is something like this...

There are more than 200 jobs when user clicks on the workflow tab.
In these 200 jobs there can 100 jobs hanging... 100 jobs user has to perform action to move to next task.

A script has to be written to find out the jobs hanging and at what task they are hanging...

Regards,
Ganesh

kaalraa

For this ... you have to first run iwgetwfobj from your script as a system command. which gives you result something like....{id v="1224779"/} for each workflow.

Then using the ID, again you have to call iwgetwfobj with wfId as parameter ... which provides you xml. Parsing that xml would give you whether the current job is in active state or not from :

workflow name="abc" active="t"

At last you have to check for activetask... and thru active task Id... retrive the task name using getTaskName.

{activetasks}
{id v="1248297"/}
{/activetasks}

I hope .... it would resolve the issue and generate a decent report.

NOTE: Replace < with { and > with }

Scenario is something like this...

There are more than 200 jobs when user clicks on the workflow tab.
In these 200 jobs there can 100 jobs hanging... 100 jobs user has to perform action to move to next task.

A script has to be written to find out the jobs hanging and at what task they are hanging...

Regards,
Ganesh

ISCBorisB

A script has to be written to find out the jobs hanging and at what task they are hanging...

Well, write it then. It's not hard to do and nobody knows your Project
requirements better than you. It' a nice exercise and when done
you can share your code on DevNet so that few clowns can tell you how much
better they would do it if they only knew what you were talking about.

Here is an excellent starting point:
Check this Thread
and look for Ghoti code to "Clean Jobs". Granted you'd have to modify it…

Migrateduser

Dude, seriously, what are you looking for? No one is going to write your script for you. Kaalraa and ravio have already been extremely accomodating and have given you the words of wisdom you need to go and do this yourself.

So, go and do this yourself.

Adam Stoller

For this ... you have to first run iwgetwfobj from your script as a system command. which gives you result something like....{id v="1224779"/} for each workflow.

Then using the ID, again you have to call iwgetwfobj with wfId as parameter ... which provides you xml. Parsing that xml would give you whether the current job is in active state or not from :...

Alternative 1: You could probably code it fairly easily using TeamSite::WFsystem, TeamSite::WFworkflow, and TeamSite::WFtask too
Alternative 2: You might be able to accomplish much the same feat with iwqueryjobs and/or iwquerytasks -- all depends on what your actual requirements / objectives are.

cute_guy

Hi adam,

I have added many changes to the script i got from the following link.

http://devnet.interwoven.com/site.fcgi/techlib/52254 .The script i got from the tech lib will list all in tasks in the workflow.

My changes will also list the next task to which the workflow has to do the transition and also to the last will say which task has not moved ahead.

Remember jobID has to passed as input.

My question is

How to determine whether the callback has happened in task or the task is waiting for the user's activity.? I feel stuck here..

Any help would be greatly appreciated.

Regards,
Ganesh

kaalraa

My question is

How to determine whether the callback has happened in task or the task is waiting for the user's activity.? I feel stuck here..

I dont think... there would be a straight way to find out whether the task is stucked for user activity or has stucked within. One possible way i could think off ... is apart from successor and predecessor .... also provide the task type (cgitask/usertask/externaltask). This would help in a way but not completely.

Still.... if you find any other way around or a magic trick... then please share the same.

Adam Stoller

...
http://devnet.interwoven.com/site.fcgi/techlib/52254 .The script i got from the tech lib will list all in tasks in the workflow.
...
How to determine whether the callback has happened in task or the task is waiting for the user's activity.? I feel stuck here..
...

Well, certainly not the best written script I've seen but if it works - that's probably all you need.
As for your question:

if you're dealing with a usertask, grouptask (for which someone has taken ownership) - you have to assume that you are waiting for the user's activity
if you're dealing with a grouptask for which no-one has taken ownership, you're still waiting for user's activity, but it's slightly different than the above
if you're dealing with a cgitask - you might be waiting for user activity, but it is also possible that it is performing (or got stuck performing) some automated process before/after user interaction
if you're dealing with an externaltask, you should have some idea of how long it should take to complete its function - and thus be able to reliably guess whether it is "working" or "hung"
if you're dealing with a submittask or updatetask I believe it should either be "working" or it should have transitioned to another task (perhaps a conflict resolution task?) so it shouldn't actually be "hung" in either of these.
if you're dealing with a dummytask - you should be able to check the activation time, the timeout time, and the current time to verify that - if it's active - it's within its intended time period - I don't think this could get hung too easily
I think the remaining task types should be fairly easy to figure out
For any task type - if you see that it is waiting to get locks - then you know it's in a potentially hung-state and you can compare the current time with the activation time to determine how long its been like that

Hope that helps.

cute_guy

Adam,

I have created an another script (workflow_details.ipl) that will use perl modules.This script will create a excel file (Details.xls) listing all the workflows and tasks present in workflows and also will indicate the hanged task (highlighted in red).

Hope this might be a well written script.

Regards,
Ganesh

kaalraa

If this evacuates you well out from your problem... then its all good. But still i think the solution you are exactly looking for, could not be achieved.

Adam,

I have created an another script (workflow_details.ipl) that will use perl modules.This script will create a excel file (Details.xls) listing all the workflows and tasks present in workflows and also will indicate the hanged task (highlighted in red).

Hope this might be a well written script.

Regards,
Ganesh

Adam Stoller

Adam,

I have created an another script (workflow_details.ipl) that will use perl modules.This script will create a excel file (Details.xls) listing all the workflows and tasks present in workflows and also will indicate the hanged task (highlighted in red).

Hope this might be a well written script.

Regards,
Ganesh

I think I have to agree with kaalraa - your determination of a hung task in your code is:

be hung, but you will probably get a lot of false-positives.