om een gepersonaliseerde navigatie te krijgen.
om een gepersonaliseerde navigatie te krijgen.
Interface applications use the person code as a key field, which is why changing it is unwise. A change to a person code can even result in an inability to link personal details, as the last known person code was different. This is why it is no longer possible to change the person code on the Person screen. If it nevertheless becomes necessary to link a different person code to an employee, you can do this by changing the Unique Personal ID (UPI).
On the Person screen, the Person code field is a read-only field as of this release, and it can no longer be changed on the screen or through an import.
If it nevertheless becomes necessary to change a person code, this can be done on the Change UPI screen.
No action is required.
If you terminate an Organizational unit with a Reference Date equal to the start date of the Organizational unit, then the end date of the organizational unit was set before the start date. As a result, it was no longer possible to consult or modify the Organizational unit.
If you terminate an organizational unit on the effective date of the same organizational unit, you will now see the following error message: Termination of this OU failed, followed by the technical details. It is still possible to delete the organizational unit as of the effective date. This has the same result as termination on the effective date.
No action is required.
Many organizations use free fields to record data that is specifically relevant to them. Many fields have default values, which is why it is desirable to be able to add and use free fields in profiles. Free fields in profiles are possible as of this release.
The search function for finding and adding a data element to a profile now also allows searching for and selecting free fields. You select a free field by typing in the code or name of the free field (element). You can call up a list of all free fields by typing free element in the Type of element search parameter. You can then enter a standard value for the selected field (element) here.
Please note
You cannot include free fields in a profile that are in use at both employee and contract level. If you try, you will receive an error message. You can resolve this by defining the free field at one level.
No action is required.
As announced in the previous release notes, we have adjusted the Leave entitlement report from release 2020-12. We have received feedback from users that they prefer to have the report available in Excel for auditing purposes. This is why the Leave entitlement report is only available in Excel format as of this release. In addition, report generation performance has been improved.
If you perform one of the following Actions on the Grant leave entitlement screen: New leave year, Correct current leave year or Undo current leave year, the corresponding report will now only be created in Excel format and no longer as a PDF. If you still want to export the report to PDF, you can do this by saving the Excel as a PDF.
No action is required.
As announced in the previous release notes, we are starting with adjustments to the reports on granting leave as part of the operational reporting improvements. We have received feedback from users that they prefer to have the Generate work schedules processing report and the Transfer of leave entitlements report available in Excel for auditing purposes. These reports are available in both Excel format and PDF as of release 2020-12. In addition, report generation performance has been improved.
If you perform the Generate work schedules or Transfer leave entitlements actions, you can export the reports in both Excel format and PDF. Excel is the default value in the Save as field.
If you want to export the report in PDF, you must change the value in the Save as field to PDF.
The GDPR Delete Personal Data screen shows you all employees who have not been employed for the last seven years. The list also includes individuals who never entered employment. In principle, you should delete the personal data of these individuals because there is no longer any purpose limitation. Sometimes, however, it may be useful not to delete this personal data, for example because an individual will be entering employment a month later. Based on feedback in the wishes portal and from the customer effort score, we have expanded the data shown on this screen so that you can recognize the individuals who never entered employment.
The Start Date and End Date columns have been added to the GDPR Delete Personal Data screen. If these columns are empty, the user may find it easier to decide whether to delete the individual’s personal data.
No action is required.
Feedback from the customer effort score for the GDPR Delete Personal Data screen following the previous release indicated a need for a greater range of personal data to be deleted.
If an employee’s personal data is deleted, the following fields will also be deleted as of this release:
contract details
details of children
Salary slip viewer
In addition, it is no longer possible to call up the salary slip of deleted individuals in the Salary slip viewer.
No action is required.
During a Gemba walk, people walk around the workplace and observe how users make of use the system to identify potential improvements, both large and small. The most recent walk revealed a need to see the manager’s employee code in the Organizational unit history. This eliminates the additional time required for looking up managers’ employee codes in the case of common surnames.
If you have selected an organizational unit and requested the history of the organizational unit, as of this release you will see the manager’s employee code in a separate column before the manager’s name. This applies to both the manager and the backup manager.
No action is required.
As of the September release, you can select an employee after selecting the free screen. This means the free screen will open immediately and you no longer have to wait until all employees have been loaded.
However, if the free screen was created as a contract screen:
The following issues have been solved as of this release:
No action is required.
If an end date was entered in a workflow as recipient through Active notification, the other workflows also disappeared from recipients.
This has been resolved. The other workflows defined for the recipients remain active until an end date is entered specifically for those recipients.
We recommend checking for the presence of workflows and recipients.
Publishing Date : 11/19/2020
Hier vind je de dagen waarop de YouServe releases in 2024 zijn gepland.
De release kalender van Visma Raet vind je hier.
Januari 2024 | ||||||
---|---|---|---|---|---|---|
1 | 2 | 3 | 4 | 5 | ||
Ma | 1 | 8 | 15 | 22 | 29 | |
Di | 2 | 9 | 16 | 23 | 30 | |
Wo | 3 | 10 | 17 | 24 | 31 | |
Do | 4 | 11 | 18 | 25 | ||
Vr | 5 | 12 | 19 | 26 | ||
Za | 6 | 13 | 20 | 27 | ||
Zo | 7 | 14 | 21 | 28 |
Februari | ||||||
---|---|---|---|---|---|---|
5 | 6 | 7 | 8 | 9 | ||
Ma | 5 | 12 | 19 | 26 | ||
Di | 6 | 13 | 20 | 27 | ||
Wo | 7 | 14 | 21 | 28 | ||
Do | 1 | 8 | 15 | 22 | 29 | |
Vr | 2 | 9 | 16 | 23 | ||
Za | 3 | 10 | 17 | 24 | ||
Zo | 4 | 11 | 18 | 25 |
Maart | ||||||
---|---|---|---|---|---|---|
9 | 10 | 11 | 12 | 13 | ||
Ma | 4 | 11 | 18 | 25 | ||
Di | 5 | 12 | 19 | 26 | ||
Wo | 6 | 13 | 20 | 27 | ||
Do | 7 | 14 | 21 | 28 | ||
Vr | 1 | 8 | 15 | 22 | 29 | |
Za | 2 | 9 | 16 | 23 | 30 | |
Zo | 3 | 10 | 17 | 24 | 31 |
April | ||||||
---|---|---|---|---|---|---|
14 | 15 | 16 | 17 | 18 | ||
Ma | 1 | 8 | 15 | 22 | 29 | |
Di | 2 | 9 | 16 | 23 | 30 | |
Wo | 3 | 10 | 17 | 24 | ||
Do | 4 | 11 | 18 | 25 | ||
Vr | 5 | 12 | 19 | 26 | ||
Za | 6 | 13 | 20 | 27 | ||
Zo | 7 | 14 | 21 | 28 |
Mei | ||||||
---|---|---|---|---|---|---|
18 | 19 | 20 | 21 | 22 | ||
Ma | 6 | 13 | 20 | 27 | ||
Di | 7 | 14 | 21 | 28 | ||
Wo | 1 | 8 | 15 | 22 | 29 | |
Do | 2 | 9 | 16 | 23 | 30 | |
Vr | 3 | 10 | 17 | 24 | 31 | |
Za | 4 | 11 | 18 | 25 | ||
Zo | 5 | 12 | 19 | 26 |
Juni | ||||||
---|---|---|---|---|---|---|
22 | 23 | 24 | 25 | 26 | ||
Ma | 3 | 10 | 17 | 24 | ||
Di | 4 | 11 | 18 | 25 | ||
Wo | 5 | 12 | 19 | 26 | ||
Do | 6 | 13 | 20 | 27 | ||
Vr | 7 | 14 | 21 | 28 | ||
Za | 1 | 8 | 15 | 22 | 29 | |
Zo | 2 | 9 | 16 | 23 | 30 |
Juli | ||||||
---|---|---|---|---|---|---|
27 | 28 | 29 | 30 | 31 |   | |
Ma | 1 | 8 | 15 | 22 | 29 | |
Di | 2 | 9 | 16 | 23 | 30 | |
Wo | 3 | 10 | 17 | 24 | 31 | |
Do | 4 | 11 | 18 | 25 | ||
Vr | 5 | 12 | 19 | 26 | ||
Za | 6 | 13 | 20 | 27 | ||
Zo | 7 | 14 | 21 | 28 |
Augustus | ||||||
---|---|---|---|---|---|---|
31 | 32 | 33 | 34 | 35 | ||
Ma | 5 | 12 | 19 | 26 | ||
Di | 6 | 13 | 20 | 27 | ||
Wo | 7 | 14 | 21 | 28 | ||
Do | 1 | 8 | 15 | 22 | 29 | |
Vr | 2 | 9 | 16 | 23 | 30 | |
Za | 3 | 10 | 17 | 24 | 31 | |
Zo | 4 | 11 | 19 | 25 |
September | ||||||
---|---|---|---|---|---|---|
35 | 36 | 37 | 38 | 39 | 40 | |
Ma | 2 | 9 | 16 | 23 | 30 | |
Di | 3 | 10 | 17 | 24 | ||
Wo | 4 | 11 | 18 | 25 | ||
Do | 5 | 12 | 19 | 26 | ||
Vr | 6 | 13 | 20 | 27 | ||
Za | 7 | 14 | 21 | 28 | ||
Zo | 1 | 8 | 15 | 22 | 29 |
Oktober | ||||||
---|---|---|---|---|---|---|
40 | 41 | 42 | 43 | 44 | ||
Ma | 7 | 14 | 21 | 28 | ||
Di | 1 | 8 | 15 | 22 | 29 | |
Wo | 2 | 9 | 16 | 23 | 30 | |
Do | 3 | 10 | 17 | 24 | 31 | |
Vr | 4 | 11 | 18 | 25 | ||
Za | 5 | 12 | 19 | 26 | ||
Zo | 6 | 13 | 20 | 27 |
November | ||||||
---|---|---|---|---|---|---|
44 | 45 | 46 | 47 | 48 | ||
Ma | 4 | 11 | 18 | 25 | ||
Di | 5 | 12 | 19 | 26 | ||
Wo | 6 | 13 | 20 | 27 | ||
Do | 7 | 14 | 21 | 28 | ||
Vr | 1 | 8 | 15 | 22 | 29 | |
Za | 2 | 9 | 16 | 23 | 30 | |
Zo | 3 | 10 | 17 | 24 |
December | ||||||
---|---|---|---|---|---|---|
48 | 49 | 50 | 51 | 52 | 1 | |
Ma | 2 | 9 | 16 | 23 | 30 | |
Di | 3 | 10 | 17 | 24 | 31 | |
Wo | 4 | 11 | 18 | 25 | ||
Do | 5 | 12 | 19 | 26 | ||
Vr | 6 | 13 | 20 | 27 | ||
Za | 7 | 14 | 21 | 28 | ||
Zo | 1 | 8 | 15 | 22 | 29 |
Copyright 2022 Visma Community. All right reserved.