(As of article publish date. Dates are subject to change, please contact your CSM for the most up-to-date information. Ranges are approximate and in the Paris time zone).
Retention policies are becoming more precise:
HR Admins are now able to choose any year range between 1 and 100 (for example 77) when setting up a new retention policy.
The old behaviour only allows users to enter years in denominations of 10 (e.g., 50, 60, 70...100).
In order to reduce page load times, notifications will be displayed on the Document Manager Core homepage / recent activity section for a temporary period of 2 months in the future.
Notifications were previously visible for up to one year, which in total slowed down the loading time considerably. Therefore, we have decided to shorten this period for a generally better user experience.
Please Note: The retention period in the database itself remains 1 year for the notifications.
We have added one new font supported by Document Generation:
In July 2021, UKG HRSD People Assist released a whole new Knowledge Base interface in open beta
This new interface makes it simpler to manage articles and categories, particularly in an international context using multiple languages.
This feature is currently under controlled roll-out: The deployment for monolingual customers is done and deployment for multilingual customers will start in December.
Check out the article with complete documentation and an FAQ on Zendesk to learn more about it: here.
Activation for multilingual customers can have minor impacts. These impacts are detailed on Zendesk: to learn more about it you can click here.
In order to expect less impacts on activation and to fully benefit from the new Knowledge Base features, it is advised to migrate the articles and categories to the international model of this new application.
To do so, a migration tool will be available in the interface in the upcoming weeks, alongside with a documentation to help you doing so.
First activation waves will start on December 15th for staging environments, then in January for production environments, once the tool is made available.
Note: the migration is not mandatory for the activation of this new application.
Tables are more and more used across articles. They enable users to better customize and display content within articles.
To get the full benefit of these assets we have improved the layout functions of the tables.
The main goal of using tables in articles is to improve clarity and readability.
Until now, they were automatically aligned to the left side of the screen, and it was impossible to modify this option.
We have now added the possibility to align the table to the left, right or center of the text, to give more options to include the table also visually to the article.
But not only can the alignment be changed now, but also users will be able to choose to display borders or not.
Borders will be displayed as dashed lines while editing and can be kept or removed in the final article.
Postponed from 21.11 release à this feature will be available in December instead.
Content within categories (articles and forms) can be restricted to a certain group of employees.
However, the employee will then not be able to access any of the content located inside a particular category.
Currently, the interface still displays all categories, which can mislead the employees in their search for relevant content, which can be confusing for the restricted employees.
To improve the user experience, the employee portal will now only display categories that are not restricted for the employee.
Example: If an employee does not have access to a certain article or form in the category “Remote”, this category will be entirely hidden to this person.
A recent bugfix on articles’ titles could generate some displaying issues: a word in the title could be split within the title, making it harder to read à Fixed on staging and production environments.
After having read an article, employees sometimes want to fill in a request form.
In order to do so, they need to go to the portal’s homepage, then back to the category and then to the request form.
Now, when reading an article, forms in the same categories as the article are suggested to the employee so that they can directly navigate to the desired request form.
It may occur that some employees no longer have access to the SSO of the company.
Employees who have left the company and are rehired, or employees who have changed positions, may lose access to SSO.
As their profile in the HRSD platform still contains the information related to the previous SMAL token, these employees can no longer connect to the Employee Portal using their email address and password and are thus excluded from completing tasks, send requests, etc.
Up until now, customers had two options:
You will now be able to update the SMAL token directly in the employee profile page in Document Manager.
Compared to before, you will gain a great level of autonomy in offering your employees a much faster service and ensuring that they are able to access anything they need to fulfill their tasks and missions.
A new and more ergonomic user interface:
--------------------------
We added a new permission “Manage employee SAML tokens”
HR users are now able to change and delete these SAML token data for employees directly.
Recommendation: As these are authentication tokens, it can be useful to limit the persons who can manage them.
Notes:
With this new release, it will now be possible to search for data sets by name using our API.
We updated the GET /datasets endpoint with a name query parameter.
Please Note: This will be used internally by the Form builder to add a search field in the configuration of a form using data sets (targeted for the next release 22.1).
This Enhancement will be released on December 22nd.
