Wednesday, September 9

Copy Custom Notifications

Copy Custom Notifications on Business Processes

Often there are times, where we should be creating multiple custom notifications may be on the same lines. Making the use of Copy Notification feature eases the creation of multiple custom Notifications.

So, make the use of Copy Notifications to lessen the burden of creating multiple notifications from scratch.

Access your Business Process and go to the Notification tab and see your existing custom notifications and click on the related actions on your custom notification and then

Business Process >> Copy Notification

Provide the Effective Date and notice the Workflow Notification that is being copied. On the next screen you will notice your custom notification being copied and you can now edit according to your need. 

Tuesday, September 8

Secured Items in Multiple Domains

Secured Items in Multiple Domains

Use this report, if you have a need to identify if any item like report, task, report field etc., are associated with multiple domains.

Unfortunately, it doesn't have any parameters that you can set before running the report. So it will take a while to run and fetch the results.

You can also make use of another delivered report,  View Security for Securable Item Not many will have access to this.


Monday, September 7

Report: Business Process and Integration Notifications

Business Process and Integration Notifications


This is a report that you can use when you wanted to check for the notification routing. For example, for one of the task in the Business Process triggered a notification and you wanted to see, if it really triggered those recipients. This can be used for both Business Processes and Integrations.

There are couple of reports that you will notice in the tenant. 
 
Business Process and Integration Notifications (Do Not Use) - This is not an indexed report and Workday is not supporting this so refrain from using this report. Do Not Use (DNU)

Business Process and Integration Notifications Indexed - Use this Report. When you give your input parameters, be mindful in providing the values, do not go for lengthier durations.

The example below shows for one day.





Notice there are 317 instances for one day. Here you can see all the notifications that got generated with date and time. 

Recipients are the individual workers or the workers from the security groups. Lastly you can see the Static Email Recipients like test@gmail.com



Sunday, September 6

All Custom Reports Errors - Identify and Fix

 Fix Custom Report errors across Tenant

Make use of the delivered report Custom Report Exception Audit to identify all the errors pertaining to the custom reports with in the tenant. This is one of the Audit report that helps in keeping your system error free.

Notice any one of the below 3 types of severity once you run the report in your tenant. Workday provides you the problem existing with the report and the possible solution to fix the issue.

Critical - Action is required and the issue to be fixed.

Warning - An alert, nothing big happens if you don't take any action.

Information - Helping you understand about some detailing on the respective report.

Notice the highlighted fields and fix the issues.

Saturday, September 5

Integration Common Issues in PROD

 Integration Common Issues in Production

Here are some of the common Issues related to files that you would encounter while supporting any type of integrations in Production. 

For example, an ongoing EIB Outbound integration, you would typically see issues like below:

File Empty:

The file that was sent to the end point is empty where as they were expecting some data in the file. You need to check your Data Source and specially parameters / filters on your integration event. Which parameters were passed during the launch of integration. Check for the data parameters, and try to run your report by passing the same parameters and see if you fetch any rows.

File Not Received:

In the above case, the file was sent but if was empty. Here, the file was not received at the end point. This is most probably something to do with your Delivery method. Check if the SFTP / FTP passwords got changed or any address / directory got changed so that you can update it and relaunch the integration.

File Has Incorrect Data:

In this scenario, the file was sent and the data in the file was not as expected. It could be of two scenarios 

1. More rows than expected 

2. Less rows than expected.

Its not always the fault on our side, there are times when your end point had a different understanding. So it is important to analyze the data as what was sent vs what is expected. You need to know your data source or web service and filters, sub filters properly. 

Example: If your file is missing some employees, you can ask for the sample Employees who are being missed and try to analyze what is causing that employees to miss in the output file. Same goes with the additional employees in the file.