Unsolved
This post is more than 5 years old
11 Posts
0
374
August 25th, 2014 12:00
Should the email approval process be an IT function and not a tenant option?
I have heard many discussions around the topic of Email approval workflows in ViPR. The general comments were that approvals are generally used for management to govern requests or for IT to control limits to provisioning storage. The current functionality allows the tenant to enter an approval email and govern themselves. However the desire to have IT be able to create the email workflow process ahead of time to limit random provisioning or for corporate management to approve tenant requests before storage can be provisioned has been expressed.
IMHO, I agree that the current workflow process does not really make sense. Ask a user to govern themselves and most likely they will not. Force all new orders for provisioning to follow a pre-defined workflow built by either IT or LOB Management seems to make way more sense to me. Thoughts?
tiwars9
16 Posts
0
August 27th, 2014 12:00
Tenants in ViPR world can be equivalent to entire departments or enterprise in case of service provider.
Normally, customers should not create tenant to manage access at the user level. if that is the case then you are right that the current workflow will not make sense. Access at the user level should be achieved through ACLs and role definitions within ViPR.
For a department or a company, the approver is expected to be a department IT admin or a Tenant Admin. Also customers can implement a full blown approval flow outside of ViPR which they could use to manage approvals for their entire infrastructure and call ViPR API accordingly.
Hope this helps.