Business Processes: Hide / Show fields in Workday

Hide / Show fields in Workday - Business Processes

Have you ever thought of hiding some fields or may be making some fields mandatory? This is achievable with a limited scope. 

Configure Optional Fields is a Task which helps you in controlling some fields on your transactions.

Say for example, while hiring an employee, You may want to hide some fields to some security groups for different reasons.

You see three possible options that you can set up on each field that you would like to hide.

• Hide for All
• Security Group - You can choose for which security group you would like to hide and which all security groups you would like to make it required. [ Hide For / Required For ]
• Require for All

General: Jobs that you typically see in Workday

Below are the typical Workday Job roles / Positions that you come across on Job portals if you are searching for one. 

Its not the exhaustive list though, but should give you a fair idea of what are the positions that are open in the job market.

Workday HCM:

Workday HRIS Analyst

Workday HCM Analyst

Workday Software Engineer

Workday Business Systems Analyst

Workday Analyst

Workday Business Analyst

Workday Consultant

Workday Configuration / Functional Analyst

Workday Tester

Workday HCM Tester

Workday IT Business Analyst

Workday Reporting Analyst

Workday Security Administrator

Workday Administrator

Workday Developer

Workday Technical Associate

Workday Integrations Specialist

Workday Integration Developer

Workday Studio Integration Consultant

Module Specific :

Workday Consultant - Benefits

Workday Consultant - Payroll

Workday Consultant - Time

Workday Payroll Configuration Specialist

Workday Consultant - LMS

Workday: Core Connector Templates

Below are some of the hand picked core connector integration templates that you generally see during work.

Core Connector for HCM -Templates:

Core Connector: Worker

Core Connector: Positions

Core Connector: Locations

Core Connector: Job Requisitions

Directory Service

E-Verify - Employment Verification

Core Connector: Job Profile and Job Family

Core Connector: Organization Inbound

Core Connector: Organization Outbound

Integration - Templates:

Enterprise Interface Builder  (EIB Related)

Cloud Integration Template   (Studio related)

Document Transformation

Cloud Connect for Benefits - Templates:

CIGNA: Medical, Dental, Wellness, FSA

Guardian: Dental, Vision, Insurance

Delta Dental of CA: Dental

Aetna: FSA, HSA, Life, Disability

MetLife: Dental, Vision

HealthPartners: Medical, Dental, Vision, Rx

Cloud Connect for Third Party Payroll - Templates:

Payroll Interface

PI External Results Inbound (Do Not Use)

Import External Payslips

Payroll Effective Change Interface

PECI - Merge Files Integration Template

External Payroll Results Inbound

Worker Effective Change Interface

iLoad- Templates:

iLoad Bulk: Process Input File Template

iLoad Bulk: Doc Splitter

Access the report - Integration Template Catalog to view all the integration templates that Workday is offering.

Integrations: Workday XSL Coding Tips

Workday XSL Coding Tips

Using Variables (Declaration) :

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

<xsl:variable name="PIPE" select="'|'"/>   [Use the delimiter that you would like to see in the output. Examples: Comma(,), Tab (    ), Pipe(|), SemiColon(;) ]

               <xsl:variable name="Record1" select="'C'"/>

               <xsl:variable name="Record2" select="'S'"/>

Using your Variable: (for above)

              <xsl:value-of select="$NEWLINE"/> [This takes the cursor to next line]

              <xsl:value-of select="$PIPE"/>  [This prints | ]

      <xsl:value-of select="$Record1"/>     [This prints C]

      <xsl:value-of select="$Record2"/>     [This prints S]

Using Fillers (Declaration):

    <xsl:variable name="Filler_Blank" select="'                                                                                                                            '"/>

            <xsl:variable name="Filler_Zeros" select="'0000000000000000000000'"/>

Using your Fillers and Substring Function: (for above)

             <xsl:value-of select="substring($Filler,1,10)"/>           [This prints 10 spaces, if you say 15 then it will print 15 spaces ]

             <xsl:value-of select="substring($Filler_Zeros,1,4)"/>  [This prints 0000 as you said 4]

Using Plain Text:

<xsl:value-of select="'TEST'"/>

Using Comment:

<!--  Your Comment Here  -->  

Using Choose:

    <xsl:choose>

<xsl:when test=" wd:Gender = 'Male' ">

   <xsl:value-of select="'M'"/>

        </xsl:when>

<xsl:when test=" wd:Gender = 'Female' ">

   <xsl:value-of select="'F'"/>

        </xsl:when>

        <xsl:otherwise>

                  <xsl:value-of select="'U'"/>

        </xsl:otherwise>

    </xsl:choose>

Using For:

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

          <Your Lines of code here>

        </xsl:for-each>

Using Templates:

    <xsl:template match="/">

        <xsl:call-template name="HeaderRecord"/>

        <xsl:call-template name="DetailRecords"/>

        <xsl:call-template name="TrailerRecord"/>

    </xsl:template>

    <xsl:template name="HeaderRecord">

          <Your Lines of code here>

    </xsl:template>

    <xsl:template name="DetailRecords">

          <Your Lines of code here>

    </xsl:template>

    <xsl:template name="TrailerRecord">

          <Your Lines of code here>

    </xsl:template>

Reporting: 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. 

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 be surprised 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.

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.

Note: You can't limit processes for schedules with a minute recurrence.