Any suggestion guys or the only route is go about customizing or writing multiple lookups on Transformation steps?
Thanks in advance,
You might want to add delay in the rows in case you get multiple input rows. Then add another delay after the AROutput step, and add a database lookup by matching some information you are pushing on to the ticket, and getting the incident ID as output.
You can also choose to create multiple transformations running in sequence but that is dependent on whether the input is 1 row at a time or multiple rows.
CMDBOutput step does return the InstnceID of the CI created. I don´t remember if AROutput does the same, but I believe it does.
You could configure the AR Output to write to a custom staging form --> From here you have AR-System Workflow which pushes to Incident-Interface and gets back the Incident ID. In your next transformation, you can refer to the entry in the staging form
Thanks Parag , We are already doing this as you said match some information you are pushing on to the ticket and then retrieve it back (in our case looking for the CI name or ReconID in the Incident Notes for the Incident Template that is used in the Job), but seems this takes a lot of resources for the job to do a full lookup on all open Incident with a specific Template when the number of Incidents with that Template is huge. Looking for something more like in webservices , where you get Incident ID as a return as soon as the Incident is created .
Thanks Gustavo, looking for something similar , but seems the AROUtput does not have that facility or I may be missing something.
Thanks Juergen, this is more of a customization and maintaining that Staging Form , that's the last resort I want to take if no other options works!