But this isn’t really true. In IFS Cloud it is possible to create new IALs:https://docs.ifs.com/techdocs/23r2/050_reporting/256_br_and_a/060_information_access_layer/020_create_ial/
Thanks Piyal! I also noticed that in the news presentations. That solves the problem!Thanks,Andreas
Any response from IFS on this issue?
https://docs.ifs.com/techdocs/23r1/070_remote_deploy/400_installation_options/130_add-on_cmp/pdmpro/
We have the same challenge at a customer, so any input would be appreciated! Our idea now is to create a modification to resolve this matter.
The session timeouts are defined in the Keycloak. It cannot be configured or changed from the Aurena client end. Your Managed Service Provider needs to help you with fetching current settings and making any required changes.Following are example setting of timeout parameters in the IAM configuration:"ssoSessionIdleTimeout": 7200"ssoSessionMaxLifespan": 36000"accessTokenLifespan": 3600Some more reading about this is found here: https://www.janua.fr/understanding-token-usage-in-keycloak/
@MPOS So you are not delivering this to a customer?
@MPOS I think I found a workaround for this. I noticed that the customer I used did not haven a record in page Locations. I created a new record for this customer and then it worked! I.e. it was possible to deliver the customer order and the serial object structure was created.Not sure if this (manually creating locations) is how it is supposed to be done? Some addresses where in that page which seems to have been automatically created, but not for the customer I was using.
@MPOS Thanks for the update! I will create a support case for this then.
We get the same issue in 22R2 when trying to deliver a Customer Order with a Sales Part that has Create SM Object flag enabled. Anyone who knows what is wrong?
Maybe this SU fix has caused the problem? Since the missing workflow have several script tasks where no language type has been entered.TEWF-1278 Two Script Task not executed when Language not specified NOTSET Workflow, Data & iOT Correction Added Language type validation to Workflow script tasks 22.2.3
This seems to be related to access to any RESOURCES added on Appearance Configuration Resources Page and used in the Appearance Cofiguration. Shouldn’t there be any other way to provide access to these images? We face a problem with the LTU users, since the LTUs don’t include the AppearanceConfiguration projection, and we can’t edit those LTU Permission Sets.
We seem to have the exact same issue in 22.1.1. I can’t find any fix for this in any of the released service updates (incl SU5). Has it been fixed for 22R1?
No news yet. We are looking at abandoning the Project Deliverables solution completely in this case. I was hoping for IFS to show some interest in this topic.
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.
