Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

If you open any of the rule files in a text editor like Notepad++ you can see they are all XML files.

...

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

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

The rules root directory also contains directories for every generated rule flows containing the .js files. The generated directory .js files are located in the root directory in part because this is their default location in the generate .js files dialog-box and would not require changing the value manually everytime.

Guidelines

  • Open the Corticon.js Studio in the root rules directory, in <environment>/osiv-webui/Rules.
  • All the rule files for a window or frame should be placed in a single directory with the same name (inside the correct Ruleflows category directory).

  • All the rule files should start with the same name as the window or frame . There (rhere is only one vocabulary and one workflow files so they should have the same name as the window or frame).

  • Every rule sheet file has should have a different suffix like _IsEnabled, _IsVisible, _Pages etc. (see rule sheet design).
    For example: EntscheidDetailWindow_IsEnabled

  • Rule test files start with the same name as their rule sheet including the suffix plus _Test and optionally or _Test<number> for multiple rule tests (see rule test design).
    For example: EntscheidDetailWindow_isEnabled_Test.

  • Generate the .js files directory in the root rules directory which is default location inĀ 

Git

Currently the .js files are included in the git repository and need to be committed instead of being generated in the build. There is a risk of the rules and .js files not matching in this approach. For example: if the rules were updated and someone forgot to generate the .js files.

...