Workday Catch Up Behavior - Scheduling Reports / Integrations

Workday Catch Up Behavior - Scheduling Reports / Integrations

Catch Up Behavior - Scheduling

While scheduling the Reports or Integrations, you will come across Catch Up Behavior field which is mandatory. Using the Catch Up Behavior option enables you to limit how many times processes run after maintenance issues cause errors. 

During the maintenance window / Unplanned outage, if your reports or integrations were supposed to be running as per the schedule during that time you will use Catch up Behavior selection to tell what you want to do on the missed recurrences.

You will see the below options available. First time scheduling you will only see (Run Once and None)

Run Once  - Selecting this option will Catch Up one time if it missed.

None         -  Selecting this option will NOT Catch Up at all even though it missed.

Legacy      -  Selecting this option will Catch Up the old /earlier expired ones. This is going to be deprecated in the future. 

[Don't get panic if you don't see this now]

Example: If you schedule a process to run multiple times in a day when your environment is down for maintenance, you can limit the process to run once instead of catching up all missed occurrences.

Steps to Enable Report as Web Service

Steps to Enable Report as Web Service

When to use report as web server ?

-You can use the web service enabled report in an Outbound EIB.

-It can be used by an External web site if you enable your report as web service.

Note:

Only ADVANCED and SEARCH Report types allows you to make your report Web service enabled.

You can also set up Web Services Options on the Advanced tab of the report definition.

How to create a custom reports ?

How to create a custom reports ?

Workday allows you to create Custom Reports. There are variety of reports that you can create.

Task: "Create Custom Report"

There are 8 different reports that you can create depending on the need of the reporting.

-Simple

-Advanced

-Matrix

-Search

-nBox

-Composite

-Transposed

-Trending

Up on the Report Type selection, dynamically some more fields will show up. 

Compensation Tasks and Reports

Compensation Tasks and Reports

Here are some of the commonly used Compensation related Tasks and Reports:

Compensation Eligibility Rules

View Compensation Eligibility Rule (also Create, Edit)

Create Compensation Grade (Edit)

Edit Compensation Grade Profile (View)

Compensation Package

Compensation Packages

Create Compensation Package (Edit)

Create Hourly Plan

Create One-Time Payment Plan

Create Salary Plan

Create Allowance Plan

Create Commission Plan

Compensation Steps

Compensation Rule Assignment

Employee Compensation Audit

Compensation Spreadsheet

Compensation Changes Report

Maintain Compensation Elements

Compensation Elements

Maintain Compensation Element Groups

Compensation Element Groups

Total Compensation

Total Compensation Template Audit

Compensation Summary

Employee Compensation Details by Job Profile

In Progress Compensation Changes

Out of Order Compensation Changes

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.

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>