• State Verified Answer
  • Locked Locked
  • Replies 12 replies
  • Subscribers 62 subscribers
  • Views 15010 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?

  • 0 over 7 years ago

    Yes, there is a policy script that is part of the provisioning policy, that script works as expected, but that's not the script that I'm talking about.

    There is a script that runs in the If-Then branch (LE Max Automatic Hours), it checks the requested changes of the virtual attribute is less than the max automatic hours of the group (This is where the script runs and returns a value).

    When I put an Out-File in the script, it does not output until AFTER the user has been prompted and has filled out an approval reason. After they hit submit, it runs the If-Then branch perfectly but it should not be prompting for approval unless it gets the an approval action in the If-Then branch.

  • +1 over 7 years ago
    We found out this is a bug and will be fixed in 7.0.3