Introduction

Before building applications with Coactive, some key concepts and definitions need to be understood to help accelerate your ability to generate solutions in the Coactive Framework.

They are as follows:

  1. Definition of data records (Tables) that the application will be utilizing.
  2. Construction of the user interface (Layout and Forms) that will facilitate CRUD (create, read, update, delete) functions across the data.
  3. Creation of Conditional Formats and the creation of Security Groups.
Terminology

Below is a reference table of coactive terms and how they translate to traditional database or spreadsheet terminology.

coactive
Traditional Database Spreadsheet
Workspace Database Workbook
Table Table Worksheet
Column Column Column
Conditional Format N/A Conditional Formatting
Defining Tables and Columns

Click "CREATE" in the top left, and select “Table”.

Various attributes of the table may be edited in the Table Editor.
Here is a detailed description of attributes that may be configured in the Table Editor.

In the lower portion of the Table Editor there are tabs that allow user to edit additional features of the table including the addition of Columns/Fields to the current table. 

Click the plus sign icon below the Columns tab to add a new Column to your table.
Here is a detailed description of attributes that may be configured in the Column Editor.  

Creating Forms
  1. Click 'CREATE' and select “Form”. 
  2. Choose a Table from the selection window, as all views are based off an existing Table.
  3. Columns from the selected Table can be selected for the new form.   

When all desired columns have been selected, select either “Finish & Load” or “Finish & Suppress Load”. This will force the form to launch without data loaded and can be disabled in the Form Editor.  

The Form now may be edited by switching to Design Mode, or clicking the arrow tool.
Here are additional details on editing forms.

Conditional Formatting

Conditional Formats are overlays applied to entire records or individual fields; either automatically or manually. These overlays are used to control data appearance and behavior of records within the Coactive Framework. (1) A New Conditional Format may be created by selecting the main create Icon , and selecting “New Conditional Format”. This will (2) launch the Conditional Format Editor.
Here are additional details on Conditional Format attributes.

Security Groups

Security Groups are objects that define what the Users that belong to them can and cannot do within the application. Security Groups contain basic permissions, which can be further refined by modifying other objects in the application.  A New Security Group may be created by (1) clicking on the main create Icon , and selecting “New Security Group”. This will (2) launch the Security Group Editor.

Glossary of Terms

These are commonly used terms and references that coactive and products built on the coactive framework use.

Term Definition
Database The logical location that contains all the columns/fields, tables, records, tasks, formats etc. Each coactive workspace will have it's own database.
Category Use categories to allow administrators to differentiate permissions for Table, Column and Form. This differentiation is enabled by categorizing two columns within a table with different permissions assigned.

Every table must have a category assigned. If one isn't selected the category 'General' will be assigned. Fields in the General category inherit the table security settings. To add a category simply type it in the category list.
Tables Tables are the primary data management tool in Coactive. Records are displayed much like in a spreadsheet with sort, filter, edit, add, and delete options based on tasks and fields available. Use shift and ctrl keys to select values or records for copying.
Action Similar to Macros, actions are pre-defined set of operations that can be edited to perform any operation a designer would like.
Task  One or more actions used in sequence in a Coactive solution.
Workflow Workflows are used to load data and execute a Task.  This is typically done in the background in a hidden form.
Relationship Relationships are connections between records of different Tables. Relationships can be created or broken automatically via field change or manually. Examples include using drop-downs, adding sub-grids, or loading data from a form based on a saved variable.
Collapsible Group A subsection of a Coactive Form that may have a grid, form, or other entities. It may or may not have a distinct name.
Column Components of a table with defined data type, expression, and other settings.
Record A collection of data which satisfies the column requirements of a given table and form configuration.
Table Used to define a collection of fields that belong adhere to the same requirements. Similar to a data set in a spreadsheet or a table in a database.
Conditional Formatting Formatting applied as an overlay to grid or form data. It may affect the appearance or access to a specific field or record. Used with conditional formatting a designer can customize the user experience.
Sub-grid Any form containing a grid that has been assigned a 'Listener' in the Form Editor and has a Form Type of 'Related View'. The sub-grid will only show records related to the record selected in the Parent Grid  Users can use sub-grids to form and maintain one-to-many relationships in coactive.
Editors Each entity in Coactive has an editor,  available in the right rail,  which provide options to define and configure each aspect of a solution.
User User objects represent individuals with access to the database. User objects are members of one or more User Groups and may be deactivated.
User Group User Groups are objects that define what the Users are able to access in the configuration. These contain basic permissions which can be further refined by adding to specific forms.
Form Forms contain grids, fields, and buttons designed as a user interface. However, in coactive, a designer also uses hidden forms as workflows to perform calculations, filter a pop-up, or update related records in the background so as to not be seen by the user.
Have more questions? Submit a request

0 Comments

Please sign in to leave a comment.