# Service Now requirement | Need to understand feasibility

**URL:** <https://developer.sailpoint.com/discuss/t/service-now-requirement-need-to-understand-feasibility/112854>\
**Category:** SHF Discussion and Questions\
**Tags:** provisioning, sailpoint-identity-security\
**Created:** [April 18, 2025, 9:09am UTC](https://developer.sailpoint.com/discuss/t/service-now-requirement-need-to-understand-feasibility/112854 "2025-04-18T09:09:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Dsinha1](https://avatars.discourse-cdn.com/v4/letter/d/b19c9b/32.png) [@Dsinha1](https://developer.sailpoint.com/discuss/u/Dsinha1)\
**Post date:** [April 18, 2025, 9:09am UTC](https://developer.sailpoint.com/discuss/t/service-now-requirement-need-to-understand-feasibility/112854/1 "2025-04-18T09:09:52Z")

</div>

Use case:

There is a complex SNOW Form already in use. Client wants that submission will be still in SNOW UI but actual provisioning must happen from IDN.

All those parms which will be filled in SNOW form should pass as a API payload while provisioning which provisioning in target through IDN.

The payload must contain entitlements as well as some other mandatory additional attributes (which are not entitlements). Since the access request API in IDN allows only Role/Entitlements/Access Profiles how to achieve this use case by passing additional parms along with entitlement.

Note: There are approx. 35-40 additional attributes which cannot be marked as entitlements.

---

<div class="post-metadata">

**Author:** ![iamology](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/iamology/32/6964_2.png) [@iamology](https://developer.sailpoint.com/discuss/u/iamology)\
**Post date:** [April 18, 2025, 11:43am UTC](https://developer.sailpoint.com/discuss/t/service-now-requirement-need-to-understand-feasibility/112854/2 "2025-04-18T11:43:34Z")

</div>

What is the purpose of these additional attributes in ISC?

---

<div class="post-metadata">

**Author:** ![agutschow](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/agutschow/32/8543_2.png) [@agutschow](https://developer.sailpoint.com/discuss/u/agutschow)\
**Post date:** [April 18, 2025, 8:56pm UTC](https://developer.sailpoint.com/discuss/t/service-now-requirement-need-to-understand-feasibility/112854/3 "2025-04-18T20:56:44Z")

</div>

In the payload of the request, you are allowed to include clientMetadata. These are arbitrary key-value pairs that can be used include information such as the ServiceNow request number, justification, or any other values that you wish.

 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/d/6/d6bfbc51379f1a06784dc8ba4224521311a4bd6e.png)

 ![image](https://global.discourse-cdn.com/sailpoint/original/3X/2/9/294d754983e9f7f9757c6547e708a0b8fe53aa97.png)

This information will be accessible if you use the API (`list-access-request-status`) to retrieve the event.

---

<div class="post-metadata">

**Author:** ![Dsinha1](https://avatars.discourse-cdn.com/v4/letter/d/b19c9b/32.png) [@Dsinha1](https://developer.sailpoint.com/discuss/u/Dsinha1)\
**Post date:** [April 21, 2025, 8:08am UTC](https://developer.sailpoint.com/discuss/t/service-now-requirement-need-to-understand-feasibility/112854/4 "2025-04-21T08:08:48Z")

</div>

The purpose is like , for usertype1 : it required to send users DC, Localname, Phone , Fax , Domain , and more details to pass in service now ticket body.

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [June 20, 2025, 8:09am UTC](https://developer.sailpoint.com/discuss/t/service-now-requirement-need-to-understand-feasibility/112854/5 "2025-06-20T08:09:08Z")

</div>

Closed on June 20, 2025, 8:09am UTC

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.