Releases Youforce Portaal

11-08-2021 Wijziging in gebruikers details pagina nieuwe inloggen (change 2873168) In verband met meerdere reacties over foutmeldingen en/of het zeer traag laden van de gebruikerdetails voor het nieuwe inloggen, hebben we een wijziging aangebracht i...

Dit document bevat een beschrijving van nieuwe functionaliteit en verbeteringen in deze release. De wijzigingen komen deels voort uit meldingen van onze klanten. Waar het relevant is, verwijzen wij met een nummer naar ons interne systeem waarin wij meldingen van klanten (change …..) registreren. Algemene informatie Dit document bevat belangrijke aanvullende informatie voor de Youforce portal release op donderdag 4 april 2019. Gewijzigd en verbeterd Extra disclaimer in Zend en Ontvang Waarom  Wanneer een bestand goed is verzonden aan Raet, wordt het automatisch verwijderd van uw lokale systeem. De IBU handleiding waarschuwt dat u geen systeemmap of map met belangrijke bestanden moet selecteren. Deze waarschuwing wordt nu ook getoond op de pagina Zend & Instellingen.  Hoe De disclaimer is toegevoegd bovenaan de pagina Bestandsuitwisseling | Zenden. De disclaimer is toegevoegd bovenaan de pagina Bestandsuitwisseling | Instellingen. Snellere integratie van ziekmeldingen tussen BO4 Online en Arbodiensten  Waarom  In bepaalde gevallen duurde het erg lang voordat ziektemeldingen werden verzonden naar Arbodiensten (Arboned, ArboUnie, enz.). In uitzonderlijke gevallen duurde dit meer dan 24 uur Hoe Er zijn technische verbeteringen aangebracht om het exporteren van ziektemeldingen vanuit BO4 Online naar de Arbodiensten te versnellen. Deze berichten worden nu binnen 20 minuten verzonden. Publishing Date : 3/28/2019

General These release notes are for API developers only. New Renew sandbox* credentials in the API developer portal Why When sandbox credentials for the API developer portal expire, developers have to be able to renew their own credentials - without the intervention of an administrator of the developer portal -. How A new button called "Renew credentials" will appear when the credentials are expired. After clicking this button your credentials are reset.   Your action If your credentials for the API developer portal are expired the button will be shown automatically to reset them. * = sandbox is a general expression for a test environment. Here it does not refer to any specific Visma | Raet product (such as HSS Sandbox). Publishing Date : 8/15/2019

Dit document bevat een beschrijving van nieuwe functionaliteiten en verbeteringen in deze release. De wijzigingen komen deels voort uit meldingen van onze klanten. Waar het relevant is, verwijzen wij met een nummer naar ons interne systeem waarin wij meldingen van klanten (change …..) registreren. New Youforce Medical Leave Management (MLM) API Why In order to support Medical Leave Management integrations we have created a new product the public API. How The end-point will be available under: https://api.raet.com/yfo/mlm/... Your action In order to start consuming this end-point as a customer of HR Core Business Global you need to request the MLM product to your API with a ticket in 4Me Youforce National Identifiers (NID) API Why In order to support applications that need the National Identifiers we have created a new product for the public API. How The end-point will be available under: https://api.raet.com/yfo/nid/... Your action In order to start consuming this end-point as a customer of HR Core Business Global you need to request the MLM product to your API with a ticket in 4Me Identity and Access Management (IAM) documentation on the developer portal Why The new API for IAM is available and in order to consume it the documentation is now on the developer portal How Go to the developer portal (https://developers.raet.com) and go to the section API Library, here you will find the IAM documentation Modified and improved New cost center for Jumbo added Apigee made a change in the way they handle URL encoding and decoding. This forced us to update a specific solution where we filter, based on specific parameters. This bug was fixed earlier in a hotfix and we deployed a new solution last release. During the release we noticed a problem which is now fixed. In this release we will deploy the improvements Publishing Date : 12/20/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. General information This document contains important information for the Youforce portal (File Transfer) August release on Tuesday, July 30, 2019. New New IBU client version 3.9.6 available Why We have released a new version of IBU client to improve security. We strongly recommend updating IBU to this latest version. After the 30th of August old IBU versions won't work properly. How In previous versions of IBU, the encrypted password is stored in the IBU.ini file.    To improve security, we have removed the password from the IBU.ini file and stored it in Windows Credentials Manager. This new version 3.9.6 of IBU client will be available on July 31. This software supports the exchange of files between Youforce Send & Receive application and your local environment. You can download the new IBU version via the News page on Youforce Portal (see News or Publications | Youforce). Even if you are already working with the previous version of IBU, we urge you to replace it with version 3.9.6 on all your 'IBU'-devices. Most incidents regarding incorrectly exchanged files are caused by the use of previous IBU versions. See also the IBU manual available in Youforce | Publications | Youforce (News item: Send & Receive - New IBU version and manual). Your action Note: We urge you to upgrade IBU to this latest version. After August  30 old IBU versions won't work properly. Changed and Improved Modifications to IBU Server components Why We have made several improvements to improve the stability of IBU (Send and Receive) How Several IBU Server components will be updated. IBU Server will not be available on July 30th, from 18:00 to 0:00 (CET) during required maintenance to install the updates. File exchange in Send & Receive and the IBU client executable in standalone mode cannot be used during the maintenance interval either. If you have planned critical file exchanges during this period, we advise you to reschedule these activities. Please contact your administrator. Impact for IBU Standalone If your organization uses a scheduler to automatically upload files to or download files from the Youforce server using IBU client in standalone mode, you should pay special attention to the following. File exchange with IBU standalone will not work during the maintenance interval. IBU standalone will start processing files left on the client or server after the maintenance has ended, on the first automatically scheduled start afterward. If IBU standalone tries to connect to IBU server during the maintenance interval, error messages will be generated and logged. Depending on your local configuration, e-mails may also be sent to your organization's administrator. Such error messages are normal and can be ignored. If IBU server goes down in the middle of processing a file exchange, the transfer may fail. In this case, an appropriate error message will also be logged. In some cases, it might be necessary to send or receive the corresponding file manually afterward. If the requested file has disappeared from the server list, you may contact the Raet Service Desk to have it restored. If your organization would rather prevent the above-mentioned errors, you are advised to switch off your local scheduler for IBU standalone during the maintenance interval. Your IT professional can take care of this, or you may contact your Raet consultant. Solved Changes YF - Ibu standalone doesn't accept passwords longer than 14 characters: (change #4438685) Message Password policy IBU client/ standalone (filetransfer.youforce.biz)  differs from password policy for Youforce user login1.youforce.biz. In Youforce it is possible to use passwords longer than 14 characters. However, such a password cannot be used with IBU Stand Alone. IBU only accepts a maximum of 14 characters. Solution The new version of IBU now accepts passwords longer than 14 characters.  Your action Install IBU Client 3.9.6. as soon as possible.  Publishing Date : 7/25/2019

25-02-2021Organisatienaam in activatie e-mail Nieuwe inloggenWe krijgen veel feedback op de mail die gebruikers ontvangen om hun nieuwe Youforce account te activeren. Medewerkers die bij meerdere organisaties werkzaamzijn ontvangen ook meerdere e-m...

Dit document bevat een beschrijving van nieuwe functionaliteiten en verbeteringen in deze release. De wijzigingen komen deels voort uit meldingen van onze klanten. Waar het relevant is, verwijzen wij met een nummer naar ons interne systeem waarin wij meldingen van klanten (change …..) registreren. Algemene informatie Dit document bevat belangrijke extra informatie over de Youforce Portal release op donderdag 7 maart 2019. Gewijzigd en verbeterd Wijzigingen in de IBU-serveronderdelen Waarom We hebben een aantal verbeteringen aangebracht voor meer stabiliteit en betere prestaties van IBU (Zenden en Ontvangen) Hoe Verschillende IBU-serveronderdelen worden bijgewerkt. De IBU-server is hierdoor op 7 maart tussen 18:00 en 00:00 uur niet beschikbaar. Tijdens deze periode wordt het vereiste onderhoud voor de installatie van de updates uitgevoerd. Bestandsuitwisseling in Zenden en Ontvangen en de IBU-client die wordt uitgevoerd in de zelfstandige modus kunnen tijdens deze periode ook niet worden gebruikt. U kunt tijdens deze periode beter geen kritieke bestandsuitwisseling doen. Neem contact op met uw beheerder. Gevolgen voor de standalone modus van de IBU-client Als uw organisatie gebruikmaakt van een scheduler voor het automatisch uploaden van bestanden naar of het downloaden van bestanden van de Youforce-server via de IBU-client in de zelfstandige modus, moet u rekening houden met het volgende. Bestandsuitwisseling met de standalone modus van de IBU-client werkt niet tijdens de onderhoudsperiode. De verwerking van bestanden die nog op de client of de server staan na de onderhoudsperiode wordt gestart tijdens de eerstvolgende automatisch geplande verwerking. Als de zelfstandige modus van de IBU-client tijdens de onderhoudsperiode verbinding probeert te maken met de IBU-server, worden er foutmeldingen gegenereerd en gelogd. Afhankelijk van de lokale configuratie worden er mogelijk ook e-mailberichten verzonden naar de beheerder van uw organisatie. Dergelijke foutmeldingen zijn normaal en kunnen worden genegeerd. Wanneer de IBU-server tijdens de verwerking van bestandsuitwisseling uitvalt, mislukt de overdracht mogelijk. In dit geval wordt ook de bijbehorende foutmelding gelogd. In sommige gevallen moet het betreffende bestand naderhand handmatig worden verzonden of ontvangen. Wanneer het aangevraagde bestand uit de serverlijst is verdwenen, moet u contact opnemen met Raet Service Center om het bestand te herstellen. Als uw organisatie bovenstaande fouten liever wil voorkomen, kunt u de lokale scheduler voor de standalone modus van de IBU-client het best uitschakelen tijdens de onderhoudsperiode. Uw Youforce beheerder kan hiervoor zorgen of u kunt zelf contact opnemen met een Raet-adviseur. Zenden en ontvangen - Nieuwe IBU-handleiding en IBU-client versie 3.9.4 beschikbaar. Waarom We hebben ook een nieuwe versie van de IBU-client uitgebracht om de stabiliteit en prestaties te verbeteren. Hoe De nieuwe versie van de IBU-client (3.9.4) is sinds 15 februari beschikbaar. U hebt deze software nodig om bestanden uit te wisselen met de Youforce-applicatie Zenden en ontvangen. U kunt de nieuwe versie downloaden via de nieuwspublicatie op Youforce Portal (zie Nieuws of Publicaties). Ook als u al werkt met een andere versie van de IBU-client, raden we u aan deze te vervangen door versie 3.9.4 op elk apparaat waarop een oudere versie is geïnstalleerd. Versie 3.9.4 is de meest stabiele versie. De meeste rapporten over onjuist uitgewisselde bestanden worden veroorzaakt door het gebruik van een oudere IBU-versie. Bovendien is er een nieuwe IBU-handleiding beschikbaar. Alle vorige handleidingen zijn nu gebundeld in één handleiding. Hierin vindt u alle informatie over de installatie, het gebruik en de configuratie van Zenden en ontvangen. Vanaf deze publicatie zijn alle eerdere edities van de handleiding voor Zenden en ontvangen ongeldig. Er is bovendien een Engelstalige handleiding beschikbaar. U vindt de nieuwe handleiding in Publicaties Youforce | Youforce - Productinformatie | Algemene informatie. Publishing Date : 2/22/2019

General information This document contains important information for the 2019-11 release of Youforce Portal. The changes below will be deployed on the 5th of November. Identity & Access Management Option to disable login through login.youforce.biz Why  With the introduction of the new login method, it is necessary to disable the login through login.youforce.biz. This to make sure that all users are using the new login method. How To disable the 'old' login, go to Settings | Youforce Management | User settings | Manage user settings. We have introduced a new setting to the Settings of users with certificates: Disable login via login.youforce.biz for all users in the company. This will add a new authorization to all users (default is activated): Blok Aanmelden login. If you want to give users access through login.youforce.biz for a longer period you need to deactivate this authorization. What will happen All users logging in through login.youforce.biz after authentication will be presented the following message: Your company has deactivated the login through this page. Please, access through the new login procedure The link in this message will redirect to the new login page. For who This functionality has been specifically been introduced for companies transferring to the new login using Youforce accounts. For more information on this topic please go to the basic description. Or go to the FAQ list with this sort cut. Publishing Date : 10/29/2019

Modified and improved Spike arrest for authentication end-points Why In order to prevent that the authentication end-point is no longer available for others - due to overloading by one implementation - it will be protected with spike-arrest. This means that more then 100 requests per minute will be respond to a 429 error code. Action No action is needed from the developer. This response will be automatic and should not have any impact as the token is valid for 2 hours Solved Messages The API sandbox for the HR Core Business Base API was not returning data Message The people end-point is not returning data using the API sandbox Solution A new version of the sandbox is released. The connection between the gateway and the back-end is restored. All configurations have been checked and automated tests are now in place to prevent this from happening in the future. Your action If you were using the sandbox for testing in the past it is now operational again. Publishing Date : 3/20/2020

New Quota check on authentication end-point Why In order to properly protect the authentication end-point the check on quota was added. When an application now tries to request to many tokens it will be blocked and ensures that all users have a good experience. How The quota check is automatically active. Action There is only action needed if you receive a 429 response in your application. At that point you are reaching the maximum quota and you need to check the amount of authentication requests. A token has a lifetime of two hours so in general only every two hours a token needs to be requested. Publishing Date : 7/28/2020

New Developer portal documentation on the community Why We want to improve the developer experience and improve the way we can update documentation on APIs. This is why we started to move the developer portal to the community. At this time all documentation can be found in the community and everyone with access to this environment can request access to the developer section. How Please go to: https://community.raet.com/developers/ Developer portal documentation updated (IAM (users)) Why Although we are moving the developer portal to the community, we also want the existing developers portal to be up to date. One of the sections missing was the documentation about the users end-point within the IAM domain. This documentation is now added and available in the portal. How Please go to: https://developers.raet.com  Improvements Error response on spike-arrest and quota Why When hitting the spike-arrest or quota on the API up until now the response was a generic 500 response. It was unclear for you what was going on. We have improved this and when hitting these limits you will now get a proper 429 error response. Improved error response on 501 error Why The 501 error was not following our standards, we now improved the response body based our standards. Publishing Date : 2/25/2020

General These release notes are for API developers only. Bug fixes APIs People and Organization API: In a multi page call the tag for the next link was called next Delta. With this release, we prevent the renaming of the tag and it will be next link. Proxies public_yfo-authentication_oauth-provider-jwt-r2: The authentication proxy was containing a bug regarding special characters. In this release, the problem is fixed and the proxy is updated. Publishing Date : 10/25/2019

Improvements Modifications to IBU Server components Why We have made several changes to improve the stability of IBU (Send and Receive) How Several IBU Server components will be updated. IBU Server will not be available on September 29th, from 18:00 to 0:00 (CET). File exchange in Send & Receive and the IBU client executable in standalone mode cannot be used during the maintenance interval either. If you have planned critical file exchanges during this period, we advise you to reschedule these activities. Please contact your administrator. Impact for IBU Standalone If your organization uses a scheduler to automatically upload files to or download files from the Youforce server using IBU client in standalone mode, you should pay special attention to the following. File exchange with IBU standalone will not work during the maintenance interval. IBU standalone will start processing files left on the client or server after the maintenance has ended, on the first automatically scheduled start afterward. If IBU standalone tries to connect to the IBU server during the maintenance interval, error messages will be generated and logged. Depending on your local configuration, e-mails may also be sent to your organization's administrator. Such error messages are normal and can be ignored. If the IBU server goes down in the middle of processing a file exchange, the transfer may fail. In this case, an appropriate error message will also be logged. In some cases, it might be necessary to send or receive the corresponding file manually afterward. If the requested file has disappeared from the server list, you may contact the Visma | Raet Service Desk to have it restored. If your organization would rather prevent the above-mentioned errors, you are advised to switch off your local scheduler for IBU standalone during the maintenance interval. Your IT professional can take care of this, or you may contact your Visma | Raet consultant. Publishing Date : 9/16/2020

Modified and Improved Increase security of settings page in Send and Receive Why  Security of settings page in Send and Receive has been increased. Directory names will not accept the following characters anymore: ' " * < > { } ? ^ % How Directory names are validated before storing their values in the system. If any of the invalid characters are filled and the button "save" is clicked, an error message is shown informing the users that the directory name contains invalid characters. Additionally, the changes will not be saved in the system.  Your action No action is needed. Publishing Date : 3/30/2020

New IAM API (users) documentation on the developer portal Why We released the IAM API in the previous release. The general documentation was already available on the developer portal. The part that missing was how the users end-point could be used. This new section in the developer portal describes this and allows a developer to find the necessary documentation. In the near future the section IAM API and IAM API(users) will be merged into one section. How Please visit https://developers.raet.com, on this page to go to the section API library and here you will find the section IAM API (users).  Improved Extended time out on HR Core business base API Why Using the HR Core business base API we see that the use cases are growing and with it, the size and complexity of the requests are increasing. We now updated the time out to make sure that these calls can be supported and do not result in a time out for the user. How Within the service gateway, we control the settings for each API and here we increased the time out to 2 minutes Your action There is no action necessary, this time out is automatically updated for all users Publishing Date : 1/28/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. General information This document contains important additional information for the Youforce Portal release on Tuesday, June 4, 2019. Improved and modified IBU client version 3.9.5 available Why We have released a new version of IBU client to improve stability. Please install this version no later than 31 August 2019. After this date the old IBU versions won't work properly. How This new version 3.9.5 of IBU client will be available on June 5. You need this software to exchange files with the Youforce Send & Receive application. You can download the new version via the news publication on Youforce Portal (see News or Publications | Youforce). Even if you are already working with another version of IBU, we strongly advise you to replace it with version 3.9.5 on all your devices, as this is the most stable version. Most reports about incorrectly exchanged files are caused by the use of older IBU versions.See also the IBU manual available in Youforce | Publications | Youforce (News item: Send & Receive - New IBU version and manual) Your action IMPORTANT: Please install this version no later than 31 August 2019. After this date this old IBU versions won't perform properly. Differentiate the status description when files have status 3 or 12. Why From client version 3.5 on, the IBU client uses a temporary directory for downloading files. While receiving files, the data is written to this temporary directory and the status changes to Verwerkt (Processed). Only when the complete file has been received will it be copied to the final destination directory, after which the temporary file will be deleted. The status ID is then changed internally, but the status description remains the same: Verwerkt. In the Send & Receive Logbook page, both statuses will read Verwerkt. As a result of this, you will not be able to see whether or not files have been placed in the final destination directory. How The first status description has been changed from Verwerkt to Controleer. Note: We have also added a new Disclaimer to the Send & Settings page. If you only see the value Controleer, you are not using the latest version of IBU. We strongly recommend that you replace it with the latest version: 3.9.5.    Allowed IBU file masks for sending files updated Why IBU file masks for sending files are used to validate that files that are going to be uploaded have the correct name. The file masks configured in the IBU modules below are too generic. For security reasons, masks need to be more specific. How Allowed file masks for sending files have been updated for the following IBU Modules: IBU Module Module Name Old File Masks New File Masks 65 RPE Online *.* *.csv *.dat *.db *.txt *.xls *.xlsx *.xnf *.xpf 402 Zenden naar Hosted BO4 * *.7z *.csv *.dat *.doc *.docx *.dotx *.frm *.har *.log *.mon *.pdf *.pfx *.prn *.rar *.rtf *.tru *.txt *.xls *.xlsx *.xml *.zip  406 Zenden naar Hosted BO4 RPSA *.* *.csv *.dat *.msg *.pdf *.pfx *.prt *.txt *.xls *.xlsm *.xlsx *.xml *.zip 701 PB&Core * *.csv *.sha512 *.txt *.xml *.xnf *.zip     Please see the appendix "Allowed file masks for sending files" in the IBU Manual for additional information. This manual will be published on June 5. Note: Files that are recognized as unusable by the selected application (based on the file mask) are not sent and are not deleted from the source folder. In case none of the files in the source folder satisfies the mask, the below status 102 message will be shown in Send/Receive. If you receive this message, check if the correct files are in the folder. Be aware that no warning will be issued if only part of the files satisfies the file mask.  Publishing Date : 6/3/2019

Solved Changes Medical Leave Management tasks are not properly sorted in My Tasks panel (change #542883) Message From 2017 on, tasks from Medical Leave Management are presented to the responsible manager in the Tasks panel on the Youforce Portal Desktop. Per module and task type, the tasks for the manager should be listed in ascending order of deadlines, the earliest date on top. The ordering should be identical to the one used in the Medical Leave Management application itself. However, this is not the case. In the Tasks panel the ordering appears to be random.  Solution After this release, the tasks from Medical Leave Management will be properly sorted. Your action No action nee Default tabs in the portal menu bar not logical and not desired (change #428942) Change  When new user accounts are created after an import from HR Core into the Youforce portal, the new users can access the Youforce employee/manager portal. On the desktop of Youforce, they will find tiles for all modules they are authorized to use. In most cases, some of these tiles have preset tabs in the portal menu bar on top. They allow the user to work in several modules in parallel, The individual users can add and rearrange menu bar tabs via the My Settings page, option Menu Bar. Finally, their desktop and menu bar could look like this: However, the default tabs displayed for new users, have come to be considered as inconvenient. The preset tabs did not correspond to the most often used modules.  Solution For us, it is difficult to predict which modules are favored. So the preset tabs have been minimized. After the change the only default tabs are: Home: the new Home landing page for HR Core Beaufort online customers. Proforma Lite: a modest salary calculator app which is freely available for all customers Note that the default tabs will only show for users of companies that are authorized for Home or Proforma Lite. Without authorization, the menu bar may be empty initially. Of course, users can still add, arrange and delete tabs. Finally note that the preset tabs on the professional Youforce portal are different from the ones on the manager and employee portal, and they can also be changed by the user independently of each other. Your action No action needed. Publishing Date : 6/23/2020

Announcement Transition to technical protocol TLS 1.2 for IBU. Why Visma | Raet stopped supporting TLS 1.0 and TLS 1.1 for all products except for the interfaces (IBU) last 30 November 2019.  Through this adaptation Visma | Raet takes a step towards an even safer and more reliable Youforce as of 6 June of 2020. As of that date, Visma | Raet will stop supporting TLS 1.0 and TLS 1.1 for IBU as well. Transport Layer Security (TLS) is the technical protocol that takes care of an important function in the browser: encryption of data traffic between your computer and our servers. Currently, there are three prevalent TLS protocols: 1.0, 1.1 and 1.2. For now, IBU supports all three versions. The use of TLS 1.2 entails the application of the latest and safest encryption techniques. Visma | Raet will disable the older and less safe protocols (TLS 1.0 and TLS 1.1) for IBU. How Some old browsers do not support TLS 1.2. These can no longer be used to connect to Youforce as they do not use the corresponding TLS 1.2 protocol. You will have to use a newer browser. Links to and interfaces with Youforce that connect using TLS 1.0 or TLS 1.1 will also no longer function after the transition to TLS 1.2. IBU Server will not be available during the maintenance interval on 6 June, from 09:00 to 17:00 (CET). File exchange in Send & Receive and the IBU client executable in standalone mode cannot be used during the maintenance interval either. If you have planned critical file exchanges during this period, we advise you to reschedule these activities. Please contact your administrator. Your action Ensure that the links that are managed by yourself support TLS 1.2 prior to the specified date. As of 6 June of  2020, all Visma | Raet IBU interfaces will only support TLS 1.2. Impact for IBU Standalone If your organization uses a scheduler to automatically upload files to or download files from the Youforce server using IBU client in standalone mode, you should pay special attention to the following. File exchange with IBU standalone will not work during the maintenance interval. IBU standalone will start processing files left on the client or server after the maintenance has ended, on the first automatically scheduled start afterward. If IBU standalone tries to connect to IBU server during the maintenance interval, error messages will be generated and logged. Depending on your local configuration, e-mails may also be sent to your organization's administrator. Such error messages are normal and can be ignored. If IBU server goes down in the middle of processing a file exchange, the transfer may fail. In this case, an appropriate error message will also be logged. In some cases, it might be necessary to send or receive the corresponding file manually afterward. If the requested file has disappeared from the server list, you may contact the Raet Service Desk to have it restored. If your organization would rather prevent the above-mentioned errors, you are advised to switch off your local scheduler for IBU standalone during the maintenance interval. Your IT professional can take care of this, or you may contact your Raet consultant. Publishing Date : 6/4/2020

Algemene informatie Dit document bevat belangrijke extra informatie over de Youforce Portal – Release van IBU-server en ONS-connector op donderdag 7 februari 2019. Technische verbeteringen in IBU-server Wijzigingen in de IBU-server Waarom De IBU-serveronderdelen zijn bijgewerkt. De IBU-server is hierdoor op 7 februari tussen 18:00 en 00:00 uur (CET) niet beschikbaar. Tijdens deze periode wordt het vereiste onderhoud voor de installatie van de updates uitgevoerd. Bestandsuitwisseling in Zenden en Ontvangen en de IBU-client die wordt uitgevoerd in de zelfstandige modus kunnen tijdens deze periode ook niet worden gebruikt. U kunt tijdens deze periode beter geen kritieke bestandsuitwisseling doen. Neem eventueel contact op met uw beheerder. Impact IBU standalone Als uw organisatie gebruik maakt van een scheduler voor het automatisch uploaden van bestanden naar - of het downloaden van bestanden van - de Youforce-server via de IBU-client in de standalone modus, moet u rekening houden met het volgende. Bestandsuitwisseling met de zelfstandige modus van de IBU-client werkt niet tijdens de onderhoudsperiode. De verwerking van bestanden die nog op de client of de server staan na de onderhoudsperiode wordt gestart tijdens de eerstvolgende automatische planning. Als de zelfstandige modus van de IBU-client tijdens de onderhoudsperiode verbinding probeert te maken met de IBU-server, worden er foutmeldingen gegenereerd en gelogd. Afhankelijk van de lokale configuratie worden er mogelijk ook e-mailberichten verzonden naar de beheerder van uw organisatie. Dergelijke foutmeldingen zijn normaal en kunnen worden genegeerd. Wanneer de IBU-server tijdens de verwerking van bestandsuitwisseling uitvalt, mislukt de overdracht mogelijk. In dit geval wordt ook de bijbehorende foutmelding gelogd. In sommige gevallen moet het betreffende bestand naderhand handmatig worden verzonden of ontvangen. Wanneer het aangevraagde bestand uit de serverlijst is verdwenen, moet u contact opnemen met Raet Service Desk om het bestand te herstellen. Als uw organisatie bovenstaande fouten liever wil voorkomen, kunt u de lokale planner voor de zelfstandige modus van de IBU-client het best uitschakelen tijdens de onderhoudsperiode. Uw IT-professional kan hiervoor zorgen of u kunt zelf contact opnemen met een Raet-adviseur. Publishing Date : 1/31/2019