Concepts are the fundamental structures that form the backbone of data in Robosme CRM.
A concept defines what data will be stored, how this data will be related, and how it will be presented to the user.

Every record created in Robosme must be part of a concept. Forms, lists, charts, workflows and reports work directly through concepts.

In short:
Concept = Data + Behavior + View

Role of Concepts

Thanks to concepts:

• You can create a one-to-one data model for your business
• You can enable different teams to work with different screens and information
• You can transform your processes into system behavior

Therefore, concept design is the most critical step of customization.

Concept Types

Concepts in Robosme are generally divided into three groups:

System Concepts

Concepts that form the core of the platform.

• Cannot be deleted
• Structurally limited
• Some fields and behaviors cannot be changed

Definition Concepts

Recurring data sets used as references.

• Country
• City
• Unit
• Universal definitions

Typically used in lookup fields.

Custom Concepts

Concepts created specifically for the business.

• Fully customizable
• Fields, relations, forms and lists are free
• Enables one-to-one adaptation of processes to the system

Concept Properties

When creating a concept, not just a table, but the behavior set of the concept is defined.

The following settings determine how the concept will work in the system.

Basic Information

• Display Name
  The name displayed in the user interface. Managed through the translation document and supports multiple languages.
• System Name
  Internal system and database reference name. Another concept with the same system name cannot be created.
• Description
  Explains the purpose of the concept. Managed through the translation document and supports multiple languages.
• Visual
  A visual can be defined for the concept. Used in menu, list and relation views.

Behavior Settings

These settings determine the fundamental behaviors of the concept in the system.

• Activity Concept
  Marked if the concept represents an activity type (Email, Phone, Meeting, etc.),
  When Activity is selected, the Ownership setting becomes selected and read-only. Primary Field definitions are hidden.
• Ownership
  Enables ownership of records on a user or team basis.

Functional Features

These features enable the concept to work with user interaction and processes:

• Favorite
  Allows users to add records to favorites (follow them).
• Business Process
  Enables the concept to work with staged business process (stage) logic.
• Notes & Documents
  Allows adding files and notes to records.
• Queue
  Allows records to be added to queues.
• Media
  Allows visual and media content to be associated with records.
• Quick Create
  Allows quick record creation from lookup fields.
• Approval
  Enables concept records to enter the approval process.

Relation and Activity Features

These features are especially used in activity and relation-intensive scenarios:

• Multi-Lookup / Multi-Reference
  In multi-lookup and multi-reference fields, determines which concepts can be selected as relations. This allows controlled relationships to be established with multiple concepts through a single field.
• Activity Participant
  In activity concepts:
• Sender
• Receiver
• Participant
  roles can be defined.

Participant types can be customized and ordered.

• Activity Relation
  Distinguishes:
• Which record an activity is related to
• Which record is a participant in

Plays a critical role in timeline and reporting.