This appendix contains definitions of certain terms used in this reference manual.
| Variable | Description |
|---|---|
| Action Buttons | Product-specific functions or navigation that the user can invoke. "Post," "Encumber," and "Distributions" are examples of actions. |
| Block | The representation of an entity on a form. For example, the Vendor block consists of the attributes pertaining to the Vendor entity. |
| Canvas | The surface on which interface items and prompts are physically drawn. Canvases are displayed in a window. |
| Context | The information necessary to uniquely identify an instance of an entity. For example, when viewing a Sales Order line, a user should also see the Sales Order Number in order to retain context. |
| Dialog Box | A window used to enter information needed to complete a specific action. The user must interact with this window before proceeding. |
| Editable Field | A field that allows the user to type information. A field may dynamically change from editable to noneditable as the user operates the form. Nonenterable fields include context, overflow regions, session-disabled, dependent fields, and fields on queried records that cannot be changed. |
| Folder | A type of block that allows users to customize the screen and query criteria. |
| Field | An interface element that displays information to the user and/or accepts input from the user. Text items, check boxes, and poplists are examples of fields. Also known as "Widget" or "Item." |
| Gateway | A hybrid format consisting of a Summary, Detail, and Find windows. The summary block is almost always a Folder block. From the gateway the user can perform inquiries or limited updates. For example, the Discrete Jobs Gateway in Work In Process (WIP) allows the user to find Discrete Jobs, inquire on details and perform limited updates to them. |
| Master-Detail | A relation between two entities that indicates a hierarchy of information. For example, a Sales Order consists of a Header entity and a Line entity; the Header is the master of the Line, and the Line is the detail of the Header. |
| Modal | A state where the user must supply specific information before continuing operation of the application. A dialog box is modal, implying that the user can only operate on that window, and must indicate when they are done (usually by pressing "OK," "Done," or "Cancel" buttons). |
| Origin | The point of a widget that corresponds to the (X,Y) position that locates it. |
| Organization | The current value of the organization, set of books, business group, etc., that the user is running. |
| Overflow Region | A single-record, display-only set of fields that display attributes related to the current record of a multi-record block. |
| Prompt | A label that uniquely identifies an item. "Salesperson" and "Item Description" are examples of prompts. |
| Record Scroll Bar | A scroll bar that controls the set of records displayed. |
| Region | A set of related items within an entity. "Currency Information" is a region of the Purchase Order Header entity, consisting of the Rate, Type, and Date fields. |
| Region Scroll Bar | A scroll bar drawn within a region that controls the visible portion of a scrolling region. |
| Save | The process by which data is committed to the database. Explicit saves are initiated by the user (for example, choosing Save from the File menu, or pressing the Save button). Implicit saves are those inherent in the nature of a function (for example, approving a document saves the transaction). |
| Siblings | A relation between entities indicating that two or more entities have the same master entity. There may or may not be a relation between the sibling entities themselves. A Sales Order may have both Lines and Credits, but there is not necessarily a relation between the Lines and Credits entities themselves. |
| Toolbar | A series of iconic buttons that replicate common actions on the Menu, such as Save and Print. |
| Window | A screen in a graphical user interface (GUI) environment. A window is a frame enclosing a surface, on which elements are painted. |
| Workbench | A workbench is a more powerful form of gateway. Typically users could perform a significant portion of their job functions from the workbench and keep the workbench open all day. For example, the Orders Workbench allows the users to find Orders and Returns and enter, update, approve, cancel, and place them on hold. |