Expert
ExpertYes, it was not that easy.
So we can send the sub entity name to servicenow but it is not mapped to correlation ID. Unfortunately. Still all events are pointed to one incident whereas the need is to get them as separate incident if that sub entity is different
ContributorHi
I'm finding this exact behavior when testing the latest version of the app. In the example I gave previously when the correlation_id is built in PowerFlow (old sync pack version) it uses the sub_entity_name value (%Y) for the sub_id value :
In the later version when its calculated in SNOW it calls the determineCorrID function in the TaskMappingHelper script include to generate the correlation_id field value. In that function its using the u_sub_entity_id field value in the import table for the sub_id value :
We are testing a solution where we've cloned the TaskMappingHelper script include in SNOW and have updated the function to use source.u_sub_entity_name field instead of source.u_sub_entity_id
This seems to be working for us. Unique incidents are created for different sub-entity values based on the sub_entity_name field.
hope this helps !
