A list that enables you to assign security access on an individual object and user basis. Choose an object instance and define the security for all users, roles, and groups for that object; or choose a specific user, role, or group and define the security for specific objects for the selected user, role, or group.

Status information that can be applied to formulas, items, and other Optiva objects. You can create a list of acceptable approval values on the Symbol form for most symbols.

A portion of a rule that defines your company’s specific naming conventions for the creation of new formulas and other Optiva objects. You can configure rules to control how users can name new objects. Naming rules provide consistent naming practices and increase efficiency because users do not have to remember or look up a naming convention. Auto Codes can be used along with Copy Methods to create a rule that controls the name and attributes of new objects.

The individual pieces of an auto code that defines an object naming convention. For example, the formula code COLOR.037-BLUE-NP\001 consists of five Auto Code Segments.

Part of the context information that is used to define the attributes for a finished product. Brand represents the company’s brand name for the specific product. The Brand context is configured through the C_BRAND enumerated list.

Text description that is displayed on buttons in Optiva. Some examples are Verify, Instruct or Calc on the Formula form. Button labels can be renamed to match the names that are currently used in your company. Customized labels provide name recognition that can ease users into the Optiva application.

This is the custom enumerated list. A type of enumerated list that enables you to add your own entries. You can create completely new enumerated lists for extension fields. These lists are displayed as drop-lists. The user can select pre-defined values from these lists when they specify data. You configure custom enumerated lists in the Enumerated Lists form.

A discrete category to which an object belongs. Each symbol, such as formula, can have a collection of classes. An object may belong to only one. Classes are configured in the Enumerated Lists form, usually as C_SymbolCLASS, such as C_FORMULACLASS. Users assign an object to a class in the object form.

Class represents a type of Optiva object or symbol, such as formula, item, specification or parameter. Used as part of the import process that declares what type of object is being imported. Users create objects under a specific class or symbol type, such as a pizza sauce formula called PIZZA_ SAUCE\ 0001. PIZZA_ SAUCE\ 0001 is an object of class type "formula".

Part of the context information that is used to define attributes for a finished product. Companies represent: customers, vendors, suppliers, testing facilities for approving formulas, manufacturing facilities for producing the end-products.

Use the Company form to configure company information.

Attributes that define the finished product of an Optiva object, such as a formula or item. Context information includes Selling Location (Location form), Manufacturing Location (Location form), End Use (Enumerated List form, C_ENDUSE), End User (Enumerated List form, C_ENDUSER), Brand (Enumerated List form, C_BRAND), Product Type (Enumerated List form, C_PRODTYPE). Users select from allowable values that you define.

Scripts that instruct Optiva to change or omit a property of a new object so that it differs from a traditional new or copied object. For example, 90% of new formulas in your company have value X for a parameter. The default record contains value X for the parameter so that each new formula has the parameter pre-filled.

For the 10% of new formulas that have a different value, you can create a Copy Method that assigns value Y to the parameter. Users can choose whether to apply a Copy Method when they are creating new objects.

A rule consist of Copy Methods and Auto Code Segments. Copy Methods are scripted in the Copy Methods form and are associated with a rule in the Create Rules form.

The part of Optiva that enables you to configure some of the visual features of Optiva, such as data fields and form labels. This functionality lets you define filters to organize the display of parameters, extension fields, custom tabs, attached documentation, items, and workflow tasks for both security purposes and to make it easier for users by displaying only what they need to view.

In Configure Templates, you can create custom tabs for every role-based template and add extension fields to those tabs.

Text descriptions, displayed on a form, that identify a field, drop-list, check box, radio button, etc. You can rename a data field label in the Field Label form.

An object record that contains data that is used every time a new instance of the object is created. All objects, such as formulas, items, instructions, etc. can have default records with a code of @DFLT (@DFLT\@DFLT for formulas). Set up default records with data that should be used every time a new instance of an object is created. When a user creates and names a new object, the new object is pre-filled with information from the default record, therefore minimizing user input. Default records for objects also contain default security information. You can create lab specific default records for formulas, named @DFLTlabname.

Security settings that you want used every time a new instance of the object is created. Default records for formulas and items contain security information and other data.

You can specify security for items and formulas through the default records. Security controls the read/write/copy/delete privileges for the owner (creator), group member, and non-group member for this type of object. When a user creates a new object or copies an object of this type, the default security is applied.

The extension field that derives its values based on an association to values in a related primary field.

Specific information of an instance of an object, used to identify different attributes. For example:

• TP0 – rollup parameters
• TP1 – information parameters
• TP2 – equation total parameters
• TP3 – cost parameters
• PER – permission
• ST – set membership

Detail codes are defined in the import process of an object.

A context attribute that can be assigned to formulas, items, and other Optiva objects to define the use of a finished product. The End Use context is configured through the C_ENDUSE enumerated list.

A context attribute that can be assigned to formulas, items, and other Optiva objects to define the user of a finished product. The End User context is configured through the C_ENDUSER enumerated list.

Enables you to define the entries for drop-lists. Users choose from these lists to select a value for a field such as class, location, etc. You can modify existing enumerated lists or create new ones for extension fields in the Enumerated List form.

Enumerated lists consist of standard enumerated lists and custom lists (C_name). Administrators can customize enumerated lists in three ways:

- Change the descriptive labels in a standard list.

- Add unique entries to "C_" (custom) lists.

- Create new enumerated lists for extension fields.

Used to derive a parameter value. These parameters are usually classified as Equation Total parameters in the Lab form. Define the equation in the Equation form and associate the parameter in the Parameter form.

Mathematical and programming type commands that are used to assemble an Optiva equation. Equations are derived to pull parameter or item values from a formula to calculate other parameters. Equations can be used to show alert messages.

Equation functions are used within scripts, similar to the ones that are used for copy method and workflow. See the Infor Optiva Scripting Administration Guide for more information.

Value assigned to an equation to define what type of equation parameter it is calculating.

Also called object creation event. These are user-initiated occurrences that are assigned to a rule to control the creation of new or copied objects.

The extraction of Optiva data into an .XML file or a tab-delimited text file that can be used by applications other than Optiva.

Create extension fields in the Symbol form. You can create fields where users select values from an enumerated list or look up or enter text. These fields can be single-valued or multi-valued. Extension fields are displayed in the Main or Extensions tab for the web client.

File name and directory path of a file that you want to integrate into Optiva. You must include a name that you want to be displayed to the user. Assign a user code to control access. Use the File Locations form to specify these location settings.

Also called data filters. A view that reduces (organizes) the display of parameters, extension fields, attached documentation, items, and workflow tasks to make it easier for users to see only the information that they require. Filters can provide a unique level of security for users who are allowed to use them.

The windows in Optiva that users work with to add, update, and review data. Labs define which forms to include on the Optiva menus. The roles define various levels of security for forms.

A character that controls the display of Optiva data in a form or spreadsheet. The A format is the most commonly used.

A label to identify a collection of entries in a menu. Form groups can be assigned to a Lab to control the group of forms that are available to users in that lab.

The title displayed in the title bar of an Optiva web page. Form labels can be customized. For example, the Formula form can be renamed to Formulation Editor.

The security that is applied to individual forms based on a specific role. Form security controls what a user of a specific role is allowed to do with the data displayed in a form. Security ranges from no access to read/copy/write/delete. Configure form security in the Lab form and Role form.

A combination of ingredients and instructions. Most work that is performed by a formulator is transcribed into a formula. But the formula can represent and regulate more. Any business function can be represented by a formula.

The Formula form specifies the characteristics of the formula and holds in one place the information that is associated with a formula, such as: ingredients and instructions, yield, brand and product information, technical parameters, byproducts, production status, genealogy, and security. Users can perform calculations and scaling on formulas.

Parameters that are required in a script to perform a function. Scripts define the copy methods, equations and workflows. They have a specific syntax of variable name, function and arguments:

Dim variable As Type

variable = function("argument1","argument2",...)

See the Infor Optiva Scripting Administration Guide for more information.

A code that organizes the documents and notes that are attached to an object. Users select a function code from a drop-list whenever they add a document or note. Function codes are configured separately for each object in the Symbols form. Filters determine which function codes are available to a role.

Table of data. For example, formula parameters are displayed in a grid (table) in the Parameters tab of the Formula form.

A designation of more than one user for the purposes of assigning security access to an object. Members of a specified group can be allowed more access to an object than is normally granted to them through their role.

Status information to categorize the reasons why an object, such as a formula, is being held.

The process of adding external data into Optiva’s database using specially formatted text files. An import is performed for large amounts of pre-existing data instead of manually entering data through the Optiva graphical user interface.

A text file, in XML format, that prepares external data for import into Optiva. The data must be mapped to the Optiva database structure using Optiva import language tags. Tags define classes (fields associated with the class and detail about the classes).

A generic term to describe part of a formula. Items can be: raw materials, packaging material, process equipment instructions, user instructions, cost, labor, QC test, or other formulas.

Defines the major modules and forms to include on the menus.

Represents a group (business unit, department, etc.) that is interested in a specific subset of Optiva data that pertains to them and the product they are developing. A lab organizes and filters data of common interest to reduce clutter and improve usability. The types of data that are assigned to a lab are formulas and technical parameters, set codes, and form security.

Each user is assigned to one or more labs. When users log in to a lab, they are exposed to only the data that is important to them; that makes searches and selecting from lists less cumbersome.

Text that is shown in the Optiva graphical user interface. Labels apply to fields, forms, menus, buttons, tabs, and tool tips. You can configure and customize these labels, to suit the specific terminology and requirements of your company.

A set of miscellaneous attributes of Optiva behavior that can be specified at the Lab level.

A context attribute that can be assigned to formulas, items, and other Optiva objects to define the sites where manufacturing and selling take place. Context attributes can be used in searches. Locations are defined in the Location form.

Dialog window that enables users to select specific Optiva objects with which to work. In the web client, the lookup enables a new object to be created or deleted. The list of objects can be organized into subsets to simplify the lookup process for the user. For example, a subset can show only objects that are created by a certain Formulator. Customize the lookup by configuring an SQL query to specify the appropriate data and then updating these tables: FsLookupSet, FsLookup, FsLookupLang, FsQuery.

A formula that is used as an ingredient item in another formula. The formula is assigned a manufactured item code and can be designated as a master formula.

A context attribute that can be assigned to formulas, items, and other Optiva objects to define where manufacturing takes place. This is created the same way as any other location, except that a check box is selected to declare it as a manufacturing location. Context attributes can be used in searches.

The current production formula, which can be used as an item in other formulas. Users indicate a master formula on the Formula form. You can configure the indicator to be read-only.

A role that entitles users to some special privileges beyond the read/copy/write/delete access. For example, master users can set a grid profile for the entire system and undo checked-out objects for all users.

You can configure menu names in the Configure Menu form and you can rename the form labels in the Web Label form.

Now known as system code.

A unique Optiva entity, such as a specific formula, item or parameter. Objects are defined on their own separate form and can be looked up, searched, referenced, and viewed. Each object is created as a certain symbol type, such as Formula, Item or Company.

You can configure symbols by adding attributes and capabilities to the symbol that do not already exist. This modifies and extends the behavior of the symbol in these ways:

• To enable the symbol for use with Workflow so that users can launch a workflow on an object created under that symbol.
• To define annotation categories, such as a safety warning, accessed using the paperclip button.
• To define sets to classify objects.
• To define extension fields to store additional information.
• To define status and approval codes for the symbols.

The control of access to a specific object or record on a Group, Role and User level. When an object is copied, the new object has the default security settings, not the adjusted security settings of the object that was copied.

The pages in the Optiva web client that users work with to add, update, and review data. Labs define which pages to include on Optiva’s menus and the roles define various levels of security for pages.

Parameters dictate the characteristics of the formula such as the percentage of sodium, the pH level, the boiling point, the cost, the drying time, and the SPF level. The parameters of a formula are derived from the parameters of the items. Parameter values change when the item values change. The four types of parameters are: rollup (values pulled up and possibly scaled from the formula’s items), cost (values derived from production costs), informational (not rolled up nor scaled but can be used in calculations), and equation total (values calculated from values of other parameters).

The control of user access to Optiva by administrating passwords for each user. Access to the database is determined by a user name and password. In the User form, you can specify Login Attempts, Life Span, and Reuse for the Password.

The extension field whose values control the values in a dependent field according to a pre-defined association. See also dependent field and extension field.

A context attribute that can be assigned to formulas, items, and other Optiva objects to define the type of product. Context attributes can be used in searches. You configure the available product types from which users can select in the C_PRODTYPE enumerated list.

Values that determine Optiva’s behavior regarding the user interface, such as unit of measure displays in tables. Profiles are configured at different levels of use: the entire system (Profile form), each lab (Lab form), or individual users (User form).

A system code that allows users to identify reasons for working on a formula. Users can select this when defining a new version of a formula.

A link from one object to another type of object. In the same way that you can add items to a formula on the Item Lines tab, you can add other types of objects, such as companies or specifications, on the References tab of the Formula form. You can edit a reference directly from the References tab. You can create a copy of the referenced object without leaving the References tab. Most Optiva objects can reference other objects. You configure the types that are available.

A system code that enables users to identify the type of reference when they are adding references to an object such as a formula or specification (used in conjunction with reference status code).

A system code that enables users to identify the status of the relationship between the object and its reference when they are adding references to an object such as a formula or specification (used in conjunction with reference code).

Roles enable access to forms and filters. Each role defines the available forms and tabs and the level of access for each (read/copy/write/delete).

What happens when a user is assigned to a role? Access to dialog boxes, forms, and tabs is controlled by the role that is associated with the lab the user is logged into.

Roles define security for types of objects. For example, a role can specify that for formulas in general, users in that role can copy but not write. Filters specify that only users within a specific role can use the filter, and the special security that comes with it.

Templates can vary by role. In other words, the template for the Item object can be configured differently for the @DFLT role than for the RL_ADMIN role. If desired, you can have separate templates for each type of item. For example, you can have a separate configuration for Raw Material items and another template configuration for Packaging items. Role templates are configured in the Configure Templates page.

A function whereby the parameters of an item or sub-formula influence the values of the parameters in the formulas that use them.

Formula Rollup, an automated process, recalculates formulas to incorporate parameter value changes in items and sub-formulas.

Formula rollup allows automated rollup of:

• all formulas
• all formulas containing a specific item
• all formulas marked for rollup through the Optiva Workflow module
• all formulas listed in the Formulas form

A set of instructions to control the creation of new objects. A rule can contain auto code segments and copy methods. You configure a rule to control how users can name new objects and to copy information from existing objects to pre-fill some fields in the new object. Rules are configured in the Create Rules form.

A structured set of function statements used within Optiva to define a copy method, workflow or equation. Scripts use Visual Basic .NET scripting, syntax of variable name, function and arguments:

Dim variable as Type

variable = function("argument1","argument2",...)

For more information, see the Infor Optiva Scripting Administration Guide.

A list of matching search criteria. You can customize the display of search results to include more or less details. You can pivot the table to combine all the parameters for each formula in a formula search.

Access privileges (i.e. read/copy/write/delete) to an object. These security privileges are based on the owner, group,or role. Security is applied to forms, tabs, dialog boxes, objects in general and specific instances of objects.

A context attribute that can be assigned to formulas, items, and other Optiva objects to define where selling takes place. This is created the same way as any other location, except that a check box is selected to declare it as a selling location. Context attributes can be used in searches.

See manufacturing location and location.

A classification for objects that can be used in searches and to filter lookups. For example, a set of formulas can belong to the set Food or Beverages.

Set templates are pre-configured objects with specific attributes. When set templates are assigned to objects, only the sub-set of attributes are available for the object. For example, a set template for dairy products reduces parameters for assigned objects to calcium and saturated fat.

Used with Advanced Workflow Management (AWM). These calendars define the workdays, non-workdays, working hours per day, and any overrides for a specific location.

These calendars are used by Optiva to calculate the start date and end date for each task. These calendars are also used to calculate the load percentages for each user who is assigned to the task.

Excel spreadsheet for loading Optiva data.

An indicator for a formula or item that describes how far along in the development process the object is. You can also set up a numbering scheme for status codes to enable Optiva to automatically set the status code value for a formula when it is copied or saved. Define status codes on the Symbol form.

A group of indicators for a formula, item or other Optiva object that include Status, Approval, and Hold. Users assign values to describe:

• how far along in the development process the object is (Status)
• whether to hold development or manufacture (Hold)
• the current level or authorization (Approval)

You define status codes and approval codes on the Symbol form. You define hold codes on the Enumerated List form.

An Optiva object type, such as formula or item.

A system code, formerly known as a miscellaneous code, is an indicator that is used to categorize information in the database. Some system codes are shipped with Optiva. For example, ADMIN is a group code that can be used to categorize system administrators.

Functionality for administrators to configure and maintain Optiva. This includes configuring labs and other basic Optiva components, customizing the user interface, and specifying security.

A profile that determines Optiva’s behavior, set for the entire system.

A sub-section of an Optiva form that organizes related information for display and data entry. Administrators can customize tabs by renaming the label of the tab and by controlling who has access to the tab.

The text description that is displayed on a tab of an Optiva form. For example, some forms have a tab labeled Main. Tab labels can be customized.

The control of access applied to individual tabs on a form, based on a specific role. Tab security is specified in the Role form, from the Form Security tab. Tab security ranges from no access to read/write.

Also called import tags. Special indicators in an import text file that structure and outline the data that is being imported. Tags map the external data to the existing fields in the Optiva database. Tags include FsImport, FsObject, FsDetails, FsDetailRow, and FsField.

Help text that is displayed when a user holds the mouse over a text field or button within Optiva. Tool tips can be customized to display different text.

Defined by Optiva. UOM is a standard that is used to measure and convert quantities of items. UOMs are the lowest level building block of the Optiva application. UOMs are usually assigned to parameters. Items then have parameter values assigned to them, usually using a UOM. These values are then rolled into formulas as items are added directly (to formulas) or indirectly (through sub-formulas).

UOM types are categories of units of measure. One UOM type can have several instances of UOMs. For example, the Mass UOM type can have LB and KG units of measure.

Person who is logged into Optiva.

Settings for a specific user that determine Optiva’s behavior regarding the user interface, such as table formats, window size, language, and unit of measure displays in tables. Configure user profiles in the User form.

A pre-configured query that a user can select to display a list of objects directly or indirectly related to the current object. Views are available on the Reports tab of most object forms. You can configure a view to display where the current object is used in other objects. Or, you can configure a view to display objects that are created by the same user. Views are configured by creating an SQL query to define the data that you want to retrieve and then update these tables: FsLookup, FsLookupSet, FsLookupLang, FsQuery.