|
1 | 1 | --- |
2 | 2 | title: "Version Control" |
3 | 3 | linkTitle: "Version Control" |
4 | | -description: "This section includes user guides related to Version Control in {{% ctx %}} Gateway." |
| 4 | +description: "Displays the flow hierarchy for the current user indicating whether the flows are the same as or differ from the Master Repository." |
5 | 5 | weight: 90 |
6 | 6 | --- |
7 | 7 |
|
8 | 8 | # {{% param title %}} |
9 | 9 |
|
10 | 10 | ## Summary |
11 | 11 |
|
12 | | -The Version Control feature displays the Group hierarchy of the flows for the current user, identifying whether the current user’s flows, stored in the user’s sandbox repository, are up to date with the Master Versions, stored in the Master Repository. |
13 | | - |
14 | | -| | | |
15 | | -|------------------------------|-----------------------------------------------------------------| |
16 | | -| **Roles Required:** | Admin | |
| 12 | +The Version Control page displays the flow hierarchy for the current user, indicating whether the current user’s flows, stored in the user’s repository, are the same as or differ from the Master Versions, stored in the Master Repository. |
17 | 13 |
|
18 | 14 | ## Anatomy |
19 | 15 |
|
20 | 16 | {{< figure src="/images/Version Control.png" title="Version Control" >}} |
21 | 17 |
|
22 | 18 | Only flows with Edit permissions for the current user are displayed in the Version Control grid. |
23 | 19 |
|
24 | | -Any flow versions, in the user’s repository, that are ahead of the Master Version, in the Master Repository, are indicated by an upward pointing arrow, and may be selected to be Committed as the Master Version by using the `Commit Changes` button. |
| 20 | +## Actions |
| 21 | + |
| 22 | +### Get Master |
| 23 | + |
| 24 | +Any flows that have been committed to the Master Repository by another user are indicated by a downward pointing arrow [Add image here]. These newer Master Versions may be pulled into the user’s repository by selecting them and clicking the `Get Master` button; if `Get Master` is selected for a flow that also has user uncommitted changes, these changes will be lost and the flow will be overwritten with the Master Version from the Master Repository. |
| 25 | + |
| 26 | +See the [Use Version Control][Use Version Control tutorial] tutorial for a step-by-step guide. |
| 27 | + |
| 28 | +### Commit Changes |
| 29 | + |
| 30 | +Any flows in the user’s repository that have uncommitted changes are indicated by an upward pointing arrow [Add image here]. These flows may be committed to the Master Repository by selecting them and clicking the `Commit Changes` button; if any flows selected to be committed have a new Master Version committed by another user a dialog will be displayed prompting conflicts to be resolved by taking either the version to be committed (`Take your version`) or `Take master version` resulting in a `Get Master` being performed. |
25 | 31 |
|
26 | | -Any flow Master Versions that have been Committed to the Master Repository by another user are indicated by a downward pointing arrow, and may be selected to be retrieved from the Master Repository and stored in the user’s repository using the `Get Master` button. |
| 32 | +See the [Use Version Control][Use Version Control tutorial] tutorial for a step-by-step guide. |
27 | 33 |
|
28 | 34 | ## Remarks |
29 | 35 |
|
30 | 36 | ### Known Limitations |
31 | 37 |
|
| 38 | +* There is no prompt to resolve conflicts when getting the Master Version of a flow that has uncommitted user changes. |
32 | 39 | * It is necessary for the parent groups to have edit permissions in addition to the flows, to enable the display of the flows in Version Control. |
33 | 40 |
|
34 | 41 | ## See Also |
35 | 42 |
|
36 | 43 | ### Related Concepts |
37 | 44 |
|
38 | | -TODO |
| 45 | +None |
39 | 46 |
|
40 | 47 | ### Related Tutorials |
41 | 48 |
|
|
0 commit comments