Authorisation Node Advice

[Lee C]

Hi

I have a workflow and capture form setup at the moment for when someones account is requested to be suspended, i want this to reject if the requestor doesn't meet any of the below 2 criteria

The requestor Is not from HR - (our hornbill is setup where it looks like on the user profiles it has in custom field attribute 6 the department/service the requestors are part of, see below) so if on custom fields attribute 6 if it doesnt have HR i would like the ticket rejected, i know how to reject tickets i just dont know what nodes to use for the department check 

The requestor is not higher up in the management chain than the line manager This one might be quite hard to do i admit as all i can go off is can Hornbill check the user account to be suspended in AAD who the line manager for that is and then email that persons manager? so in effect emailing the line managers manager, or can i do that via hornbill automation where it emails the line manager like i have it below and it also then emails the line managers line manager if that makes sense?

I currently have my workflow setup where all it does is email the line manager for authorisation that shows on the hornbill record for the account that is to be suspended as below

[Victor]

On 08/04/2024 at 08:50, Lee C said:

i want this to reject if the requestor doesn't meet any of the below 2 criteria

From my understanding of the scenario you described, these criteria are taken from the user profile, specifically, the custom attribute values that can be set against a user. If that is correct then you can make use of the Core -> Users -> Get user Details node, which will return the user custom attributes that you can use in the workflow decisions...

[Berto2002]

We have a flow that escalates the line management structure so you can find your way up the tree: use a Get User Details node and in there you will find the manager ID. Feed that into another Get User Details node and you then get their line manager, etc.

In your case of viewing the custom attributes, just use a "contains" to search for a unique value.