These runners are related to working with Core for Success Factors.
The runners are:
CoreSFLoader
This runner will load objects into Core for Success Factors
Configuration options
| Attribute | Data type | Default | Description |
|---|---|---|---|
| addHash | boolean | true |
Whether to save the extractHash lookup |
| checkDocType | boolean | false |
Whether to check if the document type exists before uploading the document |
| connection | LookupDetails, mandatory | none | The name and key to the lookup with the Core connection details. |
| workspaceSearchField | string | sf_person_information:user_id |
The field used in the employee workspace search |
The connection object should contain:
authHost- server that provides authenticationcontentHost- server that provides content functionalitysubscriptionName- subscription name for the Core subscriptiontenantId- tenant ID for the subscriptionuserId- user id from the API credentials for the Core subscriptionuserSecret- user secret from the API credentials for the Core subscription
Message attributes
| Option | Data type | Description |
|---|---|---|
| docDate, mandatory | string | The date for the document. |
| docType, mandatory | string | The document type. |
| employeeId, mandatory | number | The employeeId. |
| sourceFile, mandatory | SourceFile | The extracted file information. |
It adds the following attributes to the message object:
outcomethe outcome of the file uploadworkspaceIdthe id number of the workspace where the file was uploaded
DocPipelinesSSFLoader
The Document Pipelines integration to Core for Success Factors was full of errors when this was first created. The problems were eventually resolved, but in the time we were waiting we wrote the API based runner and would recommend using that instead.
Pipelines also has problems with logging when running multi-thread. It's impossible to determine which thread the log comes from.
This runner is stored in a repository on Github.