# Add Entitlement Metadata values in Webservice application

**URL:** <https://developer.sailpoint.com/discuss/t/add-entitlement-metadata-values-in-webservice-application/58293>\
**Category:** SHF Discussion and Questions\
**Tags:** webservice-connector, identity-security-cloud, provisioning, entitlements\
**Created:** [May 29, 2024, 1:05pm UTC](https://developer.sailpoint.com/discuss/t/add-entitlement-metadata-values-in-webservice-application/58293 "2024-05-29T13:05:32Z")\
**Posts on this page:** 7\
**Page:** 1

<div class="post-metadata">

**Author:** ![gourab](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gourab/32/18650_2.png) [@gourab](https://developer.sailpoint.com/discuss/u/gourab)\
**Post date:** [May 29, 2024, 1:05pm UTC](https://developer.sailpoint.com/discuss/t/add-entitlement-metadata-values-in-webservice-application/58293/1 "2024-05-29T13:05:33Z")

</div>

Hi,  
I am developing an webservice connector. I need to create a json body on Add entitlement operation. Is there any way OOTB by which I can populate entitlement metadata values from plan in json body directly on Add entitlement operation?

Thanks  
Gourab

---

<div class="post-metadata">

**Author:** ![ashutosh08](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ashutosh08/32/11459_2.png) [@ashutosh08](https://developer.sailpoint.com/discuss/u/ashutosh08)\
**Post date:** [May 29, 2024, 2:54pm UTC](https://developer.sailpoint.com/discuss/t/add-entitlement-metadata-values-in-webservice-application/58293/2 "2024-05-29T14:54:12Z")

</div>

Hi @gourab,

Please use before operation rule to print your plan and if the details are available that you are looking then you can reference it using json attribute reference.

Otherwise, you may call an API in your before operation rule to get extra details.

Document for your reference.

> **[get-entitlement | SailPoint Developer Community](https://developer.sailpoint.com/docs/api/beta/get-entitlement)**
>
> Get an entitlement

Thanks

---

<div class="post-metadata">

**Author:** ![ipobeidi](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ipobeidi/32/16000_2.png) [@ipobeidi](https://developer.sailpoint.com/discuss/u/ipobeidi)\
**Post date:** [May 29, 2024, 3:39pm UTC](https://developer.sailpoint.com/discuss/t/add-entitlement-metadata-values-in-webservice-application/58293/3 "2024-05-29T15:39:17Z")

</div>

hey @gourab !

yes there is , everything that you put into the Provisioning policy , for add entitlement Update Policies, is going to be present to be called using the $plan.METADATA$ format.

Yes use a Rule is also a possibilitty but it may create unnecessary lag.

Best

---

<div class="post-metadata">

**Author:** ![gourab](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gourab/32/18650_2.png) [@gourab](https://developer.sailpoint.com/discuss/u/gourab)\
**Post date:** [May 29, 2024, 6:50pm UTC](https://developer.sailpoint.com/discuss/t/add-entitlement-metadata-values-in-webservice-application/58293/4 "2024-05-29T18:50:12Z")

</div>

> [@ipobeidi](#):
>
> oing to be present to be called using the $plan.METADATA$ format.

Hi @ipobeidi ,  
I have tried but it is not working as expected. Do you have any sample policy where you are passing the attribute and metadata?

---

<div class="post-metadata">

**Author:** ![ipobeidi](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ipobeidi/32/16000_2.png) [@ipobeidi](https://developer.sailpoint.com/discuss/u/ipobeidi)\
**Post date:** [May 29, 2024, 6:58pm UTC](https://developer.sailpoint.com/discuss/t/add-entitlement-metadata-values-in-webservice-application/58293/5 "2024-05-29T18:58:20Z")

</div>

Sure, Like the account creation the UPDATE operation also have a provisioning policies

```auto
{
    "name": "Update",
    "description": null,
    "usageType": "UPDATE",
    "fields": [
        {
            "name": "metadataAttribute",
            "transform": {
                "type": "accountAttribute",
                "attributes": {
                    "sourceName": "Source",
                    "attributeName": "xablau"
                }
            },
            "attributes": {},
            "isRequired": false,
            "type": "string",
            "isMultiValued": false
        }
    ]
}

```

you can have logic or even transforms on it. and populate accordingly  
this for attributes or anything else. In the plan, is going to show as AttributeRequest but as you controll the provisioning that shouldnt be a problem.

---

<div class="post-metadata">

**Author:** ![ipobeidi](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/ipobeidi/32/16000_2.png) [@ipobeidi](https://developer.sailpoint.com/discuss/u/ipobeidi)\
**Post date:** [May 30, 2024, 8:15pm UTC](https://developer.sailpoint.com/discuss/t/add-entitlement-metadata-values-in-webservice-application/58293/6 "2024-05-30T20:15:35Z")

</div>

hey @gourab as we talked, you need a Before Provisioning Rule to put the values iin the plan so you can capture it using the OOTB function.

best!

---

<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:** [July 29, 2024, 8:16pm UTC](https://developer.sailpoint.com/discuss/t/add-entitlement-metadata-values-in-webservice-application/58293/7 "2024-07-29T20:16:32Z")

</div>

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