Add entitlement operation for webservice connector

[apattana (Amisha Pattanaik)]

Please be sure you’ve read the docs and API specs before asking for help. Also, please be sure you’ve searched the forum for your answer before you create a new topic.

Please consider addressing the following when creating your topic:

• What have you tried?
• What errors did you face (share screenshots)?
• Share the details of your efforts (code / search query, workflow json etc.)?
• What is the result you are getting and what were you expecting?

Hi All,

I need to add entitlement operation in a webservice connector. In the body I have to pass two other type of entitlements as input and the response id need to be added to an account attribute. When I created one Add entitlement type operation and try to achieve the process its throwing error like "Error: Incomplete items. Please contact your administrator.

Provisioning

Exception while updating account. Error: No configuration found for’Add Entitlement-User_role’. Please add at least one operation and try again.,Exception while updating account. Error: No configuration found for’Add Entitlement-User_Sponcer’. Please add at least one operation and try again."

here User_role and User_Sponcer are two entitlement which I need to give as input in the body.

example body : [

{

    "user__v.id": "123",

    "role__v.name__v": "Editor",

    "sponsor__c.name__v": "Biophytis",

    "sponsor1__c.name__v": "",

    "status__v": "active__v"

},

  {

    "user__v.id": "123",

    "role__v.name__v": "Viewer",

    "sponsor__c.name__v": "",

    "sponsor1__c.name__v": "Biophytis",

    "status__v": "active__v"

}

]

Response :

{

"responseStatus": "SUCCESS",

"data": \[

    {

        "responseStatus": "SUCCESS",

        "data": {

            "id": "xyz1",

            "url": "/api/v25.3/vobjects/user_role_setup__v/xyz1"

        }

    },

    {

        "responseStatus": "SUCCESS",

        "data": {

            "id": "xyz2",

            "url": "/api/v25.3/vobjects/user_role_setup__v/xyz2"

        }

    }

\]

}

[BhanuK1 (Bhanu Kondi)]

Hi @apattana , Do you have two entitlement aggregations?

[BhanuK1 (Bhanu Kondi)]

If you have two entitlement types, then you should be able to see two Add entitlement operation types, in each operation define the body to add only that entitlement type, like for User_role,
body should be
{

"user__v.id": "123",

"role__v.name__v": "Editor",

"sponsor__c.name__v": "Biophytis",

"sponsor1__c.name__v": "",

"status__v": "active__v"

}

for user_sponcer, body should be
{

"user__v.id": "123",

"role__v.name__v": "Viewer",

"sponsor__c.name__v": "",

"sponsor1__c.name__v": "Biophytis",

"status__v": "active__v"

}

dont combine both the request body and make sure to select correct add entitlement operation type

[apattana (Amisha Pattanaik)]

@BhanuK1 Thank you Bhanu. Here the problem is if the role is editor then the sponcer field should be sponsor__c.name__v, and if the role is viewer the sponcer field should be sponsor1__c.name__v. The field name is different in application side. so for that i added one add entitlment operation and created one rule. with 2 add entitlement I am not sure about the body for sponcer

[apattana (Amisha Pattanaik)]

if I add two separate operations then I am getting below error

Error: Incomplete items. Please contact your administrator.

Provisioning

Exception occurred while performing ‘Modify’ operation on identity ‘123’: Error: Error executing before operation rule for endpoint ‘Add entitlement_Record Security_Role_sponcer_v’: BeanShell script error: bsh.ParseException: Parse error at line 115, column 42. Encountered: ; BSF info: VeevaRIM add Entitlement Record Security Before Operation Rule at line: 0 column: columnNo

[BhanuK1 (Bhanu Kondi)]

Did you use before operation rule for the Add entitlement operation?

[apattana (Amisha Pattanaik)]

Yes. I had added. with hardcoded value without rule also its throwing error

[Santhakumar (Shantha Kumar)]

Do this first?

• Create two separate operations in the connector:
  • One for User_role
  • One for User_Sponsor
• Define the body template for each operation so it only contains the fields relevant to that entitlement type.
  • For User_role, include role__v.name__v and whichever sponsor field is appropriate.
  • For User_Sponsor, include the sponsor field and the corresponding role reference.
• Do not combine them into a single request body. SailPoint expects one entitlement per operation call.
• Map the response: In each operation, configure the responseElement so SailPoint knows to pull the id from data.id in the response and store it in the correct account attribute.

Example flow of structure

Operation: Add Entitlement – User_role

• Request body:

json

{
  "user__v.id": "123",
  "role__v.name__v": "Editor",
  "sponsor__c.name__v": "Biophytis",
  "sponsor1__c.name__v": "",
  "status__v": "active__v"
}

• Response mapping: data.id → account attribute user_role_id

Operation: Add Entitlement – User_Sponsor

• Request body:

json

{
  "user__v.id": "123",
  "role__v.name__v": "Viewer",
  "sponsor__c.name__v": "",
  "sponsor1__c.name__v": "Biophytis",
  "status__v": "active__v"
}

• Response mapping: data.id → account attribute user_sponsor_id

[hyungsunkang93 (Hyung Sun Kang)]

That error is a pure BeanShell syntax issue — line 115 has an unexpected ;, so you’ve got an unclosed brace, paren, or quote right above it. Fix that before anything else, the connector never reaches the body logic until the rule compiles. And when you say “no rule also fails,” double-check you actually detached the Before Rule from the operation, not just emptied its contents — otherwise it keeps getting invoked.

Also, since the sponsor field name is tied to the role, you don’t really need a rule at all. Each Add Entitlement operation already knows its entitlement type, so just hardcode sponsor__c.name__v in the User_role body and sponsor1__c.name__v in the User_Sponsor body. The operation routing handles the conditional for you.

[BhanuKondi]

@apattana , You should have two operations for the Add entitlement , one for User_role and one for User_sponcer, and in the request body define whatever the fields required and use before operation rule if you need to manipulate the fields