Mijn Communities
Help

Releases YouServe

Sorteren op:
29-10-2020 When start creating a new employee, the department and function table is empty (change 2323684) Self Service Education only When starting a new employee process, the department and function table is empty. This is solved now. The val...
Volledig artikel weergeven
06-10-2020 13:47 (Bijgewerkt op 01-02-2022)
  • 0 Antwoorden
  • 0 kudos
  • 250 Weergaven
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
Volledig artikel weergeven
21-08-2020 20:49 (Bijgewerkt op 31-01-2022)
  • 0 Antwoorden
  • 1 kudos
  • 236 Weergaven
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
Volledig artikel weergeven
21-02-2020 17:39 (Bijgewerkt op 31-01-2022)
  • 0 Antwoorden
  • 0 kudos
  • 232 Weergaven
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
Volledig artikel weergeven
19-03-2020 22:12 (Bijgewerkt op 31-01-2022)
  • 0 Antwoorden
  • 1 kudos
  • 228 Weergaven
Notifications Give feedback on our software Use Wootric to give immediate feedback on our software. If you work with HR Core Business - Payroll Business, we will ask you for feedback in the application starting in January 2020. We will ask you a single closed question and we will ask you to provide additional background to your answer in Wootric, an online questionnaire platform. This will help us understand your priorities better so that we can improve the planning and development of new functionality. Your answers will be completely anonymous, and we will not share the results with third parties. Changed and improved Email address verification Why Email addresses are used in related applications for handling workflows. Invalid email addresses can cause workflow disruptions. The system needs to check whether the address is valid to prevent such problems. How  Employee > Employee > Employees If you enter an email address in the Email address field, the system will check whether the address consists of a user, an @ symbol and a domain. If the email address is invalid, an error message will be returned upon saving. Your action Check email addresses for accuracy. If an existing email address has an invalid format, you will receive an error message when you save any change in the Employees screen. This will also happen when you change another field in the screen and the Email address field contains an address that does not have the required format.  Active notifications for on-call contracts Why According to the Balanced Labour Market Act, which enters into force on 1 January 2020, employers are obliged to offer on-call workers a contract after 12 months of at least the average working time over the past 12 months. This offer must be made at the latest by the 13th month. In order to take action in time, you will need a notification as the end of the 12th month of an on-call contract approaches.  How Settings > Active notification > Define notification  The On-call contract option has been added to the notification conditions. You can now define a notification specifically for on-call contracts. When defining a notification, for example, a notification 12 months after the start date of an on-call contract, select Start date (Contract) as the source date type. Then go to the Conditions tab and select On-call contract = Yes for the appropriate condition. Your action If you have employees with an on-call contract, you can define a notification that will warn you when the end of their 12th month (measured from the start of the contract) is approaching. Visma | Raet logo in reports Why The acquisition of Raet and the combined Visma | Raet brand mean a new corporate logo. Reports will feature our new logo starting with this release. How Rapporten Het Raet-logo in de rapporten is vervangen door het logo Visma | Raet. Uw actie No action is required.  Resolved notifications Export files rejected in HR Self Service files because of Enters (change 1549928)  Notification  If an export was sent to HR Self Service and it contained an extraneous Enter, for example in a note field, the file was sometimes rejected.  Solution This has been solved by correcting any extraneous Enters in a file. HR Self Service now no longer rejects the file.  Your action No action is required.  Incorrect negative leave balance following simultaneous leave requests (change 1722007) Notification If two leave requests arrived at HR Core Business simultaneously, the second request was sometimes debited from the wrong leave box, resulting in an incorrect and negative leave balance.  Solution We have reprogrammed the software. Leave requests coming from different systems are now processed one at a time. Your action No action is required.  Publishing Date : 12/20/2019
Volledig artikel weergeven
20-12-2019 16:33 (Bijgewerkt op 31-01-2022)
  • 0 Antwoorden
  • 0 kudos
  • 221 Weergaven
Notifications Grant leave entitlement report We are working on improving the operational reports. While we are heading towards the turn of the year, we are entering the period in which the HR processes regarding the granting of leave entitlement are executed. This means that it makes sense to to prioritize improving the report Grant leave entitlement. Increase of performance will be part of the improvements. Based on feedback from our users, we have determined that it is preferable to have the report Grant leave entitlement available in excel. so that it can be easily used for control purposes. Therefore, as of the December release, the report will only be available in Excel format. Should there be a need to export this report to pdf, you can do this by saving the excel as pdf.   New Integration of terms of employment Germany Why  At the companies that are remunerated by our partner Lohn AG, in Germany, the need arose for integrated terms of employment with specific data for remuneration in Germany.  How Employee > Contract > Terms of employment package > Integration Germany If, during implementation, the Visma | Raet consultant has added the Integration Germany terms of employment to the terms of employment cluster, this will be available in the Terms of employment package. The fields displayed in the Integration Germany terms of employment screen contain data that is required for remuneration in Germany, supplemented in some cases by company-specific fields. You can find more information about these terms of employment and the fields related to them in the online help. Action No action is required. Proposed UPIs report Why For applications that will make use of HR Core Business through APIs, including Verzuim 2.0 and Identity & Access Management, it is necessary to award a Unique Personal Identity (UPI) to each employee. To support you in this process, we have developed a report that shows: whether the UPI fields have been filled out whether there are conflicts related to the completed UPI fields, for example with regard to the unicity of a UPI in relation to the employee’s citizen service number (BSN) UPIs proposed by the system You can use this report to generate the proposed UPIs.  How Reports > Check > Proposed UPIs In the Proposed UPIs screen, you can specify whether you want to generate the report in Excel or CSV. Please note: if you use leading zeros for employee codes and/or UPIs and you open a CSV file in Excel, these leading zeros may be omitted. You can then specify which employees you want to see in the report under Employee selection: Conflicts only This selection only shows employees for whom there are conflicts based on their UPI and BSN, or on their last name or date of birth. No UPI only This selection only shows employees who do not have a UPI. No UPI and related employees This selection shows the employees who do not have a UPI and employees who are related to these employees based on their BSN, last name or date of birth. All This selection shows all employees.  Finally, you can choose whether or not to include comments in the report. If you enable this option, you might see comments about a work conflict, for example. The Proposed UPIs report will be available as an Excel or CSV document under My reports. The language used in the report is English, as the links the UPIs will use tend to also be in English. You can find more information and explanations about the various columns in the online help. Action No action is required. Modified and improved GDPR Delete Personal Data expanded Why In the feedback we received from our customers on the new GDPR Delete Personal Data tool, we were asked to expand the number of personal data fields that are deleted by this functionality.  How Employee > Employee > GDPR Delete Personal Data  If an employee’s personal data is deleted, the following fields will be also deleted as of this release: Employee data ·         Date of birth ·         Identity  ·         UPI Partner data ·         Partner’s last name ·         Partner’s first and middle names ·         Partner’s phone number ·         Street (employee) ·         House number (employee) ·         House number suffix (employee) ·         Postal code (employee) ·         Town/city (employee) ·         Country of residence Action The data can be deleted by using the GDPR Delete Personal Data menu option. GDPR Delete Personal Data linked to Self Service Why Before this release, personal data and workflows in Self Service that could no longer be stored under the GDPR had to be deleted manually. As of this release, when an employee is deleted using GDPR Delete Personal Data, a notification will automatically be sent to Self Service as a reminder to delete the employee data there as well. How Employee > Employee > GDPR Delete Personal Data If an employee is deleted using GDPR Delete Personal Data, the letter V (Dutch: verwijder) will appear in their Self Service profile as a reminder to delete their data. Action If you use the GDPR Delete Personal Data menu option, a notification will be sent to Self Service indicating that the employee has been deleted. UPI unicity check only for citizen service number Why In practice, especially when rehiring, you might encounter a newly hired employee whose name is written slightly differently than when they were previously employed, but whose citizen service number (BSN) already occurs in the system, indicating that they are in fact the same person. That is why the unicity check, which assesses whether a UPI is unique, is limited to the BSN. The last name and date of birth are only checked when there is no BSN available.  How Employee > Inflow/Outflow > Create employee Employee > Inflow/Outflow > Create employee with profile group Management > Data exchange > Modify UPI The UPI unicity check goes as follows: If a UPI that is entered for an employee is already linked to another employee with the same BSN, the UPI will be accepted. If a UPI that is entered for an employee is already linked to another employee with a different BSN, the UPI will be rejected, and an error message will appear. If the existing employee with the same UPI does not have a BSN, the unicity check takes place on the basis of the employee’s last name and date of birth. Action No action is required.  UPIs based on BSN for Import and Self Service Why  Since the previous release, when entering the BSN for a new employee using the Create employee or Create employee with profile group wizards, the system checks whether that BSN is already known by the client and auto-populates the Unique Personal ID field with a suggested value if this is the case. From now on, this will also happen for new employees who are added using Import or Self Service. How HR Self Service  Manage > External changes > Upload external changes file > Raet Basic document If a new employee is entered using their BSN and the system finds that a UPI already exists for this BSN, the application will auto-populate the UPI field with this UPI when importing or entering through HR Self Service. The field will remain empty until the import is completed. This means that an auto-populated UPI will not be visible while entering a new employee in Self Service. It will only become visible when the data is synchronized with HR Core Business. Action No action is required. Resolved notifications Language value does not appear in HR Self Service (change 2271307) Message For some employees, the PS10 Language heading did not appear on the form in HR Self Service. Because the language heading (i.e. the PS10) is entered as a standard value at the national level and can be overwritten at the employee level, it was not included if it was not explicitly entered at the employee level. Solution This has been resolved. As of this release, the national level is also included for each employee in the export to Self Service. Action No action is required. Publishing Date : 10/22/2020
Volledig artikel weergeven
23-10-2020 24:04 (Bijgewerkt op 31-01-2022)
  • 0 Antwoorden
  • 0 kudos
  • 218 Weergaven
New Employee with employment date in the future in Self Service Why  Users must be able to enter changes through Self Service for employees with an employment date in the future. As of this release, employees with an employment date in the future can be exported to HR Core. How Settings > Data exchange > Self Service parameters The Toekomstige medewerker verzenden (Send future employee) field has been added to the Self-service parameters screen. When Yes is selected, employees with a date in the future are included in the export. The start date of the employee data will be the employment date, meaning changes only apply as of the employment date. Changes with an effective date before the employment date will automatically be assigned the employment date as effective date. Changes regarding sickness and time off are an exception. When such changes have an earlier effective date, this will result in export failure from Self Service to HR Core. Your action If users must be able to check or change the data of employees with an employment date in the future through Self Service, the Toekomstige medewerker verzenden (Send future employee) field must be set to Yes. In addition, the Youforce users extended feature must be used to export future employees to the portal as well. Contact the Visma | Raet Service Desk; they will create a link to the portal. New leave type – Supplementary childbirth leave (WIEG) Why With the introduction of the Dutch Supplementary Childbirth Leave Act (Wet Invoering Extra Geboorteverlof (WIEG)) a new leave type was required. As of this release the leave type Aanvullend geboorteverlof (Supplementary childbirth leave) can be selected with a start date of 1st of July 2020 when assigning a new leave type to the Leave scheme. How Settings (instellingen) > Leave > Leave scheme The Leave scheme screen now includes the leave type Aanvullend geboorteverlof (WIEG) (Supplementary childbirth leave (WIEG)) at Type of leave. Click   on the right of the Leave scheme screen at Types of leave (Verlofsoorten). Select the Aanvullend geboorteverlof (WIEG) (Supplementary childbirth leave (WIEG)) leave type. Registering leave balance at Extra individual leave entitlement We recommend registering the leave balance at Extra individual leave entitlement and not at Aanvullend geboorteverlof (Supplementary childbirth leave) in the Leave scheme. The balance depends on the number of consecutive weeks an employee wants to take off. This need not be the maximum of 5 consecutive weeks. As of release 2020-06, individual leave entitlement for supplementary childbirth leave will be automatically dealt with when the child is registered. No duration specification The duration need not be specified. The 6 months duration after the child’s date of birth is not checked. Linking supplementary childbirth leave to Continued payment during leave (Uitsplitsing) Settings > Leave > Leave to Payroll (Verlof koppeling Payroll) Supplementary childbirth leave can be linked to the Continued payment during leave (breakdown) employment benefit in Payroll Business. Do so by selecting Aanvullend geboorteverlof (Supplementary childbirth leave) in the Type of leave field and next linking it to Payroll by selecting Aanvullend geboorteverlof (HRE) (Supplementary childbirth leave (HRE)) in the Verlofuren verrekening payroll (Payroll leave hours settlement) field. Registering time off entitlement and expiration date Employee > Leave > Extra individual leave entitlement The Extra individual leave entitlement screen contains the Leave entitlement field where the employee’s balance can be specified. The expiration date of 6 months following the child’s birth can be specified in the Expiration date field.  Your action If supplementary childbirth leave is to be used, register the data as specified above.  Modified and Improved  Buttons available again in the Request for leave screen Why In the new layout of the Request for leave screen, the Back button and Export button were no longer available. Clients have indicated they would prefer these to be available again.  How Employee > Leave > Request for leave When a Request for leave is opened, the following buttons are available at the top right: One step back Advanced search History Add Your action No action is required. Solved Message Removing extra individual leave entitlement (change 1901905) Employee > Leave > Extra individual leave entitlement Message When extra individual leave entitlement was registered and Fixed was selected in the Type of entitlement field, the entitlement could not be deleted. The Delete button at the bottom of the screen was no longer available. Solution This has been resolved; extra individual leave entitlement can be deleted again as of the May release. Your action Check if fixed extra individual leave entitlement is still registered that should be deleted. Publishing Date : 4/24/2020
Volledig artikel weergeven
24-04-2020 16:29 (Bijgewerkt op 31-01-2022)
  • 0 Antwoorden
  • 0 kudos
  • 217 Weergaven
Modified and Improved Person code read-only from now on Why 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). How Employee > Person > Person  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.  Management > Data exchange > Modify UPI If it nevertheless becomes necessary to change a person code, this can be done on the Change UPI screen. Action No action is required. Error message when terminating Organizational unit on start date Why 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.  How Settings > Formation & Organization > Organizational Units 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. Action No action is required. Using free fields in profiles Why 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. How Settings > Recording > Profiles 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. Action No action is required. Leave entitlement report now only in Excel Why 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. How Settings > Leave > Grant leave entitlement 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. Action No action is required. Generate work schedules processing reports and Transfer of leave entitlements reports in Excel and PDF Why 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. How Settings > Work pattern > Generate work schedules Settings > Leave > Transfer leave Entitlements 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.  Action If you want to export the report in PDF, you must change the value in the Save as field to PDF. Start and end dates added to the GDPR Delete Personal Data screen Why 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. How Employee > Employee > GDPR Delete Personal Data 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. Actions No action is required. GDPR Delete Personal Data - data to be deleted expanded Why 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. How Employee > Employee > GDPR Delete Personal Data  If an employee’s personal data is deleted, the following fields will also be deleted as of this release: contract details Position  Department  Location  Cost center Organizational Unit  details of children Child’s initials Child’s first name Gender Child’s first and middle names Memo Date of child’s death Salary slip viewer Reports > Salary breakdown > Salary slip viewer In addition, it is no longer possible to call up the salary slip of deleted individuals in the Salary slip viewer.  Actions No action is required. Manager’s employee code is now shown in the Organizational unit history Why 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. How Settings > Formation & Organization > Organizational Units 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.  Action No action is required. Solved Messages Free screens - comments regarding September release modifications (2239929) Message 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: it was not yet possible to select an employee the screen opened the entire list of employees again after the user consulted an employee or tried to cancel, which could cause a timeout Solution The following issues have been solved as of this release: Starting with this release, free screens that have been created at contract level will not open immediately with all employees, but with a blank screen. Once the screen opens, you can search by employee and employee code, just like on the free screens that have been created at employee level. If you click Cancel after opening the free screen for an employee, you will return to the first search screen and no longer to the screen showing all employees. You can then resume searching for an employee. Actions No action is required. Workflows disappear from notification definition when setting receiver end date (2180114) Message If an end date was entered in a workflow as recipient through Active notification, the other workflows also disappeared from recipients. Solution Settings > Active notification > Notification recipients  This has been resolved. The other workflows defined for the recipients remain active until an end date is entered specifically for those recipients.  Action We recommend checking for the presence of workflows and recipients. Publishing Date : 11/19/2020
Volledig artikel weergeven
19-11-2020 22:44 (Bijgewerkt op 31-01-2022)
  • 0 Antwoorden
  • 0 kudos
  • 216 Weergaven
Notifications Feedback on our application Why From the April release, we will ask you for feedback on our application through a closed question. With this you can let us know what you think of specific functionalities and whether they meet your needs. In order to better interpret the information that has now been obtained, we will ask your feedback about certain processes in the coming months by asking a few specific questions. How If you choose a user group, we will ask you to indicate by a number to what extent you would recommend HR Core / Payroll Business to others and you can also explain your answer. We will also ask a similar question after completing a process. Questions are only asked for a specific period of time for that specific functionality. Depending on the period, a question will never be asked to you more than twice and your answers will remain anonymous. Your action If you receive a question about the use of the application, we ask you to answer it as much as possible, so that we know better what you think of certain processes and screens. This allows us to improve functionalities in a more targeted manner. New Automatic entry of Unique Personal ID (UPI) with employee code Why Unique persons must be identifiable in interface applications, including Medical Leave Management and Talent Management. That is why in future the use of a Unique Personal ID (UPI) will be mandatory. This allows you to link employees with the same UPI within a customer and in the future deliver them to the Visma | Raet applications as one person. To ensure entry of the UPI is as easy as possible, the Unique Personal ID (UPI) field can be auto-populated with the employee code. If automatic generation of the employee code is opted for, this code can now also be used as UPI and the Unique Personal ID (UPI) field in the Employees screen can be auto-populated. If employee codes are used that are not automatically generated, the Unique Personal ID (UPI) field can be auto-populated with the already available employee code. Refer to Updating Unique Personal ID (UPI) of existing employees How Settings > Recording > Parameters employee code The Parameters employee code screen (where is specified whether the employee code should be generated and assigned automatically when creating a new employee) now includes the Auto-populate UPI  option. When this option is enabled, the system will also populate the Unique Personal ID (UPI) field with the automatically generated employee code. Your action If this new feature is to be used, the data in the Parameters employee code screen must have been specified as described above.  Updating Unique Personal ID (UPI) of existing employees Why When creating a new employee, the Unique Personal ID (UPI) field can be auto-populated with the employee code. To ensure the employee code can be used as UPI with existing employees so it need not be specified manually, an option is now available to auto-populate the Unique Personal ID (UPI) field with the employee code. How Employee > Employee > Employees As of this release the Update UPI  field is included in the Employees screen. This field is used to ensure the system populates the Unique Personal ID (UPI) field with the employee code where an existing employee is concerned. This is done as follows: Set the Update UPI  field to Yes. The Unique Personal ID (UPI) field then becomes read only. Click Save and refresh the screen. The Unique Personal ID (UPI) field now contains the employee code and is no longer read only. The Update UPI  field is cleared as the field has been updated. During the update the system checks if the UPI is unique to the client. Where an equal UPI is concerned, the employee must have the same last name and date of birth. If this is not the case, an error message will be displayed. Note: when the UPI is updated with the employee code through the Update UPI  field and is next overwritten manually, the overwritten value applies.  Your action No action is required. New Integration elements screen Why The specified expense policy is necessary for the link with Mobile Expense in order to indicate which expense policy applies to an employee. No additional feature in HR Core Business is required. As more data is expected to be required in the future for the various links without an additional feature in HR Core Business, a separate screen has been created for registering such employee data. How Settings > Recording > List of values As of 1-1-2020 the Expense policy list of values has been added to the Element field in the List of values screen. It can be used to define expense policies that can be assigned to an employee through the Integration elements screen. Employee > Contract > Integration elements As of 1-1-2020 the Integration elements screen has been added to the Contract menu. Through this screen the correct expense policy for an employee can be specified in the Expense policy field for integration with Mobile Expense. The available values to choose from are registered in the Expense policy list of values as described above. Your action In order to use the new feature, the list of values must be created and the correct value must be assigned to the employees concerned as described above. Solved Message Error message when importing branches of organizational units has been modified (change 1914674) Message When importing branches for organizational units, the error message Specified start date is before the employee’s employment date was displayed. This was due to the fact that the branch was linked to an organizational unit that did not yet exist on the effective date. However, the text of the error message suggested that it concerned employees. Solution The error message is a general message that is displayed when data is linked to an element that does not yet exist on the effective date. As of this release the text has been modified as follows: Specified start date (yyyy/mm/dd) is before the date (yyyy/mm/dd) of the element to be linked. Note: this message is now also included in the Self Service failure report. Your action No action is required. Publishing Date : 6/18/2020
Volledig artikel weergeven
18-06-2020 22:20 (Bijgewerkt op 31-01-2022)
  • 0 Antwoorden
  • 0 kudos
  • 209 Weergaven
Changed and improved Sector and Risk group in Digipoort for week 42 sickness notification Why Pursuant to the Labor Market in Balance Act and starting on 1 January 2020, HR Core Business and Payroll Business will no longer use the Risk Group to determine the unemployment insurance (WW) contribution. The UWV (employee insurance agency) still uses this field as an identification key, meaning they still expect to receive it.  How Although you no longer need to register the risk group in HR Core Business, we will continue to transmit it to UWV. Starting on 1-1-2020, we will fill out the following risk premium groups for a new payroll tax number and/or sector code: 07 for the employment agency sector (sector code 52) 03 for the graphics sector (sector code 09) 01 for other sectors Your action No action is required.  Generate work schedule for a maximum of two years Why Until this release it was possible to set the end date for generating a work schedule as 31-12-9999, which meant that work schedules could be generated in advance for thousands of years. This could lead to enormous amounts of work schedule data, which could inundate interfaced systems. It can also be convenient to generate a work schedule for shorter periods to conduct periodic checks from time to time.   How Settings > Work pattern > Generate work schedule  You are now required to enter an end date in the End date (max. 2 years) field. This can be up to two calendar years in advance from the Start date field. If you enter an end date that is more than two calendar years in the future, the system will not accept the date and will delete your entry in the End date (max. 2 years) field. Your action No action is required. Resolved notifications E-mail addresses with certain extensions were no longer stored in HR Core Business (change 1866682) Notification It was no longer possible to save e-mail addresses with the extension @xx.xxx.com in HR Core business, because these were not recognized as a valid e-mail address. However, it is sometimes necessary to save e-mail addresses with the extension @nl.visma.com, as well as e-mail addresses with the extension @visma.com (the extensions shown are examples). Solution This has been resolved. Starting with this release, you can once again save e-mail addresses with a @xx.xxx.com extension.  Your action No action is required. Publishing Date : 1/23/2020
Volledig artikel weergeven
23-01-2020 20:32 (Bijgewerkt op 31-01-2022)
  • 0 Antwoorden
  • 0 kudos
  • 207 Weergaven