Release Notes - November 28, 2023

Advance repayments start in the month that follow the advance payment.

If you add an advance for an employee after any monthly pay run closes, then the employee is paid the advance in the next month and the first repayment is scheduled for the following month.

We have added the following workflows in the back end to improve account management when handling benefit account transactions:

• A workflow to calculate the account balance and values in the brought forward column
• A workflow to fix the historical values of account transactions

These workflows prevent data corruption of the values in the brought forward column and facilitate calculating the benefit account balance correctly.

We have improved the content displayed in the validation messages, confirmation messages, and fields (that you would view when working with working patterns) to make them:

• Shorter
• Meaningful
• Consistent
• User-friendly

We have enhanced the method of handling time calculations for standard working patterns in this release.

When creating a standard working pattern, you do not need to enter the contracted hours per day of employees manually. When you click Generate Pattern, the Contracted duration per day field automatically calculates and displays the contracted work duration of employees in hours and minutes.

For more information

•   Creating standard working patterns

As a leave approver, when viewing the details of any leave request task in Tasks, you can view information about whether the leave dates conflict with any other employees.

Leave pay calculations correctly account for the following plan limits if they are configured for sick leave types:

• Maximum number of leave days
• Tiers

As a platform admin, when generating a report for a specific business from the Yomly Admin platform, you can set up custom access to it for only the required audiences.

To do this, do the following:

1. On the Businesses page, find the business for which you want to generate a report and click Edit in the Action column.

   

2. Go to the Reports tab and click + Generate New Report.

   

3. Enter the details of the report.

4. In the Audience field, select the audiences for whom you want to set up custom access to the report.

   

5. Click Generate Report to generate the report locally for the business.

You can revisit and modify the configured custom access to local reports when customizing the platform. This is similar to setting up rules to display or hide any platform feature for the required audiences.

Advanced customization enables you to implement granular user access control (as a platform admin) instead of hiding or displaying entire features of the platform.

You can do this by setting up permission-based rules for different UI components when customizing the platform. Permissions enable you to configure custom access for different audiences.

By granting or restricting access to UI components, you can control what your platform users can see and do.

You can configure multiple permission-based rules for the same UI component.

In this phase of enhancements, we bring you the following advanced customization capabilities:

• Ability to allow or restrict audiences from filtering and downloading data related to employee availability in Calendar
• Ability to allow or restrict audiences (who are authorized to view the salary information of the respective employees) from viewing data and performing actions in each tab of the Salary tab on the employee profiles.

• Ability to allow or restrict audiences from doing the following in Payroll even when only specific employees (for example, platform admins) have complete access to Payroll:

  • Completing pay runs
  • Issuing payslips
  • Reopening pay runs

You can use scripting to select the employees you want to include in an audience. The platform supports industry-standard scripting languages such as JavaScript and Python.

This feature enables you to create a custom group of employees based on specific and complex conditions.

To select the employees you want to include in your audience using scripting, do the following:

1. When creating or editing an audience, after entering the required details, select Use Advanced Audience.

2. Enter you script in Audience Selection Script.

3. Click Run Script.

   The script runs and displays the details of the selected employees.

   

   The script considers all other conditions that you have configured when entering the details of the audience. For example, if you have selected one or multiple roles, the script selects only employees who match those roles.

4. If required, refine your script to select employees based on your requirements and run it again.

5. When the list of employees selected meets your requirements, click Save to save the audience.

As a platform admin, you can set up custom access to features of the platform at the global level by configuring permission-based rules from the Yomly Admin platform.

As audiences are business-specific, you can set up permissions that are based on user roles.

As a platform admin, you can reset the passwords of your platform users when your business uses multiple methods of user authentication.

To change any employee's password, go to the Account tab on their profile and click Generate new password.

Previously, Tasks displayed missing document tasks even for employees who weren't part of the audiences configured for the respective document types.

This issue is fixed now.

Previously, the pay run notification sometimes displayed different statuses of querying (or re-querying) pay runs from their actual status. You needed to refresh the page to see the real-time statuses pay runs.

This issue is fixed now.

Previously, when the All Goals page was filtered by assignee, the first page of the results displayed no data in the Assignee column.

This issue is fixed now.

Previously, if you attached a document from a data container in any process governed by a pipeline, the pipeline's workflow was affected. The pipeline would stop at its last transition phase.

This issue is fixed now.