SDIM Additional Custom Field Issue

Identity Security Cloud (ISC) ISC Discussion and Questions
, ,
1

Hi Team,

I am getting difficulty in saving any new additional fields in SDIM, whenever I am trying to save and update the configuration, updated attribute disappear from SDIM configurations, Does anybody face this challenge, Please note that Servicenow Catalog has already these fields which I am trying to fill the values. I have raised ticket with SailPoint Support as it seems to be bug.

Can anybody help with how ro provide the velocity expression on additional fields, I was trying out to give below expression but that dont work for us I can see static data at that field, I tried below expression to pass on email field which is already present in catalog item.

Let me know if anyone of you have face similar situations, your help is need to get this done.

$!{plan.identity.attributes.email}

!plan.identity.attributes.email

2

Hi Gagan,

You can use the below syntax for custom variables. You may need to add custom field in provisioning plan using before provisioning rule.

                "upo_department": "$!{plan.arguments.identityDepartment}",
                "upo_business_unit": "$!{plan.arguments.identityBusinessUnit}",
                "upo_location": "$!{plan.arguments.identityLocation}",
                "upo_company_code": "$!{plan.arguments.identityCompanyCode}",
                "upo_zip_code": "$!{plan.arguments.identityZipCode}

You can follow below link for more details.
Working with Velocity Template Language in ITSM Ticketing - Compass)

Thanks

3

Hi @LearningStar

This issue typically happens when the additional field isn’t properly defined in the serviceRequestSchema. Even if the field exists in the ServiceNow catalog, it also needs to be declared correctly in the SDIM configuration under the “Additional Attributes” section.

A few quick checks:

  • Ensure the field name matches exactly (case-sensitive) what’s defined in the ServiceNow catalog.
  • Use Velocity like this: ${plan.identity.attributes.email} — avoid the exclamation mark unless using null checks.
  • After adding the custom field in SDIM, make sure to save and reload the page to confirm it persists — if not, it may be a UI bug and the field might need to be added manually in the raw JSON schema.

Since you already raised it to SailPoint Support, that’s the right move if it’s a potential bug.

Let us know how it goes.

Reagrds.
Mustafa