Releases YouServe

12-05-2021 Improved filtering in Workflow definition overview (change 498602) In Settings/ Workflow definition overview, on the Active, Completed, and Authorisations columns the filtering results will match exactly the filled value. 07-05-2021 Er...

Notifications Again - Duplicate sick reports were added when importing consultant’s Excel file The September release notes included this message about incorrect addition of duplicate sick reports as described below. Due to a problem with this modified functionality we have revoked the modification on 30 August 2021. The modification has now been improved and will again be available in the October release. Why When an Importing absence file was read in the Import Excel file (Consultant) screen that inadvertently contained duplicate sick reports, the Sick leave screen showed two lines with active sick leave. However, only one sick leave is allowed per contract. In the Sick leave screen it is not possible to enter a new sick leave for an employee with an active sick leave because the system checks for this and an error message will be displayed. When importing sick leave this check was not performed, resulting in duplicate sick reports with the same start date. How Management > Import/Export > Import Excel file (Consultant) Employee > Illness > Sick leave The software has been modified to ensure an Importing absence file with duplicate sick reports no longer results in duplicate active sick reports when it is read using Import Excel file (Consultant). We have also made sure this is not possible through other channels for reporting sick leave, such as API and HR Self Service. Action No action is required. Person level improved – Identity now processed in the same way as UPI We made the following functionality available on 1 September 2021. Why When an employee is hired, the system can determine whether it concerns a new or a returning employee. With a new employee the system assigns a new UPI or Identity. Identity (7013) is used to identify the user in the portal. Unique Personal ID (UPI) (7014) is used to identify a person and can also be used when the person level is not used. With a returning employee the system used to assign the old UPI but not necessarily the old Identity. This resulted in problems in the portal and other systems. That is why the system now processes the UPI and the Identity in the same way. How To enable the system to process the UPI and the Identity in the same way, the software has been modified as follows.  Settings > Recording > Parameters UPI As of 1 September 2021 the name of the Parameters UPI screen has changed to Parameters UPI/Identity. The Fill Identity with field has been added to specify what the employee’s Identity field should contain. When the employee’s Identity is already known in the system, i.e. a person with an Identity already exists for the UPI, the known Identity is used. Note: the preference specified in the Fill Identity with field for Identity applies when a new Identity has to be created. The Fill Identity with field has the following values: Generate automatically The Identity field is to be specified by the system automatically. With this option the Sequence number field and the Leading zeroes option are displayed.  Enter a sequence number if the Identity that is automatically generated should be based on this sequence number +1, this sequence number +2, etc. If the Leading zeroes option is selected, the Total length field is displayed and the leading zeroes are added to the automatically generated Identity up to the maximum length specified in Total length.  Use employee code The Identity field will automatically be filled with the employee code. Use employee UPI The Identity field will automatically be filled with the UPI. Use Identity preference The Identity field will automatically be filled with a preference value. This field will be made available through Self Service. For example, Email address or a value from the organization’s free fields. This field can be modified through an import. When nothing is entered here, the Identity field will remain blank. When Use Identity preference is selected in the Parameters UPI/Identity screen, the Identity preference field can be changed in HR Core Business, or the value will be entered through Self Service when the 10526800PS category is included in the Self Service workflow/processes. In all other cases the Identity preference field remains blank and cannot be changed in HR Core Business. Inflow/Outflow > Create employee Employee > Employee > Employee (supplementary)  The Identity preference field has also been added to the Employee (supplementary) screen and in the Create employee wizard, so it is assured in all our processes. Note: when an Identity is explicitly specified when creating an employee using Self Service category 7013PS, that value will be adopted in HR Core Business without validation. Validation will take place during processing. When in the Parameters UPI/Identity screen it has been specified that the Identity should be assigned automatically, the Identity field can remain blank. The Identity will then be assigned automatically. Action Specify your option in the Fill Identity with field in the Parameters UPI/Identity screen with the required start date to ensure one method is used for the Identity throughout the organization. Include category 10526800PS in the Self Service processes if the Identity preference field is to be used.  Modified and Improved GDPR – Some data was wrongly synchronized between Person level and Employee level Why Some data was wrongly synchronized between the Person level and the Employee level. Some of the data has to be removed or anonymized to comply with GDPR. How  The data that was wrongly synchronized between the Person level and the Employee level has been removed from the synchronization process. The data that had to be removed or anonymized to comply with GDPR has later been added and will be properly removed or anonymized as of the October release. Action No action is required. Work schedule can now be generated for a period longer than 2 years Why Up till now work schedules could only be generated for a maximum period of 2 years. Where parental leave is concerned, for example, work schedules for a period longer than 2 years are useful, which is why as of this release a work schedule can be generated for a longer period. How Settings > Work pattern > Generate work schedule As of the October 2021 release a work schedule can be generated for a maximum period of 4 years. Action No action is required.  Solved Messages List of values only consisted of 20 pages (2851105) Message  The List of values screen only showed a maximum of 20 pages. When the list of an Element consisted of more than 20 pages it was not possible to view all the values.  Solution This has been resolved and as of this release the List of values screen includes more than 20 pages. Action No action is required.  HRSS parental leave failure (2848055) Message  It was not possible to request parental leave with a start date that equaled the date of employment.  Solution The software has been modified and as of this release it is possible to hire an employee on, for example, 01-10-2021 and request parental leave as of 01-10-2021. Action No action is required. Publishing Date : 9/21/2021

On Wednesday September 11th we have put an extra release in production in which we changed the following. Changed and improved Search function Archive extended Why Self Service users usually check for mutations from recent history. Too many items are displayed based on current filters. How It is now possible to search for mutations per effective date. The search function of the Archive has been extended with effect from 11 September 2019 with an effective date (from and including) filter. In addition to the user-friendliness, this screen will retrieve the data faster by using the new filters. This filter shows as default value the mutations with an effective date starting from 3 months ago to today. If desired, you can select a different time period. Your selection will be saved for the duration of the session. If you press the red filter then you clear the period and you can select a new period. If you leave this screen and then return to it, the last used selection will be displayed again. The starting date that can be searched is the starting date that you see in the top right of the forms. Publishing Date : 9/16/2019

  This document describes the new functionality and improvements introduced by this release. Some of these changes have been inspired by messages and reports from customers. Where relevant, we have included a number in the section title to refer to the identification of the message (change .....) in question in our system. Modified and improved 1.  Travel distance calculation parameters – Google Maps to Webservices Why As was specified in the March release notes, we will start using Webservices again instead of Google Maps as of the April release. Below you will find information on the major changes you as a client will experience. What has changed? Calculation of number of kilometers In Google Maps the calculation was always based on the optimum route. In Webservices the calculation is based on the shortest or fastest route. You will have to specify your choice in the set-up once. See Your action. House number and house number suffix When Webservices was used in the past, it was not possible to calculate the distance between the house number of the location and the house number of the employee. This was possible with Google Maps, but house number suffix could not be used. This time Webservices calculates the travel distance using both house number and house number suffix. No house number of location When no house number is specified for a location, the calculation will be based on the central location of the specified postcode. Foreign addresses and Country field The travel distance for foreign addresses can now be calculated as well. When it concerns a location, the field Country must be entered correctly. If no country is specified, the calculation will automatically be based on The Netherlands. When will calculation take place When the transition is made from Google Maps to Webservices, nothing will change in the already calculated data. A distance calculation will take place when: You change the address data of the location. You change the branch of an employee or add a location. You change the employee’s address data. You want to determine the travel distance collectively. You change the field Automatisch berekenen (Calculate automatically) for the employee from No into Yes. Your action Maintenance > Repository > Configurate traveldistance calculation The Route field has been added again to the Send Data for determination of traveling distance screen. With Webservices the route can be calculated based on the fastest or shortest route; the default value is Fastest route. If you want to use the shortest route, you have to modify this field. If the field was already set to Fastest route before Google Maps was used, this value will now also be used. Maintenance > Repository > Determine travel distance collectively (Reisafstand collectief bepalen) The transition from Google Maps to Webservices does not result in automatic recalculations. If you want the travel distance for the entire company to be recalculated to ensure everyone uses the same route calculation, you can have the travel distance determined collectively. Company > Location If there are foreign locations and you want to include these in the automatic travel distance calculation, the Country field must be entered correctly. 2.  Configurate traveldistance calculation – Additional Rounding option (change 530662) Why If you have the commuting distance calculated by Payroll Business automatically, you can now also round the travel distance up to whole kilometers. How Management > Repository > Stuurgegevens reisafstandsbepaling (Travel distance calculation parameters) The Rounding up (whole kilometers) option (Afronden naar boven (hele kilometers) has been added to the Rounding travel expenses commuting km field (Reisk. Afronding km woon-werk) in the Configurate traveldistance calculation screen. Your action Management > Repository > Determine travel distance collectively (Reisafstand collectief bepalen) If you want to use the new option, Payroll Business has to re-determine the commuting distance of all employees. To enable this, you have to specify the required Reference date in the Determine travel distance collectively screen: 1-1-2019 or later. 3.  Travel distance calculation – Block until address changes Why If you had made deviating agreements about the travel distance calculation, or had consciously opted for calculating the one-way trip distance yourself, you could only select No in the Automatisch route berekenen (Calculate route automatically) field in the employee’s Travel expenses screen. As a result, no calculation would ever be made until you changed the field to Yes. As of this release you can have the travel distance calculated automatically when the address of the branch or of the employee changes. How Employee > Terms of employment > Terms of employment > Travel expenses The No, until address change option (Nee, tot adreswijziging) has been added to the Calculate route automatically field (Automatisch Route berekenen) in the employee’s Travel expenses terms of employment screen. When you select this option, the number of kilometers you have specified yourself will be used until the address of the location or of the employee changes. When one of these addresses changes, the No, until address change value in the Calculate route automatically field will be automatically changed to Yes. Your action When you want to use the No, until address change option, you can specify this in the Calculate route automatically field in the employee’s Travel expenses terms of employment screen. 4.  OE code displayed in the organizational structure Why When improvements to the workplace were identified – in lean terminology referred to as the Gemba walk – it was specified that the names of the organizational units were often very similar. This applies in particular to companies with a large organizational tree structure. It is, therefore, preferable to not only display the organizational unit’s description, but also its code. How Management > Repository > Organizational structure > Organizational units When the organizational tree structure opens, you will now see the description of the organizational units followed by a code in between brackets, for example Business Unit Amersfoort (10001).  Your action No action is needed. Resolved notifications 5.  Empty lines in collective leave report (change 431045) Message Company > Leave > Collective leave Sometimes empty lines were included in the report that was generated when entering collective leave. This was due to the fact that a collective day of leave was assigned to employees who were specified as being employed in the future. It was impossible to retrieve the name of such an employee, resulting in an empty line.  Solution The software has been modified. As of this release the names of employees not yet employed are also included in the report for whom a collective leave deduction in the future applies.  Your action No action is needed. 6.  Workflow could not be linked to active notification (change 1289064) Message Management > Active notification When linking a workflow to active notifications, an error message was displayed and linking was no longer possible.  Solution This problem has been solved and the workflow can be linked again as usual. Your action No action is needed. 7.  Leave - Leave date in overview and registration of double hours when not settling (change 1155337)  Message Sometimes double hours were displayed in the Not settled column (Niet verrekend) where leave was concerned that should not be settled. An employee had booked 8 leave hours that should not be settled. However, the overview stated a balance of 16 hours that should not be settled. Solution Employee > Leave > Leave balance  This problem only concerned the Not settled column (Niet verrekend) and has been solved. Your action No action is needed. 8.  Leave requested, other hours than expected are processed (change 1236776) Message Leave request through HR Self Service When leave was requested and a start and end date were specified as well as the hours, half of these hours were booked per day, and 24 hours on the last day of the leave period. This was due to the fact that the work schedule was created twice and the hours were, therefore, divided across both schedules. Because an end date was specified as well as the required leave hours, the remainder of the hours was allocated to the last day of the specified period. (With a maximum of 24 available hours per day.) Solution The software has been modified as of 1 January 2019 and no more double work schedules are created. Your action No action is needed. Publishing Date : 3/22/2019

Notifications Translated screens Some of the HR Core Business and Payroll Business screens have been available in English and German so far. However, we are receiving more and more requests to make the application fully available in other languages. In the course of this year, we plan to translate more screens: HR professional screens will be translated into English, German and French. Screens for payroll professionals and other users will be translated into English. As of this release, a large part of the screens of the Employees menu has been checked and translated. The other menu options will follow in the coming releases. Once this menu is fully translated, we'll let you know. Note Some fields have a list of values defined at the Client or Company level. In this case, you administer the list and the translations. You can maintain the list at Settings > Recording > List of values  New New field - No Risk Policy applies Why To make the WAO/WIA registration easier, we have added the No Risk Policy applies field to the WAO/WIA registration screen as of 1-1-2021.  How Employee > Illness > WAO/WIA registration. You can enter yes or no in the No Risk Policy applies field. The field is also included in the data integration package for upload to Medical Leave Management. Action No action is required.  Modified and Improved  Employees with the same Start and End date of employment were not sent to Youforce Portal (1631185) Why If an employee was given the same End of employment date as Start of employment date, the End of employment date was not sent to the Youforce Portal. As a result, the End of employment date did not appear in the underlying systems. How As of this release, if you enter an End of employment date for an employee that is the same as the Start of employment date, the End of employment date will be sent to the Youforce Portal and then on to the underlying systems. Action Management > Data exchange > Portal Management Redeliver (employee) To ensure that the data (in this case the End of employment date) is the same in HR Core Business and the Youforce Portal, you can resubmit an employee’s data to the Youforce Portal with the Portal Management Redeliver (employee) function. This will also update the underlying systems such as Management Information. From the June release you can use this link for both the V1 and the V3 link. Digi-ZSM - Report of illness at 42 weeks sometimes not sent to UWV (2594769) Why The report of illness at 42 weeks was not always sent to UWV. How This issue has been resolved. The report is now sent to UWV as usual. Action No action is required. Performance - Occupancy overview in HR Self Service (2705936) Why When requesting the occupancy overview in HR Self Service, it sometimes took an inordinate amount of time before the information was displayed, or it was not displayed at all. How We have implemented improvements in collaboration with HR Self Service so that the information is displayed faster and the screen no longer freezes. Action No action is required. Solved Messages Leave reports in Management Information not aligned with HR Core (2608937) Message  The leave data in the reports in Management Information (MI) occasionally differed from the leave data in HR Core. This was because the leave data was not properly transferred to the MI reports. Solution We provided a solution for this issue on 29 April 2021. See Action what you need to do to ensure that the MI reports show the correct leave data. Action Settings > Grant leave entitlement > select Correct current leave year You must correct the current leave year at company level in HR Core Business to ensure that the MI reports contain the correct leave data. When you correct the current leave year, the data for all previous years will also be corrected. Keep in mind that it may take some time before the current data is available for consultation in the MI reports. It is not possible to grant parental leave in the leave scheme (2695815) Message  Prior to this release it was possible to check the Parental entitlement field for different types of leave within one leave scheme. However, upon saving, the system froze and the change was not saved. Solution From this release, a message will appear if the Parental entitlement field is checked for another type of leave within the scheme.  Action No action is required.  Type of illness in Sick leave screen did not match help text (2713858) Message The list in the field Type of illness did not correspond to the types of illness in the help text on the Sick leave screen. Solution The help text has been adjusted so that the correct values now appear in the explanation of the Type of illness field.  Action No action is required. Leave entitlement cutback - reason not available (2726639) Message It was not possible to record the reason for reducing leave in the Cutback leave rights screen.   Solution This issue has been resolved. You can now indicate the reason in the Reason leave entitlement cutback field in the screen mentioned above.   Action To ensure that the correct reasons appear under Reason leave entitlement cutback, you must choose the value again at Settings > Recording > List of values. After this, you can save the cutback of leave entitlement with the correct reason. Publishing Date : 5/21/2021

Notifications Online release sessions The first release session was organized on Tuesday, March 2 as part of a pilot to explain the March release in more detail. The pilot will be continued during the coming months and a one-hour info session will be arranged in the week following the release to further explain the most important changes. We will devote extra attention to what you, as a customer, need to do in order to get the most out of modified or new features. We hope that this will clarify the Release Notes and the Actions listed for some of the changes. The second release session following the April release will take place on Tuesday, March 30, at 14:00 (CET). We will let you know how to sign up for the release session via the Community as soon as possible. You can also contact your Customer Success Manager. New Job information screen - new Job category field Why It may be useful to indicate which jobs have much in common, which is why the April release will include the new Job category field in HR Core Business.  How Settings > Formation and Organization > Job information As of 1 January 2021 the Job information screen includes the Job category field. It can be used to specify the category a specific job belongs to. The possible values can be specified using the List of values function.  Settings > Recording > List of values > Job information The Job category list of values has been added to the Element field list in the Job information screen. Jobs can be clustered more easily through this list of values. Note: there is no interdependency between the Job category and Job values. The new Job category field will also be added to the Recruiting API that is being developed.  Action If you want to use the new feature, you can create a list of values. If you do not want to use this feature, you need not do anything.  Employee (supplementary) screen - new Candidate ID (ATS) field  Why As of this release the new Candidate ID (ATS) field is available for registering details about the recruitment of an employee.ATS stands for Applicant Tracking System, a generic name in recruitment systems. How Employee > Employee > Employee (supplementary) As of 1 January 2021 the Employee (supplementary) screen in the April release includes the Candidate ID (ATS) field. This is a free field for registering how an employee was recruited (max. 50 characters). Action No action is required.  Sick leave screen - new fields in Additional information tab  Why As of this release the Additional information tab includes two new fields for registering information about sick leave. How Employee > Illness > Sick leave The Additional information tab in the Sick leave screen includes two new fields: Action list: The corresponding list of values can be maintained per client. Brief note: An alphanumeric field for the input of text (max. 100 characters). Settings > Recording > Free fields Create the fields by selecting Settings > Recording > Free fields. These fields can then be selected for all screens and added using Settings > Recording > Expand screen. All the added extra fields are included in the Extra information panel. The new fields are included in the MLM domain API. This means that the fields can also be used in Medical Leave Management. Action No action is required.  Solved Messages Updating person fields when creating a new employee Message When creating a new employee where the person layer has been activated and the person has already been created, the following may occur: If a person had been created with, for example, House number suffix and a new employee was created without House number suffix, the House number suffix was sometimes not removed for that person. Solution This has been resolved. The fields are now correctly updated when a new employee is created. Action No action is required. No scrollbar in Expand screen function (change 2511657) Message Settings > Recording > Expand screen When the number of screen elements added through the Expand screen function is so large they cannot all be displayed on the screen, no scroll bar was available to view the remaining added elements. Solution Following this release, a scrollbar is displayed when there are more elements that can be displayed on the screen.  Action No action is required. Leave balance incorrect (change 2591261) Message Sometimes the leave balance was set to 0 following recalculation. Solution This has been resolved as of this release.  Action No action is required. Leave year presentation error (change 2486514) Message Settings > Leave > Grant leave entitlement Sometimes the leave year was presented incorrectly when executing the New leave year action. Solution This has been resolved; as of this release the leave year is presented correctly again.  Action No action is required.

Announcement Together towards a better performance The stability and performance of Self Service is not on the level you may expect. The professionals (PSA users) in particular may be affected by this. Reliability of our products / applications is very important to us. For this reason we are working intensively with a number of our cusomers to improve this. In the Self Service release notes a new chapter is added: ‘Together towards a better performance’. In this chapter we will inform you about the improvements we are implementing as to stability and performance. In the recent past the following enhancements were achieved. The usage of databases is optimized, making it possible for more traffic to be handled at the same time.  We moved to a new version of the database. This new version is able to handle traffic faster. Monitoring of all databases is improved. This enables us to anticipate and react to possible changes in data traffic in an improved manner. Specific processes concerning the reporting of performance issues were aligned with a number of customers. By being in direct contact with our customer we get more insights in user experience and this contributes to identify and handle the specific causes of underperformance. These steps will lead to an improved user experience. The coming period we will continue to take more steps towards a better performing product. It is possible that you will occasionally experience hindrance. We are working hard to minimize this as much as possible. Publishing Date : 8/23/2019

Notification Unique Personal Id mandatory Why  As you will have read in previous release notes and in the interim update, the Unique Personal ID (UPI) will become mandatory. Initially, this will only apply to: users of the new solution for Medical Leave Management users of the generic API for Identity & Access Management (IAM) in combination with the Youforce users extended interface. The UPI is not yet mandatory if you only use the Youforce users extended HR interface without the other interfaces mentioned above. How  Settings > Data exchange > Raet HR interfaces > Youforce users extended  An additional option will be made available to users of the interfaces mentioned above. This option will force UPI submission to the Youforce portal.  Your action  No action is required. If you are going to use one of the applications mentioned above, Visma | Raet will contact you to set up the correct settings.  New Application feedback Why In the previous release notes we informed you that the Customer Effort Score will be launched starting with the September release. When a specific procedure has been performed, a closed question will be displayed concerning the procedure. This enables you to provide us with feedback on new functionalities. This feedback in turn enables us to introduce process improvements.   How As of the September release, a closed question will be displayed when the following actions are performed: Employee > Employee > GDPR - Delete personal data – when the Delete button has been clicked. Employee > Inflow/outflow > Proposed transition payment – when the Save button has been clicked. The question is: How easy was it for you to complete this task or action? You can answer this question by assigning a score. Based on your score, you will then see a follow-up question: Score of 1-5: What can we improve to make it easier to perform this task/action?Score of 6-7: What did you find easy about performing this task/action? Your action Please provide an answer when you see a question about the use of the application. In this way we can assess your opinion on certain processes and screens, enabling us to focus on targeted improvement. Personal data available at the Person level Why It is becoming increasingly necessary to distinguish between personal data and employment data in interface applications such as Medical Leave Management and Talent Management. A combination of this data at the employee level has always been available in HR Core Business.  However, it is not only necessary to request personal data from the interface applications, but also to enter personal data from those applications. For example, a change of address for employee A also applies to copies of employee A in other applications. In the new Person level, specific personal data, such as address data, can now be synchronized with other employees, regardless of whether these employees work for the same company. The employees must belong to the same client, however.  Initially, the new Person level will only be available for clients switching to the new solution for Medical Leave Management or the generic API for Identity & Access Management (IAM) in combination with the Youforce users extended interface. In the future, it will be available in more interface modules.  How Employee > Person > Person The Person screen will be added to the menu. Once the Person level is available, a person will be generated based on the Unique Personal ID (UPI). The UPI will ensure that employees with the same personal data will be linked to the same person. If you then change any of the following data for one of the employees, the change will not only be implemented for the person, but also for any other linked employees. The Person screen shows the basic data of all employees linked to the person: Person code * Initials * Formatted name Prefixes Surname * Date of birth * Example: Employee 100, A. Apple, and employee T100, A. Apple, both have UPI 100 and are therefore linked to person 100, A. Apple. Employee 100's address is changed to Lindenlaan 8 in Amersfoort. This means that the address of person 100, A. Apple, will be changed to the same new address. The address of employee T100, who is also linked to person 100, will also be changed immediately.  This personal data synchronization applies to the following data elements: Data element   Initials Personal email address First and middle names Personal phone number First name Cell phone number Surname Office phone number Prefix Street Formatted name salutation House number Own name code House number suffix Partner's name Location description Title (prefix) ZIP/Post code Title (suffix) Town/city: Gender Country of residence Date of birth Foreign region Place of birth Street (postal address) Country of birth House number (postal address) Language House number suffix Date of death Postal address location description Citizen service number (BSN) ZIP/Post code (postal address) PING ID City/town (postal address) Nationality Country Email address Foreign region New screen for Unique Personal ID changes Why The Unique Personal ID (UPI) will serve as the unique key for generating a person from employees. The UPI will then be distributed to other applications. For example, the generic API for Identity & Access Management (IAM) will use the UPI as a unique key to recognize users and associated authorizations. Any changes to the UPI can therefore have major consequences. A modified UPI may disable the authorization of a person, and therefore the associated employee. Great care must therefore be taken when making any changes to a UPI. A separate screen is available as of this release for specific situations where a UPI change is unavoidable, such as registering an incorrect UPI. How Management > Data exchange > Modify UPI The Modify UPI screen is available in HR Core Business as of this release. The screen is available as of 1 January 2020, and it includes the following fields: Update UPI If you choose Yes, the UPI will be updated with the employee code. Unique Personal ID (UPI) - You can enter a UPI here. Note: if you have selected Yes for Update UPI, this field will be inactive. Employee > Employee > Employees You can save the UPI in the wizard screens Create Employee - Step 1 of 6 - Employee and Create new employee with profile group. However, once it has been saved, you can no longer change the UPI on the Employee(s) screen. You will have to use the Modify UPI screen. Your action Activating the Person level will be part of an implementation project for the applications mentioned above. Visma | Raet will contact you if this applies to your organization. The UPI must be completed when the Person level is activated.  Modified and improved GDPR - Delete employee screen name changed Why  User feedback has revealed that the name of the GDPR Delete employee screen is confusing. It suggests that an employee can be fully deleted, even though this screen is used only for deleting personal data. We have therefore decided to change the name of this screen.  How  Employee > Employee > GDPR Delete Personal Data As of this release, the name of the GDPR Delete employee screen has been changed to GDPR Delete Personal Data.  Your action No action is required.  State/Province added to Employee Address Details screen Why  An employee's state/province may be needed for various purposes. It may be useful to record the federal state (Germany) or the region (Belgium) of employees working in those countries, or the employee's province in the Netherlands (or other relevant sub-regions). You can also use this field for compiling reports. The state/province field has been added to the employee's address data screen for this purpose, and you can define values for this field in a values list.  How  Employee > Employee > Employee address details As of this release, the state/province field has been added to the Employee address details screen.   Settings > Recording > List of values The state/province element has been added to the Element field list. You can define your own values for the state/province field in this list.   Your action If you wish to use the new state/province field, you must first define values in the corresponding list.  Solved Message Problems opening free screens (change 1898805) Message  When selecting a free screen in the menu, the screen sometimes failed to open. This was because all employees with data in the screen were first loaded.  Solution  As of this release, you can now select an employee after selecting the free screen. This means you no longer have to wait until all employees have been loaded. Once you select an employee, the screen opens immediately.  You can still opt to open a free screen in the old way and not select an employee. If you do so, all employees with data in the screen will be loaded.  Your action No action is required.  Publishing Date : 8/21/2020

This document describes the new functionality and improvements introduced by this release. Some of these changes have been inspired by messages and reports from customers. Where relevant, we have included a number in the section title to refer to the identification of the message (change .....) in question in our system. Verbeteringen Betrouwbaardere levering van gegevens voor de HR Data Feed Waarom Veel van onze klanten vertrouwen op de HR Data Feed voor de levering van operationele gegevens voor hun ERP-, CRM-, Procurement-, Fleet Management- of Identity and Access Management-oplossingen en hun financiële oplossingen. Het is gebleken dat de hoeveelheid gegevens en het gebruik van de HR Data Feed steeds intensiever wordt en dat dit van invloed is op de verwerking en tijdige levering van bestanden. Dit willen we graag verbeteren. Daarom hebben we een aantal extra stappen ingevoegd om het verwerken van gegevens en het afleverproces te verbeteren en ervoor te zorgen dat gegevens vóór 06.00 uur 's ochtends beschikbaar zijn. Hoe In komende releases worden verbeteringen doorgevoerd om tijdige levering van gegevens in de toekomst te garanderen. Uw actie Er is geen actie nodig. Opgeloste meldingen Rapportmodel en HR Data Feed zijn uitgebreid met meer dan 130 nieuwe velden (change 1023780, 1027135, 1030221, 1030249, 1030391) Waarom We hebben het rapportmodel en het HR Data-model uitgebreid voor een beter gegevensbereik, door meerdere klantaanvragen tegelijk te groeperen.  Hoe Toevoegingen Alle velden voor de entiteit Garantie Loon zijn toegevoegd Er zijn twee velden aan de entiteit Overuren toegevoegd (G) Uren tijd/tijd extra (Overuren) (L) Uren tijd/tijd extra (Overuren) Velden voor Toeslagen Vast Uitgebreid toegevoegd Veld Z5 en verder Er zijn twee velden aan de entiteit Medewerker toegevoegd UPI Contract volgnummer Er is een veld aan de entiteit Rol Toewijzing UM toegevoegd Het veld Incl onderliggende OE’s Uw actie Er is geen actie nodig. Gegevens in standaardrapporten R-AL-10300 en R-AL-10320 komen niet overeen (change 999473) Melding Wettelijk verlof van vorig jaar ontbreekt in rapport R-AL-10300. Wettelijk verlof van vorig jaar wordt weergegeven in het standaardrapport R-AL-10320. Na analyse is gebleken dat Wettelijk verlof van vorig jaar niet wordt weergegeven in rapport R-AL-10300 vanwege een vervaldatum. Oplossing Het rapport is gewijzigd. Vanaf deze release worden in het standaardrapport R-AL-10300 dezelfde gegevens weergegeven als in het rapport R-AL-10320. Uw actie Er is geen actie nodig. Publishing Date : 1/31/2019

Notifications Menu adapted - Inflow changed to Inflow/Outflow Why Adding the menu option Proposed transition payment and the wizard Copy employee - Transition payment  means that outflow processes are now supported via the Inflow menu, alongside the inflow processes. With the January 2020 release, the name of the menu item has therefore been changed from Inflow to Inflow/Outflow. How Employee > Inflow/Outflow The name of the menu item has been changed. Your action No action is required. Resolved notifications Incorrect presentation of leave - Leave exceeding the annual limit was booked in the old year (change 1888123) Notification While Leave Year 2019 was still active, leave from 2020 was sometimes taken. These deductions were recorded in the Settled column for 2019. However, when the new year was created, these deductions were also processed in the new year, with the transferred hours also being reduced by this amount. Only after the recalculation of the previous year were these deductions correctly processed and entered in the Settled column for 2020.   Solution The time at which leave is taken determines how the leave is booked and provides the basis on which HR Core Business recalculates the relevant leave years. From now on, leave booked for 2020 while the 2020 leave year has yet to be created will be debited as soon as the leave balance for leave year 2020 becomes available. In other words, it will no longer be initially debited from the 2019 balance. Leave booked in 2019 will be debited from the 2019 leave year. Leave booked in 2019 while the 2020 leave year is already available, will be debited from the balance of the 2019 leave year. Any balance carried forward from 2019 to 2020 will be reduced by this amount. In the event of leave being booked in previous, inactive years, make sure that all previous years are automatically recalculated. Your action We advise you to remove leave year 2020 by using the action Undo current leave year. The actual leave year will be 2019 again. Here you can calculate the leave balance again by using the action Current leave year correction. After finishing this action you can create the leave year 2020. Authorization group - new authorization group not immediately visible (change 1418078 ) Notification When a new authorization group was created, this new group was not immediately visible and could not be assigned. This was because HR Core Business always checked whether an authorization group was available on the first day of the current period and only then displayed it on screen. Solution The checking procedure has been changed. HR Core Business now reviews the entire (current) period to see which authorization groups are available and which should, therefore, be displayed. Your action No action is required. Problem saving email addresses that contain uppercase letters (change 1924212) Notification Saving an email address that contained an uppercase (i.e. capital) letter was not possible because it was not seen as a valid entry. This was due to a new validity check for email addresses. Solution The check has been adapted so that you can simply save email addresses that contain uppercase letters. Your action No action is required.   Publishing Date : 2/21/2020

Announcements We have adjusted the june release notes.    Easycruit fields added to the 'Aannemen kandidaat' form On the form 'Aannemen kandidaat' (Accept candidate) there are now 5 fields on the "Aannemen kandidaat" form which are filled in with a (correct) value from Easycruit. However, with the import we are getting a mismatch with Self Service fields because the layout of the self-service fields differ from that of Easycruit. These values on those 5 fields are causing an error message on the form. These error messages are not acceptable. That is why we have decided to remove the automatic filling in of these 5 fields. This will take place in the July release. it's concerning these 5 fields: Gender (Geslacht) Salutation (Aanhef) Nationality (Nationaiteit) Marital Status (Burgerlijke staat) Country (Woonland) New Add attachments in recruitment process All Self Service We have a new functionality available to add attachments from Easycruit. After selecting a candidate, the user can add attachments, with a few clicks, from Easycruit to the Self service process and can now be redirected to the personnel file.  In the July release we will add 2 improvements into this process:  All attachments shall be default selected when entering the form "Kandidaat aannemen" to reduce the step to go back; After clicking on the button "Kandidaat aannemen" you get a message: ""Please note! If you press the" Accept candidate "button, you cannot go back to add attachments from Easycruit." Until the July release these instructions are the way to add the attachements from Easycruit: When a user is in the form 'Aannemen kandidaat', the user can click on the 'paperclip'. A selection screen with all available attachments will now appear. You can select or deselect each attachment on the screen. After clicking on the OK button, the user sees the selected attachments. The user can go back by clicking on the paperclip, to adjust the selection. The selected attachments are processed within the (re)hire process. The user can continue with the (re)hire process by clicking on the button: 'Kandidaat aannemen'. Modified and improved Easycruit fields added to the 'Aannemen kandidaat' form The new fields are placed on the existing 'Aannemen kandidaat' form and are immediately visible and are linked to the corresponding Rubric codes of the HR Core systems. You do not have to take extra steps. We have added the following fields to the 'Aannemen kandidaat' form. The data for these fields is provided by Easycruit: E-mail (E-mail) Telephone (Telefoon) Mobile phone (Mobiele telefoon) Solved changes Rehire: error message when searching for employee (change 1512580) Problem In one specific case, an error message appeared during employee searches. Solution As from this release, the error will not occur anymore. '500' errors in Start menu and no buttons inside a workflow (change 1443182) Problem Clicking the Start menu causes an error message to appear.  Solution As from this release, the error will not occur anymore. Error in rounding totals to exactly zero in spreadsheet (change 1354358) Problem There are some values that are very close to 0 (for instance, 2.2204460492503131E-16 or -2.2204460492503131E-16). Because of the way computers run calculations, the result of 1.1 + 0.6 -1.7 is not exactly zero (0). In this case, the value shown on the spreadsheet could be 0.00000000000000022. The problem is that we are not using twice the value of 0.00000000000000022. Instead, we are changing the value to string (treated as text), which results in 2.22.  Solution Our software will now convert small values like 0.00000000000000022 to valid values, according to the rubric (the decimal property). Note: There is a limit, and values below 0.00000000000000000000000000001 will be converted to 0.00.. Publishing Date : 5/31/2019

New Reason for end of employment now also mandatory when importing external changes and using HRSS Why As of January 2020 the reason for end of employment has to be specified within the context of wage tax return and pension return. As of the February release it was already mandatory to provide a reason in the End of employment reason field in the Employee screen. When no reason is specified, the data in the screen cannot be stored. However, if an employee’s end of employment was specified by importing an end of employment date using, for example, Import/export > Import CSV, external links using Batch input or changes through HRSS, the availability of an end of employment reason was not checked. As of this release the system checks whether an end of employment reason has been specified when importing an end of employment date using the above-mentioned files. When no end of employment reason is available, the file will not be processed to prevent incorrect returns. How When a file that is imported contains an end of employment date, the system checks if the end of employment reason is also available for the employee concerned. If no end of employment reason is available, this will be reported and the whole file will be rejected. Your action When changes regarding an employee’s end of employment are not entered using the Employee screen in HR Core Business but through an interface or HRSS, you must modify the interface or HRSS form to be able to continue to use the change flow. Changed and improved New leave year included in overview Why When a new leave year was assigned, it was not included in the overview. The leave year to which the actions Correct current leave year and Undo current leave year applied was displayed. As of this release the leave year to which the New leave year action applies is also displayed. How Settings > Leave > Grant leave entitlement When a leave year is assigned through the New leave year action, the leave year is displayed when the action has been performed. When assigning leave has not been completed yet or has failed, no leave year is displayed. Your action No action is required. Solved Messages User is created in portal for inactive employee (change 1655273) Message When an employee’s end of employment was reported and the organizational unit was unlinked, a new user was created in the portal. The reason was that the change regarding the employee’s organizational unit resulted in new provision of details to the portal. Solution The software has been modified. When the organizational unit of an inactive employee is unlinked or modified, no details are provided to the portal. Your action No action is required. Employee data cannot be changed due to date of birth in the future (change 1834761) Message When entering employee data, a date of birth in the future was specified and stored by mistake. When the screen was reopened, it was blank and the date of birth could not be corrected. Solution The date of birth has been corrected by importing the correct date of birth. As of this release the system checks if a date of birth is in the future. Such dates can no longer be stored. If you enter a date in the future, the following error message will be displayed: Geboortedatum - Een toekomstige datum is niet toegestaan. (Date of birth - A future date is not allowed.) Your action No action is required. Leave balance 2019 could not be exported (change 1924008) Message It was not possible to export all the leave entitlements of 2019 of employees because the Export button was not available when another year was selected. Solution This has been modified and the leave entitlements can be exported again. Your action No action is required. Leave overview of previous years could not be exported (change 1169353) Message It was not always possible to export an already closed leave year from an employee’s leave overview; the opened year was exported instead. Solution We have ensured that when exporting previous leave years the correct data of the correct year is exported. Your action No action is required. Publishing Date : 3/19/2020

This document describes the new functionality and improvements introduced by this release. Some of these changes have been inspired by messages and reports from customers. Where relevant, we have included a number in the section title to refer to the identification of the message (change .....) in question in our system. Improvements Improving reliability of delivery for the HR Data Feed Why Many of our customers rely on the HR Data Feed to consume operational data to drive their ERP, CRM, Procurement, Fleet Management or Identity and Access Management Solutions and Financial Solutions and our monitoring shows we have been experiencing rapid growth of data and usage of the HR Data Feed which is impacting our ability to process and deliver the files in a timely manner. We wanted to improve this, so we have executed on several steps to improve the performance of processing all data, improve the delivery process and make sure that they become available before 06:00 am. How Additional enhancements and improvements further guaranteeing timely delivery are planned for the future and will follow in subsequent releases. Your action No action is required. Resolved notifications Report Model and HR Data Feed have been extended with more than new 130 fields (change 1023780, 1027135, 1030221, 1030249, 1030391) Why By packaging multiple customer requests simultaneously we have extended the report model and the HR data model to provide better data coverage. How Additions All fields related to the Garantie Loon entity have been added Two fields from the Overuren entity have been added (G) Uren tijd/tijd extra (Overuren) (L) Uren tijd/tijd extra (Overuren) Fields from Toeslagen Vast Uitgebreid have been added Fields Z5 and further Two fields from the Medewerker entity have been added UPI Contract volgnummer A field from the Rol Toewijzing UM entity has been added Field Incl onderliggende OE’s Your action No action is required. Data displayed in the standard reports R-AL-10300 and R-AL-10320 do not match (change 999473) Message In report R-AL-10300 there is Wettelijk verlof of last year missing. In the standard report R-AL-10320 the Wettelijk verlof of last year is actually being displayed. Analysis confirmed that Wettelijk verlof of last year is not being displayed in report R-AL-10300 because of an expiration date being taken into account. Solution The report has been modified, and starting with this release standard report R-AL-10300 will present the same data as presented in report R-AL-10320, Your action No action is required. Publishing Date : 1/31/2019

Solved Messages Base of employee master data - salary rounded to one decimal (2762418) Message The salary is rounded to 1 instead of 2 decimals in the Base of employee master data. Solution This has been resolved. As of this release, the salary is rounded to 2 decimals. Action This can be checked by selecting Employee > Employee > Base of employee master data. Closed organizational units wrongly forwarded to Portal (1253731) Message Sometimes the following error message was displayed in the Grouped User Management Logbook in the Portal: Role assignment Manager not processed: Organizational unit xxxxx not found. The managers of organizational units (OUs) that were already closed were mistakenly specified for the closed organizational units. Solution As of this release, no data of already closed organizational units is forwarded and the error message is no longer displayed. As a result, the Grouped User Management Logbook is more structured and any errors can be detected more easily.  Action No action is required. Employee is not forwarded to the Portal (2710118) Message Synchronization between the Person entity and the Employee was not always successful. Employees for which the Identity and/or Citizen service number fields had no value were not synchronized with the persons in question, and the employees were not forwarded to the Portal. Solution This has been resolved. The order of synchronization from the Person to the Employee is now correct and the employee is forwarded to the Portal. Action No action is required. Long-term illness and maternity leave - value of PIB date field incorrect (389486) Message Calculation of the PIB date field (Permanent Incapacity Benefit (Restrictions) Act (Wet Verbetering Poortwachter)) was incorrect when there was a period of maternity leave between two sickness registrations, as a result of which the second sickness registration was not marked as continuous. Solution A sickness registration is continuous when the period of recovery between two sickness registrations is less than 28 days. As of this release, the maternity leave period is no longer included when determining these 28 days. In the above situation, the second sickness registration is now considered to be continuous and the PIB date field will show the correct date. Action The maternity leave period is now considered where new sick reports are concerned. Already registered sick reports are not automatically modified. To ensure the correct PIB date of existing sick reports is calculated, the sick report following maternity leave must be removed and re-entered. Generating mail merge documents no longer works (2783083) Message In the Employee address details screen, the (mailmerge) indication was not visible at the aggregate fields for the mail merge address. As a result, mail merge documents could no longer be created.  Solution The (mailmerge) indication has been re-added to the following fields: Street / House number (mailmerge) (7569) Postcode / City (mailmerge) (7570) Country (mailmerge) (7568) Action No action is required. Publishing Date : 6/17/2021

New My Reports notification Why You will now receive a notification to let you know that a report is waiting in My Reports, so you can continue to work on other tasks in the meantime. How Location: Bar at the lower left of the screen > rightmost icon, Notifications A Notifications icon has been added to the bar below the menu at the lower left of the screen.  When you create a report, you will see the number 1 next to the icon as soon as the report is available in My Reports. If there are more reports available that you have not yet viewed, you will see how many next to the Notifications icon. Click on the Notifications icon to open the list. You will then see the notifications of the reports that are ready for you in My Reports, along with their creation date and time. Click on a notification to go straight to My Reports.  The notifications are cleaned up weekly, but you can also remove a notification manually by clicking on the X next to it.  Your action  No action is needed. Modified and improved Codes shown in Employment contract selection screens Why The Employment contract screen fields now show - between brackets - the code that is associated with the chosen value in order to assist users in selecting values in fields with a list or a search function (magnifying glass icon). If the values you can choose from are very similar, the codes may help to distinguish between them. How Path: Employee > Contract > Employment contract Click in a field to make a selection from a list and you will see the corresponding code in brackets after the description. If you use the magnifying glass icon to open a field selection screen, you will see that the Value column with the corresponding code has been added next to the Description column. Your action No action is needed. Notices of recovery with a date in the future are now sent to the Absenteeism Manager Why Notices of recovery entered for a date in the future were not sent to the Absenteeism Manager. How Employee > Illness > Absenteeism This problem has been resolved: as of this release, notices of recovery for dates in the future will be sent to the Absenteeism Manager.  Your action Because previously recorded notices of recovery for dates in the future will not be sent to the Absenteeism Manager, you will have to enter these again. Please delete your old notice of recovery before entering the new one. Publishing Date : 10/25/2019