Can we update Account attribute from ISC workflow?

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

hello everyone,

We have a requirement to update the downstream application(JDBC) account attribute using custom form, . One of the requirement is to limit the scope of the identity that Is

1.Populate identities in the dropdown if user has ‘A’ Account, if not don’t populate.
2.when we select the user, auto populate user “A” account attribute in the read-only field(Next field ).

Can we do it above criteria in ISC SailPoint ?

Is it feasible to update account attribute from ISC workflow ?

Thanks.

2

Hi @saikumarS ,

Can’t this be handled using attribute sync? or is this a different requirement to manually update the attributes?

3

Hi @saikumarS,

The account attribute cannot be updated unless the “Update Account” operation is triggered. This typically occurs during the following events:

  • Adding an entitlement
  • Removing an entitlement
  • Attribute synchronization

Could you please share a brief overview of your requirement? This will help us address it more effectively.

4

Hi theja,

Thaks for the reply.

We wanted to temporarily increase the Line Limit of a user in ABS source to a different value, this should remain through the day and then return to its original value.

5

Hi Sidharth,

I wanted to update a Account attribute for one down Strem application via workflow launcher ,by selecting user in the form.

6

Hi @saikumarS

I think we can do this also

  • You can use a dynamic identity filter to populate only those identities that have an account on application A.
  • Use a transform or identity attribute to fetch and display the account attribute in a read-only field once the identity is selected.
  • A workflow can be triggered on form submission to call an action that updates the account attribute via provisioning.
  • Use “Update Account” action with appropriate provisioning policy and ensure the account is correlated.

Just give it a try.

Thanks
Manvitha.Nalabolu

1 Like
7

Hello @saikumarS
This use case is serviceable, you can do using a FLAT FILE source.
→ Grab the response from the FORM into a Workflow
→ Use that Workflow to create a account for that identity on a Flat File Source and put that value in an account attribute there.
→ Map that account attribute to an Identity Attribute
→ Now use the said Identity Attribute in your Attr Sync mappings on your JDBC source

As this is the only way you can update any attribute be it identity or account and get it populated to downstream system.

Thanks

2 Likes