Action Type - The Action Type defines whether and how a decision or decision group interacts with its context node using the following values:
•None: do nothing;
•Update: execute only if the node is present;
•Create if Necessary: if the node is not present then create it and proceed as for update;
•Create: create a new node regardless (only valid for collections);
•Always Create: create a new node and its immediate parent (only valid for nodes that are the immediate children of collections).
Alias - Aliases are used to improve the readability of the Logical English view of formulas. An alias consists of concise descriptive/naming text that replaces long, technical-looking navigation XPaths in the formula’s Logical English, making verification easier for non-technical business experts.
Argument - An argument is an operation or literal that provides a value to its parent operation. Each operation has a defined set of arguments (the number actually ranges from zero to unlimited, depending on the operator). The term argument is used in IDIOM in the same way that an Excel function uses arguments.
Boundary Bar - The Boundary bar clearly marks the boundary between the Explorer and Workspace panes. It has a different colour for each of the main IDIOM functions and allows you to clearly see what a particular Workspace pane is being used for, which can be useful when you have multiple Workspace panes open and need to move between them.
Business Rules - Business rules are not used with any precise meaning in IDIOM, but in general will refer to operations and groups of operations within formulas; that is, the business rules for a decision can be found in the formulas used by the decision.
Collection (node) – A collection is a node that has a cardinality of more than one with respect to its parent. Also known as multi-valued, or ‘repeating’.
Context Node - The node on the schema that provides an explicit reference point. All navigation and ‘reachability’ is relative to the current context node. The term context node is used in the following situations:
•The node that a decision/group, a formula, or a UDO is located on within the schema pane.
•The last referenced collection within a formula – when a node list operator is used, it changes the context node to the collection that it is pointing to.
•The node within a collection that is currently pointed by a decision group when the External Context operator is used.
Control Decision - A decision that does not return any value to the decision request document.
Customized Schema - A source schema must be customized before it can be used in a repository. Customization has two primary roles: identifying the nodes that will be visible in the schema pane; identifying the nodes that can be created or updated by decisions. The customized schema also contains variable nodes and aliases.
Customized Schema pane - The Customized Schema pane is found at the left hand side of the Workspace and displays all of the decisions and formulas that use its nodes as context nodes. It therefore becomes a navigation tool for decisions and formulas.
Datatype - A datatype classifies data based on its allowed values. IDIOM uses the following set of datatypes:
•String: character data values;
•Int and Long: Integers – Long is a much larger value that Int and should not normally be used;
•Decimal;
•Date and DateTime;
•Boolean.
•Time
Decision – “A single definitive outcome that is the result of applying business knowledge to relevant data for the purpose of positively directing the activity of the business”. A decision is a single derived value that implements some aspect of business policy. Decisions are definitions associated with one output field in a schema that provide an effective dated link to the formula(s) that are used to calculate the output values.
Decision Designer - A decision designer is a generic term for somebody who is involved with building decision models.
Decision Group - A decision group is a named group of decisions and other decision groups that all respond to the same event. At runtime, the decisions/groups in a group execute in order from top to bottom (subject to formula controlled exits).
Decision Model – “An ordered assembly of decisions that creates new and proprietary information to definitively determine an optimal course of action for the business.” All of the decisions and decision groups are displayed in the decision model. New decision group(s)/decisions are created here and the order of decision execution is specified by the left to right, top to bottom order of the decision group(s)/decisions within this palette.
Decision Node - A decision node is an output node in the schema that is the context node for the decision, and to which it will write any value that it creates.
Decision Request – A decision request is one instance of an external application call to the IDIOM Decision Engine. The decision request will pass in, and will receive back, one or more XML documents that contain the full extent of data that the called Decision Model requires. Sometimes the term is used to refer to the XML document(s) used in the request.
Decision Service - The decision Service is the means by which the application obtains access to the business rules. The service provider is the IDIOM Decision Engine.
Dynamic Table Contents - Dynamic Table Contents are Table Content data that is supplied by an application to the IDIOM Decision Engine using a specific interface, so that Table Contents can be maintained externally to the Repository and supplied when needed.
Effective Date – Effective date has two parts and two distinct meanings. It is a) the date that is used by a model to select an effective dated component; and b) it is the date nominated on the component that cause it to be selected. The a) side effective date is used to select the b) side component whenever the decision model access the component. On the a) side, there is always an effective date for a decision model when it is executing. This effective date is defaulted to ‘today’ but it can be overridden by the calling application on the call to the Decision Service, and/or by assigning an effective date within a Formula using the Set Effective Date operator. On the b) side, the effective dated components include Formulas, Formula References, and Tables, which have IDIOM supported effective dates. Table rows, decisions, and decision models themselves can also be effective dated through various techniques (SEE Versioning). Generally a new effective date on a component date sunsets the prior (if any) effective date. End dating is only used in the specific case of a formula reference.
Floating Formula - A floating formula is a formula that is not associated with any particular decision but is available to any decision within the Repository. They are useful as a means of keeping commonly used formulas, or commonly used parts of formulas, easily accessible to decision designers. For example, a formula that determines if the Cover Type is valid or not may be used by more than one decision. By using a floating formula, the decision designer can save time and effort by reusing a formula that has already been built.
Formula Comment - A formula comment appears in the tool tip whenever the mouse passes over the particular area of a formula that a comment has been created for. In IDIOM, tool tips automatically appear over the operators indicating their datatypes. Additional information may also be added, such as why a particular operator was used or who authorised the use of a certain operator.
Formula Label - A formula label can be added to a complex formula in order to clarify the function of certain operators or groups of operators within the formula. The principal function of a formula label is to create paragraph breaks in the Logical English view of the formula to increase its legibility.
Formulas - A formula is the logical expression that describes the transformation of named input variables into a decision output.
Formula Reference - A formula reference is a link between a formula and a decision. Multiple Formula References allow one Formula to be used by multiple Decisions; and for a Decision to be associated with multiple Formulas over time (there can only ever be one Formula effective for a Decision at one time).
Formula Palette - The formula palette appears in the Workspace pane with the blue theme. It is here that new formulas are created using operators on the hover tabs; you can also view the operators and arguments of existing formulas in this palette.
Host Application - A host application is any existing or new customer application that will include and use Decision Services.
IDIOM Decision Engine - The IDIOM Decision Engine is compiled from the code that is generated by the IDIOM Decision Generator for use within the host application. This has no `user visible' parts, but may be controlled via a configuration document.
IDIOM Decision Generator - The IDIOM Decision Generator transforms repository documents into computer source code (Java or C#).
IDIOM Decision Manager - The IDIOM Decision Manager is a desktop application that creates, manages and releases repository documents.
IDIOM Decision Suite - The IDIOM decision Server is a combination of desktop applications and deployed objects that allows users to define, manage, deploy and execute decision models.
Industry Standard Schema - An Industry-standard schema is one based on industry standard definitions of core business objects, such as those produced by ACORD, HL7, UBL etc. These XML schemas define a standard shareable vocabulary for data exchange between businesses.
Intermediate node - Intermediate nodes occupy the levels between root and leaf nodes. Each intermediate node is the root of a substructure that extends to the lowest level of the schema. Substructures correspond to XMLSchema elements known as complexTypes.
Leaf node - A leaf node is the lowest level node in a schema. These nodes represent the data fields in a decision request and correspond to XMLSchema simpleTypes or attributes.
Logical English view - The Logical English view of a formula is a presentation format that is closer to natural English, and which may be more suitable for a non-technical audience and may, therefore, be a suitable format for verifying the formula with business domain experts. Logical English is highly structured and is guaranteed to be unambiguous.
Nested decision group - A nested decision group is formed when a parent decision group contains child decision groups.
Node - A node is an element or attribute in a schema.
Node Visibility - During Schema Administration, the Node Visibility view is used to mark the nodes from the source schema that will be visible in the customized schema.
Operation - An operation is a specific transformation of values, as supplied by arguments, into a single, more valuable outcome. An operation is defined by an operator and its arguments.
Operator - An operator is a prebuilt primitive building block for Formulas.
Output node - An output node is a node on the customized schema that is associated with output from a decision. It is a synonym for decision node.
Repeating node - A repeating node is an intermediate or leaf node that represents a collection of values, such as strings, numbers or dates. It is also known as a multi-valued node and a collection.
Root node - A root node is the topmost node in a schema.
Rules Repository - A rules repository is a container for business rules.
Release Process - Running the release process transforms the desired decision model/repository into generated code, which can then be deployed into a suitable environment.
Render - When you use a schema in IDIOM, IDIOM takes the source schema file (an .xsd file) and renders, or translates, the schema into a tree format more suitable for users to use. This process does not alter the fundamental data definition within the schema itself other than to limit recursive structures.
Repository Administrator - A Repository Administrator is a user who is responsible for creating, setting up and managing a repository for rules development and has unrestricted access to that repository.
Repository definition screen - The Repository definition screen is the screen in which the Administrator defines the name, ownership and purpose details of the repository and creates/deletes the workgroups within that repository.
Schema - A schema is a definition of a valid XML document. This term is always used to refer to the formal W3C meaning of schema, usually marked as an `.xsd' or `.xs' document. IDIOM uses the schema to describe the `business objects' against which IDIOM will define rules.
Schema Maintenance - Schema Maintenance is performed by the Administrator and is most frequently performed when changes have been made to a source schema that affects the customized schemas that are based on the source schema.
Source schema - A source schema is an XML document conforming to the W3C XMLSchema specification. It is used to describe data within an IDIOM Repository.
Tabs - Tabs allow you to move between panes. IDIOM uses two types of tabs, standard tabs and hover tabs.
Table contents - A ‘Table contents’ is a complete set of rows for a table. A Table might have multiple Table contents, each of which must be effective dated. A set of Table contents is also known as a Table set.
Table - A Table defines the columns for multiple rows of reference data. It defines the existence of the table prior to the insertion of actual data in the form of rows.
Test Executive - The Test Executive is an application that manages and executes test profiles that execute nominated decision models against externally supplied test data.
Test Executive console - The Test Executive console is used during testing and contains tabs for the Source Code Generation, Compilation and IDIOM Runtime Execution panes. These detail any errors that have been picked up during the execution of the test during generation, compilation or runtime, respectively.
Test Profile - A Test Profile allows you to save your basic test settings, which specify the platform for testing, the input file(s) and the first and last decision group(s) to be included in the test. An unlimited number of Profiles can be saved and opened as needed. This saves you time as you will not need to redefine the input files and so on every time you wish to execute a test.
Tree view – (Formula) In the Tree view format, a formula is displayed in such a manner that each line represents an operation or an argument used in the formula.
User – A person who has an IDIOM Decision Manager login. A user has a role (Administrator, Workgroup Administrator, Formula Expert) and may be registered to specific workgroup(s) within the repository.
Validation - Validation is available for Decision Models to verify the integrity of the Decision Model. Some errors in decision model construction are only meaningful when the model needs to be generated. At this time, these errors need to be identified so that the generation can generate valid results. Validation runs hundreds of checks across each model and may produce Validation Errors.
Validation Errors - Three categories of validation errors may occur during Validation. These include:
•Critical Validation Errors - these can be considered fatal and will prevent IDIOM from compiling at runtime. Shown in red text.
•Warning messages - these appear when elements within the repository are incomplete or effective dates have been set at inappropriate times. However, they are merely notifications to the user and will not prevent compilation. Shown in orange text.
•Information messages - these are used to let the user know of any information that may be important to the validation process (other than information from the categories above). They do not prevent IDIOM from compiling at runtime. Shown in blue text.
Workgroup - A workgroup defines a team that is responsible for the development of one or more decision models.
Workgroup Administrator - A Workgroup Supervisor is a user who also responsible for managing users within their workgroup, and for performing some restricted tasks in the life cycle of a decision model.
Workspace - The Workspace is found at the right hand side of the Explorer and Customized Schema panes and it is the area in which most of the work within IDIOM is performed. For example, the formula palette and decision model open in the Workspace.