Available with Standard or Advanced license.
Error features and error features marked as exceptions have special behavior depending on how they are treated during the version reconcile process. Error features can only be updated by repairing the error (making an edit) or by marking an error as an exception.
The results of the reconcile process on errors and exceptions in the parent (default) version are summarized in the examples below.
Any error created in the parent (default) version, regardless of whether it is marked as an exception, is brought into the child version as a result of the reconcile (as shown in Examples 1 and 2 below).
Note:
For branch versioning, in the following examples, Version1 is the default version and Version2 is a child of the default.Example 1
Example 2
Any preexisting error marked as an exception in the parent (default) version is marked as an exception in the child version after the reconciliation.
Any error or exception that is deleted in the parent (default) version (either by fixing the error or by the validation process) is deleted from the child version as a result of the reconcile process.
The results of the reconcile process on errors and exceptions in the child version are summarized in the following examples.
Any error created in the child version is deleted as a result of the reconcile process and, by definition, is covered by a dirty area. The error can then be rediscovered by validating the dirty area.
Any error created in the child version and marked as an exception remains an exception as a result of the reconciliation. By definition, it is covered by a dirty area.
An error that existed in the parent (default) version and is marked as an exception in the child version remains an exception as a result of the reconcile process and is covered by a dirty area. However, if the error was fixed in the parent (default) version, it remains fixed in the child version (as illustrated in Examples 3 and 4 below).
Example 3
Example 4
An exception that existed in the parent (default) version and is marked as an error in the child version remains an error as a result of the reconcile process and is covered by a dirty area. However, if the exception was fixed in the parent (default) version, it remains fixed in the child version (as shown in Examples 5 and 6 below).
Example 5
Example 6
An error or exception that existed in the parent (default) version and is fixed in the child version remains fixed as a result of the reconcile process as shown in Examples 7 and 8 below.
Example 7
Example 8
There are cases in which the same error can be created in both versions by validating a dirty area that existed in the parent (default) version when the child version was created. If this error is marked as an exception in either the parent (default) or child version, the reconcile results in duplicate error features. In these cases, the error features are covered by a dirty area and reduced to a single error or exception when the dirty area is validated. This is illustrated in the two examples below.
Example 9
Example 10
