Hi @Kalpa Hewavitharana, @AveTonitM , I’m little confused of this. In Case CS0073685, IFS talking about "IFS Support Portal for IFS Cloud Partners", you talking about “Service Now”, please unify terms In same case CS0073685, I’m asking if it is required have separated account for each customer, and answer was: NO, you should have one Partner Account with access to Customers, if it is not correct, what is reason of Dropdown list “Account”? Could you please check it again? Hi Filip, “Service Now” is the ticketing platform that is used by IFS to handle Support issues for IFS Cloud customers (is it a replacement of LCS case tracking system, but with different and advanced functions that are not used in LCS). "IFS Support Portal for IFS Cloud Partners" is an internal parameter that is used in Service Now platform. You do not need to worry about it at this moment.I have gone through the case CS0073685 and it seems like there is an issue with how your account is setup. This informa
Hi Toni, Please find below responses for the four questions raised. The Customer Support Portal (https://support.ifs.com/csm) was referred to as Service Now as that is the platform that IFS is using to support all IFS Cloud customers. You can follow the KBA https://community.ifs.com/support-services-faqs-282/how-can-i-register-for-an-ifs-support-account-3948 and open the Request IFS Portal Account (Cloud) FINAL.pdf for instructions Explained above Partner should create separate support accounts for each customer that they work. This should be done using a customer email address (not from the email that you have as a partner). The regular partner account will not allow you to create cases/requests for the customers in Support Portal.
Further response:IFS Cloud Version Updates: Release notes and Fixed issues for IFS Cloud Version : https://community.ifs.com/ifs-cloud-version-updates-197
Based on the questions raised here and through CS0075417, we would like to share below information as Q & A.Q: How bugs are handled in IFS Cloud?A: Bug fixes are handled the same way as for legacy products:- Issues are reported by the customers through Service Now- Evaluated by IFS Support- Passed to RnD if deemed to be problem with the core product Q: How to find the already reported BUGs for IFS Cloud?A: In the community: https://community.ifs.com/search/activity/topics?userid=155 (There are number of threads for each release and for each service update) Q: How to find already solved BUGs for IFS Cloud?A: As above - in the IFS Community. There is no separate access to list of reported and fixed bug fixes as it has been in LCS for legacy product. Q: How to report BUG for IFS Cloud?A: By reporting the problem/issue with the application in Service Now. Q: How to get correction into environment - is it possible, or only was is merge whole Service Update?A: By applying relevant Servic
Adding the error message as text so that it is visible in search.Parameter error,certificate verification failed. path does not chain with any of the trust anchors
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
