2020 Release 2 In Preview Tenants

 2020 R2 - Available In Preview Tenants

With around 300 new or enhanced features Workday geared up for the new 2020 Release 2. As you all know we have two releases every year, its the version change (upgrade) of Workday in the second half of this year too. This is the second release in this year, the last one was in the month of March 2020 [2020 R1].

The preview tenants will get the version change one month prior to the release in Production. On the 8th of August 2020 we got the Preview tenants (Sandbox Preview and Implementation Preview) upgraded with the latest version i.e. 2020 R2. 

Here are some details regarding the Release. 

Aug  8,  2020 - Features available for Preview (Sandbox Preview, Implementation Preview)

Sep 12,  2020 - 2020 R2 available in all tenants (PROD, Sandbox, Implementation also)

Workday Data Centers - Workday Tenants

Here are the Sandbox Preview URLs that you can pick to login according to your organizations data centers.. Make sure you give your tenant name:

Atlanta:   impl.workday.com/<tenantname_preview>/login.htmld

Portland: wd5-impl.workday.com/<tenantname_preview>/login.htmld

WD3:       wd3-impl.workday.com/ <tenantname_preview> /login.htmld

WD10:     impl.wd10.myworkday.com/ <tenantname_preview> /login.htmld

WD12:     impl.wd12.myworkday.com/ <tenantname_preview> /login.htmld

WD102:   impl.wd102.myworkday.com/<tenantname_preview>/login.htmld

Access  the below Standard reports to see the new features and enhancements.

What's new in Workday

What's new in Last 7 days

What's new in Last 6 Months

What's new in Workday Data Sources

What's new in Workday Report Fields

What's new in Workday Reports

Report: All Reports and Tasks - Report Definition

All Reports and Tasks in the Tenant

I got requests from some people as how to access all the reports and tasks in the tenant. Here is the post which gives you the report definition to access all the reports, tasks and their related domains.

You need to know how to Create Custom Report to build a report and see the results.

         👇 Click below to download the attachment 

                                               All Tasks and Reports - Report Definition

General: How to turn off emails while testing in Non-Production Tenants?

While Testing in Non-Production turn off your emails

When you are testing in Non-Production Tenants like Sandbox, Implementations, be cautious and make sure you turn off your email notifications or route it to you,  else you would be spamming and creating unnecessary emails in your organization.

Testing represents, which ever changes / enhancements involves in sending email notifications to your Employees, Managers or any security groups.

Access the task - Edit Tenant Setup - Notifications to set up this restrictions.

Restrictions: 

1. Disable All Emails - No Emails will be generated.

2. Redirect All Emails to Contact - To a single contact in your tenant all the mails will be sent.

3. Redirect All Emails to Email Address - To a single emails address all the emails will be sent.

OMS Environment Selected for Restriction - Choose if you want to include / exclude any tenant here in this setup.

Integrations: XML to XSL Coding - Sample 2

XML to XSL Sample Coding - Having reference ID's

Here is another sample coding of xml to xsl. This highlights as how to handle some fields having reference ID related information especially you see this in Workday XML vs Simple XML.

Notice the highlighted Workday XML code for the field Gender. If you compare with other fields like Age or Employee_ID , this field (Gender) is showing up additional information like wd:type and so on. Understand that this is nothing but the object related information. Read this to understand more about reference ID's Reference ID's Explained

Workday XML Sample:

<?xml version="1.0" encoding="UTF-8"?>

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

  <wd:Report_Entry>

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

    <wd:firstName>Steve</wd:firstName>

    <wd:lastName>Morgan</wd:lastName>

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

<wd:ID wd:type="WID">98juht8074e54970962128e1105a</wd:ID>

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

</wd:Gender>

    <wd:Age>56</wd:Age>

  </wd:Report_Entry>

  <wd:Report_Entry>

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

    <wd:firstName>Logan</wd:firstName>

    <wd:lastName>McNeil</wd:lastName>

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

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

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

</wd:Gender>

    <wd:Age>40</wd:Age>

  </wd:Report_Entry>

  <wd:Report_Entry>

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

    <wd:firstName>Joy</wd:firstName>

    <wd:lastName>Banks</wd:lastName>

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

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

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

</wd:Gender>

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

  </wd:Report_Entry>

</wd:Report_Data>

Use the Below highlighted code to access the information which is of type BO.

XSL Sample:

<?xml version="1.0" encoding="UTF-8"?>

<xsl:stylesheet xmlns:xsl="http://www.w3.org/1999/XSL/Transform"

   xmlns:wd="urn:com.workday.report/WD_Sample_Report" version="2.0">

<xsl:output method="text" indent="no"/>

<xsl:strip-space elements="*"/>

<xsl:variable name="NEWLINE" select="'&#xa;'"/>

<xsl:variable name="PIPE" select="'|'"/>

<xsl:template match="/">

    <!-- Header Record --> 

    <xsl:text>Employee ID</xsl:text>

        <xsl:value-of select="$PIPE"/>

<xsl:text>First Name</xsl:text>

        <xsl:value-of select="$PIPE"/>

<xsl:text>Last Name</xsl:text>

        <xsl:value-of select="$PIPE"/>

<xsl:text>Gender</xsl:text>

        <xsl:value-of select="$PIPE"/>

<xsl:text>Age</xsl:text>

<xsl:value-of select="$NEWLINE"/> 

<xsl:for-each select="wd:Report_Data/wd:Report_Entry">

    <!-- Detail Record --> 

        <xsl:value-of select="wd:Employee_ID"/>

                <xsl:value-of select="$PIPE"/>

    <xsl:value-of select="wd:firstName"/>

                <xsl:value-of select="$PIPE"/>

    <xsl:value-of select="wd:lastName"/>

        <xsl:value-of select="$PIPE"/>

    <xsl:value-of select="wd:Gender/@wd:Descriptor"/>

        <xsl:value-of select="$PIPE"/>

    <xsl:value-of select="wd:Age"/>

        <xsl:value-of select="$NEWLINE"/>

 </xsl:for-each>

    <!-- Trailer Record --> 

 <xsl:text>End of Records</xsl:text>

 

</xsl:template>

</xsl:stylesheet>

Test

Use XLS Transformer to test the above code.

Result:

Employee ID|First Name|Last Name|Gender|Age 1234|Steve|Morgan|Male|56 1235|Logan|McNeil|Female|40 1236|Joy|Banks|Male|42 End of Records

Additional Reads:

XML to XSL Coding - Sample 1

XSL Coding Tips

Free XSL Transformer Online

Business Processes: BP Critical Errors

How to identify Business Processes with Errors & Fix?

Some times we see few of the transactions falling flat, saying Processing Error! You can rely from time to time on one report i.e.

Business Process Exception Audit - Report

Using this report we can find all the BP's that have Critical Errors and Alerts. If you want to see and address your Warnings as well, check the Include Warnings Checkbox. But Warnings won't hard stop you. Your main target should be to zero any critical errors.

This is a great report to identify all critical errors at one place and fix it individually.

Once you run the report, it results like below.

Highlighted in Yellow

Severity                          : Critical / Warning

A Problem Exists With : Shows which step your BP has problem or as a whole.

Problem / Solution        : Provides you with possible solution to fix the same. Follow this, it will help you in fixing the issue mostly.

For Example: Click on one of the A Problem Exists With item which will take you the respective BP to fix as shown below. It gives you a clear detail as what is missing in this BP.

The related actions menu in the A Problem Exists With column is the same as the related actions menu on an individual step on the BP's View Definition page.

If a business process is broken, Workday automatically sends a Fix Business Process task to Business Process Administrators and provides a link to correct the business process definition.