It is not possible to pass a profile with the account creation body

I need to provide a profile when I create an account, but the mapping does not occur as expected

{
    "name": "$plan.displayName$",
    "username": "$plan.email$",
    "externalId": "$plan.identificationNumber$",
    "type": "BASIC",
    "enabled": true,
    "profiles": [
        {
            "id": $plan.profileName$  
        }
    ]
}

the attribute $plan.profile Name$ is not replicated when a request to create and add a profile is made

That’s because ISC is triggering 2 operations, first create account without any attributes marked as entitlements, and then a second modify operation to add the entitlement(s). If the profiles part is a must in the request body to create an account, then I would suggest modifying the body in BeforeOperations rule and add a common profile

2 Likes

It is possible to increase the execution interval between each operation, creating an account and adding a profile happens at the same time and therefore does not work.

@clebercarvalhoRaise It’s a default behavior, whenever you request for an access connector checks whether the account is there or not, if account is not there it first creates the account and then add the requested access to the account. So there is no chance where you can increase the execution interval.

With respect to adding the profile in the request body you can surly add that in beforeOperation rule in create account http operation as suggested by @iamnithesh .

You will need to get the requestEndpoint and update the body then return the updated requestEndpoint.

Regards,
Shekhar Das

3 Likes

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