Username Generator with uniquecounter /variable with a custom starting value

SailPoint Human Fabric (SHF) SHF Discussion and Questions
1

Hello Everyone,

We are using IdentityIQ currently and maintain Identity name as “V” ( number is being picked as the next sequence from DB in IIQ).

We are moving from IIQ to ISC soon and when we turn ISC on, we have to start the username from the next sequence number for the new employee.

I saw the Username Generator transform and wanted to check if there is a possibility to set the uniquecounter or any other Global environment variable with a custom value ( the value being the next sequence to be generated for the new employee). This uniquecounter / variable can be used as the username for the next new employee and incremented by 1 to set for the next employee. is there a possibility in ISC to define these kind of variable or unique counter?

Thanks

Vasu.

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?
2

Hi @vasubh Have you searched the forum? There are a number of posts on sequential numbering. Here’s a live one: Unique Sequential ID Creation in Create Account Policy

3

No, SailPoint ISC does not support a persistent global counter/sequence variable like IIQ for Username Generator transforms. uniqueCounter only checks uniqueness during generation — it cannot be pre-seeded or maintained as a DB-style sequence.

Typical workaround is:

  • use an external system/API to maintain the sequence

  • or migrate to a pattern based on HR attributes/randomization instead of strict sequential IDs.

4

Hello @vasubh ,

We can use below approach.

OPTION 1

  1. Create a new JDBC based Connector Source in ISC. Provision this source to all the Users as part of BirthRight provisioning through Roles in ISC. Inside the Create Account policy of this source, we will call the required Sequence and generate the next value and fetch that value from ResultSet and get it populated in Account Attribute of this JDBC source
  2. Inside identity profile, create an identity attribute and map this new account attribute with it.
  3. Then, provision your AD source.

You need to consider of using this DB and making sure its reachable from your VAs

OPTION 2

  1. Create Before Provisioning Rule cloud rule where you are providing the starting value of SEQUENCE and providing the END VALUE of SEQUENCE inside the rule
  2. This will be a bit of error prone approach, but you can think about it.

Thank You,

Regards

Rohit