• State Verified Answer
  • Locked Locked
  • Replies 12 replies
  • Subscribers 62 subscribers
  • Views 15004 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
    The workflow is triggered by a virtual attribute change. This virtual attribute is on the form they fill out and is also a required field. The workflow if-then activity checks for max automatic hours, which is a stored virtual attribute on the group class that is the most hours they can request for elevation. The If-Then activity checks the max automatic hours against the requested change for the virtual attribute in the form to decide if they'll automatically be placed in the group or if more than the max automatic hours, it'll trigger the approval.

    From what I'm seeing, they get the approval prompt right after saving. It isn't running the workflow to see if the activity needs approval but after they enter a reason for approval, if the hours is less than the max, it automatically places them in the group but the page displays that the operation has been submitted for approval even though it was successful.
Reply
  • 0 over 7 years ago
    The workflow is triggered by a virtual attribute change. This virtual attribute is on the form they fill out and is also a required field. The workflow if-then activity checks for max automatic hours, which is a stored virtual attribute on the group class that is the most hours they can request for elevation. The If-Then activity checks the max automatic hours against the requested change for the virtual attribute in the form to decide if they'll automatically be placed in the group or if more than the max automatic hours, it'll trigger the approval.

    From what I'm seeing, they get the approval prompt right after saving. It isn't running the workflow to see if the activity needs approval but after they enter a reason for approval, if the hours is less than the max, it automatically places them in the group but the page displays that the operation has been submitted for approval even though it was successful.
Children
No Data