Release management

Running an on-premise system meant that adopting new functionality required a project, including upgrade planning, testing cycles, IT resources, and downtime. For many companies, that overhead meant staying on older versions long after better functionality was available.

As a cloud-delivered SaaS solution, Infor PLM for Fashion removes that overhead. The application is updated automatically on a regular cadence. New capabilities are available to every customer as soon as those capabilities are released. There is no upgrade project, no waiting, and no version lag between teams.

Updates come in different sizes. Smaller improvements and fixes are delivered continuously. Larger functional changes are managed through feature switches, which give your team control over when and how you adopt them.

See the information on the release cadence of PLM for Fashion in the release calendar.

Feature toggles

When an existing feature changes for technical reasons or to improve a process, a feature toggle enables a gradual transition for your organization.

A feature toggle comes with a defined transition period. This period gives teams time to review the change, update work methods, and train users before the new behavior becomes the default.

Not all feature toggles are equal. Security levels are assigned to each feature toggle so you can understand the type and urgency of a change. Levels range from zero-impact background updates to immediate changes. For example, a security requirement can require an immediate change.

All entirely new features that are not changes to existing behavior are handled through standard setup and configuration. These features never disrupt what your team already has in place.

This table shows the types of feature toggles:


Feature toggle type	Description
1 - Zero impact	Typically release in service and feature releases.
2 - Functional setting	Automatically enabled but does not affect the user unless the configured settings are enabled in the application. Only implemented in a feature release.
3 - Functional setting with time to test	After the testing time, the feature becomes visible. Only implemented in a feature release.
4 - Process change	An expected change with time to test, usually at least six months. Only implemented in a feature release.
5 - Immediate	Expected process change. Only implemented in a feature release.
6 - Immediate	Process change. Available for implementation at any time, for example, due to security or other regulations.