In a script DOM instances are inserted/updated. These instances are shown in an LCA table by use of GQI Query Object Manager Instances. So there’s always an update of LCA table with Fetch data nedded on new or updated DOM instances.
Hi Harald,
If the actions of creating/updating DOM instances is triggered from the LCA itself, you may be able to get a nice user experience by triggering fetching the DOM data in the table again after this user action. An example is when you have a panel that created or updated a DOM instance, you could have a close button that closes the panel and refetches the data. You could also add this as an action to the save/update button you may have.
If these creates or updates are done in the background by scripting that is not triggered by the app itself, and you want to visualize them live in the table. Then you could look into creating a GQI ad hoc data source. Within this data source, you have full control over how the data is fetched & sent to the LCA. Using the ‘IGQIUpdateable‘ you can then add real-time updates so the table in the LCA keeps up-to-date using a subscription on the DOM data.
Feel free to share some additional details on your use-case, maybe there are other ways to provide this functionality.
Hi Harald,
I see that this question has been inactive for some time. Do you still need help with this? If not, could you select the answer (using the ✓ icon) to indicate that the question is resolved?