Term

Definition

Main UI

Primary Coghead user interface used by Members (as distinguished from Coglet Widgets or custom UI).  Through this interface Members can navigate through the Accounts and Applications with which they are associated.  The main UI has a Home page, an Account Management interface and an Application interface.

Coglet Widget

A Coglet is a slice of Application functionality much smaller than a complete Application, intended to be embedded in a Web page (outside of Coghead). Typically, a Coglet Widget presents a filtered list of Records from a Coghead Collection or a detail Form-View for a particular Record and associated actions.

Home Page

Member-centered page in the Main UI that allows the Member to navigate through their accounts and applications, access Support Resources and Coghead Community content.

Manage Account Interface

Members with administrative privileges can use the Account Management interface to manage Users, Groups, Permissions and Billing related aspects of the selected account.

Application Interface

The basic building block in Coghead – is composed of a set of data containers and associated Actions. Each Account has a list of Applications.

Tabs

Coghead applications must have at least one tab. A tab can display information associated with a Collection of Records or with a single Record.

Navigation Panel

Displays custom links for quick navigation within an account and shortcuts to Support resources, as well as update messages.

View Panel

Displays the list of Records in the selected Collection tab. 

Form Panel

Displays data for the selected record. The form is used to enter new records or modify existing records.

Term

Definition

Member

A person with a valid Coghead login ID.

 Application

 A container for Applications, Users, Groups, Permissions and Application Data within Coghead. Account usage parameters such as Users, Application data size, and Attachment data size provide the basis of billing.

 User

 A User represents the assignment of a Member to an Account. One Member can be a 'User' in more than one Account.

 Groups

 A set of Members within an Account. Groups are used to control Permissions. E.g., a Group is given a set of Permissions for an Application and as a result all Members assigned to that Group are able to execute those permissions.

 Application

 The basic building block in Coghead – is composed of a set of data containers and associated Actions. Each Account may have numerous Applications.

 Permission

 An ability to do something (like Read, Write, or Execute) a particular artifact in Coghead (e.g. an Account, an Application, a Collection, a Record, an Action).

 Linked Application

 A Linked Application is basically a Coghead façade on an application that is hosted outside of the Account in question. The Linked Application could be connected to an External (Non-Coghead) Application via webservice apis or could simply be connected to a Coghead Application in a different account.

 Data Set

 A Dataset contains only the data associated with an Application and can be separated from an Application definition. A particular Dataset could for example be used for testing or could be archived for historical purposes.

 Coglet

 A Coglet is a slice of Application functionality much smaller than a complete Application, intended to be embedded in a Web page (outside of Coghead).

Term

Definition

Collection

A Collection is the basic multi-record data container used in Coghead – it contains a set of Records that share a common structure (the Collection Data Structure). Applications typically contain several different Collections corresponding to the stuff managed by the application (e.g. an Order Management application could have Collections of Sales Orders, Invoices, Shipment Receipts, etc.)

 Record

 A Record is a singular top-level data object. A Record has an associated Data Structure and Form like a Collection but there is only one Record (the Item itself).

 RecordSet

 A RecordSet is a set of Items/Records in a Collection.

 Data Structure

 Each Collection and Page has an associated Data Structure that defines the set of Fields associated with the Records in that Collection or with the Page. Coghead Data Structures are tree-like (as opposed to being restricted to tabular structures used in relational databases), and include a variety of Field types.

 Form

 A Form is used to display the details of a Record or Page and to provide a means of data entry for Users.

 View

 A View is a filtered list of Records in a Collection and a tabular projection of that Collection. Views can be pre-defined and named or can be created dynamically as the result of a search.

 Action

 Actions are the way application logic is captured and executed in Coghead. An Action consists of a set of pre-defined Steps that are executed in a particular sequence. Actions can create, modify, and delete data stored in Collections and can execute Searches on Collections. In addition, Actions can invoke other Actions, including calls to Linked Applications.

 Version

 Application definitions are Versioned, and can be separated from the Application Data Sets with which they are associated. Each Application Version contains the Collection, Page, & Action definitions they encompass. Versions can either a Prototype Version or a Production Version as designated by an Application administrator. At any time there can be only one Active Production Version and one Active Prototype Version. The Active Prototype can be promoted to production and then become the Active Production Version.

Term

Definition

Expression

Expressions are XPATH expressions that provide the ability to specify more complex Field values and search expressions.

 Field

 Fields are the elements from which Data Structures are constructed. A variety of Field types are supported in Coghead.

 Simple Field

 A Simple Field is used to hold simple data types like Strings, Numbers, Dates, & Currency.

 Group

 A Group is used to compose other Fields into more complex structures – e.g. creating an address field from street, city, state, and zip code fields. (can be done through the 'concat' function)

 Link Field

 A Link Field points to a Record or Item in a Coghead Application. The Link field displays a single Data Field associated with target object.

 View

 An embedded View within a Data Structure. This View is either linked to a remote collection or to a local (embedded) collection. A filter property determines which records are associated with the View (for the linked case). All records are associated with the local case.

 View Field

 The fields from the View that are to be projected (i.e. the columns in a grid display of the View).

Term

Definition

Action Step

Individual Steps within an Action definition are called Action Steps. They include the following types:

 Retrieve Records

 A step that executes a search on a Collection and returns a list of Records.

 Perform Action

 A step that executes an Action on a Coghead Application (including Linked Applications).

 Set Value

 A step that modifies Field values on a particular Record.

 Branch

 A Branch step allows conditional branching in an Action.

 Loop

 A Loop steps allows looping sequences of execution in an Action.

 Exit

 The Exit step facilitates premature termination of the Action.

 For Each

 The Foreach step allows a sequence of Steps to be executed for each Record returned by a search.

 Alert

 The Alert step provides a way to notify a User of some context relevant information from within an Action or to assign a Work Item to a User.

 Action Variable

 Action Variables are used to store data inside of an Action definition. There are two primary types of Action Variables:

 Record Variable

 Used to hold the value of a single Record of a particular type.

 Recordset Variable

 Used to specify a search Expression and to hold the search result which is a list of Records.

 Additional Input

 Additional Input is an Action Variable and associated Form that is used to collect additional data when the Action is executed.