IPA Proxy Restrictions

robert-canham

We recently upgraded to landmark 11 IPA only.  One of the new features we want to take advantage of is the proxy feature now that it does tasks.  However, I was wondering if anyone knows of a way to restrict proxy assignments so someone doesn't delegate down the chain of command (i.e. a director asking a manager to approve requisitions).  We have a single approval required on our requisitions and they're routed based on the dollar amount to various levels of leadership.  So, it wouldn't be good if a manager was granted a director's approval limit for a time.

One thought I had was if I could trigger a flow when a proxy is added, but we haven't done much landmark work since we're IPA only so I'm not sure if this is possible.

russel-cornelson

You could automate the process of assigning proxies using a process flow.



Host a webpage with a form to trigger a workunit, essentially you could place two date fields on the form and a button "Find Proxy User". That could make a HTTP call to /bpm/trigger to trigger a workunit in IPA.



The process flow could make a landmark transaction to look up the "Originator" which would be the person who clicked the button. Then look up the position of that employee, now based on that employees position you could find a list of available approvers at a specific position or higher and either automatically assign a proxy user or send that list of available approvers to the "originator" so they can select one of them to delegate to.



Aka, flow comes back to originator in user action, they could add a PfiMessage to the workunit with the desired proxies name, then take an action like "get confirmation" ... which could send a user action to the desired resource for "acceptance" ... this way the person being assigned would have acknowledged that they will be responsible for approvals during the desired range.



Ultimately the flow could then create the proxy assignment ... thereby allowing you to use a security role to limit adding proxies to only the user running landmark/grid.