Administration

These items are part of more administration type of abilities.

Roles

An important part within the application is working with roles. From the Infor OS platform, we work with two PLM standard roles. We use those standard roles for initiating the user in the PLM space. In PLM, we can add more non-standard roles to a user. A role controls the CRUD permissions and you can connect them to different views in the application.

Views

The application comes with standard layouts, called views, for list or detailed screens.

You can define specific views for roles, using standard list and detail views as base. The fields on a details view are made hidden or read-only. New fields introduced through new functionality are included in existing custom views.

Views support these features:

  • Publish new standard fields on a standard view to custom define views

  • Add extended fields

  • Rearrange fields on list views and detailed views

  • Make fields read-only

  • Use a main SortBy and sorting direction

  • Associate views to a role

Users

Users are always generated through the Infor OS platform and come with default roles.

You can associate custom, specific roles to users on top of the generated role through the Infor OS provisioning process. Users are internal users.

External users are created through Infor OS External Entity Management and are clearly separated from internal users.

User groups

User groups are defined within the application, for easy access to hierarchy, notifications, and reports.

User groups for internal users are distinct from user groups for partner users.

Database version

Your organization works in a database version. You can copy, activate, import, and export a database version to and from another tenant. Customers use multiple database versions in a testing tenant. Some settings are global and some are per database version. In Production tenant, you would work with one database version.

Feature toggles

In case an existing feature changes due to technical or functional improvements, you can set a feature toggle. The feature toggles have a transition period so there is enough time to adopt the new way of working. In certain cases, a feature toggle has an immediate impact. For example, if you must install something right away for security reasons. The feature toggles have security levels, giving you good insight to the type of change. All new features not part of changes are normally taken care of by the set up or configuration.

This table shows the types of feature toggles:
Feature toggle type Description
1 - Zero impact Typically released 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.