Configuration of an ERP system means choosing paths in predefined processes and setting parameters that determine the process flow of the application. It also includes the addition of custom data objects such as custom fields and custom entities. These types of amendments can be applied after the build and deploy processes as well as being part of the software delivery itself. If configurations are meant to be supported by IFS or an IFS partner, it is recommended that the configurations are delivered in the build and deploy processes. Simple configurations, applied in the environment using administration tools, are typically managed by the customer directly. The Customer will then take full responsibility and make sure it is not interfering with software logic. In such configurations it is not recommended to use coding like PLSQL and SQL as it will typically be dependent on the underlying code. Often when coding is needed in a configuration, it is better to implement it using a customization.
Before you start configuring, we strongly recommend you to read through the Best Practices Guide.
IFS Aurena pages are possible to configure. Please refer to the Contents section for a description of the available configuration capabilities.
Another configuration type is events. They are used as triggers to call standard or configured processes based on conditions. IFS Cloud support a variety of actions to perform when an event is triggered. For this please refer to here
Configurations will be explained under three main categories as per the above contents. Below graph will give a better idea on how the Configuration Documentation content is distributed.
|Client Side Configuration
(Aurena Page Designer)
|Aurena Page Designer Basics|
|Context based Configuration|
Create Custom Entity
||Command Action Configuration|