Design option for view only AM

Question

We are creating an ItemAM that will be opened, updated, and then closed. There will be two types of users that use this AM, those with edit capabilities and those with view only capabilities. Once the item is closed no updates are allowed, so the item will remain in a view only state. We are looking for some ways to model this. We want to maintain state when the ItemAM is opened by users with update responsibility. However, we do not want to maintain state if the item is opened by a user with view only. Once the item is closed we do not want to maintain state, since you cannot change the item. What's the best way to model this? Can a personalization be used to check the responsibility or item status and not save state when the item is brought up in view only mode? We anticipate that about half the time the item will be brought up in edit mode and the other half in view mode. I am looking for recommendations on the best way to implement this.

Answer 1

It is not correct to think of AM being update allowed or not, VO is the one that captures the updates and applied it to the DB via EO.
As far as your problem is understood, based on the responsibility, you either want the page/field to be update allowed or update not allowed.
For this , you can make the beans render as read only when the page loads based on the responsibility
or
you can always have the page/bean as update allowed and in the submit action discard the changes based on the selected responsibility.
Thanks
Tapash