This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Temporal Membership Approval - ARS 7

In our old instance of ARS, we had a workflow that executed when someone requested temporary membership of a group. This would add them no matter what if the hours they wanted didn't exceed the maximum amount of hours and if it was more, it would prompt approval.

In our new ARS 7 setup, I have done the exact same, except it now prompts for approval even if the hours entered is less than the max amount. When they enter a reason, it informs them "The operation has been submitted for approval" except it instantly adds them to the group after they submit a reason and not informing them they've been added to the group.

I've noticed it's not running my workflow until after they submit a reason in the approval dialog. In ARS 6.9, it would run the workflow immediately. Is this a bug?

Parents
  • The script being executed passes the correct value. I've tested this by doing an Out-File on the return value. As I've explained, this isn't executed until after the approval prompt.

    I've even entered in false triggers into the approval if-else branch (Description of target object equals 1 for instance) and it still prompts the approval window.

    All other workflows are disabled.

    If I leave the workflow but disable the If-Then branch, it works properly....

Reply
  • The script being executed passes the correct value. I've tested this by doing an Out-File on the return value. As I've explained, this isn't executed until after the approval prompt.

    I've even entered in false triggers into the approval if-else branch (Description of target object equals 1 for instance) and it still prompts the approval window.

    All other workflows are disabled.

    If I leave the workflow but disable the If-Then branch, it works properly....

Children
No Data