• State Verified Answer
  • Locked Locked
  • Replies 12 replies
  • Subscribers 62 subscribers
  • Views 15003 views
  • Users 0 members are here
Options
Related
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

michael.otis
over 7 years ago

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
  • 0 over 7 years ago

    GT Max Automatic Hours - There are no parameters
    LE Max Automatic Hours - Checks Requested Changes of "TemporalHours" virtual attribute is less than Max Automatic Hours for the group (Checked by Script Function)

    Workflow is triggered by a change in the TemporalHours virtual attribute.

    This is exactly the same way we have it set up in our ARS 6.9 instance... Like I said before, it isn't running the workflow until after the approval prompt. After specifying a reason and hitting ok, does it only run the workflow and it runs correctly.

     

Reply
  • 0 over 7 years ago

    GT Max Automatic Hours - There are no parameters
    LE Max Automatic Hours - Checks Requested Changes of "TemporalHours" virtual attribute is less than Max Automatic Hours for the group (Checked by Script Function)

    Workflow is triggered by a change in the TemporalHours virtual attribute.

    This is exactly the same way we have it set up in our ARS 6.9 instance... Like I said before, it isn't running the workflow until after the approval prompt. After specifying a reason and hitting ok, does it only run the workflow and it runs correctly.

     

Children
No Data