How to get only workflow stuck steps which are performed by WF Agents

Hi,

We are trying to get the all workflow steps which are stuck at particular sted and which are performed by WF Agents or Item Handler(Auto Process) and we are trying with "MAPTASK_SUBTYPE=115" but still we are getting all user steps also.

Is there anyway to get only those steps which are stuck at any agent step.

Regards,

Mukhesh Nalla.

Find more posts tagged with

Comments

Colin_Schmidt

You’ll have to get some information from OT Support on this. It’s probably in the WSUBWORKTASK.SUBWORKTASK_FLAGS or WMAPTASK.MAPTASK_FLAGS. That’s something I’d like to know too. One way would be to dump the field out for all Item Handlers of a Test WF that has 1 with an Agent and the other without. But that still probably wouldn’t give you the bit-map you need.

Colin J

From: eLink Entry: Content Server LiveReports Forum <livereportsdiscussion@elinkkc.opentext.com>
Sent: Friday, August 31, 2018 5:54 AM
To: eLink Recipient <devnull@elinkkc.opentext.com>
Subject: How to get only workflow stuck steps which are performed by WF Agents

How to get only workflow stuck steps which are performed by WF Agents

Posted bymukhesh.nalla@cognizant.com (Nalla, Mukhesh) On 08/31/2018 06:49 AM

Hi,

Is there anyway to get only those steps which are stuck at any agent step.

Regards,

Mukhesh Nalla.

[To post a comment, use the normal reply function]
Forum:	Content Server LiveReports Forum
Content Server:	My Support

appuGmail

Thought someone from OT WF would chime in but here's what I think,

Some of these are buried in the WF Oscript code but in many cases you might be able to do some self research by doing something like this

You want Debug=2 and wantLogs=true in 16 these are all in different places
In the WF agent the default is to use the DA and in old systems one only had a scheduled agent to do this

##DA SETTING DEFAULT
#FIFOProcessingOrder=false
##DA SETTING DEFAULT
FIFOProcessingOrder=true

I you have a small system to play with then you should see wfagent3001.out,the connect with the same # is the DB transactions for the thread,

this is the scheduler for wfagents stuff and it should show you the SQL that the WFagent code runs to get the TASKS from all WF's that are outstanding from date Now()

Most organizations do not have good people who know how to run old kind of agents so DA is what is used and it makes the wild goose chase difficult.

So it should be something like this

select getdate(),Work_WorkID, Work_OwnerID, Work_ManagerID, Work_Status, Work_OwnerPerms,

SubWork_SubWorkID, SubWork_Title, SubWork_Status, SubWorkTask_TaskID,

SubWorkTask_PerformerID, SubWorkTask_Title, SubWorkTask_DateMilestone,

SubWorkTask_DateDue_Max, SubWorkTask_Status, SubWorkTask_Flags, MapTask_StartDate,

MapTask_Type, MapTask_SubType,

SubWorkTask_PerformerID, a.Name SubWorkTask_PerformerID_Name

from CS16User.WWork, CS16User.WSubWork, CS16User.WMapTask, CS16User.WSubWorkTask

left outer join CS16User.KUAF a on (SubWorkTask_PerformerID=a.ID)

where SubWork_WorkID=Work_WorkID and

SubWorkTask_WorkID=Work_WorkID and

SubWorkTask_SubWorkID=SubWork_SubWorkID and

SubWorkTask_Status>1 and

Work_Status=2 and

SubWork_Status=1 and

MapTask_MapID=SubWork_MapID and

MapTask_TaskID=SubWorkTask_TaskID and

( MapTask_StartDate is NULL or

( MapTask_StartDate is not NULL and getdate() >= MapTask_StartDate ) ) and

( SubWorkTask_Status in ( 6,200,201 ) ) ;

the 6,200,201 are actually Flags/Constants that in Oscript reads like WAPI.SUBWORKTASK_STATUS_SENDINGON,WAPI.SUBWORKTASK_STATUS_READY_BG,WAPI.SUBWORKTASK_STATUS_CONTINUE_BG

In all likeliness it will find the 115 tasks and do further processing.The above query results sets are the ToDo for this run and it will execute further Oscript to send the tasks on.

Ciao,

..... appnair appunair( Livelink Rocks )

Well, if I called the wrongnumber, why did you answer the phone?
James Thurber, New Yorker cartoon caption, June 5, 1937

On Fri, Aug 31, 2018 at 5:54 AM, eLink Entry: Content Server LiveReports Forum <livereportsdiscussion@elinkkc.opentext.com> wrote:

How to get only workflow stuck steps which are performed by WF Agents Posted bymukhesh.nalla@cognizant.com (Nalla, Mukhesh)On 08/31/2018 06:49 AM

Hi,We are trying to get the all workflow steps which are stuck at particular sted and which are performed by WF Agents or Item Handler(Auto Process) and we are trying with "MAPTASK_SUBTYPE=115" but still we are getting all user steps also.Is there anyway to get only those steps which are stuck at any agent step.Regards,Mukhesh Nalla.
[To post a comment, use the normal reply function]
Forum: Content Server LiveReports Forum
Content Server: My Support