skip to main content
Corticon Studio: Quick Reference Guide : Vocabularies : Populating a new Vocabulary : Creating Vocabularies for Open Edge : Locking and unlocking Corticon Vocabularies
 

Try Corticon Now
Locking and unlocking Corticon Vocabularies
There are advantages to locked and unlocked Vocabularies:
*When your rule development has many Rulesheets and Ruletests, you might want to add a measure of control over Vocabulary changes. Locking the Vocabulary prevents you from accidentally changing an entity or attribute, thereby invalidating rules and calls from databases.
*When OpenEdge developers use Corticon for their business rules, they use Progress Developer Studio to integrate their ABL projects with Corticon Decision Services. During import of a Business Rules Vocabulary Definition (BRVD) created in Open Edge, a Corticon mechanism flags vocabulary entities, attributes, and associations as read-only. This protection keeps you from accidentally modifying the Vocabulary such that it no longer matches its source in OpenEdge. If you want to define transient attributes, constraint expressions, or make other modifications to the vocabulary in Corticon you will need to unlock it. When doing so, you need to be sure that your modifications do not make the vocabulary incompatible with its source in OpenEdge.
You can choose to lock a Vocabulary in Studio by selecting the Set to Read Only option, as shown:
Once locked, all the icons in the Vocabulary display a padlock symbol.
In a locked Vocabulary, all functions in the Vocabulary editor are display-only, including Custom Data Types and Database Access. Undo (and Redo) options will toggle the mode until the Vocabulary file is saved.
A locked Vocabulary can be unlocked by selecting the Set to Read/Write option.
Note: In Vocabularies created through BRVD import, changes that you make when unlocked and then locked again, continue to reflect the OE origin of BRVD imported attributes and entities. You should never rename attributes or entities that are bound to OpenEdge or EDC resources as they would likely cause data synchronization problems.