This section details how to incorporate (consolidate) business rules, interfaces, and files from one version of an application into the currently open version.
¶ Selection of source application and version
In this step, you choose the application and version from which new changes will be imported into the current open version.
¶ Parameters
App path: location of the source application. Clicking on the field will open a window to browse the system folders and choose the desired application.
Version: version of the source application from which you want to incorporate new changes.
Business rules - Modules: a selector to choose the modules you want to incorporate.
Business rules - Replace matching nodes outside these modules: This option is relevant if there is a node within the selected modules for consolidation that has an identifier matching a node’s identifier in the target version (current), but in the target version, it exists in a module outside of the selected consolidation modules. If this option is checked, the properties of these nodes will be replaced by the new nodes. If it’s unchecked, the new nodes in question will be renamed with the suffix “_new” after consolidation.
Interfaces: a selector to choose which interfaces you want to incorporate.
Files: if this option is checked, all files within the source version will be compared with the files within the target version.
Version metadata: if this option is checked, the metadata.json file within the source version will be compared with the one in the target version.
When clicking on the “Next” button, Pyplan will calculate the differences between the source version and the target version and display them in the next step.
¶ Comparison and selection of differences to apply
In this step, the differences between the source version and the currently open version will be displayed.
¶ List of elements with differences
On the left side, nodes, interfaces, and files in which there are differences between the two versions are displayed.
The checked elements will be the ones that will be applied when confirming the changes.
¶
Meaning of icons by color
Green: a new element that will be added.
Yellow: an existing element that will be modified.
Red: an element that will be deleted
¶ Comparison of the chosen element
On the right side, the differences of the chosen element are displayed. What is shown under “Old” are the properties of the current open version. What is shown under “New” are the properties of the source version. If the change is confirmed, the properties displayed under “New” will be applied.
In the case of choosing a Business rules element, the differences are presented in two tabs:
Properties: shows the node properties such as title, position on the diagram (x, y), size (w, h), among others.
Definition: shows the node’s definition (Python code).
For the rest of the elements (Interfaces, Files, and Version metadata), only differences are shown under the Properties tab.
¶ Confirmation of changes
Clicking the “Confirm” button will apply the chosen changes.
Considerations:
Changes applied in Files and Version metadata are irreversible.
Changes in Business rules and Interfaces can be reverted if the changes are not saved in the application.
¶ Consolidation summary
In this section, you can see a summary of the changes applied in the current open version.
The changes applied in Files and Version metadata are final. The changes in Business rules and Interfaces will be saved if the application is saved.
¶ Database with applied changes
In the version folder, after a consolidation is applied, all the changes are recorded in a file named “consolidations.db”.
Keep in mind that if the changes in Business rules or Interfaces are not ultimately saved in the application, they will still be impacted in the database.