Skip to content

Commit 49c37bc

Browse files
authored
Merge pull request #186035 from cmmdesai/patch-1-24-2022
Onboarding module update
2 parents fb089af + 6f94381 commit 49c37bc

File tree

1 file changed

+14
-0
lines changed

1 file changed

+14
-0
lines changed

articles/active-directory/app-provisioning/sap-successfactors-integration-reference.md

Lines changed: 14 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -296,6 +296,20 @@ The SuccessFactors connector supports expansion of the position object. To expan
296296
| positionNameFR | $.employmentNav.results[0].jobInfoNav.results[0].positionNav.externalName_fr_FR |
297297
| positionNameDE | $.employmentNav.results[0].jobInfoNav.results[0].positionNav.externalName_de_DE |
298298

299+
### Provisioning users in the Onboarding module
300+
Inbound user provisioning from SAP SuccessFactors to on-premises Active Directory and Azure AD now supports advance provisioning of pre-hires present in the SAP SuccessFactors Onboarding 2.0 module. Upon encountering a new hire profile with future start date, the Azure AD provisioning service queries SAP SuccessFactors to get new hires with one of the following status codes: `active`, `inactive`, `active_external`. The status code `active_external` corresponds to pre-hires present in the SAP SuccessFactors Onboarding 2.0 module. For a description of these status codes, refer to [SAP support note 2736579](https://launchpad.support.sap.com/#/notes/0002736579).
301+
302+
The default behavior of the provisioning service is to process pre-hires in the Onboarding module.
303+
304+
If you want to exclude processing of pre-hires in the Onboarding module, update your provisioning job configuration as follows:
305+
1. Open the attribute-mapping blade of your SuccessFactors provisioning app.
306+
1. Under show advanced options, edit the SuccessFactors attribute list to add a new attribute called `userStatus`.
307+
1. Set the JSONPath API expression for this attribute as: `$.employmentNav.results[0].userNav.status`
308+
1. Save the schema to return back to the attribute mapping blade.
309+
1. Edit the Source Object scope to apply a scoping filter `userStatus NOT EQUALS active_external`
310+
1. Save the mapping and validate that the scoping filter works using provisioning on demand.
311+
312+
299313
## Writeback scenarios
300314

301315
This section covers different write-back scenarios. It recommends configuration approaches based on how email and phone number is setup in SuccessFactors.

0 commit comments

Comments
 (0)