What is Workday Customer Central?

Customer Central

We often listen to this term Customer Central in Workday. Its a Workday tenant that sits on top on all non-production tenants, which allows customers to view all non-production tenants in one place. 

Using Config Catalog in the Customer Central you can make your tenants back to Factory Default configs. Customer Central is a new tenant in each customer environment that resides over all customer non-production tenants during their life as a customer. Customers must have a Customer Central tenant in order to access the tools. No customer data is housed within Customer Central. It only provides a means for managing other tenants and access to the new tools

There are certain tools that are accessible through Customer Central.

• Tenant Health Dashboard - An availability status of each of the tools, Information relating to the setup of each user in the tenant
• Configuration Catalog - Migrate specific data sets from Factory default to non-prod tenants
• Access of all non -prod Tenants - Centralized view, easy to access and maintain.

Additional Reads:

Workday Community

Power of One

The Power of One

Power of One

Power of One is the heart of everything that works in workday. All customers are on the same version of Workday: one code-line, one version, and one Workday Community—Workday calls it as the Power of One.

Empowerment is the foundation of a happy customer base, and Workday’s latest measurement revealed 97% customer satisfaction. In true democratic fashion, members of Workday community even suggest and then vote on new features. The Workday Brainstorm is an incredibly innovative program, with customers having contributed hundreds of ideas to our products through the years.

There is only one version of Software in Workday at any point. These 4 reasons contribute to the success of Workday.

• One Source of Data - Turn insight into action. With a single system for finance, HR, and analytics, Workday gives you total visibility coupled with the power to act on it
• One Experience -  Workday gives you the intuitive and informative experience you need to manage change and engage your workforce. As technology advances, Workday automatically delivers the latest interface innovations to you without requiring any process or configuration changes on your end. See how our approach profoundly impacts the success of our customers.

• One Security Model - Security is at the heart of our business. We provide protections that traditional software vendors can’t. We build, and continually update, rigorous safeguards into every product to maintain the highest level of security.

• One Community - Through a highly engaged ecosystem, our customers share ideas and best practices as a community, and actively engage product teams on the next innovations.

What is Workday Community?

Workday Community

This is a platform for all the Workday Partners, Workday Customers,  and Peers who are working on Workday. Here you can collaborate with other Workday Enthusiasts, share ideas, propose solutions, brainstorm, post questions, seek answers etc.,

Community helps customers to enhance their knowledge on various Workday Applications.

You get access to Workday if you are a Workday Customer, Workday Partner, or Workday Employee.

Workday Community

In Workday's words:

"The Workday Community supports, educates, and empowers customers by connecting them with peers and partners. Members share ideas and best practices through a variety of collaboration tools, including contributed solutions, forums, and user groups. And if customers have great ideas for product enhancements, they can let us know. In fact, we've put more than 1,800 brainstormed ideas into the product. It’s a model of shared success that’s only possible with our unique technology platform."

How to change Logos or Colors in WorkdayTenant?

Ever wonder if there is any possibility that we can change the colors or logos of the tenant that you are working.

Yes it is possible with the task Configure Tenant Branding.

The primary reason to change the Color of your tenant would be to differentiate the tenants (Production, Sandbox, Implementation, etc,.) as you know all the tenants including Production resembles same with respect to look and feel.

You can change the tenant colors which in deed will change the colors of the applications on the home dashboard.Changing these colors will change the color of your title bars and profile menus too.  It's not possible to change individual application/worklet colors.

Task: Configure Tenant Branding


To Change Branding Color


View Branding Logo

Branding banner View

Small Branding Banner View

Small Branding Logo View

Integrations: What is WECI in Workday Integrations ?

WECI

WECI, Worker Effective Change Interface, to detect the effective change events of worker. 

The Worker Effective Change Interface is an outbound integration that sends a full effective stack of worker data to third party systems. In addition to the already delivered functionality of corrections, rescinds, indirect, future and retro transactions, there are additional data sections and enhancements customers need in order to fulfill their third party system requirements.

Additional data sections will reduce customer effort in mapping fields required for the downstream system. Adding attributes will increase the flexibility of the connector so that customers can tailor the data extracted to the third party system.

Because of the resource-intensive nature of a WECI event, it is not an appropriate solution for frequent runs or for near real-time integrations, and because WECI returns the full stack of transactions, frequent runs are not necessary. In general, WECI should not be run more than once per day per supervisory org.

Unlike PECI, WECI includes contingent workers in it's output. It will run for the entire active worker population or can be restricted by the "Restrict Results By Orgs" launch parameter. Note that only supervisory orgs can be entered in this launch parameter.

WECI is not designed for time periods of inordinate lengths. Although WECI does not restrict effective and entry date ranges to pre-defined limits, WECI time periods should typically not be longer than a month. Extended time periods of several months or years, will likely cause issues when attempting to process excessive future-or-historic data for which WECI was neither designed nor tested. Restrict time periods to common sense intervals required to feed downstream endpoints.

These are the use cases of WECI:

• Non Payroll Applications i.e. that require full effective stack changes like Data Warehouses, Data Hubs or Compensation Planning applications.
• For Payroll Applications, WECI could serve as a bolt on to PECI in case where PECI has a given limitation for a specific use case of an industry or client that WECI can address.

Common Issues: 

Issue: 

Fields marked as "Include in Output" are not coming through in the output file, even when changed.

Resolution:

Ensure that in the parent section the desired output sections are checked "Include in Output". Selecting child elements does not automatically select the parent element to include in output.

Issue:

The following unexpected error has occurred: Multiple Worker Effective Change Interface - Summary DIS documents found! Should only be one!

Resolution:

Do not orchestrate multiple WECI integrations off of a single BP.

Issue:

A completed hire event is reported and a subsequent effective change updates a value required by the downstream system, such as National ID.

Resolution: 

CCW would only report a single transaction with all the values for transactions subsequent to the hire, so an updated National ID would be automatically included in the HIRE transaction. However with WECI, each transaction is reported independently, therefore there will be separate HIRE and DTA transactions for the HIRE event and subsequent change to National ID. The post-processing transform will need to detect the HIRE event and inspect the following effective changes for values that need to be included on the HIRE event transmitted to the payroll vendor

Issue:

Multiple contact data changes are not consolidated by WECI.

Resolution:

For example suppose there are two contact data changes in an effective date range on different effective dates. On the first date the employee changes their home address, and on the second effective date, their email address changes. The payroll vendor only supports a single row for changes to contact information. In this case all changes containing data for the single row required by the vendor need to be detected during the transform and consolidated in a single row before being transmitted to the vendor.