Creating Vocabularies

Vocabularies contain all the information which can be used in conditions and updated in actions. For example: The form field and the datasource field values we use in conditions, and the form field and page (tabs) enabled and visible properties we can set in actions.

...

Vocabularies can be generated either for an entire window and everything in it (all the datasources, forms, pages and ribbons) including nested frames, or just a frame with everything in it but not including nested frames so frame vocabularies are much smaller and simpler than window vocabularies which can be very big.

...

The Generate Vocabulary window creates a vocabulary file with the same name as the window or frame and the .ecore extension. Currently the file is saved out to the pasoe temp directory (c:\temp at OSIV). After the vocabulary file is generated, copy the file to your workspace (see file and directory structure).

...

The rules root directory is located in the osiv-customer webui/Rules directory (in the frontend project repository).

The root directory contains a Ruleflows directory for all the rule files. The Ruleflows directory is organized into directories according to categories similar by module similar to the ClientLogic frontend and OSIV3G source backend source directories. For example: Entscheid, Sendung, Stamm etc. directories.

...

• Open the Corticon.js Studio in the root rules directory, in the /osiv-customer webui/Rules directory.
  
  
• All the rule files for a window or frame should be placed in a single directory with the same name (inside the correct module directory, in the Ruleflows category directory).
  
  
• All the rule files should start with the same name as the window or frame (there is only one vocabulary and one workflow files so they should have the same name as the window or frame).
  
  
• Every rule sheet file should have a different suffix like _IsEnabled, _IsVisible, _Pages etc. (see rule sheet design).
  For example: EntscheidDetailWindow_IsEnabled.ers
  
  
• Rule test files should start with the same name as their rule sheet including the suffix plus _Test or _Test<number> for multiple rule tests (see rule test design).
  For example: EntscheidDetailWindow_isEnabled_Test.ert
  
  
• Generate the .js files directory in the root rules directory which is also the default location in the Corticon Generate Ruleflow dialog-box.

...

Taking into account that UI rules are mostly made up of many simple rules and how the rules are mostly divided in the specification at OSIV, the rules should be divided in the following way -

...