Advanced Settings

Update existing SuccessFactors picklist mappings and add additional attributes.

Picklist Mapping Configuration

SuccessFactors picklist mapping is for Update operations only.

  1. Enter the Picklist Mapping as required for your tenant configuration. For example, BusinessEmail=<Picklist OptionID> or BusinessPhone=<Picklist OptionID>. For more information, refer to Provisioning of Email, Phone, and Username Attributes.

  2. Press Enter.

  3. Repeat steps 1 and 2 until all values have been entered.

  4. Select Save.

Include Compound Employee API Entities

Note
Ensure that the defined and validated attributes you want to add are in the Include Compound Employee API Entities field on the managed system as well as in the connector configuration.

Older SuccessFactors connectors have predefined values for Include Compound Employee API Entities. To add new attributes to the managed system, make sure the attribute used as a column in the SOAP query returns a valid result. If the SOAP query response is valid, then that attribute can be added to the Include Compound Employee API Entities field. Separate multiple entries with a comma.

For example, if the SecondaryAssignments attribute is added to Include Compound Employee API Entities, then the following query execution in the SOAP tool returns a valid result:

select person,personal_information,address_information,email_information,phone_information,employment_information,job_information,compensation_information,paycompensation_recurring,paycompensation_non_recurring,accompanying_dependent,alternative_cost_distribution,job_relation,BenefitsIntegrationOneTimeInfo,BenefitsIntegrationRecurringInfo,deduction_recurring,deduction_non_recurring,global_assignment_information,ItDeclaration,personal_documents_information,associated_employee_information,person_relation,payment_information,direct_deposit,EmpCostAssignment,national_id_card,dependent_information,emergency_contact_primary,DRTMPurgeStatusOverview,SecondaryAssignments from CompoundEmployee where isContingentWorker in(‘true’,‘false’) and user_id IN(‘xyz’,) ORDER BY start_date DESC

Exclude Compound Employee API Entities

Use this feature to exclude Personally Identifiable Information (PII) data from your aggregation results. Adding an entry to this field will cause all the associated attributes of the employee API entry to be excluded from your aggregation results. For example, if you enter personal_information in the list, then attributes associated to personal information, such as first name and last name, are not aggregated.

  • In the Exclude Compound Employee API Entities field, enter the entity you want to be excluded from your aggregation results and then press the Enter key. You can enter multiple entries using this method.

    Caution
    If you add an unsupported entity or misspell the entity, your aggregation will fail.

    Only the following entries are supported:

    • personal_information

    • address_information

    • email_information

    • phone_information

Additional Attribute Mapping

You can customize the aggregation of attributes or add custom attributes by defining the attribute name and its navigation path that the connector uses to aggregate from SuccessFactors. For more information on SuccessFactors schema attributes and SFAPI, refer to the Aggregation of Additional Schema Attributes Using SFAPI topic.

Note
Ensure that names of schema attributes added under attribute mapping are also added in the source account schema.

  1. Enter a name for the Schema Attribute.

  2. Enter the attribute Navigation Path (SFAPI Path) as defined in SFAPI. For example: /person/employment_information/job_information/pay.

  3. Repeat steps 1 and 2 until all values have been entered.

  4. To query for additional attributes, enter the name of the compound employee API extended sub-structures/entities (separated by a comma) in the Include Compound Employee API Entities field.

  5. Select Save.