Thursday, June 4

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>

Monday, June 1

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.


Wednesday, May 27

Security: Session Time out minutes


Edit Workday Account - Task allows you to set the Session Timeout Minutes Enforced for an individual user.

How ever, some times even though you enforced  it takes a default of 15 min or asks you to key in between 5 min to 20 min. The one possible reason for this is that you being a Security Administrator, you might have added all the user based security groups to your id [Assign User-Based Security Groups for Person].  There is a security group which restricts this mostly - Credit card Administrator.

Workday Account session time out
Which ever security groups have access to the Domain - Manage: Credit Card Data will not have more than 15 min of time out minutes, you can not override beyond the limit.

Remove this Security Groups if you are not using really then you should be comfortably override this.

Tuesday, May 26

Reporting: Not able to choose or create calc fields which are non-indexed

Reporting: Not able to choose or create calc fields which are non-indexed


If you are not able to create any calculated fields or use some of your fields in your report to filter it is because of the Data source that was selected is indexed.

Go to Advanced Tab, 


Report Performance >>  Optimized for Performance - Un-check the checkbox so that it allows you to use non-indexed fields on your report for filtering or create calculated fields

Remember that this could impact the performance of the report.

Thursday, May 21

Integrations: Notifications Sample

Integrations- Notifications Sample

We use Notifications on the scheduled Integrations specially to monitor if there is any abnormal behavior like the process getting aborted or failed or other below reasons. Once you set up the notification you can receive an email with the configured message.

Most commonly used Integration Statuses in Production are:

Aborted

Completed

Completed with Errors

Failed

Not Run due to Exceptions on Future Process


Some of the Fields that you can use on Notification while building your message:

 

  • Integration System
  • Integration Event
  • Integration Event Status
  • Integration Attachment
  • Created from Integration Process Event


Sample Email:  Try to build with the below sample. Using Text and External Fields (Bold) 


Subject:

 

Integration System : Integration Event Status

 

Body: 

 

Integration System is Integration Event Status

 

Line break

 

Integration Event URL is Integration Event

 

Line Break