Integrations: Integration System User (ISU)

7 Steps to create and Assign ISU to the Integrations

Integration Security Users also popularly known as ISU are used to assign the integration Worker Account. (It is created in majority of the cases for your vendors / third party systems)

Here are the 7 Steps to Create and Assign your ISU's to the Integrations.

1. Create Integration System User (ISU)

2. Create Security Group - Integration System Security Group (ISSG)

3. Assign the Integration System User to Security Group ( ISU --> ISSG )

4. Find out the list of all domains required for the particular template in WD Community 

5. Assign Newly created security group to all the domains (ISSG --> Domains)

6. Activate pending security policy Changes

7. Assign the Integration System User to the Integration - (Related actions > Workday Account > Assign ISU)

Security: Create Audit Log - Report

Create Audit Log - Report

To Identify:

Which all transactions were done by a user (Workday Account) in the said duration?

Who ran the transaction like Task, BP in the said duration ? 

You can make use of Create Audit Log report to generate one.

Input your details: Be cautious while choosing the From and To Moment, try to give a lesser duration to get the results faster. If it is a lengthier duration, Workday will throw an error.

Provide the workday account you are auditing for and also a specific task if any. 

Notice that it will take you to the Create Audit Log - Background Process.

Click on the generated xls report to see the transactions based out of the input given while running Credit Audit Log report.

Integrations: List of Packaged / Core Connector Templates

Integration Template Catalog

Use this report to see what are the delivered Packaged Connectors and Core Connectors. This report helps you in making out which template you want to use based on the requirement.

Look at the sample, Kronos Employee Extract Template.

Also click on the View Details to see the Integration Services, Attributes and Maps. This let you see these details before you head start with the selected / identified template.

Integrations: Workday xml vs Simple xml

Workday xml vs Simple xml

There is a difference between Workday XML and Simple XML. Let us understand with a generated report.

 Here is the sample report for 3 EEs. 

We are selecting 6 fields. Shown below are the field types.

Employee ID    - Text

Worker             - BO (Single Instance)

First Name        - Text

Gender              - BO (Single Instance)

Marital_status  - BO (Single Instance)

Age                     - Numeric

Navigation to generate XML -  (Make sure firstly your report is a RaaS Report)

Go to Your Report >> Related Actions >> Web Services >> View URL's

When you generate your xml's , Notice below:

In Simple XML all fields are just fields, it do not differentiate where as in Workday XML notice that the WID's and reference id type show up for each instance related fields ( Single Instance / Multi - Instance).

We can say that, when you run the report and see the related actions on any of the column values, then that is likely to give you WID and reference id type.

Simple XML:

<wd:Report_Data xmlns:wd="urn:com.workday.report/pb_Advanced_Report">

<wd:Report_Entry>

<wd:Employee_ID>1234</wd:Employee_ID>

<wd:Worker>Aidan Mitzner</wd:Worker>

<wd:FirstName>Aidan</wd:FirstName>

<wd:Gender>Male</wd:Gender>

<wd:Marital_Status>Single (United States of America)</wd:Marital_Status>

<wd:Age>48</wd:Age>

</wd:Report_Entry>

<wd:Report_Entry>

<wd:Employee_ID>1235</wd:Employee_ID>

<wd:Worker>Wesley Kingston</wd:Worker>

<wd:FirstName>Wesley</wd:FirstName>

<wd:Gender>Male</wd:Gender>

<wd:Marital_Status>Single (United States of America)</wd:Marital_Status>

<wd:Age>31</wd:Age>

</wd:Report_Entry>

<wd:Report_Entry>

<wd:Employee_ID>1236</wd:Employee_ID>

<wd:Worker>Xaviere Francois</wd:Worker>

<wd:FirstName>Xaviere</wd:FirstName>

<wd:Gender>Female</wd:Gender>

<wd:Marital_Status>Free Union (France)</wd:Marital_Status>

<wd:Age>42</wd:Age>

</wd:Report_Entry>

</wd:Report_Data>

Workday XML:

<wd:Report_Data xmlns:wd="urn:com.workday.report/pb_Advanced_Report">

<wd:Report_Entry>

<wd:Employee_ID>1234</wd:Employee_ID>

<wd:Worker wd:Descriptor="Aidan Mitzner">

<wd:ID wd:type="WID">12831f1b82954a3a0ad85fb85367</wd:ID>

<wd:ID wd:type="Employee_ID">1234</wd:ID>

</wd:Worker>

<wd:FirstName>Aidan</wd:FirstName>

<wd:Gender wd:Descriptor="Male">

<wd:ID wd:type="WID">d3afbf8074e54970962128e1105a</wd:ID>

<wd:ID wd:type="Gender_Code">Male</wd:ID>

</wd:Gender>

<wd:Marital_Status wd:Descriptor="Single (United States of America)">

<wd:ID wd:type="WID">5e50cb12452487de0caf7f262d4f</wd:ID>

<wd:ID wd:type="Marital_Status_ID">Single_USA</wd:ID>

</wd:Marital_Status>

<wd:Age>48</wd:Age>

</wd:Report_Entry>

<wd:Report_Entry>

<wd:Employee_ID>1235</wd:Employee_ID>

<wd:Worker wd:Descriptor="Wesley Kingston">

<wd:ID wd:type="WID">480fa11010d6501bfc3dad351f1d</wd:ID>

<wd:ID wd:type="Employee_ID">1235</wd:ID>

</wd:Worker>

<wd:FirstName>Wesley</wd:FirstName>

<wd:Gender wd:Descriptor="Male">

<wd:ID wd:type="WID">bf8074e549ffb070962128e1105a</wd:ID>

<wd:ID wd:type="Gender_Code">Male</wd:ID>

</wd:Gender>

<wd:Marital_Status wd:Descriptor="Single (United States of America)">

<wd:ID wd:type="WID">5e50cb12452487de0caf7f262d4f</wd:ID>

<wd:ID wd:type="Marital_Status_ID">Single_USA</wd:ID>

</wd:Marital_Status>

<wd:Age>31</wd:Age>

</wd:Report_Entry>

<wd:Report_Entry>

<wd:Employee_ID>1236</wd:Employee_ID>

<wd:Worker wd:Descriptor="Xaviere Francois">

<wd:ID wd:type="WID">b31600011066de010d5410b714d0</wd:ID>

<wd:ID wd:type="Employee_ID">1236</wd:ID>

</wd:Worker>

<wd:FirstName>Xaviere</wd:FirstName>

<wd:Gender wd:Descriptor="Female">

<wd:ID wd:type="WID">3bec2d0d420283f76f51b928d885</wd:ID>

<wd:ID wd:type="Gender_Code">Female</wd:ID>

</wd:Gender>

<wd:Marital_Status wd:Descriptor="Free Union (France)">

<wd:ID wd:type="WID">f0f5d5eb405b9ffa48755d4d8b41</wd:ID>

<wd:ID wd:type="Marital_Status_ID">Free_Union_France</wd:ID>

<wd:ID wd:type="Marital_Status_Code" wd:parent_type="WID" wd:parent_id="6971ffb4bf0b116fe7651ec789a">UNIFRA</wd:ID>

</wd:Marital_Status>

<wd:Age>42</wd:Age>

</wd:Report_Entry>

</wd:Report_Data>

Security: View Security for Securable Item

View Security for Securable Item

Often, we rely on Functional areas, Domains to see how your task or report is secured. Consider this task if you have access to.

This is a great task to identify the security of any delivered items like tasks or reports or data sources. Let us take a sample task - Create Position. (This is just like your workday wild search)

The next screen as below shows the list of tasks and reports that you can check the security.

Click on View Security to view the list of Security Groups allowed and the Functional area the task or report belongs to. Additionally you can see the Menu / Navigation.