1 Introduction

System Customization Management (SCM) is a tool for Agile e6 administrators that provides a way to manage customization code in Agile e6.

1.1 What is System Customization Management (SCM)?

System Customization Management (SCM) is a tool for Agile e6 administrators and consultants that provides a sophisticated method to manage customization code in Agile e6. The SCM tool provides a controlled method for transferring customization code from one source environment to another target environment.

1.2 SCM Supports Best Practices for System Customization

Best practice for creating custom enhancements and modifications is to:

1. Develop the custom code in a separate development environment of Agile e6.

2. In the development environment, thoroughly test and validate the custom code.

3. Transfer the development custom code to an Agile e6 test environment where key users can verify that all features are fully functional.

4. Transfer the now validated custom code from the Agile e6 test environment to the production Agile e6 environment.

1.3 Overview of SCM Capabilities

In the system customization process, you must identify the modifications in one environment and transport them to a different environment. SCM provides capabilities that enable you to:

• Select/identify modifications

• Assign modifications to so-called change packages or bundles

• Manage the existing bundles within an environment

• Export the bundles into a set of files

• Import the set of files and activate the modifications in another environment

1.4 Usage of SCM

The following figure illustrates the general flow of actions, when working with SCM tool. This is an iterative process where the user will repeat the process as many times as needed to thoroughly define, export, and test the system customization.

Figure 1-1 Flow of Action when working with SCM Tool

In order to follow best practices, you will use two different Agile e6 environments:

• A separate test environment, which includes a test source application and a test target application.

  Develop, test, analyze, and verify the customization code in the test environment.

• The production environment.

  Only after the customization code has been fully tested and verified in the test environment, then transfer the customization code to the production environment.

1. Configure the test environment Source and Target application as described in the Chapter ”Configuring the Source Environment and the Target Environment. See

2. Develop the custom code in the separate development test environment of Agile e6. Define the SCM bundle and prepare to transfer it to the test target application.

3. Transfer the custom code to the test development target application. In the test development environment, thoroughly test and validate the custom code.

4. Transfer the development custom code to an Agile e6 test environment where key users can verify that all features are fully functional.

5. Repeat steps 2 through 4 as many times as needed until the customized code is ready to be deployed in the Agile e6 production environment.

6. Transfer the now validated custom code from the Agile e6 test environment to the production Agile e6 environment.

1.5 Overview of SCM Objects and Features

1.5.1 Bundles

Bundles are the basic ”envelope” to organize and manage modifications.

For more information, see Chapter ”Bundle Objects”.

1.5.2 Patches/Modules

In addition to bundles, SCM provides the concepts of Patches and Modules. Patches and Modules are a set of bundles. For example, you might create a patch for a rollout which includes several independent bundles from different application areas such as document management, item management, or project management.

For more information, see Chapter "Managing Patches and Modules".

1.5.3 Data Analysis Tools

SCM also provides data analysis tools. The "where-used" for a specific object, shows whether the object is part of any other bundle. Consultants and administrators use this feature to assure that the correct, consolidated modification makes it into the bundle. The "Check Structure" feature reviews the structure of the current object and adds the subordinate objects to the current bundle.

In addition to adding objects to a bundle, you can enhance the bundle with objects of type INF. INF objects can be used to structure the content of the bundle or they can be used to include further instructions for handling the bundle.

1.5.4 Check Structure

The "Check Structure" feature reviews the structure of the current object and adds the subordinate objects to the current bundle. Check Structure will consider, for example:

• Menus

• (Sub-) Forms

• Tables

• Logiview procedures

• Messages

1.5.5 Import

Opens a dialog to specify the loader file name and the path to import the loader file

1.5.6 All Modifications

Opens a list of all modifications which allows you to run where-used queries across all bundles in the current environment.

1.5.7 Loader Imports

Opens the list of Loader Imports and shows which packages have been imported in the current environment.

1.5.8 Configuration

Opens the SCM configuration list.