Skip to Content
author's profile photo Former Member
Former Member

Rule resolution fails in "Loop Until" loop.

Dear all.

Part of my workflow contains a loop (until). The first step in this loop has a dialog task and the agent(s) for this task is determined by a rule. Depending on the result of this step, the loop will be exited or the next step (still within the loop) has the initiator as the agent. The initator executes the step and the loop will start over with the first step. But this time the resolution of the rule to determine the agent of the first step fails.

Has anyone any idea of what's going on?

Regards,

Lande

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

4 Answers

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 04:26 PM

    Could you tell us more about the rule? What kind of rule you are using?

    Just to make sure that it is not related to authorisations, give SAP_ALL to both of the users.

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 01:15 AM

    Hi Lande

    Try simulating the rule (PFACH_DIS) with the workflow log open in a separate session so you can pass the actual values into each simulation iteration so you can see what is happening and, if necessary, debug the rule. This will tell you where the problem is. Most likely issue is going to be the actual values passed from the workflow container to the rule in the second pass.

    Regards

    Gareth

    Add a comment
    10|10000 characters needed characters exceeded

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 03:45 AM

    Please check what parameters you are passing in the rule container and accordingly test the rule in PFAC_dis and check whether it is working or not.

    Thanks

    Arghadip

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member

      Well I would guess that in one of the steps, the parameter that is passed to rule is being changed and thats why it fails in the second go. Most probably this is due a return bidning (Task->WF) in one of the steps. So if the data is not supposed to be changed by the step then remove the return binding for the rule parameters and that should solve the issue !

      Let me know if it really did !!

      regards,

      Anuj Sethi

  • author's profile photo Former Member
    Former Member
    Posted on Dec 05, 2007 at 10:44 AM

    Thanks all for the input. I have investigated the authorizations further and it solves the issue. Thanks, Lande.

    Add a comment
    10|10000 characters needed characters exceeded

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.