SDIM Velocity: How to Populate "Requested For" and "Requested By" Fields in ServiceNow Ticket?

Hi Experts!

We’re working on integrating SailPoint with ServiceNow using SDIM (Service Desk Integration Module) and have a use case where we need to populate specific fields dynamically in the ServiceNow ticket using Velocity scripting.

Once a certification campaign is completed, the following fields should be populated in the ServiceNow ticket:
Requested For → should be the user whose access will be revoked
Requested By → should be the certifier (the person who approved the revocation)
Requestor Group → static value (search field)
Catalog → static value (dropdown field)
System → static value (dropdown field)

Currently:
The “Requested For” field is displaying a serviceID instead of the actual user to be requested.
The “Requested By” is not populating with the certifier’s ID/email as expected and is always blank.
Even static values (e.g., for Catalog) are not displaying in the ServiceNow ticket.

we tried the following but the value is not displaying in the ServiceNow ticket:

  1. $!plan.arguments.request.id
  2. $!plan.arguments.identityRequestId
  3. $plan.request.id
  4. $request.requesterId
  5. #foreach($request in $plan.requests)$!{request.operation}account’${request.id}'#end
  6. Tried also doing static value of email in “Requested by” field
  7. $!plan.arguments.requested_for

Has anyone successfully achieved similar functionality with SDIM Velocity?
Any idea how we can correctly pull the certifier ID and target user into the respective ServiceNow ticket fields or are we missing any steps that should be done?


For this if you are looking to populate the employee number of the user, you may have to modify the SDIM Rule
It would be more of like for every other usecase you will have. Update the SDIM Rule, add new arguments in the Rule example, loginId, EmployeeNumber, EmployeeLocation etc. and then reference it in the SDIM connector as $!plan.arguments.loginId

If you are looking for how to add these fields in the SIDM Rule P.S this post

I am attaching the reference link for more information.

Hi @neeraj99, thanks for your reply.
Will the before provisioning rule will also work to use cases wherein we use the Certification campaign to revoke an access?

yes it should. if the end goal is to create a ticket on SNOW, then yes.

do you have a sample code?
cause right it it indeed creating a servicenow ticket after we completed the action for certification campaign, but the fields are not populating. only the “Request Description”.

From the above link that i have shared you can try something similar.

Hi @neeraj99 , just an update.
i am now able to populate the fields, it turns out that the backend value is incorrectly mapped.

1 Like