Feature configuration deployment

Feature configuration can be deployed with the Perfion Deployment. This step in the wizard allows the user to select which configurations that should be deployed.

Selection

The wizard page for feature configurations is shown below.

Open

The selection list contains all features that has a configuration defined. Multiple configurations can be selected.

Right clicking a configuration opens a menu that contains a “Show configuration” menu item. Clicking this item, will show the currently selected feature configuration. This view is read only.

Open

Matching in target system

Feature configurations are matched to feature configurations in the target system. This is done by comparing the name of the root feature of the configuration to the root features of configurations in the target system.

The match is done case insensitive. Some examples below:

If a match is found, the feature configuration is flagged for update instead of creation.

Dependencies

Feature configurations are dependent on both feature definitions and feature data. The deployment wizard will automatically resolve all dependent features definitions and feature data.

Feature definitions

Each feature definition in a feature configuration will be flagged as required in the deployment. A required feature definition is treated the same way as if, the user selects a specific feature definition for deployment.

The required feature definitions will be shown in the feature definition selection and the summary. Both are explained later.

Item dependency and Feature Data

Deploying a feature configuration requires feature data for its item dependencies. The target system is checked for each item required in the feature configuration. If they are found, no feature data will be transferred. If, on the other hand, the feature data is not found, it will be transferred to the target system.

Finding required feature data

Finding the required feature data is done by searching the target system for feature data that matches. The following rules must be met.

• The feature definition must match

  • Since this feature is included in the configuration, it will be created automatically via the deployment if it does not exist in the target system.

  • If it does already exist in the target system, the feature definition must be selectable.

    • If it is not, an error message is generated, and the deployment will be halted.

• Feature data hierarchy must match

  • Example

• Localizable feature data must match its base value in the selected matching language.

  • Example: (Selected match language: EN)

Validation of found feature data

If the Perfion Deployment finds a match for the required feature data, some validation rules must be meat. Since feature data is matched using its base value, limitations are present. These can be seen below.

• Duplicate item values in source system cannot be present

  • This will only be an issue if both items are in the feature configuration

  • Example:

• Duplicate item values in target system cannot be present

  • This affects all feature data on the relevant feature definition

If any of these rules are broken, an error message is generated, and the deployment is halted.

Data transfer

A feature configuration is considered a single object. When a configuration is transferred, all data in it is transferred.

• Features

• Item dependencies

• Default values

• View choices

The Perfion Deployment will not try to merge a feature configuration if it is found in the target system. Instead all data for the feature configuration in the target system is deleted before the source feature configuration is inserted.

The result is a 100% match in the deployed source and target system feature configuration.