Configuring a Custom Logical Unit involves naming and deciding which attributes it should have. The name should reflect the business object you want to create. The attributes are the characteristics of the business object. For example if you want to create the Custom Logical Unit Car, it might have the attributes: Name, Manufacturer, Model, Color, Car type, Engine type, Equipment package etc. Configuration also include modifying an existing Custom Logical Unit. The modification can be to change an existing attribute or to add a new on the Custom Logical Unit.
To start working with a Custom Logical Unit in IFS Enterprise Explorer, navigate to Solution Manager -> User Interface -> Custom Objects -> Custom Logical Unit. In the Custom Logical Unit page press the New button. Enter Logical Unit Name and enter a short description of the Custom Logical Unit and its purpose. It can also be wise to enter some text that identify the process that the Custom Logical Unit is used for. That way it is easier to keep track of the custom functionality that has been added for a particular reason. Use the same identification text on the custom functionality that belong together. In the Custom Objects overview it is then possible to search for all custom objects that have the identification text.
Adding a Custom Attribute is done in the Attribute Tab of the Custom Logical Unit page. When you add a Custom Attribute or edit an existing one, you will go through a wizard for entering metadata about the Custom Attribute.
Note. For Custom Logical Unit is it not supported to add a Local attribute. See definition of Local Attribute.
To add translations to a Custom LU one translates the Custom Attributes belonging to the LU. These translations will then be used when creating a Custom Page for the LU.
It is possible to run one or several attributes through a diagnostic test before trying to publish. This test checks the integrity of the configuration so that it can be published. This is typically useful when configurations have been transferred (exported/imported) between environments. Also, after an application upgrade it can be useful to validate the configuration before trying to publish the object.