Subworkflow --->agent problem

[Former Member]

Hi experts,

i have a subWF which i am calling from main WF

first step of the SubWF is user decision step where the agent is a USER ( hardcoded say AX5155) . Also task in that is general

when i execute the SubWF separately the first step works fine and i get a workitem in Users Inbox.

but when i execute from main WF ...the hardcoded agent ( AX5155) does not get assigned to SubWf's user decision...

can any one help

i tried searching the entire forum

[Former Member · Accepted solution]

please prefix US to the user id and try..

it will work...

[Former Member · Accepted solution]

Hi

Even if i use US with the User ...it only works if the sub WF is exceuted independently ....it does not work with the main WF

[paul_bakker2 · Accepted solution]

Hello,

Instead of hardcoding the user, copy it to a container element and use that in the step.

Then, if it doesn't work, you can check if the container element has the proper value or not.

regards

Paultje Bakker

Hanabi Technology

[Former Member · Accepted solution]

please check whther you have done correct binding between your main WF to your sub WF.

And also check the WF log for more clarity

[Former Member · Accepted solution]

Hi Paultje,

i have used a container element but still it works properly when SubWF is executed independently

but when it is called from main WF it doesnot wrk properly

also the binding is proper that is why i can see the sub WF step called properly with IN Process status

any more help ?

[paul_bakker2 · Accepted solution]

Hello,

So does the value get copied correctly into the container element? Check this by looking in the workflow log.

This will narrow down where the problem is.

regards

Paultje Bakker

Hanabi Technology

[Former Member · Accepted solution]

Hi

I noticed one difference in the workflow log

i am able to see the container element ( with proper value ) when Sub WF executed independently

but cannot see the container element altogether when executed from main WF

[Former Member · Accepted solution]

Did you check the task # of the subwf assigned in main workflow is same as the one for the subwf which you check independently?

Are you binding the user id from main wf to sub? if so, is the binding corrct? check wflog and verify.

[Former Member · Accepted solution]

Hi

I can see my subWF getting called from main WF in the WF log

also i am not passing the userid from the binding

ia m using a container operation in the sub WF

still the problem persists

any help ?

[Former Member · Accepted solution]

in your main WF that particular container should be marked as EXPORT and in sub WF that particular parameter shud be marked as IMPORT.

[narin_nandivada3 · Accepted solution]

Hi Ravi,

Is 'US' got concatenated when the value got passed to subworkflow?

Alternative:

By going to agent assignment screen of the task(if its not standard) and Create a agent assignment by pressing F5 and Assign User ID.

Regards

Narin.

[Former Member · Accepted solution]

Hi ,

i am NOT passing that particular user id from main to sub WF .....i have created a local variable( container op) in sub WF

hence the task of main WF is just to call the sub WF...

[narin_nandivada3 · Accepted solution]

Hi,

But How are you passing the local variables to Sub WF. Are you exporting to Memory. If not Export the same variable to the Sub workflow container.

Regards

Narin

[Former Member · Accepted solution]

Hi

When i say local variable...i mean i have created a sub WF container elemwnt where export import is not ticked..

it is just used to assing the hardcoded USER to AGENT

[Former Member · Accepted solution]

What is the status of workflow/sub workflow according to workflow log? Is it in Error as the agent is left blank?

[Former Member · Accepted solution]

You shud dclare it locally...

it has be an import parameter...

Since if your run independenly you are getting it....

which means...there shud be a problem with binding from main Wf to sub WF or with the properties of that parameter (IMPORt/EXPORT)

[narin_nandivada3 · Accepted solution]

No Matter if you haven't ticked the export/Import for that WF container element.

Check the Binding from Main WF --> SUB WF.

Check the workflow log to know whats the actual value thats getting flowed to Sub WF.

From your problem it seems to be fair that there would be a problem in Main WF to Sub WF binding.

[Former Member · Accepted solution]

Hi experts

Can anyone pls help

[Former Member · Accepted solution]

Did you check the binding and properties of the container element as i suggested?

what's the result?

[Former Member · Accepted solution]

As i told i am not passing anything from main WF to SUB WF though binding...

Also my sub WF is called properly as i can see in WF log.

First step of Sub WF is a container element(its properties has no export/import tick) which is assigned a USER.

but when the second step ( user decision ) step of sub WF is executed it goes in ready mode as it is not able to get the agent .

I saw the technical detail log ...when i execute the subWF independently it shows the container elemetn proerply with user and hence it works ok

but when i execute the main WF ..surprisingly it doesnot show the container operation of subwf and hence the next step is not getting the agent

[Former Member · Accepted solution]

In control tab...

You might have checked the option..step not in WF log...

please uncheck and check the WF log...whether your are getting in the container or not...

[Former Member · Accepted solution]

Hi

that option is unchecked only that is why i seee it when i execute sub WF independently

but cannot see when executed from main WF ( and i think this is the problem as the userdecision is not able to get the agent after taht )

[Former Member · Accepted solution]

sub wf is in INPROCESS status and userdecision in READY .. it is not getting the agent

Edited by: Ravi Mehta on Oct 14, 2009 8:48 AM

[Former Member · Accepted solution]

In container ioperation...how are you passig the agent?

[Former Member · Accepted solution]

i have assigned a hardcoded value USAQ5145 to operator called agent using assignment operator..where AQ5145 is my id

then i am using that container element &agent& in the user decision step

[Former Member · Accepted solution]

Please check both the main and subWF are marked as General task.

Because when your run sub WF...you are getting it...

but when you execute from main WF...you are not getting it...

[paul_bakker2 · Accepted solution]

Hello,

You wrote:

"I am able to see the container element ( with proper value ) when Sub WF executed independently

but cannot see the container element altogether when executed from main WF"

So you're saying that the placing of the hardcoded user name into the container element doesn't work in the subworkflow?

Exactly how are you doing it? Container operation?

regards

Paultje Bakker

Hanabi Technology