| 24 | | |
| 25 | | = Saving concepts/CMs = |
| 26 | | |
| 27 | | == Saving concepts == |
| 28 | | 1. Once a concept is saved withing a locked CM the changes are reflected in the server-side model but not saved permanently (db). Concept lock is kept untill the CM is saved/reverted |
| 29 | | 1. Once a concept is saved from another editing point changes are saved in the model and in the db |
| 30 | | 1. If a new concept is created within a locked CM it is added to the server-side model and individual search index but not saved persistantly |
| 31 | | 1. If a new concept is created withing other editing points it is added to the server-side model, common search index and saved persistantly |
| 32 | | 1. If a concept in a CM was changed by another source (e.g. in a infoItems cockpit or VV) |
| 33 | | 1. User has to get a signs that concepts were changed |
| 34 | | 1. e.g. some symbol displayed as a concept icon |
| 35 | | 1. If user opens such a concept it has to be refreshed from the server |
| 36 | | 1. Flex-application should send "refresh"-requests periodically to get informed about changed concepts |
| 37 | | |
| 38 | | == Saving CMs == |
| 39 | | |
| 40 | | 1. All read-only CMs should get a flag "dirty" if the editing user saved/closed it |
| 41 | | 1. e.g. some symbol displayed |
| 42 | | 1. User can refresh the CM contents from the server |
| 43 | | 1. User can request a CM lock if the editing user closed the CM |
| 44 | | 1. Flex-application should send "refresh"-requests periodically to get informed about changed CMs |
| 45 | | 1. If the user closed a CM without saving, the server-side model has to be reverted |
