Functionalities
This connector supports only Provisioning.
The functionalities of this connector enable exporting and modifying Workers in a Workday system. Workers include employees and contingent workers. It does not support creating or deleting workers in a workday system. The connector can execute reports in Workday to fetch additional details of workers.
The connector also enables exporting Workers From Transaction Logs. Changelog is a feature that can be configured within Workday to capture changes for different business processes that the client chooses. The workday connector can then pull the data changes within a certain time period. In addition we can also send in the Subscriber Reference ID to get the transactions specific to that subscriber ID.
The connector also supports exporting References from a Workday system. The connector also enables exporting details by executing reports in Workday.
The connector also enables exporting details by executing reports in Workday.
Provisioning Integration
| Data Format |
Export |
Create |
Modify |
Delete |
Trigger |
|
Worker |
Yes |
No |
Yes |
No |
No |
|
Reference |
Yes |
No |
No |
No |
No |
|
WorkerFromTransactionLogs |
Yes |
No |
No |
No |
No |
|
Report |
Yes |
No |
No |
No |
No |
Prerequisites
Ensure that these prerequisites are satisfied:
-
Workday is installed, configured, and running.
-
An administrator account that can be used to establish a connection and has authority to manage workers on the connected system.
The following services and operations are used in a workday connector and therefore the Administrator account should have the required permissions in Workday to execute these operations:
|
Service |
Operation |
Purpose |
|
Human_Resources https://community.workday.com / custom/developer/API/ Human_Resources/v28.0/ Human_Resources.html
|
Get_Workers |
To fetch worker details |
|
Get _Job_Family Groups |
To fetch family group information. |
|
|
Get_Workday_Account |
To fetch account details for a worker |
|
|
Get_Server_Timestamp |
To authenticate connected system during Test Connection |
|
|
Change_Personal_Information |
To manage personal information of a worker |
|
|
Change_Other_IDs |
To manage other IDs of a worker. | |
|
Change_Preferred_Name |
To manage preferred name of a worker | |
|
Change_Legal_Name |
To manage legal name of a worker. |
|
|
Change_Additional_Names |
To manage additional name of a worker. |
|
|
Add_Workday_Account |
To add an account for a worker |
|
|
Update_Workday_Account |
To update the Workday account of a worker |
|
|
Maintain_Contact_Information |
To update contact information like Address, Phone, Email and Web- Address. |
|
|
|
|
|
|
Integrations https://community.workday.com /
|
Get_References |
To fetch possible vales for fields having predefined values. Filter processing in Worker export and lookup is done by using this API. |
|
Put_Reference |
To update the worker ID |
If the Administrator account does not have any of the above permissions in Workday, the following error is displayed during the connector operation:
Error: Agent Execution Failed. Processing error occurred. The task submitted is not authorized.
Creating and Managing the Connected System
Connected system can be managed from both Admin UI and Workflow and Connectivity studio. The step by step explanation to create is provided in the following sub sections. Clicking on the connected system from the listing page(admin UI)/selecting the desired system and clicking on View button (Studio) will take you to a detail page where you can can manage the connected system.
Create from Admin UI
-
Log in to Identity Administration and click the Systems tab.
-
On the Connected System View page, click the Add button and select the Workday connected system from the Type drop-down list. The Connected System Details page displays the default values:
-
Enter the desired information:
Definition Supported Connectors
Displays whether the connected system is Identity only, Provisioning only, or both. Type Select the connected system type. Locale
Select the preferred language (default: English). Locale specific information such as Display Name and Description can be added only while modifying the connected system. Name The name for this connected system. Note: The name cannot be modified later. Display Name The display name of the new connected system. Description The description of the connected system. Associated With
Select how the connector associated with this system will run:
- Server (default) - Runs locally on the Provisioning/Identity Server.
- Global Identity Gateway - Runs remotely on a Global Identity Gateway cluster member. Note: Only GIG clusters that have at least one registered and enabled member will display in this list.
- See Using the Global Identity Gateway with Connected Systems for additional information.
Password Reset By Enables administrators to configure password management functions normally available to Users and OBO (On Behalf Of) Users: - OBO User Only - Connected system and account association information is displayed only in Self-Service user management (for OBO Users). OBO Users can reset passwords for accounts on this connected system. Administrators can perform all user management functions for this connected system (e.g., enable/disable, validate, associate user, and password reset). End users will not see their accounts on this connected system in Self-Service and Kiosk; therefore, they cannot reset passwords for accounts on this connected system.
- Users and OBO User - Connected system and account association information is displayed in Self-Service password reset, Self-Service - Kiosk, and Self-Service user management. Self-Service users, Kiosk users, and OBO Users can reset passwords for accounts on this connected system. Administrators can perform all user management functions for this connected system (e.g., enable/disable, validate, associate user, and password reset).
- External - Connected system and account association information is not displayed in Self-Service password reset, Self-Service - Kiosk, and Self-Service user management. Self-Service users, Kiosk users, and OBO Users cannot reset passwords for accounts on this connected system.
Note: When user management configuration enables OBO Users to perform password resets, this definition must be set to OBO User Only or Users and OBO User. For connectors that support Provisioning only, there is no password reset capability.
Provisioning Option Select the provisioning option: - Automated (default) - The connected system functions as a normal connected system; there are no restrictions.
- Administrative - The connected system cannot be used as an object in a workflow.
Enable HPAM Support Select to make the connected system HPAM enabled (default: cleared). Note: This can only be set for systems that support Identity. Enable Transfer Of Accounts Select to make the transfer of Accounts enabled (default cleared). Connection Information Server URL The URL of the Workday Server. To enable a secure SSL connection, use the HTTPS protocol.
Note: This connector uses the Java keystore for SSL communication with the system. See the guide Configuring SSL for additional information about enabling SSL.
Tenant Name The tenant name in the Workday Server.
Web Service Version Version of the Workday Web service to be called.
Service Account Name The name of the administrative user account used to connect to the server.
Service Account Password The administrative user password.
Connection Timeout The maximum number of seconds to wait for the Web Service to respond before the connection attempt times-out. 0 means no time out.
Configuration Details Enable Advanced Logging When this is selected, all requests will be logged in a file named WorkdaySOAPMessages.log under the logs folder. The location of the logs folder depends on the component from where the connector is executing, Provisioning server / GIG / Workflow Studio.
Password Expiration Support Expiration Options For Admin/OBO User Password Reset Specify the password expiration: None or Immediate. System Owner Adds or removes users assigned as the owners of the system. Displays the Connected System Owner Search page for selecting users. The HPAM column indicates whether the system owner is authorized to use the HPAM feature. The Approvers column indicates whether the system owner is an approver in the approval process.
-
Click the Test Connection button to test the Connection Information:
- If successful, this message may display:
Message: Connection from Provisioning to the connected system was established successfully.
- If unsuccessful, this message may display:
Error: Failed to establish connection from Provisioning to the connected system.
Note: If the connection fails, additional messages may display providing more information regarding the failure, and additional information may be posted to the Provisioning and Identity logs.
-
(Optional) To select owners of the system, click the System Owner Add button. The Connected System Owner Search page displays:
-
To select owners of the system, click the System Owner Add button. The Connected System Owner Search page displays:
- To add additional system owners, click the Add button.
-
- On the Connected System Details page, click the Add button to save the configured connected system. The Object Category Association page displays a list of categories that are already associated and/or can be selected to add additional associations to this connected system:
-
Select one or more available object categories or provide search criteria and click the Search button to find specific categories to select. If there are no available categories to select, proceed to Step 7.
-
Click the Add Association button to associate the selected object categories to the connected system.
-
-
Click the Back button to return to the Connected System View page. The new connected system displays in the list.
See Copying, Modifying, and Deleting Connected Systems for additional information.
Creating from Studio
- Log in to the Workflow and Connectivity Studio and click Connectivity ► Add Systems on the menu bar. The Add Connected Systems window displays.
- Select the Workday connected system from the Type drop-down list. The default values display:
-
Enter the desired information:
Definition Type Select the connected system type. Name The name for this connected system. Note: The name cannot be modified later. Display Name The display name of the new connected system. Description The description of the connected system. Supported Connectors Displays whether the connected system is Identity only, Provisioning only, or both. Only connectors that support Provisioning are available here. Associated With Select how the connector associated with this system will run: - Server (default) - Runs locally on the Provisioning/Identity Server.
- Global Identity Gateway - Runs remotely on a Global Identity Gateway cluster member. Note: Only GIG clusters that have at least one registered and enabled member will display in this list.
Password Reset By This feature is not available for this connector. Provisioning Option
Select the provisioning option:
- Automated (default) - The connected system functions as a normal connected system; there are no restrictions.
- Administrative - The connected system cannot be used as an object in a workflow.
Enable HPAM Support Select to make the connected system HPAM enabled (default: cleared). Note: This can only be set for systems that support Identity. Enable Transfer Of Accounts Select to make the transfer of Accounts enabled (default cleared). Connection Information Server URL The URL of the Workday Server. To enable a secure SSL connection, use the HTTPS protocol.
Note: This connector uses the Java keystore for SSL communication with the system. See the guide Configuring SSL for additional information about enabling SSL.
Tenant Name The tenant name in the Workday Server.
Web Service Version Version of the Workday Web service to be called.
Service Account Name The name of the administrative user account used to connect to the server.
Service Account Password The administrative user password.
Connection Timeout The maximum number of seconds to wait for the Web Service to respond before the connection attempt times-out. 0 means no time out.
Connection Information Enable Advanced Logging When this is selected, all requests will be logged in a file named WorkdaySOAPMessages.log under the logs folder. The location of the logs folder depends on the component from where the connector is executing, Provisioning server / GIG / Workflow Studio.
Password Expiration Support Expiration Options For Admin/OBO User Password Reset Specify the password expiration: None or Immediate. -
Click the Test Connection button to test the Connection Information:
- If successful, this message displays:
Message: Connection from Studio to the connected system was established successfully.
- If unsuccessful, this message displays:
Error: Failed to establish connection from Studio to the connected system.
Note: If the connection fails, additional messages may display providing more information regarding the failure.
-
Click the Apply button to apply changes. The Category Association window displays.
-
Select one or more object categories from the Available Categories list or enter a category name and click the Search button to find a specific category to select. If there are no available categories to select, proceed to Step 6.
-
Click the Add button to associate the selected object categories to the connected system.
-
-
Click OK to accept selected categories.
See Copying, Modifying, and Deleting Connected Systems for additional information.
Using the Connected System for Provisioning
Perform these procedures to configure the connector:
Note: If the number of records to be processed exceeds one thousand, we recommend configuring the workflow to use bulk mode, which lowers the memory consumption of the system by streaming data to files. Because data is streamed for every task, performance of the workflow execution will be decreased due to increased read-write operations. See the Workflow and Connectivity Studio document for details on how to configure bulk mode.
Configuring for Export
Perform these procedures to configure the connector for data export:
From the Workflow and Connectivity Studio, select the Workday UserExport workflow listed under the projects folder.
If a workflow does not already exist, create an import workflow. See the Workflow and Connectivity Studio document for details on creating import workflows.
Configuring the Export Connector
- In the Design pane, double-click the export object (the first workflow object after the Start object). The Configure Data Source window displays:
- From the Configure Plug-in tab, set these properties as required:
| Associated Connected System | Select the connected system from the list. The export operation will be done from this connected system. |
| Data Formats | Select the type of data format to use: Worker (default), WorkerFromTransactionLogs, Reference or Report |
| AsOfEffectivceDate |
Specify the effective date based on which the worker details have to be fetched. To fetch future dated worker information, a value after that date must be set for this property. The date must be given in the format yyyy-MM-dd. This property is available only for Worker and WorkerFromTransactionLogs data formats. |
| DeltaExportMode |
Select the type of attribute to export if a change takes place (this works in conjunction with ExportMode when DeltaExport is selected):
This property is not available for WorkerFromTransactionLogs data format. |
| DynamicConnectedSystem |
Select the global variable to use as the dynamic connected system name. This works in conjunction with DynamicCon- nectedSystemOption when GlobalVariable is selected. |
| DynamicConnectedSystemOption |
Select how to control Dynamic System Support:
|
|
ExcludeInactiveWorkers |
Specify whether to exclude terminated workers. This property is available only for Worker data format. |
| ExecuteGIGAssociatedTaskAsynchronously | If this property is True, GIG associated tasks will execute asynchronously. |
| ExportMode |
Select the type of data to export:
|
| Filter |
Specify a filter to return only those entries that match the search criteria. This property is available only for Worker data format. Use the Set Filter button that becomes active to create a filter (see Set Filter below). |
| GetWorkerByID |
Specify the ID of a worker to fetch the details. This property is available only for Worker data format. |
| IncludeEntireChainOfPostionMana gers |
Set this to TRUE to return details of all managers in the position management chain. Setting this to FALSE will return only the details of direct manager. This property is available only for Worker and WorkerFromTransactionLogs data formats. |
| InitialTransactionStartDate |
Specify transaction start date to be used for the initial execution. Succeeding executions will use the time of the previous execution to set the transaction start date. The date must be given in the format yyyy-MM-dd. This property is available only for WorkerFromTransactionLogs data format. |
| MaxResults |
Select the maximum number of results to be returned (this works in conjunction with ExportMode when FullExport is selected). If this is 0, all entries matching the search criteria are returned. If MaxResults is set for WorkerFromTransactionLogs data format, the entries ignored during export on reaching max results will not be fetched again in the next export. |
| OverrideFieldIntegrationSystemID |
Specify the integration system ID corresponding to which the IntegrationOverrideFields are to be fetched. This property is available only for Worker and WorkerFromTransactionLogs data formats. |
| ReferenceType |
Select the type of reference to be exported:
This property is available only for Reference data format. |
| ReportConfiguration |
Configure this to execute report and fetch additional details of workers. This property is available only for Worker and Report data formats. Use the Configure button that becomes active to configure reports (see Report Configuration below). |
| ResultsPerPage |
Specify the number of entries to be fetched from Workday in a single call. |
| SubscriberReferenceID |
Specify the subscriber reference ID if transaction log subscription needs to be subscriber specific. This property is available only for WorkerFromTransactionLogs data format. |
| Transaction_DateRanges |
Specify the date range calculation option to be used:
This property is available only for WorkerFromTransactionLogs data format. |
| Transaction_Effective_From |
Specify the earliest Effective Date as marked within the Workday system. This can be configured as a particular date in the format yyyy- MM-dd or date time in the format yyyy-MM-dd hh:mm:ss a. This can also be configured as the number of days to be incremented (+X) or decremented(-X) with current date time. The value configured is considered only when Transaction_Effective_Through is also configured. If this property is not configured and Transaction_Effective_Through is configured, the value for this setting is taken as the time of previous execution of this task. This property is available only for WorkerFromTransactionLogs data format. |
| Transaction_Effective_Through |
Specify the latest Effective Date as marked within the Workday system. This can be configured as a particular date in the format yyyy- MM-dd or date time in the format yyyy-MM-dd hh:mm:ss a. This can also be configured as the number of days to be incremented (+X) or decremented(-X) with current date time. This property is available only for WorkerFromTransactionLogs data format. |
| Transaction_Updated_From |
Specify the earliest Updated Date as marked within the Workday system. This can be configured as a particular date in the format yyyy- MM-dd or date time in the format yyyy-MM-dd hh:mm:ss a. This can also be configured as the number of days to be incremented (+X) or decremented(-X) with current date time. The value configured is considered only when Transaction_Updated_Through is also configured. If this property or Transaction_Updated_Through is not configured, the value for this setting is taken as the time of previous execution of this task. This property is available only for WorkerFromTransactionLogs data format. |
| Transaction_Updated_Through |
Specify the latest Updated Date as marked within the Workday system. This can be configured as a particular date in the format yyyy- MM-dd or date time in the format yyyy-MM-dd hh:mm:ss a. This can also be configured as the number of days to be incremented (+X) or decremented(-X) with current date time. The value configured is considered only when Transaction_Updated_From is also configured. If this property or Transaction_Updated_From is not configured, the value for this setting is taken as the current time. This property is available only for WorkerFromTransactionLogs data format. |
| WorkerType |
Select the type of workers to be exported:
This property is available only for Worker data format. |
|
Note:
|
|
Set Filter
Setting the filter is a means to narrow the search scope and return specific results:
| Element | Description |
| Attribute |
Select the attribute of the filter. This represents the attribute name for searching the Workday. Only WorkerID and WorkerDescriptor can be used as filter attributes. |
| Comparison | Select the operator value for this filter. |
| Value |
Enter the required result value. |
| AND Condition List |
Creates an AND statement comparing selected conditions. If there is more than one condition in this list box, all conditions must be true. |
| OR Condition List |
Creates an OR statement comparing selected conditions. If there is more than one condition in this list box, one of the conditions must be true. |
| Filter Syntax | Displays the filter syntax used to retrieve entries from the LDAP directory and to build the export list. |
| Edit Filter Manually |
Check this box to manually edit the filter in the Filter Syntax to build complex filters. |
- Using logical AND/OR, generate the complex filter to narrow the search result.
- Click OK when complete to return to the Configure Data Source window.
Report Configuration
This is configured to execute reports and fetch additional details of workers from Workday. Click the Configure button. The Workday Configured Reports List window displays:
| Element | Description |
| Name |
Displays the report name. |
| Method | Displays the method, Get or Post of the report. |
| Enabled |
Displays the report status. |
| Add |
The Workday Report Configuration window displays to add a new report. |
| Copy |
Creates a new report based on the selected report. |
| View |
The Workday Report Configuration window displays to view or modify the selected report's properties. |
| Disable |
Enable/disable the selected report. |
| Delete |
Deletes the selected report. |
| Export |
Exports reports to an XML which can be imported to another installation. |
| Import |
Imports reports from the selected XML file. Only new reports will be imported; if there is already a report with the same name, it will be skipped during import. |
Adding a New Report
Click the Add button. The Workday Report Configuration window displays the Report Settings tab:
- Enter the report name to add.
- Execute Report per Worker checkbox will be active and enabled by default for Worker data format. This is not supported for Report data format. When this is turned ON, report is executed for each worker. When this is turned Off, report will be executed first and then the workers are exported and merged with report attributes as per the mapping configured in Response Settings tab.
- Select a Method, Get or Post for the report.
- The report is Enabled by default. Disable the Enabled checkbox, if required.
- The Server URL will be populated by default from the Workday System details.
- Enter the Report URL.
- Add the parameters and its values for the report, if required. Parameters can be set using worker attributes when Execute Report per Worker is ON. For e.g., Employee_ID=##WorkerID##. Paging for Report data format can be controlled by two of the following parameters:
$PageNumber, $StartIndex, $EndIndex and $ResultsPerPage. For e.g.,
Page=##$PageNumber## and PageSize=##$ResultsPerPage##. -
Click on the Response Settings tab.
- Enter the Record Name if the report attribute names are to be prefixed.
- Browse or enter a sample Data XML path. The XML tree will be populated based on the selected XML.
- Select a node from the tree and click "Set Entry Node" button to set it as entry node.
- Link Report Data with Worker Attributes section is displayed only when Execute Report per Worker checkbox is turned Off. Configure a mapping here to link between Worker record and Report record. For e.g., WorkerID ►>Employee_ID.
- Click OK. The configured report gets listed in the Workday Configured Reports List window.
Notes:
-
Multiple reports can be added.
-
If reports are configured and enabled, the Value of ReportConfiguration in Export Plugin window will be displayed as “Configured and Enabled”. If reports are configured, but none are enabled, the value will be ”Configured and Disabled”. If report is not configured, the value will be ”Not Configured”.
-
The attributes of the configured and enabled reports should list in the Configure Link window. Move the required report attributes to the Selected list for exporting the report.
-
The administrator account of Workday system should have the required permissions in Workday to execute the reports.
-
-
(Optional) Select the Attributes Only standard attributes display:
Modify schema attributes using these buttons:Element Description Add Adds additional attributes to the list. The Add New Attribute dialog displays. Export Exports the schema list to an XML file.
Import Imports the schema list from an XML file.
Reset Schema Resets the schema definition to the default schema prepackaged with the IdM Suite, plus any global variable added.
- (Optional) Select the Appearance tab to change how the Connected System object displays in the Design pane.
- Click OK to save any changes and return to the Workflow and Connectivity Studio window.
Configuring the Export Link
-
In the Design pane, double-click the export link between the export object (the first workflow object after the Start object) and the Data Mapper object. The Configure Link window displays:
Element Description Source Attributes Select the attributes to export.
Selected Attributes Displays default attributes and those attributes that have been selected from the Source Attributes.
Notes: The check boxes are used only for delta export operations. These checked attributes will always be exported whether they were changed or not. Usually, the attributes that are selected as mandatory attributes help in identifying or verifying an entry when completing mapping functions.
Format Displays the Format Date window to specify a date/time format to be applied to the selected date type attribute, for example, BirthDate. During export, the attribute's value is converted to the specified format. See the Format Date steps below for additional information.
Note: The Format button is only enabled for date attributesAdvanced Settings Displays the Configure Attributes window for selecting any attributes that need to be encrypted. - From the Attribute Selection tab, select attributes to export. Usually, these attributes that are selected (mandatory attributes) help in identifying or verifying an entry when completing Data Mapper functions.
- (Optional) Click the Format button to specify a date/time format to be applied to the selected date type attribute. The Format Date window displays
- Select the Include Time check box to add the timestamp with the date.
- Select the 24 Hour or 12 Hour option button and then select the required date/time format.
- Click OK to save the selected format. The Configure Link window
- Select the Include Time check box to add the timestamp with the date.
- Click OK to save any changes and return to the Workflow and Connectivity Studio window.
- Deploy the workflow by selecting Deploy ► New Deployment.
See the Workflow and Connectivity Studio document for details of deployment options. - Manage and run the deployed workflow from the Admin UI ► Server tab.
See the Identity Suite Administration Guide for details.
Configuring for Import
Perform these procedures to configure the connector for data import:
- Configuring the Import Connector
- Configuring the Import Link
From the Workflow and Connectivity Studio, select the Workday UserModify workflow listed under the projects folder.
If a workflow does not already exist, create an import workflow. See the Workflow and Connectivity Studio document for details on creating import workflows.
Configuring the Import Connector
- In the Design pane, double-click the import object (the last workflow object). The Configure Data Source window displays:
-
From the Configure Plug-in tab, set these properties as required:
Element Description Associated Connected System Select the connected system from the list. The import operation will be done to this connected system. Data Formats Select the type of data format to use: Worker. DynamicConnectedSystem Select the global variable to use as the dynamic connected system name. This works in conjunction with DynamicConnectedSystemOption when GlobalVariable is selected. DynamicConnectedSystemOption Select how to control Dynamic System Support (DSS): - None - There will not be any Dynamic System Support.
- Transaction-SystemName - The value of the Transaction-SystemName attribute in data will be used as the dynamic connected system. The connected system name must be passed as the value of the attribute Transaction-SystemName; if it is missing in data, the operation will fail.
- GlobalVariable - Select a global variable to use as the dynamic connected system name from the property DynamicConnectedSystem.
See the Dynamic System Support appendix in the Workflow and Connectivity Studio document for additional information.
ExecuteGIGAssociatedTaskAsynchronously If this property is True, GIG associated tasks will execute asynchronously. Id * Enter the attribute that contains the value used to uniquely identify the user account user ID on the connected system (ACCOUNT_ID column of the FISC_USER_ACCOUNT table).
loginId * Enter the attribute that contains the value used to uniquely identify the user account login ID (uniqueId) on the connected system (ACCOUNT_USERNAME column of the FISC_USER_ACCOUNT table). Notes:
* Id and loginId are used by the Provisioning Policy and IdentityHub features to populate the ACCOUNT_ID and ACCOUNT_USERNAME columns of the FISC_USER_ACCOUNT table of the Product database. See the ‘Provisioning Policy’ and ‘Provisioning Using the IdentityHub’ chapters of the Identity Suite Administration Guide for details.
Hover the pointer over a property to view its description.
- (Optional) Select the Attributes Only standard attributes display:
Modify schema attributes with the buttons. - (Optional) Select the Appearance tab to change how the Connected System object displays in the Design pane.
- Click OK to save any changes and return to the Workflow and Connectivity Studio window.
Configuring the Import Link
-
In the Design pane, double-click the import link between the Data Mapper object and the import object (the last workflow object). The Configure Link window displays:
Element Description Source Attributes Select the attributes to import.
Check for attribute-level auditing If auditing is enabled and these attributes below are checked, Provisioning will log all events for auditing purposes.
Selected Attributes Displays default attributes and those attributes that have been selected from the Source Attributes. Check the box of any attribute required for attribute-level auditing.
Format Displays the Format Date window to specify a date/time format to be applied to the selected date type attribute, for example, BirthDate. During import, the attribute's value is converted to the specified format.
Notes: The Format button is only enabled for date attributes.
Advanced Settings Displays the Configure Attributes window for selecting any attributes that need to be encrypted. Audit Key Select the attribute to associate with the Audit Key. - From the Attribute Selection tab, select attributes to impot.
- (Optional) Select the Appearance tab to change how the link displays in the Design pane.
- Click OK to save any changes and return to the Workflow and Connectivity Studio window.
- Deploy the workflow by selecting Deploy ► New Deployment.
See the Workflow and Connectivity Studio document for details of deployment options. - Manage and run the deployed workflow from the Admin UI ► Server tab.
See the Identity Suite Administration Guide for details.
Connector Details for Provisioning
The items in the MV (multi-valued) and Export columns have these meanings:
-
Y = Yes (attribute is supported for this operation)
-
N = No (attribute is not supported for this operation)
Worker Data Format
|
Name |
MV |
Export |
Import |
Description |
|
Basic Worker Attributes: These attributes can only be exported and cannot be modified. However, WorkerID is a manadatory attribute for all modify operations. WorkerID can be modified by passing the WorkerID and Original_WorkerID. UserID of a worker can be modified, but since it is an export only attribute, Account- UserName attribute is used to add/modify the userID of a worker. |
||||
|
WorkerID |
N |
Y |
Y |
Cannot be modified but mandatory for all modify operations. |
|
WorkerDescriptor |
N |
Y |
N |
|
|
WorkerType |
N |
Y |
N |
|
|
UserID |
N |
Y |
N |
|
|
Account Attributes: These attributes can be exported and imported. Workday account can be created and modified but cannot be deleted. Account.UserName is a mandatory attribute to add/modify any of these account attributes. When creating a new Workday Account, either Account.Password must have a value or Account.GenerateRandomPassword should be set to True. |
||||
|
Account.AllowMixedLanguageTransa ctions |
N |
Y |
Y |
|
|
Account.Disabled |
N |
Y |
Y |
|
|
Account.DisplayXMLIconOnReports |
N |
Y |
Y |
|
|
Account.EnableWorkbox |
N |
Y |
Y |
|
|
Account.ExemptFromDelegatedAuthe ntication |
N |
Y |
Y |
|
|
Account.ExpirationDate |
N |
Y |
Y |
|
|
Account.GenerateRandomPassword |
N |
N |
Y |
Mandatory for creating workday account if Account.Password does not have a value. |
|
Account.OneTimePasscodeExempt |
N |
Y |
Y |
|
|
Account.OneTimePasscodeGracePeri odEnabled |
N |
Y |
N |
|
|
Account.OneTimePasscodeGracePeri odLoginRemainingCount |
N |
Y |
N |
|
|
Account.OpenIDConnectInternalIdenti fier |
N |
Y |
Y |
|
|
Account.OpenIDIdentifier |
N |
Y |
Y |
|
|
Account.OpenIDInternalIdentifier |
N |
Y |
Y |
|
|
Account.Password |
N |
N |
Y |
Mandatory for creating workday account if Account.GenerateRandomPassword is not set to True. |
|
Account.RequireNewPasswordAtNext SignIn |
N |
Y |
Y |
|
|
Account.SessionTimeoutMinutes |
N |
Y |
Y |
|
|
Account.ShowUserNameInBrowserWi ndow |
N |
Y |
Y |
|
|
Account.UserName |
N |
Y |
Y |
Mandatory for creating/modifying workday account. |
|
Basic Personal Attributes: These attributes can be exported and imported. |
||||
|
PersonalData->AdditionalNationality |
N |
Y |
Y |
|
|
PersonalData->BirthCountry |
N |
Y |
Y |
|
|
PersonalData->BirthDate |
N |
Y |
Y |
|
|
PersonalData->CitizenshipStatus |
N |
Y |
Y |
|
|
PersonalData->CityOfBirth |
N |
Y |
Y |
|
|
PersonalData->DateOfDeath |
N |
Y |
Y |
|
|
PersonalData->Ethnicity |
N |
Y |
Y |
|
|
PersonalData->Gender |
N |
Y |
Y |
|
|
PersonalData->HispanicOrLatino |
N |
Y |
Y |
|
|
PersonalData->HukouLocality |
N |
Y |
Y |
|
|
PersonalData->HukouPostalCode |
N |
Y |
Y |
|
|
PersonalData->LastMedicalExamDate |
N |
Y |
Y |
|
|
PersonalData->LastMedicalExamValidTo |
N |
Y |
Y |
|
|
PersonalData->LocalHukou |
N |
Y |
Y |
|
|
PersonalData->MaritalStatus |
N |
Y |
Y |
|
|
PersonalData->MaritalStatusDate |
N |
Y |
Y |
|
|
PersonalData->MedicalExamNotes |
N |
Y |
Y |
|
|
PersonalData->NativeRegionDescriptor |
N |
Y |
N |
|
|
PersonalData->PersonnelFileAgency |
N |
Y |
Y |
|
|
PersonalData->PrimaryNationality |
N |
Y |
Y |
|
|
PersonalData->RegionOfBirthDescriptor |
N |
Y |
N |
|
|
PersonalData->TobaccoUse |
N |
Y |
Y |
|
|
Legal Name Attributes: These can be exported and imported. LegalName.FirstName, LegalName.LastName and LegalName.Country are mandatory attributes. Legal Name can be modified but cannot be deleted. |
||||
|
PersonalData->Names->LegalName.Country |
N |
Y |
Y |
|
|
PersonalData->Names->LegalName.FirstName |
N |
Y |
Y |
|
|
PersonalData->Names->LegalName.FormattedName |
N |
Y |
N |
|
|
PersonalData->Names-LegalName.FullNameForSingapore AndMalaysia |
N |
Y |
Y |
|
|
PersonalData->Names->LegalName.LastName |
N |
Y |
Y |
|
|
PersonalData->Names->LegalName.LocalFirstName |
N |
Y |
Y |
|
|
PersonalData->Names->LegalName.LocalFirstName2 |
N |
Y |
Y |
|
|
PersonalData->Names->LegalName.LocalLastName |
N |
Y |
Y |
|
|
PersonalData->Names->LegalName.LocalLastName2 |
N |
Y |
Y |
|
|
PersonalData->Names->LegalName.LocalLocalName |
N |
Y |
Y |
|
|
PersonalData->Names->LegalName.LocalLocalScript |
N |
Y |
N |
|
|
PersonalData->Names->LegalName.LocalMiddleName |
N |
Y |
Y |
|
|
PersonalData->Names->LegalName.LocalMiddleName2 |
N |
Y |
Y |
|
|
PersonalData->Names- >LegalName.LocalSecondaryLastNa me |
N |
Y |
Y |
|
|
PersonalData->Names- >LegalName.LocalSecondaryLastNa me2 |
N |
Y |
Y |
|
|
PersonalData->Names- >LegalName.MiddleName |
N |
Y |
Y |
|
|
PersonalData->Names- >LegalName.PrefixDescriptor |
N |
Y |
N |
|
|
PersonalData->Names- >LegalName.PrefixValue |
N |
Y |
Y |
|
|
PersonalData->Names- >LegalName.ReportingName |
N |
Y |
N |
|
|
PersonalData->Names- >LegalName.SecondaryLastName |
N |
Y |
Y |
|
|
PersonalData->Names- >LegalName.SuffixDescriptor |
N |
Y |
N |
|
|
PersonalData->Names- >LegalName.SuffixValue |
N |
Y |
Y |
|
|
Preferred Name Attributes: These can be exported and imported. PreferredName.FirstName, PreferredName.LastName and PreferredName.Country are mandatory attributes. Preferred Name can be modified but cannot be deleted. |
||||
|
PersonalData->Names- >PreferredName.Country |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.FirstName |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.FormattedName |
N |
Y |
N |
|
|
PersonalData->Names-> PreferredName.FullNameForSingapor eAndMalaysia |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.LastName |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.LocalFirstName |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.LocalFirstName2 |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.LocalLastName |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.LocalLastName2 |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.LocalLocalScript |
N |
Y |
N |
|
|
PersonalData->Names-> PreferredName.LocalMiddleName |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.LocalMiddleName2 |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.LocalName |
N |
Y |
N |
|
|
PersonalData->Names-> PreferredName.LocalSecondaryLastN ame |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.LocalSecondaryLastN ame2 |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.MiddleName |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.PrefixDescriptor |
N |
Y |
N |
|
|
PersonalData->Names-> PreferredName.PrefixValue |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.ReportingName |
N |
Y |
N |
|
|
PersonalData->Names-> PreferredName.SecondaryLastName |
N |
Y |
Y |
|
|
PersonalData->Names-> PreferredName.SuffixDescriptor |
N |
Y |
N |
|
|
PersonalData->Names-> PreferredName.SuffixValue |
N |
Y |
Y |
|
|
Additional Name Attributes: These can be exported and imported. There can be multiple Additional Names for a worker. Additional Names can be created, modified and deleted. FirstName, LastName, NameType and Country are mandatory attributes for an additional name. |
||||
|
PersonalData->Names- >AdditionalName |
Y |
|
|
|
|
PersonalData->Names- >AdditionalName->Country |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName->FirstName |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName->FormattedName |
N |
Y |
N |
|
|
PersonalData->Names-> AdditionalName- >FullNameForSingaporeAndMalaysia |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName->LastName |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName->LocalFirstName |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName->LocalFirstName2 |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName-LocalLastName |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName->LocalLastName2 |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName->LocalLocalScript |
N |
Y |
N |
|
|
PersonalData->Names-> AdditionalName->LocalMiddleName |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName->LocalMiddleName2 |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName->LocalName |
N |
Y |
N |
|
|
PersonalData->Names-> AdditionalName- >LocalSecondaryLastName |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName- >LocalSecondaryLastName2 |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName->MiddleName |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName->NameType |
N |
Y |
Y |
|
|
PersonalData->Names-> AdditionalName->ReportingName |
N |
Y |
N |
|
|
PersonalData->Names-> AdditionalName- >SecondaryLastName |
N |
Y |
Y |
|
|
Other ID Attributes: These can be exported and imported. A worker can have multiple Other IDs. ID and IDType are mandatory attributes for Other ID. |
||||
|
PersonalData->IDs->OtherID |
Y |
|
|
|
|
PersonalData->IDs->OtherID- >CustomDescription |
N |
Y |
Y |
|
|
PersonalData->IDs->OtherID- >ExpirationDate |
N |
Y |
Y |
|
|
PersonalData->IDs->OtherID->ID |
N |
Y |
Y |
|
|
PersonalData->IDs->OtherID- >IDType |
N |
Y |
Y |
|
|
PersonalData->IDs->OtherID- >IssuedDate |
N |
Y |
Y |
|
|
PersonalData->IDs->OtherID- >Organization |
N |
Y |
Y |
|
|
ContactData Attributes: This consists of Address, Email, Phone and WebAddress attributes. |
||||
|
PersonalData->ContactData- >EffectiveDate |
N |
N |
Y |
|
|
ContactData->Address Attributes: These can be exported and imported. There can be multiple Home/Work address. Primary Home/Work Address cannot be deleted but can be modified. |
||||
|
PersonalData->ContactData- >Address |
Y |
|
|
|
|
PersonalData->ContactData- >Address->AddressFormatType |
N |
Y |
N |
|
|
PersonalData->ContactData- >Address->AddressID |
N |
Y |
Y |
|
|
PersonalData->ContactData- >Address->AddressLine |
N |
Y |
Y |
|
|
PersonalData->ContactData- >Address->Country |
N |
Y |
Y |
|
|
PersonalData->ContactData- >Address->CountryRegion |
N |
Y |
Y |
|
|
PersonalData->ContactData- >Address->CountryRegionDescriptor |
N |
Y |
N |
|
|
PersonalData->ContactData- >Address- >DefaultedBusinessSiteAddress |
N |
Y |
Y |
|
|
PersonalData->ContactData- >Address->EffectiveDate |
N |
Y |
Y |
|
|
PersonalData->ContactData- >Address->FormattedAddress |
N |
Y |
N |
|
|
PersonalData->ContactData- >Address->LastModified |
N |
Y |
Y |
|
|
PersonalData->ContactData- >Address->Municipality |
N |
Y |
Y |
|
|
PersonalData->ContactData- >Address->MunicipalityLocal |
N |
Y |
Y |
|
|
PersonalData->ContactData- >Address->PostalCode |
N |
Y |
Y |
|
|
PersonalData->ContactData- >Address->Public |
N |
Y |
Y |
|
|
PersonalData->ContactData- >Address->Usage |
N |
Y |
Y |
|
|
PersonalData->ContactData- >Address->Usage.Primary |
N |
Y |
Y |
|
|
ContactData->Email Attributes: These can be exported and imported. There can be multiple Home/Work Email. Primary Home/Work Email cannot be deleted but can be modified. Secondary Home/Work Email can be deleted if at least one is retained. |
||||
|
PersonalData->ContactData->Email |
Y |
|
|
|
|
PersonalData->ContactData->Email- >EmailAddress |
N |
Y |
Y |
|
|
PersonalData->ContactData->Email- >Public |
N |
Y |
Y |
|
|
PersonalData->ContactData->Email- >Usage |
N |
Y |
Y |
|
|
PersonalData->ContactData->Email- >Usage.Primary |
N |
Y |
Y |
|
|
ConatactData->Phone Attributes: These can be exported and imported. There can be multiple Home/Work Phone. Primary Home/Work Phone cannot be deleted but can be modified. Secondary Home/Work Phone can be deleted if at least one is retained. |
||||
|
PersonalData->ContactData->Phone |
Y |
|
|
|
|
PersonalData->ContactData->Phone- >AreaCode |
N |
Y |
Y |
|
|
PersonalData->ContactData->Phone- >CountryISOCode |
N |
Y |
Y |
|
|
PersonalData->ContactData->Phone- >DeviceType |
N |
Y |
Y |
|
|
PersonalData->ContactData->Phone- >FormattedPhone |
N |
Y |
N |
|
|
PersonalData->ContactData->Phone- >InternationalPhoneCode |
N |
Y |
Y |
|
|
PersonalData->ContactData->Phone- >PhoneExtension |
N |
Y |
Y |
|
|
PersonalData->ContactData->Phone- >PhoneNumber |
N |
Y |
Y |
|
|
PersonalData->ContactData->Phone- >Public |
N |
Y |
Y |
|
|
PersonalData->ContactData->Phone- >Usage |
N |
Y |
Y |
|
|
PersonalData->ContactData->Phone- >Usage.Primary |
N |
Y |
Y |
|
|
ContactData->WebAddress Attributes: These can be exported and imported. There can be multiple Home/ Work WebAddress. Primary Home/Work WebAddress cannot be deleted but can be modified. Secondary Home/Work WebAddress can be deleted if at least one is retained. |
||||
|
PersonalData->ContactData- >WebAddress |
Y |
|
|
|
|
PersonalData->ContactData- >WebAddress->Public |
N |
Y |
Y |
|
|
PersonalData->ContactData- >WebAddress->Usage |
N |
Y |
Y |
|
|
PersonalData->ContactData- >WebAddress->Usage.Primary |
N |
Y |
Y |
|
|
PersonalData->ContactData- >WebAddress->WebAddress |
N |
Y |
Y |
|
|
JobData Attributes: These can only be exported. |
||||
|
JobData- >Worker.AcademicTenureDate |
N |
Y |
N |
|
|
JobData->Worker.Active |
N |
Y |
N |
|
|
JobData->Worker.ActiveStatusDate |
N |
Y |
N |
|
|
JobData- >Worker.BenefitsServiceDate |
N |
Y |
N |
|
|
JobData- >Worker.CompanyServiceDate |
N |
Y |
N |
|
|
JobData- >Worker.ContinuousServiceDate |
N |
Y |
N |
|
|
JobData- >Worker.DateEnteredWorkforce |
N |
Y |
N |
|
|
JobData- >Worker.EndEmploymentDate |
N |
Y |
N |
|
|
JobData- >Worker.ExpectedDateOfReturn |
N |
Y |
N |
|
|
JobData- >Worker.ExpectedRetirementDate |
N |
Y |
N |
|
|
JobData->Worker.FirstDayOfWork |
N |
Y |
N |
|
|
JobData->Worker.HireDate |
N |
Y |
N |
|
|
JobData->Worker.HireReason |
N |
Y |
N |
|
|
JobData- >Worker.LastDateForWhichPaid |
N |
Y |
N |
|
|
JobData- >Worker.LocalTerminationReason |
N |
Y |
N |
|
|
JobData->Worker.NotEligibleForHire |
N |
Y |
N |
|
|
JobData- >Worker.NotEligibleForRehire |
N |
Y |
N |
|
|
JobData->Worker.NotReturning |
N |
Y |
N |
|
|
JobData->Worker.OriginalHireDate |
N |
Y |
N |
|
|
JobData->Worker.PayThroughDate |
N |
Y |
N |
|
|
JobData- >Worker.PrimaryTerminationCategory |
N |
Y |
N |
|
|
JobData- >Worker.PrimaryTerminationReason |
N |
Y |
N |
|
|
JobData->Worker.ProbationEndDate |
N |
Y |
N |
|
|
JobData->Worker.ProbationStartDate |
N |
Y |
N |
|
|
JobData- >Worker.RegrettableTermination |
N |
Y |
N |
|
|
JobData->Worker.Rehire |
N |
Y |
N |
|
|
JobData->Worker.ResignationDate |
N |
Y |
N |
|
|
JobData->Worker.Retired |
N |
Y |
N |
|
|
JobData->Worker.RetirementDate |
N |
Y |
N |
|
|
JobData- >Worker.RetirementEligibilityDate |
N |
Y |
N |
|
|
JobData->Worker.ReturnUnknown |
N |
Y |
N |
|
|
JobData->Worker.SeniorityDate |
N |
Y |
N |
|
|
JobData->Worker.SeveranceDate |
N |
Y |
N |
|
|
JobData->Worker.Terminated |
N |
Y |
N |
|
|
JobData->Worker.TerminationDate |
N |
Y |
N |
|
|
JobData- >Worker.TerminationInvoluntary |
N |
Y |
N |
|
|
JobData- >Worker.TerminationLastDayOfWork |
N |
Y |
N |
|
|
JobData- >Worker.TimeOffServiceDate |
N |
Y |
N |
|
|
JobData->Worker.VestingDate |
N |
Y |
N |
|
|
JobData->WorkerContract |
|
|
|
|
|
JobData->WorkerContract- >ContractAssignmentDetails |
N |
Y |
N |
|
|
JobData->WorkerContract- >ContractEndDate |
N |
Y |
N |
|
|
JobData->WorkerContract->Currency |
N |
Y |
N |
|
|
JobData->WorkerContract- >Frequency |
N |
Y |
N |
|
|
JobData->WorkerContract->Supplier |
N |
Y |
N |
|
|
JobData->WorkerJob |
|
|
|
|
|
JobData->WorkerJob->Location |
|
|
|
|
|
JobData->WorkerJob->Location- >Address.AddressFormatType |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Address.AddressID |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Address.CountryRegionDescriptor |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Address.DefaultedBusinessSiteAddr ess |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Address.Delete |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Address.DoNotReplaceAll |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Address.EffectiveDate |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Address.FormattedAddress |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Address.LastModified |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Address.Municipality |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Address.MunicipalityLocal |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Address.PostalCode |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Location |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >Name |
N |
Y |
N |
|
|
JobData->WorkerJob->Location- >TimeProfile |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.BusinessTitle |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.CriticalJob |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.EffectiveDate |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.EndDate |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.EndEmploymentDate |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.ExcludeFromHeadcount |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.FederalWithholdingFEIN |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.JobExempt |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.JobFamily |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.JobFamilyGroup |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.JobFamilyName |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.JobProfileName |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.ManagerID |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.PayThroughDate |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.PositionID |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.PositionTimeType |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.PositionTitle |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.StartDate |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.WorkerHoursProfileClassific ation |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.WorkerType |
N |
Y |
N |
|
|
JobData->WorkerJob- >Position.WorkShiftRequired |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionManager |
Y |
|
|
This data will be available for primary and secondary jobs. The mangers to be returned can be controlled by the export configuration property, IncludeEntireChainOfPostionManagers. If the property is TRUE, all managers in the manager chain is returned. If the property is FALSE, only the immediate manager data is returned. |
|
JobData- >WorkerJob>PositionManager-> ManagerDescriptor |
N |
Y |
N |
|
|
JobData->WorkerJob-> PositionManager->ManagerID |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionManager->Organization |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionOrganization |
Y |
|
|
|
|
JobData->WorkerJob- >PositionOrganization- >DateOfPayGroupAssignment |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionOrganization- >OrganizationCode |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionOrganization- >OrganizationName |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionOrganization- >OrganizationReferenceID |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionOrganization- >OrganizationSubtype |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionOrganization- >OrganizationSupportRole |
Y |
|
|
|
|
JobData->WorkerJob- >PositionOrganization- >OrganizationSupportRole- >OrganizationRole |
Y |
|
|
|
|
JobData->WorkerJob- >PositionOrganization- >OrganizationSupportRole- >OrganizationRole->AssignmentFrom |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionOrganization- >OrganizationSupportRole- >OrganizationRole->Worker |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionOrganization- >OrganizationSupportRole- >OrganizationRoleID |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionOrganization- >OrganizationType |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionOrganization- >PrimaryBusinessSite |
N |
Y |
N |
|
|
JobData->WorkerJob- >PositionOrganization- >UsedInChangeOrganizationAssignm ents |
N |
Y |
N |
|
|
JobData->WorkerJob->PrimaryJob |
N |
Y |
N |
|
|
JobData->WorkerStatus- >SecondaryTerminationReason |
N |
Y |
N |
|
|
JobData->WorkerStatus- >SecondaryTerminationReasonCateg ory |
N |
Y |
N |
|
|
OrganizationData Attributes: These can only be exported. |
||||
|
OrganizationData |
Y |
|
|
|
|
OrganizationData->AssignableRole |
N |
Y |
N |
|
|
OrganizationData->OrganizationCode |
N |
Y |
N |
|
|
OrganizationData- >OrganizationName |
N |
Y |
N |
|
|
OrganizationData- >OrganizationReferenceID |
N |
Y |
N |
|
|
OrganizationData- >OrganizationSubtype |
N |
Y |
N |
|
|
OrganizationData->OrganizationType |
N |
Y |
N |
|
|
EmployeeContracts Attributes: These can only be exported. |
||||
|
EmployeeContracts |
|
|
|
|
|
EmployeeContracts- >ContractDescription |
N |
Y |
N |
|
|
EmployeeContracts- >ContractEndDate |
N |
Y |
N |
|
|
EmployeeContracts->ContractID |
N |
Y |
N |
|
|
EmployeeContracts- >ContractStartDate |
N |
Y |
N |
|
|
EmployeeContracts->ContractStatus |
N |
Y |
N |
|
|
EmployeeContracts->ContractType |
N |
Y |
N |
|
|
EmployeeContracts- >ContractVersionDate |
N |
Y |
N |
|
|
EmployeeContracts- >DateEmployeeSigned |
N |
Y |
N |
|
|
EmployeeContracts- >DateEmployerSigned |
N |
Y |
N |
|
|
EmployeeContracts- >EmployeeContract |
N |
Y |
N |
|
|
EmployeeContracts- >EmployeeContractCollectiveAgreem ent |
N |
Y |
N |
|
|
EmployeeContracts- >EmployeeContractID |
N |
Y |
N |
|
|
EmployeeContracts- >EmployeeContractReason |
N |
Y |
N |
|
|
EmployeeContracts->Position |
N |
Y |
N |
|
|
EmployeeContracts- >WorkerDocument |
N |
Y |
N |
|
|
IntegrationOverrideField Attributes: These can only be exported. |
||||
|
IntegrationOverrideField->Value |
N |
Y |
N |
|
|
IntegrationOverrideField->FieldIdType |
N |
Y |
N |
|
|
IntegrationOverrideField- >FieldIdValue |
N |
Y |
N |
|
|
IntegrationOverrideField- >FieldIdParentId |
N |
Y |
N |
|
|
IntegrationOverrideField- >FieldIdParentType |
N |
Y |
N |
|
WorkerFromTransactionLogs Data Format
This data format supports the same attributes as that of Worker data format.
Reference Data Format
| Name | MV | Export | Import |
| ReferenceDescriptor | N | Y | N |
| ReferenceID | N | Y | N |
Report Data Format
This data format supports attributes based on the configured and enabled reports in the ReportConfiguration Export parameter.
Lookup Data
To filter data, use the Data Mapper rule Lookup Data.
- Log in to the Workflow and Connectivity Studio and double-click the Data Mapper object on the Design pane. The Configure Data Mapper window displays.
- Select the Lookup Data rule under the Mapping Rule column, and then click the Source Value. The Configure Lookup window displays.
- Select the Workday system from the Select System drop-down list:
- In the Enter Lookup Prefix field, enter the prefix to be added to the Lookup fields.
- Select the Lookup Type from the drop-down list, Worker, Reference or Report.
- For Worker lookup, select Worker By ID or Worker By Filter option.
- For Worker By ID lookup, click the Worker ID Pick button to select the Worker ID input attribute and click OK.
- For Worker By Filter lookup, click the Build button along the Filter and build a filter to use for lookup and click OK.
- For Worker By ID lookup, click the Worker ID Pick button to select the Worker ID input attribute and click OK.
- For Reference lookup, select a Reference Type from the dropdown list.
- Click the Fields Pick button to select the attributes to be fetched after a successful lookup.
- Use Advanced Settings button to configure additional settings required for lookup. For report lookup, use ReportConfiguration parameter to configure the reports. See Report Configuration to configure reports. Once the reports are configured, click the Fields Pick button to select the report attributes to be fetched.
- Select the Exit as Mapper Task Failed on Lookup Failure check box to exit the task with Failed status on lookup failure. It will not process the succeeding entries and will ignore the already processed entries and will not return any data. This is selected by default.
- Click OK.