Hi Dojo,
We're working with an LCA that includes several components: a line & area chart, a grid, tables, and more.
When the app is launched, users are expected to click on a Config button, which opens an IAS. In this dialog, users can configure three different elements that are then used to filter the components mentioned above. (By passing them through output script param)
Initially, these elements were stored as variables in the user session, which worked fine—until the app was reloaded. Since session variables are not persisted, they get lost upon reload, which is not acceptable for our use case.
As a second approach, we decided to store the configured elements in a DOM instance and replace the session variables (previously of type Element) with Object Manager instance references.
Currently, we’re testing with only one of the three elements. For simplicity, I stored the element ID in the name of the DOM instance and tried using it to filter the components and queries.
This approach partially worked: it applies correctly for most components, but the Line & Area chart doesn't support filtering using the DOM object (?), so it's not functioning as expected there.
I'm getting out of ideas on how to do this.
Any suggestions?
Ana
Hi Ana,
Just brainstorming here. Is it not an option to use memory files as persistent storage?