-
Notifications
You must be signed in to change notification settings - Fork 36
Automated Contractors End Date Extension with Approval
Automatically submit requests to extend end date for contractors and have a manager to approve them.
All requests made using built-in function evaluator activity will bypass AuthZ stage and approval will not happen.
Using the same technique described for AD account and mailbox approval in scenario [How to approve new AD accounts and mailboxes before they are created when requests are coming from HR] (https://github.com/Microsoft/MIMWAL/wiki/New-Accounts-Approval) you can submit requests to extend end date for contractors
Create a set !users expiring in 1 month
with users who have expiration date after today and before 31 days from today.
This is needed to prevent requests be submitted for users resigned long time ago.
Create a transition IN policy !AD: make request to extend an account
and a workflow !AD: submit request to extend contractor's end date
.
The only one step in workflow will be Update Resource activity.
Sure, you have to create one more policy that will grant permissions and will require approvals for requests submitted by contoso\fim.agent.
They are very regular MPR: !AD: approve requests from FIM Agent - account extension
and Authorization Workflow: !AD: approve account end date extension
.
Mind the step prior to approval activity. It changes request name from 'Update to person...' to 'Extend AD account expiration date for John Doe'. To do so you set the [//Request/DisplayName]
to be "Extend AD account expiration date for " + [//Target/DisplayName]
- MIMWAL Site - http://aka.ms/MIMWAL
- MIMWAL Releases - http://aka.ms/MIMWAL/Releases
- MIMWAL Documentation Wiki - http://aka.ms/MIMWAL/Wiki
- MIMWAL FAQ - http://aka.ms/mimwal/faq
- MIMWAL GitHub Code Repo - http://aka.ms/MIMWAL/Repo
- MIMWAL TechNet Q&A Forum (now read-only) - http://aka.ms/MIMWAL/Forum