Manage features

Feature types

Features are divided into six different types:

• 1-'Zero impact'

  Zero impact means that the feature enhancement does not require any training, documentation changes or configuration. An enhancement with 1-'Zero impact' does not impact end users, so it does not require any training or documentation changes. This type of change has no controlling setting and is included in any update on both Feature and Service releases.

  These are the examples of the 1-'Zero impact' type:

  • New fields in API transactions
  • New API transactions
  • New bookmark
  • Changes to default standard views and field groups
• 2-'Functional setting'

  The functional setting is a feature controlled by settings or parameters in a settings program, where only super users or administrators can manage. An enhancement with 2-'Functional setting' type can serve as a new standalone function. The setting or parameter is always released with default value set to Off. This type of change are not included in a service release. If the setting program is controlled by a toggle, the 3-'Feature toggle' is used instead.

  These are the examples of 2-'Functional setting' type:

  • Features controlled by a new or modified setting, for example, in 'Company. Connect Division' (MNS100) or 'Facility. Open' (CRS008).
  • Features controlled by a new or modified setting on order type, FAM function etc. Commonly used main data programs are not regarded as controlling programs).
• 3-'Feature toggle'

  3-'Feature toggle' type indicates a feature controlled by a feature toggle during a minimum of six months of transition period. A feature toggle is always released with the default value set to Off. There is an optional activation before the end of the transition period. When the toggle expires, the value set to On. This type of change is only included in a Feature Release.

• 4-'Feature toggle, process change'

  Features causing a mandatory process change has the type 4-'Feature toggle, process change'. If the feature has no process change, the type remains at 3-'Feature toggle'.

• 5-'Immediate, feature version'

  Features causing mandatory process changes that are not controlled by a feature toggle has the type 5-'Immediate, feature version'. This type of change is released without a controlling setting, but is only included in a feature version.

  Information about the change is published in advance through the early announcement changes, that requires advance customer action.

  These are the examples of 5-'Immediate, feature version' type:

  • Changes in appearance of UX that you cannot toggle
  • Adding length to identifier (unique) fields
  • Change of existing structure of BOD
• 6-'Immediate, any version'

  Features causing mandatory processes to change, which are released immediately, are categorized as 6-'Immediate, any version' . This type of change is released without any controlling setting and is included in any M3 release.

  These are the examples of 6-'Immediate, any version' type:

  • Some regulatory & statutory developments such as a new format for the SAF-T file
  • Emergency patches due to security updates
  • Operating system updates
  • Add/change standard menu

Manage system updates

In 'System Updates. Open' (CMS965), a record is automatically created every time the system is updated. Select sorting order '01' to sort the list on install date. For every update, a summary of the different feature types is displayed. Use option 11='Feature List. Open' (CMS975) to view a detailed list of features. The features are published in the Infor Release report.

Manage product version

In 'Product Version. Open' (CMS970) a record is automatically created every time the system is updated. Select sorting order 02 to sort the list on install date. For every update, a summary of the different feature types is displayed. Use option 11='Feature List. Open' (CMS975) to view a detailed list of features.

Manage feature list

In (CMS975) records are automatically created every time the system is updated. Every feature (KB ID for the NCD) is represented by one record.

• Select sorting order 01 to display all features included in a specific product version.
• Select sorting order 02 to display all features regardless of product version.
• Select sorting order 03 or 04 to display features based on review progress ('Under review' or 'Review completed').

Mass delete records in feature list

'Feature List. Select Operation' (CMS976) is used for mass deletion of feature list records. Select feature batch operation 4-'Delete' to delete the records.

Manage feature toggle

Features of type 3-'Feature toggle' and 4-'Feature toggle, process' are activated using a feature toggle during a transition period with a minimum of six months. However, during the transition period, you can also deactivate the feature. The feature toggle is managed in (CMS975).

The 'Update schedule' field indicates in what system update the feature is forced to be activated. Until this update the feature can be activated and deactivated as desired. The field is displayed on the E panel in (CMS975). By selecting sorting order 05 in (CMS975), (filter on update schedule) you can view all features that will be activated in a specific system update.

The 'Toggle expr' field indicates the date and the version when the feature is permanently activated. After the feature is activated, you cannot deactivate them.

Manage feature review

In (CMS975), the 'Review progress' field indicates the two major steps in the review progress:

• 1-'Under review'
• 2-'Review completed'

The field is automatically updated based on the 'Feature status' field where status 10-49 indicate 'Under review' and 50-90 indicate 'Review completed'.

Using the feature status, you can define several minor review steps within the two major review steps. The feature statuses are defined per customer, but status 10-'New', 50-'Confirmed', and 90-'Completed' are system-defined and are not deleted.

The feature statuses combined with the'Responsible' field enables you to build customer-defined workflows.

All feature review fields are managed in (CMS975).