Is it possible to populate Authorization Task details to the parent event?

May I know the assyst version that you are using ?

-There is no inbuild function for this.
-But this might be possible via ETM
-We can use the assyst destination to capture when an authorization task was authorized, then trigger the ETM. We can use the ETM to read the authorizing action description and add that to the parent event via an action or directly to the event.

If you are fine with this idea, I can give a try to create a channel and destination rule. 

Hello Rajana,

Thank you so much for your reply. My current assyst version is 

At this point any idea would be great to give a try, could you please help?

Hello,

apologies on the delay replying for this. 

I have created a simple ETM channel and configured destination.
This will identify whenever “authorized” OR “Not authorized” action was taken on authorization tasks, then it will trigger the ETM. ETM will create a new action on the parent event with authorized user, svd and the action description.

*You need to create a new custom action in assyst and provide its shortcode to ETM datamapper’s “action type” field.

Let me know If you need any adjustments 😊

Hello,

apologies on the delay replying for this. 

I have created a simple ETM channel and configured destination.
This will identify whenever “authorized” OR “Not authorized” action was taken on authorization tasks, then it will trigger the ETM. ETM will create a new action on the parent event with authorized user, svd and the action description.

*You need to create a new custom action in assyst and provide its shortcode to ETM datamapper’s “action type” field.

Let me know If you need any adjustments 😊

 

I love this example, and I would like to build upon it slightly.

Since all Authorization Tasks by definition have a parentEvent property, and all actions have an actionedById and an actioningServDeptId, this data mapper could be made slightly more efficient by removing the variable assyst search fields. This would avoid ETM having to make separate REST calls to assyst to retrieve these values.

This could be achieved by modifying the destination’s Message Filtering and Expansion to something like this for simplicity:

[*], [event]

Or more targeted approach, only transmitting the fields we care about over EMS:

[remarks], [actionedBy[name]], [actioningServDept[name]], [event[parentEventId]]

You would then be able to directly use inbound.event.parentEventId for the event field, and similarly inbound.actionedById, inbound.actioningServDeptId, inbound.actioningServDept.name etc. 

However, be careful when directly referencing a nested fields value in datamapping, you have to be certain that the that the referenced fields will always have a value. As an example using inbound.event.itemB.name in the datamapper would likely break in many instances if using my first message filter, as not all events have an itemB. The more targeted filter would never include this itemB property even if the event had one, and would thus always cause an  ScriptException - TypeError: Cannot read property "name" from undefined-error during datamapping.