Skip to content

Customer lifecycle management (CLM)

All entities support Record types, which is a functionality that enables the system to store different types of data related to each entity, and to provide different functionality.

Main menu for all contacts. Can be added to the main menu. Possible to add listviews.

The idea of the contacts is that you can have both internal and external contacts. All users in Deem Insight must be created as a contact before the user can be created.

Contact

FieldDescription
NameName of the contact. Mandatory.
PhonePhone number to the contact. Optional.
E-MailEmail address of the contact. Mandatory.
TitleTitle of the contact. Optional.
Reports toName of the person the contact reports to. Must be a contact in Deem Insight. Optional.
Business AreaBusiness area the contact belongs to. Must exist in Deem Insight. Optional.
Main accountMain account the contact belongs to. Must exist in Deem Insight and is recommended to set up. Optional.
External idExternal id of the contact. Optional.
StatusStatus of the contact (active/inactive). Mandatory.
TypeType of the contact. Can be set in Admin-Record Types. Mandatory.
CountryCountry of the contact. Can be set in Admin-Countries. Optional.
LanguageLanguage of the contact. Can be set in Admin-Languages. Optional.
Contact related to AccountList of accounts the contact is related to. Optional.
Contact related to ProjectList of projects the contact is related to. Optional.

Tasks tab: List of the tasks the contact is set as owner of.

Projects tab: List of the projects the contact is set as owner of.

Assets tab: List of the assets the contact is set as owner of.

Timeline tab: Timeline related to the contact.

Reports to tab: List of the contacts which reports to the actual contact.

Main menu for all activities (admin). Can be added to the main menu. Possible to add listviews.

The following parameters are mandatory for the activities:

FieldDescription
TypeTypes are custom, and can be set up in record types (there are some standards which can be used). You can also set default status for activity types. For example the activity type call has default status closed.
AccountAll registered accounts are available in the drop down list.
AssigneeYou can choose assignee in the dropdown list. All contacts that are either agents or has main account as the chosen account, are in the drop down list. If left blank the creator will be set as the assignee.
NameThere is no need for a unique name for each activity.
KeyThe key is automatically generated based on the selected account.
ReporterYou can choose reporter in the dropdown list. All contacts that are either agents or has main account as the chosen account, are in the drop down list.
Priority Priorities listPriorites are custom, and can be set up in priorities (there are some standards which can be used). Default priority can be ticked off in priorities. If no default priority is set, the order in the priority column will be used.
Created timeAutomatically generated when the activity is created.
StatusStatuses are custom, and can be set up in statuses (there are some standards which can be used). The available statuses varies depending on where you are in the workflow. The link between statuses and workflow are set in workflow in the admin menu.

The following parameters are optional for the activities:

FieldDescription
ProjectThe project must already exist on the account, and available projects will be found in the dropdown list. Once a project has been added to an activity, it can not be removed or edited.
NotesFree text field.
Due dateDue date can be set in the drop down calender. If a date is not selected, either left open or the current date will be filled out e.g. if the activity is set to be automatically closed.
AssetThe asset must already exist on the account, and available assets will be found in the dropdown list.
Closing reasonClosing reasons are custom, and can be set up in resolutions (there are some standards which can be used).
Closing descriptionFree text field.

We recommend to use list views to structure the different activities if activities is set up in the menu.

Example:

Activity list view

Workflow: Workflow types for tasks. Standard values are set for each task.

Timeline: Overview of all timelines for tasks.

Attachments: Overview of attachments used in issues, activities etc.

Main menu for all issues. Can be added to the main menu. Possible to add listviews.

Deem Insight is very flexible regarding the setup for both activities and issues. But the idea behind having both types of tasks is to diversify the use, where activities are for simpler tasks (e.g. follow up customers), and issues can be more complex. Usually type, workflow and statuses are completely different for these two types of tasks.

There is also a possibility to create a sub issue, which will be linked to the main issue. The sub issue is an ordinary issue, and is handled as an ordinary issue, but there is an existing link between the two issues.

New sub issue

The following parameters are mandatory for the issues:

FieldDescription
ProjectThe project must already exist, and available projects will be found in the dropdown list. The project is always attached to an account. Once a project has been added to an issue, it can not be removed or edited.
TypeTypes are custom, and can be set up in record types (there are some standards which can be used). You can also set default status for issue types.
AccountThe account is automatically set based on the project selected.
AssigneeYou can choose assignee in the dropdown list. All contacts that are either agents or has main account as the account linked to the project, are in the drop down list. If left blank the creator will be set as the assignee.
NameThere is no need for a unique name for each issue.
KeyThe key is automatically generated based on the selected account.
ReporterYou can choose reporter in the dropdown list. All contacts that are either agents or has main account as the account linked to the project, are in the drop down list.
PriorityPriorities are custom, and can be set up in priorities (there are some standards which can be used). Default priority can be ticked off in priorities. If no default priority is set, the order in the priority column will be used.
Created timeAutomatically generated when the issue is created.
StatusStatuses are custom, and can be set up in statuses (there are some standards which can be used). The available statuses varies depending on where you are in the workflow. The link between statuses and workflow are set in workflow in the admin menu.

The following parameters are optional for the issues:

FieldDescription
NotesFree text field.
Due dateDue date can be set in the drop-down calendar. If a date is not selected, either left open or the current date will be filled out e.g. if the issue is set to be automatically closed.
MilestoneMilestones are custom, and can be set up in milestones.
ProcessProcesses are custom, and can be set up in processes.
ReferenceFree text field.
ResolutionResolution types are custom, and can be set up in resolutions (there are some standards which can be used).
Resolution descriptionFree text field.

Overview of all milestones used in projects and issues. Can be managed either from the project page or from milestones in the admin menu. A milestone must be related to a project (which again is related to a customer). You can have different types of milestones. These are set up in record types in the admin menu.

Parameters for milestones:

FieldDescription
KeyThe key is mandatory, must be unique and can be chosen by the user.
NameThe name is mandatory and can be chosen by the user.
ProjectProject is mandatory. You chose the project in the dropdown list.
TypeMilestone types are set up in record types in the admin menu.
Due dateDue date can be set in the drop down calendar. Optional.
OwnerThe responsible for the milestone.
Created timeAutomatically generated when the milestone is created.
Time finishedThe date when the milestone has reached the progress point.
External idOptional. Can be used as a second key for the milestone.
StatusStatuses are custom, and can be set up in statuses.
NotesFree text field.

Main menu for all opportunities. Can be added to the main menu. Possible to add listviews.

The functionality for opportunities are similar to activities and issues. One of the differences are that you here are able to connect activities to the opportunity. You can also set an expected amount and probability for achieving the opportunity.

The following parameters are mandatory for the opportunities:

FieldDescription
Opportunity descriptionThere is no need for a unique name for each issue.
TypeTypes are custom, and can be set up in record types (there are some standards which can be used). You can also set default status for opportunity types.
AccountMandatory.
AssigneeDropdown list. All contacts that are either agents or has main account as the account linked to the account, are in the drop down list. If left blank the creator will be set as the assignee. Contacts can be set up in contacts.
KeyThe key is automatically generated based on the selected account.
ReporterDropdown list. All contacts that are either agents or has main account as the account are in the drop down list. Contacts can be set up in contacts.
PriorityPriorites are custom, and can be set up in priorities (there are some standards which can be used). Default priority can be ticked off in priorities. If no default priority is set, the order in the priority column will be used.
Created timeAutomatically generated when the opportunity is created.
StatusStatuses are custom, and can be set up in statuses (there are some standards which can be used). The available statuses varies depending on where you are in the workflow. The link between statuses and workflow are set in workflow in the admin menu.

The following parameters are optional for the opportunities:

FieldDescription
NotesFree text field.
Due dateDrop-down calendar.
AmountNumber field.
ProbabilityNumber field.
Business areaBusiness areas can be set up in the admin menu.
Closing reasonClosing reasons are custom, and can be set up in resolutions (there are some standards which can be used).
Closing descriptionFree text field.

Main menu for all accounts (customers, suppliers etc.). Can be added to the main menu. Possible to add list views.

We recommend a scheduled job to automatically create and update all account information to avoid mismatch between Deem Insight and your ERP system.

Deem Insight supports use of reports related to the account and the account type. The reports can be set under type related to reports. Here you can also set which roles that can access the report.

Account

Account tab: Fields with account information. More fields are possible to set up by using forms.

Reports tab: Several reports can be set up on accounts by using type related to report. All accounts with the same account type will have the same reports. To filter the report on the data for the selected account, use e.g. the script [customer_number] = ‘$account_externalId’ in the filter box.

Contacts tab: List of contacts related to the account.

Tasks tab: List of tasks related to the account.

Projects tab: List of projects related to the account.

Assets tab: List of assets related to the account.

Timeline tab: Timeline related to the account.

Orders tab: List of orders related to the account.

Attachments tab: Attachments related to the account.

Main menu for all assets. Can be added to the main menu. Possible to add listviews.

Account and product are mandatory and must exist prior to creating an asset.

We recommend a scheduled job to automatically create and update all assets information to avoid mismatch between Deem Insight and your ERP system.

FieldDescription
NameName of the asset(mandatory)
OwnerDrop down list (mandatory).
ProjectDrop down list (mandatory).
NotesFree text field (optional).
External idAlternative id (mandatory).
AmountNumber field (optional).
StatusStatuses are custom, and can be set up in statuses (there are some standards which can be used).
KeyUnique id (mandatory).
TypeDrop down list (mandatory).
ProductDrop down list (mandatory).
Product versionDrop down list (optional).
Created timeAutomatically created (mandatory).
Business areaDrop down list (optional).
SupplierDrop down list (optional).

Activities tab: List of activities related to the asset.

Attachments tab: Attachments related to the asset.

Can be used to connect a user to a business area or to create a separate structure.

Main menu for all business areas. Can be added to the main menu. Possible to add listviews.

The following parameters are available for business areas:

FieldDescription
KeyThe unique key (mandatory).
NameThere is no need for a unique name (mandatory).
NotesFree text field.
External idFree text field.
LanguageLanguage settings for business area.
TypeDropdown list, set to business area (mandatory).
StatusStatuses are custom, and can be set up in statuses (the standard is active) (mandatory).
Changed byName of the user who last changed the business area.
Created timeAutomatically generated when the business area is created.
Changed timeAutomatically generated when the business area is changed.

Main menu for all business units. Can be added to the main menu. Possible to add listviews.

It is possible to create a hierarchy of business units. We recommend that you start adding on the top level, and then use the parent field on the lower levels.

Business units can be used for filtering reports for the users. You can connect users to the business units and set a script on the reports so that the user will only have access to data relevant to the business units.

Business unit

FieldDescription
NameThere is no need for a unique name (mandatory).
NotesFree text field.
ParentChoose from drop down list the parent business unit. Will only be relevant if more than one business unit level has been set up (optional)
OwnerChoose owner from drop down list (optional).
StatusStatuses are custom, and can be set up in statuses (the standard is active) (mandatory).
KeyUnique key (mandatory).
TypeType are custom, and can be set up in record types (mandatory).
External idAlternative id(optional).
Created timeAutomatically generated when the business unit is set up.

Sub units: List of business units which have the selected business unit as parent.

Users: List of users who have the selected business unit set as the main business unit (field in the user settings). Only one main business unit can be set per user.

User related to business units: List of users who are connected to the selected business unit through user related to business units(list in the user settings). Multiple business units can be chosen for each user.

Main menu for all projects. Can be added to the main menu. Possible to add listviews.

We recommend a scheduled job to automatically create and update all project information to avoid mismatch between Deem Insight and your ERP system.

Deem Insight supports use of reports related to the project. The reports can be set under type related to reports. Here you can also set which roles that can access the report.

FieldDescription
NameThere is no need for a unique name (mandatory).
ResponsibleChoose from drop down list (mandatory).
OwnerChoose from drop down list (mandatory).
NotesFree text field (optional).
External idAlternative id (optional).
UrlPossible to add a link (optional).
Contract amountPossible to add the contract amount of the project (optional).
KeyUnique key (mandatory).
TypeType are custom, and can be set up in record types (mandatory).
Business areaDrop down list (mandatory).
ProductDrop down list (optional).
PriorityDrop down list, set under priorities (mandatory).
Created timeAutomatically generated when the project is set up.
StatusStatuses are custom, and can be set up in statuses (mandatory).
Business unitDrop down list (optional).
Due dateSelect date in the calendar (optional).
Show time estimatedTick off box (optional). If ticked off fields for time estimated will appear on all issues connected to the project.
Show time reportedTick off box (optional). If ticked off fields for time reported will appear on all issues connected to the project. If both boxes have been ticked off, also percent completed will appear on the issues.

Reports tab: Several reports can be set up on projects by using type related to report. All projects with the same project type will have the same reports. To filter the report on the data for the selected project, use e.g. the script [project_number] =‘$project_key’ in the filter box.

Contacts tab: List of the contacts related to the project.

Issues tab: List of the issues related to the project.

Milestones tab: List of the milestones related to the project.

Activities tab: List of the activities related to the project.

Assets tab: List of the assets related to the project.

Timeline tab: Timeline related to the project.

Attachments tab: Attachments related to the project.

Main menu for all orders. Can be added to the main menu. Possible to add listviews.

We recommend a scheduled job to automatically create and update all order information to avoid mismatch between Deem Insight and your ERP system.

Deem Insight supports use of reports related to the order. The reports can be set under type related to reports. Here you can also set which roles that can access the report.

Reports tab: Several reports can be set up on orders by using type related to report. To filter the report on the data for the selected order, use e.g. the script [customer_order_number] =‘$order_key’ in the filter box.

OrderLine tab: List of the orderlines related to the order.

Attachments tab: Attachments related to the order.

Main menu for all processes.

Main menu for all products. Can be added to the main menu. Possible to add listviews.

We recommend a scheduled job to automatically create and update all product information to avoid mismatch between Deem Insight and your ERP system.

Deem Insight supports use of reports related to the product. The reports can be set under type related to reports. Here you can also set which roles that can access the report.

FieldDescription
NameThere is no need for a unique name (mandatory).
NotesFree text field (optional).
StatusStatuses are custom, and can be set up in statuses (mandatory).
KeyUnique key (mandatory).
TypeType are custom, and can be set up in record types (mandatory).
Business areaDrop down list (mandatory).
Product groupDrop down list (optional).
Created timeAutomatically generated when the product is set up.
SupplierDrop down list (optional).

Reports tab: Several reports can be set up on products by using type related to report.

Assets tab: List of the assets related to the product.

Product versions tab: List of the product versions related to the product.

Attachments tab: Attachments related to the product.

Main menu for all product versions. Possible to add listviews. Related to product.

FieldDescription
KeyUnique id (mandatory).
NameThere is no need for a unique name (mandatory).
NotesFree text field (optional).
StatusStatuses are custom, and can be set up in statuses (mandatory).
TypeType are custom, and can be set up in record types (mandatory).
External idAlternative id (optional).
Created timeAutomatically generated when the product version is set up.
Release dateDate field (optional).

Issues tab: List of the issues related to the product.

Main menu for all product groups. Possible to add listviews. Related to product.

FieldDescription
KeyUnique id (mandatory).
NameThere is no need for a unique name (mandatory).
NotesFree text field (optional).
TypeType are custom, and can be set up in record types (mandatory).
StatusStatuses are custom, and can be set up in statuses (mandatory).
Changed byAutomatically updated.
Created timeAutomatically generated when the product group is set up.
Changed timeAutomatically generated when the product group is changed.

Activities and issues can be prioritized according to the list of possible priorities. Standard values are critical, high, medium and low. Default priority can be set.

Priorities

You are able to customize priorities in the priorities menu, where you can add a new or edit the existing ones. Default priority is selected/de-selected by using the tick off box.

Overview of all countries which can be used in the CLM. Can be maintained in the admin menu. Countries are in use in accounts and contacts.

Countries

A list of all the records in Deem Insight.

Records

When a record is opened the tabs gives you an overview of all the relations and possible configurations that can be done.

Record tabs

Makes it possible to separate a record into different types.

Record types

Configurations can be done, such as setting a default record type, access level, default status etc. You can also add custom forms, making it possible to add custom fields to the desired record type(s).

This is where you can view standard statuses and create custom ones. Some statuses are available for all records, while others are limited to specific ones. To make a status available for all records, select ‘Base’ as type when creating it.

Statuses

This is where custom fields are created. All record properties needs to be added to a form.

Record properties

The image below displays the changes that can be done to a record property (custom field). New custom fields automatically creates a field in the database. The database field name is “key + __c”.

Record property

Record properties can also be accessed from within the ‘Records’ view, where you can generate the standard properties and do changes and/or make them inactive.

Here you are able to create new fields connected to the CLM parts, such as project, account, orders etc.

The form must contain a field group and the field group must contain at least one field. It is possible to set up multiple field groups and fields for one CLM part. Fields in the same field group will appear in the same area in e.g the order card.

Form

When setting up a new form, you need to select which CLM part the form should belong to.

Available CLM parts where you can use forms

Then set up one or more field groups (name and key).

In the last tab, form properties can be set up. Here you select type of field, e.g. text.

Select type of field

After you have set up all the field groups and form properties for the relevant e.g. order card, you need to update the record type and this will connect the form to the selected CLM part.

Update record type

The new field will appear as shown in the below picture:

New form in CLM part

Resolution types for activities, issues and opportunities. Standard values are set for each type of task.

Resolutions

You are able to customize resolutions in the resolution menu, where you can add a new or edit the existing ones.

Deem Insight can be used to connect several reports from various business areas and link and filter them to the different CLM parts as e.g. account, project. Here you can configure which reports you want to connect to which CLM parts or reports.

You can filter who sees what report by using the roles under type related to reports.

Type related to report overview Type related to report Type related to report tabs

Example script: [customer_number] = '$account_key'

If you would like to connect an existing report to the account, you need to make a copy and add the script in the filter box.