Introduction to Responsive Forms

Responsive Design is a general design principle that describes a user interface that adapts its layout and dimensions to various devices or screen sizes. Responsive Forms on the Aras Innovator platform leverage this design principle to provide Forms that dynamically adjust their structure and content to deliver a seamless user experience.

Prior to Aras Innovator 30, there was a single way to define a Form for the Aras Innovator client, now called Classic Forms. This section outlines key differences between Responsive Forms and Classic Forms.

Administrator User Interface

When defining a Classic Form, an administrator creates a new Form item and uses the Classic Form Editor UI to place fields into the Form body. The admin then drags each field to its desired position in the Form. This approach assigns each field an X,Y coordinate that the Aras Innovator platform uses to render a static layout for the Form.

Responsive Forms use an enhanced admin user interface called the Responsive Form Designer. This UI enables admins to define a container-based layout by dragging and dropping structural elements and fields into the Form. Administrators can also configure the layout behavior of the Form and preview how it will look and behave for end users.

Layout Behavior

Classic Forms render content using a static layout that doesn’t change based on the size of the user’s browser window. Instead, users will be presented with scroll bars when a Classic Form’s static content does not fit in frame, or they will see additional whitespace when the static content occupies less space than the current frame.

Responsive Forms use a container-based approach to define the layout of a Form. This means that content can reflow to use the browser window’s space more effectively – minimizing the need for scroll bars and reducing unnecessary whitespace.

Data Model

Both Classic and Responsive Forms use the Form ItemType to define Forms for the Aras Innovator client. However, each approach uses a different data structure under the Form item to describe the layout, behavior, and content of the rendered Form.

This parallel architecture enables administrators to adopt Responsive Forms with minimal disruption to packaging and deployment. It also enables customers to continue using their existing Classic Forms.

Note
A single Form item might have both Classic and Responsive definitions present at the same time. However, the Aras Innovator platform will only render the definition identified by the Form’s classification. Administrators should use the Classic Form Editor or Responsive Form Designer to choose which definition will be rendered for each Form.

Note
Modifying the layout, behavior, or content of a Classic definition does not affect the Responsive definition, or vice versa.

The following process outlines how to add a new Responsive Form to an ItemType:

  1. From the Table of Contents, expand Administration and select ItemTypes.
  2. From ItemTypes Table of Contents, click Search ItemTypes.
  3. The ItemType grid appears.

  4. In the Name column, enter required ItemType click Search.
  5. Select the ItemType.
  6. The ItemType form appears. For this document, Part ItemType is used.

  7. From the Relationship tab, select Views.
  8. The existing forms linked to Part ItemType appears.

  9. Click Edit to edit the Part ItemType.
  10. Click New Form to add a new form to the Part ItemType.
  11. Add a name to the form in the Form Name column and select Default type in the Type column.
  12. Note
    This release of Aras Innovator only supports Responsive Forms with the Default view type. Support for other view types will be added in a future release. In the meantime, continue to use Classic Forms for use cases requiring view-specific Forms for Add, Edit, View, Print, Complete, or Preview views.

  13. Enter the other ItemType View properties as needed and click Done to save the changes.
  14. Double click on the newly created Form in the Relationship tab.
  15. The Classic Form Editor displays the new Form:

    Note
    New Forms are created as Classic Forms by default. Classic Forms created from an ItemType are automatically populated with fields generated based on the search grid properties for the parent ItemType.

  16. Click Switch to Responsive Form.
  17. The Form switches to Responsive mode and it’s reloaded in the Responsive Form Designer interface:

Note
When a Form is switched to Responsive mode for the first time, it receives a new empty Responsive Form definition. Switching a Form to Responsive mode does not migrate, modify, or delete the Form’s Classic content. Switching a Form back to Classic mode also does not affect the Form’s Responsive content.

This section explains all the panes, properties and functionalities of the Responsive Form Designer.

There are 3 panes for the Responsive Form Designer:

  1. Element Pane: This pane presents a list of elements and fields that the admin user can drag and drop into the form. There are two types of objects:
    • Structure Objects: These are building blocks for constructing the layout of Responsive Forms. It consists of Column, Column Sets and Group Box.
    • Column: A container that wraps a vertical stack of Column Sets, Group Boxes, or fields. All fields in a column will fill 100% of the width of the container. Columns may only be placed inside Column Sets.
    • Column Set: A container that wraps one or more Columns. A Column Set can be used to arrange Columns of content side by side, or they can be nested within Columns to give the appearance of a split Column. By default, the Columns inside a Column Set will reflow to stack vertically when the width of the Form shrinks. However, this behavior can be overridden by the administrator as needed. Column Sets may be placed inside a Column or at the root level of the Form.
  1. Group Box: A Column Set preconfigured to show a label and border. A Group Box can wrap related content, helping users identify related data even on varying screen sizes. Group Boxes can be used just like Column Sets – inside a Column or at the root level of the Form.
    • Unused Properties: These are individual fields that are preconfigured to the properties of the Form’s parent ItemType. Each field has a default control type such as text box, checkbox, dropdown, etc. As the admin user drags & drops a field into the Form, the corresponding property is removed from the Unused Properties list.
    • Note
      The Unused Properties list will only populate when the Form is related to an ItemType. To add a Form to an ItemType, open the desired ItemType and create a new View relationship to the Form.

    1. Detail Pane: This pane enables the admin user to view and edit the Form’s properties. When a structure element or field is selected in the Canvas Pane, the admin can also view or edit the properties of the selected element or field.
    2. Canvas Pane: This is where the admin user will drag & drop elements to define the content and layout of the Responsive Form. The admin can preview how the content will reflow by changing the size of the browser window or expanding/collapsing the other panes in the designer.
    3. Toggle Pane: Two buttons on either side of the Canvas enable the user to toggle the designer’s side panes on or off. This helps the admin preview the Form’s wrapping settings by changing the size of the Canvas.
    4. Toggle Guides: Enables the admin to toggle off the blue boxes that show the Form’s structure elements in the Canvas if they want to see how the rendered Form will look for an end user.

This section describes how to build a Form with the Responsive Form Designer.

Add Structure with Column Sets

The following steps outline the process of using Column Sets and Columns to create a layout structure for a Responsive Form:

  1. Click Edit in the Responsive Form Designer toolbar.
  2. From the Structure list in the Element Pane, drag and drop the required Column Sets.
  3. There are 3 Column Sets preconfigured with a number of Columns:

    • 2 Column Set: Adds a Column Set containing 2 Columns.
    • 3 Column Set: Adds a Column Set containing 3 Columns.
    • 4 Column Set: Adds a Column Set containing 4 Columns.
  4. To add more Columns to an existing Column Set in the designer, drag & drop a Column from the Element pane to a Column Set in the Canvas.
  5. Once the required Column Sets are added, it should appear as follows:

  6. Select a Column Set in the Canvas to view and edit the following properties in the Detail Pane:
    • Name: Name to display when the element is selected in the Responsive Form Designer Canvas
    • Label: Label to display to the user in the Responsive Form Designer Canvas and the rendered Form
    • Wrap Columns on Small Display: True by default. Enabling this setting allows columns to stack vertically (or “wrap”) instead of aligning horizontally when viewed on devices with limited horizontal space. This ensures content remains legible and user-friendly regardless of the screen size.
    • If the “Wrap Columns on Small Display” option is selected, the column should appear as follows:
    • On wider screen, column sets appear as follows:

      On smaller screen, column sets appear as follows:

  • If set to false, the columns may shrink down to their minimum width when the Form shrinks, but they will not stack/wrap. If the width of the Form becomes smaller than the combined minimum width of the columns, a horizontal scroll bar will appear to allow the user to access all content.
  • Show Border: False by default. Enabling this field displays a solid border around the Column Set.
Note
A Group Box is simply a Column Set preconfigured to display a label and a border. All steps described for Column Sets also apply to Group Boxes.

Adjust Layout with Column Properties

Once the Column Sets and Group box are placed, users can adjust the following:

  • Name: Name of the column.
  • Ratio: Describes the width of a Column relative to the other Columns in the same Column Set.
  • Example: A Column Set contains 2 Columns where one has a ratio of 2 and the other has a ratio of 1 (2:1). This means the first column will be twice as wide as the second column and occupies two thirds of the width of the Column Set.
  • Example: A Column Set contains 3 Columns with a ratio of 2:1:1. In this case the first column will be twice as wide as the second and third columns, meaning it occupies half the width of the Column Set.
  • Min Width (px): Minimum width that a Column will shrink to
  • Max Width (px): Maximum width that a Column will expand to

When considering sizing behavior of Columns, it’s important to note that a Column’s width settings take priority over its ratio. For example, consider a Column Set with two Columns. Column A has a Min Width of 300px and Ratio of 2. Column B has a Min Width of 100px and a Ratio of 1. This ratio of 2:1 indicates that Column A should be twice as wide as Column B. However, the parent Column Set can shrink down until all child Columns hit their respective minimum widths. In this case, Column A will shrink to 300px and Column B will shrink to 100px – resulting in an actual ratio of 3:1. If maintaining the width of Columns in relation to each other is important for a Form’s design, be sure any Min or Max Width follows the desired ratio.

Add Properties to the Form

The following steps outline the process of adding fields to a Responsive Form:

  1. In the Element Pane under Unused Properties, browse through the properties of the Form’s parent ItemType. This list shows properties that have not yet been added to the Form.
  2. Drag & drop a property into a Column. This will insert a field that has been preconfigured for the selected property.
  3. In the Detail Pane, view and update the properties of the field as needed.
    • Name: Name displayed when the field is selected in the Canvas
    • Label: Label displayed to the user in the Canvas as well as the rendered Form. Choose one of the following two options:
      • Inherit from Property: Display the label of the property, as defined on the ItemType
      • Hide: Don’t display a label
    • Help: Configure whether the field will render a help tooltip. Choose one of the following two options:
      • Inherit from Property: Display the property’s tooltip, as defined on the ItemType.
      • Hide: Don’t display a tooltip
    • Field Type: Configure the type of control to display for the field. Options are limited to controls that are valid for the data type of the linked property. For example, an Item control must be used if the property’s data type is “Item”. However, the admin may choose from multiple control types if the property’s data type is “Text”.
      • Text: A concise input field suitable for short entries.
      • Text Area: A larger input space ideal for longer pieces of text or paragraphs.
  4. Repeat the drag & drop process to add more fields to the Form. Columns may contain multiple fields.
  5. If a field should span the entire width of the Form, it may be dropped onto the Canvas, outside of any Column.
Note
Fields must be wrapped in a Column if they should have a Min Width or Max Width set. If a use case requires a single stack of fields with a minimum or maximum width, add the fields to a Column Set containing a single Column. Then set the size parameters on the Column.

Preview Responsive Form

The following steps outline the process of previewing the Responsive Form in the Responsive Form Designer:

  1. To preview the Form without the blue guides for Columns, Column Sets, and Group Boxes, click Hide Guides.
  2. The preview of the Form appears as follows:

  3. To preview how the Form will appear when spanning the full width of the Aras Innovator client, click the Close Pane buttons at the bottom left and bottom right of the Canvas. This will collapse the Element Pane and Detail Pane, respectively.
  4. The Form should appear in the expanded Canvas as follows:

  5. To view the Element Pane and Detail Pane again, click the Open Pane buttons on the bottom left and bottom right of the Canvas.
  6. To view the blue guides representing Columns, Column Sets, and Group Boxes, click the Show Guides button.

Save and View Responsive Form

The following steps outline the process of saving the Responsive Form and viewing the rendered Form in an Item View:

  1. Once all changes are made to the Responsive Form, click Done in the Responsive Form Designer toolbar.
  2. In the TOC, navigate to the ItemType associated with the new Responsive Form. Click Search.
  3. From the search grid, open an item for viewing. The new tab should display the item with the Responsive Form.

The following steps outline the process of creating Rules for Responsive forms:

  1. From the Responsive Forms page, click Manage Rules.
  2. The Form Rules appears as follows:

  3. Click Edit.

Creating a New Rule

Creating a New Rule with Value of Property

The following steps outline the process of creating a new Rule based on the Value of Property:

  1. Click New Rule.
  2. The New Rules screen appears as follows:

    NameThe name of the Rule.
    ConditionDescribes when the rule will be applied.
    BehaviorDescribes the actions that are performed when the rule is applied.
  3. Click Add Condition.
  4. NameDescription
    Value of PropertyChecks the value of a property of this item.
    PropertyProperty of this item to be checked.
    OperatorType of comparison.
    CriteriaValue used by comparison.
  5. After selecting the Conditions for the new rule, Click Add Behavior.
  6. NameDescription
    PropertyProperty to be affected by this behavior.
    Display asHidden – Field is not displayed in the form.Normal – Default Field.Read Only – Field data cannot be edited by user.
  7. Click OK to add the rule.
  8. Click Done to save the Responsive Form.

Creating a New Rule with Member of Identity

The following steps outline the process of creating a New Rule based on the identity of the current user:

  1. Click New Rule.
  2. The New Rules screen appears as follows:

    NameThe name of the Rule.
    ConditionDescribes when the rule will be applied.
    BehaviorDescribes the actions that are performed when the rule is applied.
  3. Click Add Condition.
  4. NameDescription
    Member of IdentityChecks whether the current user belongs to this identity
    IdentityIdentity to be checked.
  5. After selecting the Conditions for the new rule, Click Add Behavior.
  6. NameDescription
    PropertyProperty to be affected by this behavior.
    Display asHidden – Field is not displayed in the form.Normal – Default Field.Read Only – Field data cannot be edited by user.
  7. Click OK to add the rule.
  8. Click Done to Save the Responsive Form.

Adding Existing Rules

Rules that are created in a Responsive Form will be available to add to any other Responsive Forms.

  1. Click Add Rule.
  2. The Add Rule dialog appears as follows:

  3. Click the Search button to display all rules that have been created.
  4. Select the rule that is being added to the Responsive Form.
  5. Click OK.
  6. Click Done to save the Responsive Form.
Note
Double-Clicking a rule in the search dialog will add the Rule to the list of Form Rules and dismiss the dialog.

Edit Rules

The following steps outline the process of editing a Rule:

  1. Select the Rule that needs to be edited.
  2. Click Edit Rule.
  3. Make the edits to the rule as needed.
  4. Note
    Rules may be used in multiple forms. Editing a rule will alter the rule for all forms that currently use it.

  5. Click Done to save the Responsive Form.

Removing Rules

The following steps outline the process of removing a Rule from a Form:

  1. Select the Rule to remove from the Responsive Form.
  2. Click Remove Rule from Form.
  3. Click Done.
Note
Removing a Rule does not permanently delete it. Rules that have been removed are still available by searching in Add Rules.

Reordering the Rules

To reorder the rules, drag and drop the rules in the form rules table.

Note
To reorder rules, the form must be in Edit mode.

Packaging metadata like ItemTypes and Forms is an important part of managing an Aras Innovator instance. The Responsive Form Designer has a dedicated feature to simplify packaging. The following steps outline the process of adding a Responsive Form to a package in a few scenarios.

The Form has already been packaged in Responsive Mode

No action is required if the Form has already been added to a package from Responsive Mode. All data related to the Responsive Form definition has been added to the package definition. The Export Utility will export the current configuration, even if you’ve updated the Form since it was packaged.

The Form has been packaged in Classic Mode but not Responsive Mode

The package definition will need to be updated to ensure that all necessary data related to the Responsive Form definition is exported by the Export Utility. This update has two parts:

Remove Form from Package Definition

Always backup the database before manually modifying package definitions. Navigate to Administration > Configuration > Package Definitions in the TOC. Search for the package that contains the Form that needs to be repackaged. Open the Package Definition and click Edit. In the Package Groups tab, find and open the Form package group item. Click Edit on the Form package group item. In the Package Elements tab, find the Form that needs to be repackaged and delete it. Save and close the Package Group. Save and close the Package Definition.

Package Form from Responsive Form Designer

Follow the steps in the next section to package a Responsive Form.

The Form has never been packaged

  1. Open the Form in the Responsive Form Designer.
  2. Make sure the Form is saved and the designer is in view mode – there will be an Edit button in the toolbar instead of the Save and Done buttons.
  3. Click on the More icon.
  4. Select Add to Package Definition.
  5. The Add selected item(s) to a package dialog box appears.

  6. In the Select Package dropdown, either select the existing required package or create a new package.
  7. Click Ok.
  8. Now the Form item and the necessary related data will be included next time the specified package is exported.

Note
It’s important to use the version of the Aras Export Utility that matches the version of Aras Innovator you are exporting packages from. Starting in Release 28, the Export Utility includes an enhancement that can make exporting and importing Forms easier.