| 9 | | * Policies |
| 10 | | * |
| | 9 | Lock policies |
| | 10 | 1. One is not allowed to edit concepts in a read only CM (only view properties) |
| | 11 | 1. One is not allowed to save a CM/change CM properties for a read only CM |
| | 12 | 1. One is not allowed to edit concept properties if the concept is locked by another user (or the same user has open 2 edit dialogs for the same concept in different CMs) |
| | 13 | 1. One is allowed to add relations to a concept locked by another user |
| | 14 | 1. One is allowed to edit an unlocked concept that is in a CM locked by another user |
| | 15 | 1. CMs should get a flag "dirty" if a concept in it was changed by another source (e.g. in a infoItems cockpit or VV) |
| | 16 | 1. User has to get a signs that concepts were changed |
| | 17 | 1. e.g. some symbol displayed as a concept icon |
| | 18 | 1. If user opens such a concept it has to be refreshed from the server |
| | 19 | 1. Flex-application should send "refresh"-requests periodically to get informed about changed concepts |
| | 20 | |
| | 21 | |
