Packages

Use packages to collect and manage changes you have made to the default configuration of Aurea.CRM and distribute them to other systems.

A package is the root element that encapsulates all configuration items via processes, see Processes . A package can include the following:

• A description, which is included in the package documentation, see Description .
• A package history, which can include automatic and manual entries, see History .
• Processes, which in turn can contain configuration items, see Processes .
• An automatic version number, see Package Version Number .
• Hyperlinks and descriptive documents.

Defining a package involves the following steps, see Developing a Package :

1. Customizing the application in Aurea.CRM. This involves defining configuration items, such as formats, the data model, records, designer units etc. Refer to the corresponding manuals for more information on configuring Aurea.CRM.
2. Creating a package and entering a description for the package, see Creating a New Package .
3. Defining the processes in the package and adding the appropriate items to the processes, see Editing a Process .
4. Creating documentation, see Documentation .
5. Exporting the package from the development system and importing it into the production system, see Importing and Exporting Packages .
6. Updating the package and documentation on the development system and updating the production system, see Updating Packages .

The package is stored in the Aurea.CRM database itself. Packages are displayed in the Formats info area.

If you make changes to the data model in Aurea.CRM, you need to refresh CRM.cockpit in order to view the updated data model in the data model explorer, see Data Model .