I have a similar issue and wondered if you have any ideas please...
I need to update a Node level Data Page - long story, but think of an Administrator editing some settings at the Node level in a Data Page, and then all users reference these settings as part of their day to day work. It needs to be at Node level because it affects all users, and needs to be in a Data Page because it's just data in a table (plus we're not using Cases at all...it's a long story). Given that we can't update Node level pages....
I took the approach of
having a Requestor level Editable Data Page
displaying it in a Grid, allowing the Admin user to edit the Grid
and then 'on change' I call an Activity which loops through each item in the Data Page and update the underlying data table
I then call the FlushDeclarativePage to flush all instaces of the Requestor level Data Page (for all users)
Those pages re-load for each and every user, with the new updated values
My problem is that when I try and loop through each item in the DataPage and do an Obj-Save I get this error:
Cannot save a page with an instance of class SKO-Data-PresentationTeam: it is read-only
The table/class that I'm trying to update is one that I created through the Data tab in the designer studio. Not sure if that makes a difference?
>>> I then call the FlushDeclarativePage to flush all instances of the Requestor level Data Page (for all users)
User 1 did an update, the changes will be reflected only for user 1
The changes will be affected for user 2 only on a re-login action.
To ensure the changes to reflect for each requestor, we need a refresh strategy
a datetime property validating the initial creation to the update datetime performed via a node level declare page to force refresh the requestor data page [rebuild system pages] or prompt user to logout and login for the rule changes to take affect.
>>> It needs to be at Node level because it affects all users, and needs to be in a Data Page because it's just data in a table + think of an Administrator editing some settings
would it make sense to have an admin landing page to load & update (if any) the data via user temp page using Obj-Save followed by flushing node level declare page [flushDeclarativePage] works? so that the page can still be scoped to node level.
>>> Cannot save a page with an instance of class SKO-Data-PresentationTeam: it is read-only
could you please double check the data page 'edit mode' option whether configured to editable or not...