What is a card?

This article applies to BOOST EMPOWER licenses

Purpose of the article

Cooperlink uses the principle of the card to add metadata to the different objects managed in the application (e.g. documents, tasks, email, ...). Each card contains a set of fields representing the metadata. In a way, the card is the identity card of the object it represents.

The app administrator defines a card template that the user can use for their projects.

Some cards may require user action (e.g. approval in a workflow circuit).

Contents of a map

A card is a collection of custom fields with properties.

The cardis characterized by:

• A type (see below)
• A unique identifier (ID). The identifier allows the map instance to refer to a given pattern.
• A label (name)
• A set of fields

Example of a card: 

Card Types

Several types of cards are available:

• Workflow: card associated with the workflow data model
• Document: card associated with the Document Data Model
• Project: card associated with the Project Data Model
• Workspace: card associated with the workspace data model
• Mail: card associated with the Match Data Model

Card Templates

Different card templates can be configured in the app to allow users to use them directly within the app. In a project or workspace, manager determines which Projects, Workspace, and Documents cards are applicable. Workflow cards are directly associated with workflow templates.

Each card template can result in many card implementations within the application (instances). When a card template is modified, all cardinstances that refer to it are also modified.