Several users who try to view a document that is attached to a functional object(Maintenance>Equipmen>tFunctional Object>Functional Object), the incorrect document is returned to the screen. If you check devtool output when clicking on view and download, I noticed that the wrong document details are being sent in the request GetFileStream. This issue is user specific and occurs only for few users. 1 - All users have permission set granted which should give the required access. No permission errors are shown in the process.2- If they click download, it returns the correct document3 - If they go to the document revision record, the correct document is displayed.4 - This occurs over multiple object IDs in functional object window Any idea to resolve/investigate this issue?
When logged into the Windows 2019 Jump server with a user with administrator rights, encountered an issue while attempting to initiate the IFS Excel Add-in.Upon starting Microsoft Excel and clicking on the IFS Excel Add-in icon, the Add-in launches successfully.However, when attempting to log in, encountered the following error: Web browsers are up-to-date and not working for both edge and chrome,versions installed on this jump server,Also installed WebView2, Would appreciate your insights on what could be the root cause of this issue
In APPS10 IEE you can view users by group in “Grant permission Set to User” window,simply clicking RMB > view grants by user group. If you need to revert it click RMB > view grants by user. Grouping enabled.Without grouping
The 3rd Party app trying to integrate IFS with requires that certain messages be sent as a PATCH message. Documentation for this is found here:https://developer.paychex.com/documentation#tag/Worker/operation/updateWorkerRouting address for this which is set to use the PATCH operation. The code to trigger the message is also set with a PATCH http method: Other POST and GET messages to this service work fine, so it is not an authentication issue. While testing this interface using Postman, the PATCH works fine. When sending the same request as a POST, this gives the same result that IFS does when set as PATCH: It appears that even when IFS is set to use PATCH in both the code and the Routing Address, it is actually sending it as a POST, which is being rejected by the endpoint. I have found similar post which has been closed without a conclusion.
As per customer requirement, they need Stage application DB name to be change from EXXXXXX_NEW to EXXXXXX. Is there any impact of this change on the application. Is there anything we need to configure or re-configure after updating the DB Name?
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.
