Configuring code segments

Most organizations require specific object naming conventions, particularly for formulas. The convention can be as straightforward as serial numbering where a new formula gets the next sequential number. For example, formula 40 follows formula 39.

Or, it can be complex, with pre-defined and user-entered parts. For example, a four part formula name can include a program name, a lab name, a sequential formula number and a user’s initials.

Optiva is designed to allow multi-segment object naming conventions. The naming rule can be completely automated, assigning the entire name. Or, it can be interactive, prompting the user for some input. Different rules can be established for the same object and event. Users select from several rules when they create or copy objects.

The naming conventions of formulas and other objects have become complicated in many organizations. Typically, several portions of an object name are derived from different sources. For example, a formula name can be derived from both the formula it is copied from and the program it belongs to.

All rule codes are available to all languages that are running Optiva. The code segments are not. You must run Optiva in each language and recreate the code segments for each language that requires the rule code.