@avan SHA-1 is certainly not secure, so we strongly recommend against lowering your system’s security level. I believe you’re on Apps10, and while I couldn’t find 100% conclusive proof in the codebase, I very strongly believe that all apps work with SHA-256 at minimum, so the better option is to upgrade your obsolete and insecure certificates (and any other infrastructure) to be standards compliant. Cheers, /Rukmal Hello, thank you very much for your reply. We do indeed use Apps10. I completely agree with you that the customer should increase the security level of his certificate. Unfortunately our customer is not able to do this in a reasonable timeframe, so we are forced to find a way to ignore the obsolescence restrictions. Do you know how to force IFS to accept the certificate as secure?
Hi, a solution I have found to solve the workaround issue when using loop/jump the same configuration is to remove the automatic value of the item “RELEASE_RESERVATION” and set it to “No”. Doing so, no longer make the article disappear after first completion. This way it is no longer necessary to use internal loops.
Hi, a solution I have found is to remove the automatic value of the item “RELEASE_RESERVATION” and set it to “No”. Doing so, no longer make the article disappear after first completion.
Hi, thank you for tour respond. Modifying the qty_picked did not solve the issue. Moreover, my article has been reserved in several locations and when using loop/jump the same configuration, the article is no more visible in the list of the articles to prepare when looping as if the article has been totally prepared which is not the case.
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.
