Difference between revisions of "Shared workspaces"
(→8. Shared workspaces - Many users accessing the same repository) |
|||
| Line 13: | Line 13: | ||
In order to handle concurrent access of the GXtest database scheme there is a lock/unlock system over the artifacts on which they are working. Each element can be blocked by a user who is using it, indicating that he can change and is better if anybody else modify it. Then when he already modified it and saved it, he can "release" it to let the rest of the team work on it. When an item is checked out anyone can open it as read-only item. When someone creates an item automatically locks it for himself. If nobody else wants to modify it, it is possible to block it explicitly. This is useful when the one who wants to use it knows that it is blocked but nobody is really using it. | In order to handle concurrent access of the GXtest database scheme there is a lock/unlock system over the artifacts on which they are working. Each element can be blocked by a user who is using it, indicating that he can change and is better if anybody else modify it. Then when he already modified it and saved it, he can "release" it to let the rest of the team work on it. When an item is checked out anyone can open it as read-only item. When someone creates an item automatically locks it for himself. If nobody else wants to modify it, it is possible to block it explicitly. This is useful when the one who wants to use it knows that it is blocked but nobody is really using it. | ||
| − | To lock an item, right click on the item, "Lock". To unlock an item, right click on the item, "Unlock". The elements that were blocked have an icon with | + | To lock an item, right click on the item, "Lock/Unlock". To unlock an item, right click on the item, "Lock/Unlock". The elements that were blocked have an icon with a gray background, which are not blocked by anyone appear with transparent background, and if someone else has blocked it is displayed with red background. |
Latest revision as of 17:26, 28 March 2014
 |
 |
 |
In order to handle concurrent access of the GXtest database scheme there is a lock/unlock system over the artifacts on which they are working. Each element can be blocked by a user who is using it, indicating that he can change and is better if anybody else modify it. Then when he already modified it and saved it, he can "release" it to let the rest of the team work on it. When an item is checked out anyone can open it as read-only item. When someone creates an item automatically locks it for himself. If nobody else wants to modify it, it is possible to block it explicitly. This is useful when the one who wants to use it knows that it is blocked but nobody is really using it. To lock an item, right click on the item, "Lock/Unlock". To unlock an item, right click on the item, "Lock/Unlock". The elements that were blocked have an icon with a gray background, which are not blocked by anyone appear with transparent background, and if someone else has blocked it is displayed with red background.
Volver al GXtest Designer 2.0 User's Manual
