SuccessFactors LMS Connectors allow Administrators to automate importing data into the LMS application. Data can be supplied directly by the customer, from an integrated source e.g. Bizx Platform or a 3rd party provider e.g. Skillsoft connector. Structured TXT and CSV input files, uploaded to a dedicated SFTP location, are used as data vehicle. The system uses the information supplied in the CONNECTORS configuration (System Admin>Configuration>System Configuration) and the connectors settings (System Admin>Configuration>Connectors) allow the administrator to automate the execution process.
File is removed from FTP drive once LMS picks it up.
* Must be configured in connector properties in LMS System Configuration.
Processing Methods for Input Fields
The connectors support two modes to process the input file:
Position Method (DEPRECATED - DO NOT USE): This method requires to specify all the fields in the input file to be specified in a specific order. This method is deprecated. Do not use this method it is deprecated.
Header Method: This method uses the header row to determine the position of the input data. Only this is the supported method.
The standard connector and imports will reject a record (not the entire input file) if any of the following conditions occur:
If the input file contains a null value for a field that cannot be null. Make sure that the ‘Req’ column in the data mapping tables which indicates whether a value for a field is required is checked.
If the input file contains a value that does not comply with the data type for that input file column.
If the field input value is a reference but the value does not match the reference table.
A standard connector accepts null values in the input file unless the field is a mandatory field. The connectors will not update the fields if the input file passes a null value.
Input File Format
The input file provided by the customers must have the following characteristics in order to be processed correctly by the SF Connector:
Character Set: SuccessFactors supports only the UTF-8 Character Set in the input file.
Column delimiter character: The delimiter character will always be a pipe (“|”) character out-of-the-box but it is configurable via appropriate connector property.
Row delimiter character: !##!
Column Headers: It must be included as the first row of the input file.
Order of columns: The connector will be set to “header” method for processing the input file. This means that the order of the headers can vary since the connector reads this header row and uses it to map data to the connector fields.
Null values (empty fields): All columns indicated in the header row must be provided in the input file data. The null values can be indicated by using two consecutive pipes.
Account Code Connector: This connector adds or removes fully identified Account Code references. In addition to keep basic account code references updated, a fully identified account code also enables posting chargebacks to SAP Financials. A fully identified account code contains an ID, the account code type, and the company code.
Administrator Connector: Adds Administrators to the LMS.
Alternate Job Code Connector: This connector adds or removes additional Job Code reference to users
Class Connector: Schedules instances of existing item records and is typically used for one-time data migrations.
Compentency Connector - SF: Creates competencies and associated rating scales in in the LMS. Records are created in the BizX environment and loaded to the LMS using the connector.
Curriculum Connector: Similar to Item Connector, this connector adds new curricula and updates to existing curricula.
Item Connector : Creates new items in SuccessFactors Learning and updates existing records. It is most common for the item connector to be used for one-time data migrations, rather than an ongoing feed.
Job Code Connector: Formerly known as job position, the job code connector creates new and updates existing job code values, such as domain, if curricula should be automatically assigned, and more
Learning History Connector: Records item-based completions for existing users completion of existing item records. Both the user and the item record must exist within the system for the record to be accepted. The learning history connector is most commonly used for one-time data migrations.
Organization Connector: creates organization references and updates to existing organization references. This connector has to be populated manually or by a third party solution, there is no standard integration with BizX.
Organization Owner Connector : This connector ads organization owners to an organization
Person IDs Connector: This connector syncs the PERSON_GUID from Platform to Learning.
Position Connector: Do not use.
Registration Connector: Updates user registrations in existing Classs. Both the user and Class must already exist in the system. This connector is typically used for one-time data migrations.
Security Domain Connector: Loads new domains, updates existing records, and manages the hierarchical relationship of domains
Skillsoft Connector: Loads courses from the vendor Skillsoft. Discuss with the vendor for more information.
User Connector: Loads new users and updates existing records. Capable of creating references, such as domains.
Federal User Connector: Contains all values as the standard user connector, but adds additional fields required for Federal agencies.
User Connector - SF: Loads and updates users in an integrated environment from the BizX suite. This connector is used solely for integrated environments.
These are the standard Connectors, the customers could have their own custom connectors made by Professional Services and there is also the OLSA Connector.