skip to main content
Corticon Studio: Quick Reference Guide : Vocabularies : Populating a new Vocabulary : Creating Vocabularies for Open Edge : Applying an updated BRVD to a Vocabulary
 

Try Corticon Now
Applying an updated BRVD to a Vocabulary
If you make changes to your OpenEdge application, you might need to regenerate the BRVD file, and then re-import it into Corticon to update your Vocabulary.
A re-imported BRVD file impacts any changes you might have made if you set the imported Vocabulary into Read/Write mode. While you cannot change the Vocabulary when it is in Read Only mode, the re-import actions will proceed on a locked or unlocked Vocabulary.
Note: A re-import of a BRVD file changes the current Vocabulary. It is a good practice to choose Save a copy before re-importing in the import dialog to backup the existing Vocabulary before applying changes to it, especially if you entered Read/Write mode and made changes.
Before the re-import action is applied, a dialog displays the entities, attributes, and associations in the Vocabulary and how they will be impacted.
The status and intended actions on Vocabulary entities, attributes, and associations during a re-import can be the following:
*Match- No action if the imported element and the existing element are identical in the following ways:
*Entity: Same name and same origination (BRVD import or user-defined action)
*Attribute: Same name, same datatype, and same origination (BRVD import or user-defined action)
*Association: Same name, same target entity, and same cardinality
*UserDefined - No action if the existing element was created in Corticon.
*Add - The imported element is entered into the Vocabulary and marked as originating from the BRVD as follows:
*Entity: The entity name in the BRVD does not match an existing entity in the Vocabulary
*Attribute: The attribute name in the BRVD does not match an existing attribute in the corresponding entity in the Vocabulary.
*Association: The association name in the BRVD does not match an existing association in the Vocabulary
*Remove - Deletes the existing element if it was previously created from a BRVD element, but is not in the import file.
*Remove/Re-add - Removes the existing element and then recreates it from its definition in the import file, under the following conditions:
*Attribute: Same name but the datatype is different. (When the datatype is an enumerated list or constraint expression, if that custom data type has the same base data type as the imported attribute in the BRVD, it is a Match.)
*Association: Same name but with a different Target Entity.
Note: The Remove/Re-Add action does not apply to an Entity that originated from a BRVD. A re-import can either Add or Remove a BRVD originated entity.
*Merge - Revises an existing element marked as created locally that is now a BRVD element in the import file. The existing element will transform to be defined as an imported element (originated from BRVD) and marked as Merge, as follows:
*Entity: Same name, but created in the Vocabulary editor.
*Attribute: Same name, same datatype, but created in the Vocabulary editor. If the existing element was defined as transient mode, it is changed to base mode.
*Association: Same name, same target entity, but different cardinality or created in the Vocabulary editor.
The dialog lets you choose to Copy to Clipboard to retain the action list as this information will not be available once you proceed to apply the re-import actions.
Note: If you choose to Cancel at this point, nothing was changed.
See the Progress OpenEdge documentation for details about a complete end-to-end workflow involved in an integrated OpenEdge Business Rules environment.

Example

The following figure shows how some BRVD changes to attributes are displayed for review:
Figure 256. Review information before re-import is applied.
The revised BRVD file is being re-imported into a Vocabulary previously created from a BRVD. The following attribute changes are shown in the Review Information dialog above:
*Match – Unchanged attributes that originated in OpenEdge.
*User Defined – Added CreditDiscount only in Corticon.
*AddPostal code added in OpenEdge and then added into the latest BRVD file.
*Remove/Re-add – Changed Terms to an integer only in Corticon, but it is still a decimal in OpenEdge and the BRVD. After this action, Terms is a decimal.
*Merge – Added OrderStatus to Corticon while awaiting BRVD change from OpenEdge. The new BRVD has OrderStatus so it is a merge
*Remove - Dropped the Promise date in OpenEdge from the latest BRVD file.