Hans Karlsen (talk | contribs) (Created page with "Some systems want to make use of distinction between ''opening a page for viewing'' - and ''intending to edit the data within''. The reasons for this may be many but one that was top of mind during our design is that we have inexperienced users that are afraid to touch or update things they do not intend to update. These users can be made to feel sa lot safer if there is a switch on the page you need to flip in order to edit anything. Of course users still want to sear...") |
Hans Karlsen (talk | contribs) No edit summary |
||
| Line 4: | Line 4: | ||
Of course users still want to search and navigate the system - so a the readonly model should function much like AccessGroup ViewEnable expression - that only effect (locks down) actions and controls that actually change persistent data. | Of course users still want to search and navigate the system - so a the readonly model should function much like AccessGroup ViewEnable expression - that only effect (locks down) actions and controls that actually change persistent data. | ||
Resources and abilities available now for a framework backed per page readonly model: | |||
# a Special ViewModel variable will be detected and applied: vSysReadOnlyMode:Boolean | |||
## When seen it will be "or"ed into the ViewModel.ExternalReadOnlyExpression - sharing this expression with any AccessGroups.ViewEnableExpressions. | |||
Revision as of 15:57, 7 February 2024
Some systems want to make use of distinction between opening a page for viewing - and intending to edit the data within.
The reasons for this may be many but one that was top of mind during our design is that we have inexperienced users that are afraid to touch or update things they do not intend to update. These users can be made to feel sa lot safer if there is a switch on the page you need to flip in order to edit anything.
Of course users still want to search and navigate the system - so a the readonly model should function much like AccessGroup ViewEnable expression - that only effect (locks down) actions and controls that actually change persistent data.
Resources and abilities available now for a framework backed per page readonly model:
- a Special ViewModel variable will be detected and applied: vSysReadOnlyMode:Boolean
- When seen it will be "or"ed into the ViewModel.ExternalReadOnlyExpression - sharing this expression with any AccessGroups.ViewEnableExpressions.