Thank you for your response and for reviewing my query. We are not using the “Manage ServiceNow Ticket” action because our existing SDIM configuration integrates with the ServiceNow Catalog (installed via a plugin). This setup generates a REQ > RITM > SCTASK structure for tickets created through SDIM. In contrast, the “Manage ServiceNow Ticket” action would only create a REQ or SCTASK, which doesn’t align with our current process.
I’ve attached a sample workflow image for reference. Since we’re using a REQUEST_RESPONSE trigger, the final HTTP Request step in the workflow sends the required response.
I agree that passing formData via the “Manage ServiceNow Ticket” action is straightforward, but we’re using an SDIM integration with the ServiceNow Catalog, which creates a REQ > RITM > SCTASK structure. This setup doesn’t support the “Manage ServiceNow Ticket” action, as it would create a standalone REQ or SCTASK.
In our workflow, we use an “Access Request Submitted” event to trigger a form that collects additional data (e.g. $.form.data.additionalInfo). The workflow completes with a REQUEST_RESPONSE trigger, sending the following response to raise the ServiceNow ticket via SDIM:
My challenge is how to include the formData (e.g $.form.data.additionalInfo) in the ServiceNow ticket, Is there a way to pass formData through the SDIM ticket creation process?
We are already using this configuration in our ServiceNow SDIM integration, which successfully raises tickets (REQ > RITM > SCTASK) via the ServiceNow Catalog for disconnected applications.
For few specific applications, we have a requirement to collect additional details from the requestor during the access request process and include these details in the ServiceNow ticket
we have implemented a workflow with an “Access Request Submitted” trigger to present a form to the requestor, capturing data like $.form.data.additionalInfo. The workflow completes with a REQUEST_RESPONSE trigger to raise the ticket via SDIM, using this response: