Introduction

CRM.cockpit installation is used to manage Aurea.CRM and generate documentation in RTF format.

CRM.cockpit can be used for the following:

  • Document changes you have made to the standard configuration and output documentation to file, see Documentation . You can enter descriptions for items referenced by your package (see below), and these descriptions are included in the documentation generated by CRM.cockpit.
  • Deploy configurations on target systems. Once imported on the target system, all configuration items in the package are available in the target database, see Importing and Exporting Packages.
  • Update existing versions of the same package on a target system. Any changes to items in the package should be made on the source (development) system, and there are certain restrictions that apply to packages imported into databases that already contain data, see Importing Packages .
  • Develop demo versions by including processes and data that can then be imported into the demonstration database in one step.

Packages

CRM.cockpit allows you to create and maintain packages for Aurea.CRM, see Packages . Use packages to collect and manage changes you have made to the default configuration of Aurea.CRM and distribute them to other systems. Each package can include references to any number of processes, which in turn contain references to various configuration items, such as the data model (info areas, fields, catalogs), CRM.designer configurations, formats and files (e.g. JavaScript, XSLT), see Processes and Configuration Items .

Packages can be used to manage both Aurea.CRM win and designer configurations.

Note: designer databases are used by Aurea.CRM web, CRM.pad and CRM.mobile.

This allows you to create sector-specific packages that can easily be deployed with minimum configuration overheads. Instead of reconfiguring similar configurations from scratch, you can use a package as the basis for sector-specific installations, which only needs to be extended with customer-specific processes.

Configuration items are not configured within CRM.cockpit; you need to define these items within Aurea.CRM itself. CRM.cockpit is used to determine which of these items are included to form a package by adding items from the Aurea.CRM win and CRM.designer databases. The package itself is also saved in the Aurea.CRM win database. You can synchronize the package with the database, in order to gain an overview of the changes made to items in the database since the last synchronization, see Synchronizing Packages .

Transport Management

The package and items within the package can be exported as a .zip file and imported on your target installation, see Importing and Exporting Packages . Packages should be developed on a development system, from which the desired processes are exported. The resulting .zip file is then imported into your production environment.

Note: CRM.cockpit is used to both import and export packages. CRM.cockpit therefore needs to be installed on both the source and target systems.

You can update earlier versions of the same package on the target system, subject to some restrictions, see Updating Packages.

Creating Documentation

In addition to managing Aurea.CRM configurations, CRM.cockpit also allows you to document the various items included in a package, as well as the package itself, see Documentation . You can generate documentation in RTF format, which reflects the current state of the package. It thus becomes much easier to maintain configuration items and for other users to quickly determine the functionality of items and processes in a package.

For an overview of the terms and concepts in CRM.cockpit, see Glossary .