Hi, I’m exporting lobby pages from one environment to import into another (Cloud 23.1.3). Several of the lobby pages have link list elements that use datasources on the links. When exporting the lobby page, some of the datasources make it into the export file but not all (typically more are left out than included). I have not found anything to let me know why it’s not including all datasources in the export file. The result is that the lobby page is incomplete when imported into the other environment. Has anyone else experienced this issue? Thanks!
We are currently on Apps10 UPD13 but have noticed this issue since going live on Apps 10. On occasion, a previously visible custom field (as configured in their base profile) will no longer be visible for a user. The user discovers the issue when using a saved search (link on a start page) that references the custom field. They will get an error message referencing the field name when they click the link. Here is an example: We have found two ways to correct the issue. One method is for an administrator to delete the branch for the impacted screen from the user’s personal profile – when the user logs back in the field is visible and the saved search works. The other method is to have the user re-add the field manually to their layout (e.g., via column chooser). The symptoms and resolutions suggest that something is happening to the user’s personal profile that makes the field no longer visible. The issue happens intermittently and inconsistently – not always to users that share
We are using Apps 10 UPD13 - I’ve noticed that dates displayed in an Aurena lobby element are one day off from the date in the element data source and from how it displays in the IEE preview.My example is the MY TIME AND ATTENDANCE lobby element for MY TIME AND ATTENDANCEElement Data Source preview: Element preview in IEE - dates displayed match data source: Dates displayed in the element are one day earlier in Aurena - NOTE that the click through (e.g. clicking 6/1/2022) takes you to the correct date from the data source (6/2/2022) and not the date as displayed in Aurena:Has anyone else noticed this? Does anyone know if there is a fix?
We have some Aurena lobbies that use the context substitution variable #PERSON_ID# as the default value for the page parameter so that the lobby elements are by default based on the logged on user. In Apps 10 UPD7 this works fine with no discernable performance issues. After installing UPD9 we find that use of the context substitution variable causes elements to update slower or not at all (after a long delay), but typing in the person ID restores the performance to normal. Has anyone else experienced this issue and/or does anyone know if the use of context substitution variables on Aurena pages has changed for UPD9? Thanks!
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.
