Versions Compared
Key
- This line was added.
- This line was removed.
- Formatting was changed.
Any completed local pack, including the uploaded imported ones, can be rolled back. A rollback restores the versions of all the records in this local pack as they were before the start of the update collection, in other words, before starting works on this local pack.Deleted records are restored, and created records are deleted.
After a rollback is completed, the imported versions remain in the system as non-current outdated VCS records. You can restore these record versions manually if needed.
Example
- A configuration pack contains a record version X.
- Before the import, the target instance had a version Y.
- After the import of the local pack, the record version changed to X.
- When you rollback the local pack, the Y version of the record is restored.
Rollback a local pack
To rollback a local pack, complete the steps below:
- Navigate to Configuration → Local Pack.
- Open the local pack you need to rollback.
- Click Rollback preview to check the system's response to the record restoration.
- In the Related Lists area, open the VCS Preview Log tab.
- Filter out records in the Allowed state with the condition builder, and process possible collisions if collisions if there are any.
- Click Rollback to restore the records to the previous version.
As a result, the following changes occur:
Import result | Rollback result |
|---|---|
| A new table | The table is dropped from the database, deleting any data from itand its records are deleted. |
| A new field | The field and the information about the field is dropped from the database, deleting any data from itdeleted. |
| A deleted field | The field is restored to the database, but the original data is lost. |
| A record inserted | The record is deleted. |
| A record deleted | The record is restored with its original initial data. |
| A record updated | The previous record version is restored. |
Collision processing Anchor collision processing collision processing
| collision processing | |
| collision processing |
General process of solving the rollback collisions is the following:
- In the configuration pack that you need to be rollbackedrollback, click Rollback preview.
- Scroll down to the Related Lists area and open the VCS Preview Log tabIn the Related Lists ares, select the VCS Preview Log tab.
- Filter out the records in the Allowed state using the condition builder.
- Open one of the records. Find the information about the error in the Message field.
Make the necessary changes to solve the collisions.
- Click Save or Save and Exit to apply the changes.
- Return to the configuration pack record and click Rollback preview.
- Make sure Ensure that the VCS Preview Log record state has changed to Good.
- Repeat the steps 3-8 until all necessary records in the VCS Preview Log are in the Good state.
- Click Rollback.
Collision cases Anchor collision processing collision processing
| collision processing | |
| collision processing |
| Panel |
|---|
Collision case 1When rolling back a local pack, the state of the record is Collision. The Message field contains the following text:
Collision solving: Move the current record to the local pack , which that you need to rollback, and click Rollback preview. |
| Panel |
|---|
Collision case 2When rolling back a local pack, the state of the record is a record changes its state to Collision. The Message field contains the following text:
Collision solving: Continue the rollback. The collision record will be skipped. |
| Panel |
|---|
Collision case 3When rolling back a local pack, the state of the record is a record changes its state to Collision. The Message field contains the following text:
Collision solving: Continue the rollback. The collision record will be skipped. |
| Panel |
|---|
Collision case4The configuration pack contains some records that should be inserted as new columns into a table. When rolling back a local pack, the records are in the Warning state. The Message field contains the following text:
Collision solving: Continue the rollback. The columns inserted during the import will be deleted. |
| Panel |
Collision case 5A local pack contains a new table as an Insert record. The A rollback should cause the deletion of this table, but the records that it contains, prevent the table from removal. The state of the table record is Skipped. The Message field contains the following text:
Collision solving:Open the list of the records of the table and delete all records manually
|
| Tip |
|---|
See more examples of possible collisions in the Collisions Resolving Rules article. |
| Table of Contents | ||||||
|---|---|---|---|---|---|---|
|