Employee Assistance

Employee Assistance in Unit4 Advanced Virtual Agent (Ava) allows employees to manage all HR-related tasks, such as absences and balances. It also helps to monitor the status of the requests.

Functionality offered

• Requesting an absence
• Checking balances
• Retrieving an absence list
• Updating an absence
• Deleting an absence

Example utterances to trigger Employee Assistance

• I would like to take vacation from April 10 to April 15
• Request sick leave for tomorrow
• I am feeling unwell and won’t be able to work today
• I am planning to be off tomorrow
• What is my annual leave balance?
• How many vacation days do I have left?

ℹ️ Note: If Ava cannot process your request because of missing details, you wil be guided to correct the input.

System setup

To set up Employee Assistance, someone with administrator permissions within the ERP environment needs to perform the following steps.

Access rights

These are the specific access rights that must be configured for the required public APIs and objects. To set access to public APIs and objects see the ERPx Access setup section. For additional required setup refer to the functionality-specific implementation guides.

💡 Tip: To make your task easier, create an Ava role with the required permissions. When you need to grant a new user access to Ava, simply assign them to this role.

Unit4 ERPx

Access to the following endpoints is needed to use Employee Assistance.

• Employee balances [Public API]
• Absences [Public API]
• Objects [Public API]
• Employments [Object]
• Attribute values [Object]
• Absence codes [Object]
• User [Object]

Limitations

When creating an absence request, only consecutive calendar days are supported within a single request. An absence request must be defined by a start date and an end date that represent a single continuous date range. Requests that attempt to include non-consecutive days (for example, skipping days within a range or combining separate date ranges into a single request) are not supported and will be rejected.

When the rate limit is exceeded:

• The absence creation request is rejected.
• The user receives a rate-limit error response.
• No absence records are created for the rejected request.
• The user must retry after the cooldown period defined by the agent.

This limitation ensures:

• Consistent calculation of absence balances and limits.
• Correct interaction with work schedules and workflows.
• Reaching specific ERP limitations.