Configuration and setup
These items are part of the basic configuration and setup:
Hierarchy
A product hierarchy can be made. The hierarchy is an important part of the application as it regulates organization access, for example, who has permissions to work on what part of the product hierarchy.
-
Users or user groups can be added to the top or any other level of the hierarchy
-
Number of levels is endless – but recommended level is not too many
-
Fields controlled by hierarchy are clearly indicated when making products
-
Fields controlled by hierarchy are dependent and rule out selecting other fields when making a style, material or trim
-
In Style hierarchy, you can create multiple top nodes
-
In Material and Trim hierarchy, there is one top node, giving you the ability to use items across different style top nodes (generic materials). On materials and trims, it is though possible to make them unique by season, brand, division,and product category
Business Rules
-
Mandatory rules
-
Field dependency
-
Role dependent mandatory rules
ID generator
Ability to set up a numbering rule for product, color, or request. The rule can pick up values from the product so that there can be some logic added to the number.
Name generator
Setting up rules on how a name for a Material or a Trim must be generated, including generation of name in another language.
Exchange rate
Ability to define different type of exchange rates (for example, budget, actual, simulation).
Extended – additional fields
Ability to create additional fields to product overview pages, document library, and line planning. Fields can be text, number, date, or dropdown.
Notification
Configuration of notification for users or user groups. Currently the notifications are at the cluster level and can be email, widget, alerts.
Settings
The application has a light form of configuration for most areas within the application. With feature settings, you can activate certain behaviors and set default settings.