Actions are saved to activities and appear to users as a button that, when clicked, will display a selected form so users enter and save data in an object.
Actions on a transition allow administrators to add an automated process to an object as it moves through its workflow states.
Saved to an application, activities determine the data an end user will create, edit, and view through any actions or roles saved to that activity.
A user account settings, All Access grants users access to all object types and their objects within the organization. This means a user with these settings enabled will be able to view all objects and their data without an administrator adding the user to a role, adding one or more object types to the role, then configuring the workflow permissions.
An object type used to create data definitions, which allow you to select which relationships and references a data visualization or assessment will be drawn from.
A tool that uses a single user account to generate a link to grant multiple users limited access to Core. Users with the link don’t need to provide login credentials, but may only view the form/activity selected in the settings.
A composite of all the key elements within Core (object types, object type groups, fields, forms, roles, etc.) that directs the flow of data to end users. Applications hold activities where users complete tasks (actions) and view information (views).
Allows users to collect, review, and assess data by evaluating business activity (e.g. audit, investigation, control assessment, etc.) continuously or from a particular point in time, from different dimensions. Assessments have functionality similar to object types and can have components, workflows, objects, and can be added to applications, reports, and object type groups, etc.
Bar and Column Charts
A type of report that can be shown as bars or columns and displays data from numeric fields, select lists, formulas, relationships, and workflow states.
A field, relationship, reference, formula, or role that can be saved to an object type that can then be added to a configurable form.
A set of requirements that must be met before an object is moved to a state and an action is performed. Conditions are created on triggers in an object type’s workflow.
A feature that allows you to create custom forms for users to complete as they work through actions and views within an activity. You can create headers, include instructions, add relationships, references, formulas, and roles (components), as well as add fields that can be marked as required or read-only. You can select specific configurable forms to display depending on the current state of the object.
An auto-created state on every workflow that cannot be deleted, but its name, description, color, triggers, and transitions can be edited. An object cannot be saved until it has successfully transitioned from the Creation state to another state in the workflow.
Used to select which relationships and references a data visualization or assessment will draw its data from. The relationships and references you can choose from depend on the anchor or assessment's focus object type.
A data visualization that displays object data in a spreadsheet-style format. Users accessing a data grid through a view can sort, filter, and edit data, as well as show or hide columns, click through pages, and adjust column width or the number of rows displayed per page.
A feature that allows you to create new objects and enter relationship data in bulk by entering data on a spreadsheet, then uploading that spreadsheet into CORE. Data Import does not create new object types or relationships, but it can update existing objects’ data.
Part of a data definition, the data path displays all the relationships and references saved to the selected anchor or focus object type, so you choose which object types data is drawn from.
Displays data from a selected anchor (object type) in reports (charts, heat maps, or tables), export reports, or data grids.
An auto-created form that displays all the components added to an object type (except roles). Default forms cannot be edited, but you can control the components a user sees through configurable forms.
An auto-created state on every workflow that can be edited or deleted as needed, however, if this state is deleted, you must ensure the Creation state which is also auto-created, has another state to transition to as failure to do so will prevent an object from being saved.
The category of data that appears on an assessment. Dimensions can be custom (similar to a select list) or based upon any relationships or references saved to the focus object type.
The non-administrative users who work with CORE and its applications after the applications have been created and configured.
Permissions on a role that grants users access to specific objects based on the object types added to the role. Before a user can see any objects, the role must be added as a component on the object type and configurable form, then the user must be selected in the role field that appears on the form. Users with explicit permissions may also be granted inferred permissions so they can view objects related through relationships or references. You may also need to configure inferred permissions for roles with explicit permissions enabled.
A component added to an object type and configurable form where a user can input data. Fields can include plain text, numeric, date and time formats, as well as select lists (dropdown menus), and attachments.
A component that compiles data from numeric and variable values to generate conclusions, such as Incident Severity, Estimated Damage, or Likelihood the Incident Will Recur by displaying data on objects as a number, label (e.g. Low, Medium, High), or both a number and labels, all with optional colors. Variable data is created from numeric data from fields added directly to an object type or from fields on an object type added through a relationship or reference.
The object type selected to create an assessment. Focus object types are then used to create data definitions, which allow you to select which relationships and references the assessment data will be drawn from.
Permissions on a role that grants users access to all the records (objects) for the object type(s) added to that role. Users with global permissions do not need to be added to an object to view it nor do they need to be granted inferred permissions, but what they can do with the objects (create, read, edit, etc.) is determined by their role's workflow permissions for each state.
Additional permissions on a role that allows administrators to select which additional objects, connected through relationships or references, a user has access to without directly granting permission through the role field on a form. This ensures users within a particular role with explicit permissions are indirectly given the appropriate access to the information they need when interacting with related objects.
An object that contains the same data as an existing object referenced on an assessment. Instances are saved to the assessment and contain the same data as the original object, but are assigned unique IDs that are .1 number higher than the original. Any additional instances on the same objects are assigned IDs that continue incrementally (e.g. .2, .3, .4, etc.). You can also identify instances in a view because they display the dimensions from the assessment below their names.
A report type that uses colors and X and Y axes to show where object data falls on a scale. Heat maps are most commonly used when analyzing an organization’s risks, the likelihood the risks will occur, and the impact on the organization should they occur.
|Reference objects specific to your organization that capture important details. These are typically created when implementing a specific Core solution or app.|
One to three letters, with or without a color, that represent and help you quickly identify object types throughout the system.
A record saved to an object type (the record category). For example, Incident is the object type, while Accident, which outlines the details of an on-site incident, is the object.
The category of the data collected (e.g. Incident, Employee Record, Witnesses, Vehicles, etc.). Once a record is saved to an object type, it becomes an object. Object types can be configured to control who can access them, what fields are visible and completed on forms, and the process through which the data is collected.
Object type group
One or more object types assembled into a group for the purposes of creating a relationship. When creating a relationship, you must select an object type group, which determines which object types the data is drawn from when completing the relationship field or table on a form.
A feature through which you can duplicate the configurations and user accounts (but not the data) of an existing organization into a new organization. This is done by exporting the configurations from the existing organization into a .JSON file, then uploading the file to a blank organization through Org Manager.
A type of report. Pie charts can be shown as a full pie chart or half-pie chart and display data from numeric fields, select lists, formulas, relationships, and workflow states.
A component that indicates that multiple objects are connected through a relationship. For example, if you created a relationship called “Incident Report Writer” on the Incident object type using a group with the Employee Record object type saved to it, you can add a reference to an Employee Record configurable form to show any incidents an employee may have created. References are automatically created with relationships.
A component that connects two or more object types together when object types are added to an object type group and that group is selected when creating a relationship. For example, to track which employees are creating Incident objects, you would add the Employee Record object type to a group called “Employees,” then create a relationship on Incident using the Employees group, naming the relationship “Incident Report Writer.” Users creating new Incident objects will now be able to select or create an Employee object in the “Incident Report Writer” field to indicate who created the report.
Displays object data as it was entered into a form. This allows users to view and share non-editable, printer-friendly versions of completed forms or forms in read-only mode with other users. Note that if a user does not have permission to see an object, the form will not be displayed on the report.
Displays data from a selected anchor (object type) in pie charts, bar charts, tables, repeatable forms, or heat maps. You can also add free form text to reports.
A feature that controls the data a user can create, edit, delete, view, or manage on object types. When users are added to a role, they’re bound by the permissions configured on the role, which include global, explicit, or inferred permissions.
The various stages of the data collection process (e.g. Create, Triage, Review, Investigate, Close) that are saved to a workflow. You can create multiple states, but you must have at least two states on an object type to successfully save new objects.
A type of report that displays data in columns based on your selection in the report settings. Users can click on any of the data in the report to display a form selected by administrator. Table data can be exported to a Word or Excel file from a view.
A workflow element that defines the state an object will move to once a trigger has been clicked on a form. For example, if a user clicks the Create trigger, the transition saved to that triggers determines that the object will move to the Triage state. You can also add actions to transitions that can send emails to users within selected roles or automatically add the currently logged in user within a selected role to object so that they may access it once it has transitioned.
The event in a workflow that prompts an action and the movement of an object from one state to another. Triggers are either timed to automatically prompt an action each night or appear as clickable buttons on a form that, once clicked, moves the object to another state and performs an action based on the transition saved to the trigger. For example, clicking Create on a new Incident will move the object from the Creation state to Triage. The state an object moves to is determined by the transition saved to the trigger.
A collection of CORE users saved to a group (e.g. Employees or Managers) for the purposes of quickly adding those users to roles.
Data entered or selected in a field. For example, Name is the field, but the data entered in that field, John Doe, is the value.
Displays data visualizations and/or list of objects a user can review or edit as needed. You can specify which objects, reports, or forms are displayed based on the object type and workflow state. Views are saved to activities.
Settings that allow administrators to control the flow of data as well as define what data is displayed, where it’s displayed, and to whom it’s displayed through applications, activities, search results, data visualizations, and assignments. Workflows are comprised of states, triggers, transitions, conditions, and actions. Each object type must have a workflow.