Source Account Created Trigger Sample JSON in Documentation

What problem are you observing?

The JSON I can see from “Source Account Created” trigger is different from what I can see in the documentation. The main bug here is [source] keyword is being attached in the “sourceName” field in JSON response.

For example, I am seeing “sourceName”: “Active Directory Employees [source]” as the sourceName. Extra [source] is being attached in the response.

Also, the attributes provided in documentation for “Source Account Created” for Active Directory is very few from what I am seeing in real executions for Active Directory Source account created. There are lots of attributes being populated in workflow executed JSON when account is created in Active Directory.

What is the correct behavior?

JSON should be up-to-date in the documentation. [source] should be removed from the source name.

What product feature is this related to?

IdentityNow Source Account Created Trigger. I haven’t checked for source updated/deleted trigger.

What are the steps to reproduce the issue?

Create a dummy workflow with “source account created” trigger and end with success. Enable the workflow and once account is created n any source, you can see the executions. See the JSON execution response. You will see [source] being attached in source name.

Do you have any other information about your environment that may help?

This is happening for Source Account Created trigger in Identity Now.

Hi @kdfreeman

Basically you are saying that you see the [source] attached to the source name?

Hi @rajeshs ,

Not only that, the source presented in documentation is Active Directory. When I checked executed JSON for active directory source account created in my tenant, I am seeing lots of attributes being populated in JSON rather than what it is being provided in documentation. In documentation, the JSON response has limited attributes only, for Active Directory source.

Hi @kdfreeman

Can you please share the response here and also the link for the documentation which you are referring to ?

You can mask the confidential information in the response

Hi @rajeshs , this is the documentation that I am referring to.
Triggers - SailPoint Identity Services.

Due to data confidentiality, I can’t share exact JSON response here. I have mentioned the steps to reproduce the exact JSON above.