Configure Custom Fields

This page describes typical activities that you can or must perform while configuring Custom Fields.

Contents

Where to start

When working with Custom Fields the core part is about adding the Custom Attributes that the Custom Fields should bind to. Custom Attributes is about extending application server Logical Units with additional attributes. To be able to do that, the administrator needs to know the relation between the application Page and the Logical Unit that it is working against. While there are multiple sources where needed information can be obtained from, one of the easiest way is to start of from the actual application page. By doing that, the framework will know where you like to end up and can pre-select the correct Logical Unit and View.

Open administration page from Navigator

  1. In IFS Enterprise Explorer, navigate to Solution Manager -> User Interface -> Custom Objects -> Custom Fields
  2. Open the Search dialog, search for the Logical Unit that corresponds to the application page where you want to add a field.
  3. In the Attributes table, add a new record.
  4. When you select new in the Attributes table the Custom Attributes wizard will launch and guide you through the process of configuring the Attribute.

Open administration page from an Application page

  1. In IFS Enterprise Explorer,  navigate to the application page where you want to add a field.
  2. In Context Menu, select Custom Objects -> Fields -> Create New...
  3. The Custom Fields administrator page will open with the corresponding Logical Unit selected. The Custom Attributes Wizard is launched to guide you through the process of configuring the Attribute.  

Note: In Context Menu you can select Custom Objects -> Fields ->  Overview... This way no wizard is launched. Use this when you want to administrate/configure existing configuration.

Add/Edit Custom Attribute

Creating a new or edit an existing Attribute is done through the Custom Attributes Wizard.

Approve/Disapprove Attribute

All approved attributes is included when publishing. This flag can be used to publish only parts of the configuration. It is also a way to temporary remove an attribute from the Logical Unit without deleting the actual configuration.

Translate Custom Fields

To add translations to a Custom Field one translates the prompt of the Custom Attribute. These translations will then in runtime be picked up by the Custom Field for the language code the application is currently running.

  1. In the Custom Fields administration page, select the row for the attribute to translate.
  2. In the Context Menu for the selected attribute, select Translate...
  3. In the dialog that opens, add language code and translations for each language you want to translate to.
  4. Close the dialog.

Validate Custom Attribute metadata

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.

  1. In the Custom Fields administration page, select one or several attributes to be validated.
  2. In the Context Menu for the selected attributes, select Validate...
  3. In the Validate Custom Field Attributes dialog that opens, validate all attributes at once or one by one.

Clone as Information Card

Both Custom Fields and Information Cards is builds upon Custom Attributes. When configuring attributes for any of the two concepts, it is likely that the other object should also be used with the same attribute configuration. Because of that, it is possible to pick attributes for Custom Fields and clone them to Information Cards and vice versa.

  1. In the administration page, select the attributes that you want to clone.
  2. From the Context Menu, select Clone As [Custom Field|Information Card]

Note: It is only possible to clone Read-Only and Local attributes, this because Information Cards does not support editing.

See Also

Custom Field Examples

Introduction to Custom Fields
Administrate Custom Fields