Migrate Authoritative Source from (ultipro) users to SAP SuccessFactors, Identity Profile transforms & mappings from different sources

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

Migrate between Authoritative Source (ultipro) users To SAP SuccessFactors , Identity Profile : transforms & mappings from different sources.
also what change need to do in different source provisioning policies, all Data Points etc ?

steps to Achieve this ?
Success Factors (HR) is a our new Connector for us and need a roadmap.

2

Hi Osman

There a a few things to do:

  1. Setup connector for SuccessFactors and configure your identity and manager correlation.
  2. Create new IdentityProfile for the new source.
  3. Verify all the accounts from the new source are being correlated to existing identities correctly.
  4. Review provisioning policies and roles which reference current authoritative source and note which need to be updated.
  5. Perform the changes in your sandbox environment and change the priority of the new SF identity Profile to the be higher than the old ultipro IP.
  6. Review that all identities are now reflecting under the new identity profile and that all provisioning tests work as expected.
  7. Plan change to do relevant updates to respective provisioning policies and roles where applicable in Prod and at the end of the change, set the priority of the new SF identity Profile to the be higher than the old ultipro IP.

Hope that helps

3

In order to setup provisioning policies in Identity Profile do we have to setup codes or names
meaning :
Active, inactive etc or the option IDs in IP Provisioning Tab

38694,26393 etc

image
image230×594 11.8 KB

image
image1186×1178 69.7 KB

?

4

Hi @osmanmohammed

Yes, you will need to as part of your migration process if you intend the new Identity Profile to work in the same manner as the current one.

Thanks

5

You will need a Lifecycle state (LCS) transform that can use the SF statuses and convert them in to Identity Security Cloud LCS value.

6

This is our previous LCS Transform for ultipro source and what should be the change

{
“id”: “abcd1234”,
“name”: “LifeCycleState Transform for UltiPro”,
“type”: “static”,
“attributes”: {
“requiresPeriodicRefresh”: “true”,
“startDateCompare”: {
“attributes”: {
“id”: “StartDate Compare Transform for UltiPro”
},
“type”: “reference”
},
“tenDaysBeforeStartDate”: {
“attributes”: {
“id”: “TenDaysBeforeStartDate Transform for UltiPro”
},
“type”: “reference”
},
“employeeStatusCode”: {
“attributes”: {
“id”: “EmployeeStatusCode Transform for UltiPro”
},
“type”: “reference”
},
“value”: “#if($employeeStatusCode == ‘S’)suspend#elseif($tenDaysBeforeStartDate==‘yes’ && $startDateCompare==‘yes’)active#elseif($employeeStatusCode==‘T’)inactive#elseif($startDateCompare==‘no’ && $employeeStatusCode != ‘L’ && $employeeStatusCode != ‘S’ && $employeeStatusCode != ‘T’)active#elseif($employeeStatusCode == ‘L’)loa#{else}staged#end”
},
“internal”: false
}

image
image754×750 40 KB

Picklist values are:

Active
Dormant
Furlough
Discarded
Paid Leave
Retired
Reported No Show
Suspended
Terminated
Unpaid Leave

thanks
Osman

7

This looks okay. The picklist values and event mappings, should come from you SF team, that will make sure you’ve mapping the right ones that are being used. Every once in a while we come across some organizations that have different values mapped for some reason.

8

@sharvari @sup3rmark @jesvin90
the above list is shared by SF team.
i would need a updated rule if could help create on what needs to be changed with the previous code as we are going close to dead line with ultipro and need to switch IP ASAP?

9

ok, that’s good. I don’t understand your issue though, are you getting any error in your LCS transform mentioned above or is it not working?

10

let me rephrase my question
i did not used the above LCS transform on new IP and before mapping it
i want to make sure is the transform correct or do i need to modify as i we have a extended picklist from SF team

11

I would suggest you use the Preview feature to verify/spot check some users before you Apply Changes to your IP.

Another way to test it with all Identities is to, apply this LCS transform to any another identity attribute and apply changes to IP. Once IP refresh is complete you can use search to find out if the identities were updates with correct value in the identity attribute. If yes, you can apply it the same transform to LCS attribute and update the IP.

12

thank you will try and update
how this goes.

1 Like
13

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