User interface configuration rules - HxGN SDx - Update 63 - Administration & Configuration

Administration and Configuration of HxGN SDx

Language
English
Product
HxGN SDx
Search by Category
Administration & Configuration
SmartPlant Foundation / SDx Version
10

The following rules must be followed when changing the user interface.

Feature Sets

  • Existing feature sets and their methods and entry points must not be changed. You also must not change the display text, content order, or groupings. Feature sets themselves can be reordered on the home page, and new entry points can be added.

  • New feature sets can be created and populated with new custom methods, entry points, and, using web extensibility, integration with third-party applications.

  • Methods and entry points must not be disconnected from feature sets. These can only be removed from the feature set by removing user access to the command.

    • If the command is needed in a new custom feature set, it should be copied and added.

    • The method conditions also must not be modified. This is because a condition may be used in many places, so it should be copied and replaced as needed.

  • New commands and entry points can be added to a feature set. However, feature set changes from release to release may require additional changes to match.

API Entry Points

  • API entry points filtering must not be changed.

  • New API entry points can be created.

  • Existing entry points can be added to groupings.

  • Column sets can be changed on entry points by terminating the existing relationship and creating a new one.

Forms

  • Delivered sections and display items must not be modified.

  • New sections can be added to any form tab.

  • New forms can be created. They can be used to replace delivered forms by terminating the existing relationship between the delivered form and the class definition, and creating a new relationship for the new form.

  • Default values on relationship display items can be altered on specific display items. For example, to set the default security code and retention code.

Column Sets

  • Existing column sets must not be altered, including the content and order of the columns, because it could change the behavior of the system. Column sets must be copied and replaced.

    • Many column sets contain items that are not exposed in the list views but instead dynamically build display items on tabs on the forms, so care is required.

    • Dynamic display items from column items are an efficient way to extend forms.

  • Do not delete or terminate a column set or column items.