External Authorisation Node - Emails to a Distribution List / Authorisation Audit Trail

[AlexOnTheHill]

I don't know if there's a way to achieve this with the current setup or whether this needs to be an enhancement request.

I have been given a request to set up some authorisation nodes that go to teams via email.

I thought I could achieve this through an external authorisation node which sends to that team's DL however after testing an authorisation request I can see that there's no record of which member of the DL provides the authorisation.

Is it possible to return that information?

I have been successful in testing internal authorisation which when assigned to a team shows the team member who provided authorisation.

This may well be the way to go here but I wanted to check there wasn't something I was missing with external authorisation.

I am aware I could email the users individually however with team members changing I would prefer to avoid ongoing maintenance of the change workflow to accommodate those changes.

[Sam P]

Hi Alex, I have tried this and I don't think its possible.  My external authorisations don't need to go to a DL, they just go to one person in a Simple List however as the approver does not need to login to Hornbill to take the decision, the information is not recorded.  When my process was first launched I tried to encourage everyone to put their email address in the Reason box so I could see who had approved it, this has worked but is an ongoing battle!   I tried to cover it by adding a Tooltip to the button, however that doesn't work (I have a ticket open for this).

My understanding from previous posts is that this is basic authorisation functionality built in to Hornbill to allow approvals without allocating a full licence, however it is limited in what it can do.

[Steve Giller]

27 minutes ago, AlexOnTheHill said:

Is it possible to return that information?

No, not on the External Authorisation.
You can see exactly who completed each Authorisation and what their decision was by utilising the Full Authorisations, however for this every User being sent an Authorisation would have to be a Full User.