| | 77 | |
| | 78 | |
| | 79 | |
| | 80 | === Saving concepts === |
| | 81 | 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 |
| | 82 | 1. Once a concept is saved from another editing point changes are saved in the model and in the db |
| | 83 | 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 |
| | 84 | 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 |
| | 85 | 1. If a concept in a CM was changed by another source (e.g. in a infoItems cockpit or VV) |
| | 86 | 1. User has to get a signs that concepts were changed |
| | 87 | 1. e.g. some symbol displayed as a concept icon |
| | 88 | 1. If user opens such a concept it has to be refreshed from the server |
| | 89 | 1. Flex-application should send "refresh"-requests periodically to get informed about changed concepts |
| | 90 | |
| | 91 | == Saving CMs == |
| | 92 | |
| | 93 | 1. All read-only CMs should get a flag "dirty" if the editing user saved/closed it |
| | 94 | 1. e.g. some symbol displayed |
| | 95 | 1. User can refresh the CM contents from the server |
| | 96 | 1. User can request a CM lock if the editing user closed the CM |
| | 97 | 1. Flex-application should send "refresh"-requests periodically to get informed about changed CMs |
| | 98 | 1. If the user closed a CM without saving, the server-side model has to be reverted |
