Symptom
Business rules where values are derived from user-based or employment-based paths (for example: userConfig.Process Object.User.Global Job Information.Local Job) are not triggering during Additional Data Collection step.
Environment
SAP SuccessFactors Onboarding
Cause
- Expected behavior: Business rules that depend on user-based context are not supported in Additional Data Collection (ADC) because ADC objects use externalCode = AutoNumber, so a user context is not available.
- User-based references (for example: userConfig, candidate, parent.User, employment-based paths) are not supported in ADC for field-level or object-level rules, across rule purposes (Evaluate, Validate, Initialize, onSave).
Resolution
- Do not use ADC rules to derive values from user-based or employment-based paths (for example: userConfig.Process Object.User.Global Job Information.Local Job).
- Move derivation logic to Personal Data Collection (PDC) for the hire template, where rules run with a User externalCode context.
- If a value must be enforced in ADC, configure the field as mandatory to prevent saving without a value.
- Where feasible, design ADC rules to operate only on values stored within the same ADC object (self-contained logic), avoiding cross-user references.
- If product enhancement is required, refer to: 2090228 - How to Submit Ideas for SAP SuccessFactors Products.
See Also
Keywords
onboarding, additional data collection, adc, evaluate rule, mdf rule, userconfig, externalcode autonumber, local job, global job information, rule not populating, inconsistent rule behavior, personal data collection, pdc, employment context, candidate context , KBA , LOD-SF-OBX-CDC , Custom Data Collection , Problem
Product
SAP SuccessFactors Onboarding
SAP Knowledge Base Article - Public