Creating custom Creation Views

Create a Creation View to define new objects.

Designing a Creation View

A Creation View contains fixed and configurable UI components.

Controlling what Creation View is displayed to a user

An object type can have multiple Creation Views that are enabled. You define rules that determine what Creation View is displayed to a user. A Creation View can be displayed:

  • For all or specific profiles.
  • For one or more parent object types, if the parent object is known.
  • For any parent object types, if the parent object is known.
Most Creation Views must provide a means for the creation of a primary parent since a parent object is required for most object types. The access point determines how the parent object can be provided:
  • For Creation Views that are accessed by clicking New from a Grid View, the parent object is not known and the view must contain a relationship field that allows a user to select a parent object.
  • For Creation Views that are accessed from a relationship field in a Task View, the parent object is known since the object is open. The view need not contain a relationship field that allows a user to select a parent object. For these Creation views, if you did not select Use as default view for this object type for all profiles, you can use the Rules tab to define a rule and set Parent Types (if known at creation time) to specific parent object types or select Any for any parent object types.
    Use this feature in Creation Views for two reasons:
    • So that users do not need to select a parent object. This makes the view easier to use because selecting objects is time consuming and unnecessary because the parent object is known.
    • So that different Creation Views can be displayed based on the parent object type. For example, a Creation View for an Issue can be different depending on whether it is accessed from a parent object that is a Control versus an Asset.

For more information, see Controlling which views are displayed to users and Defining a Creation View.

When users access an object type that does not have an enabled, valid Creation View, no view is displayed.

Associating a primary parent object and parent/child objects

For most object types, a Creation View must provide the ability to associate a primary parent object.

You can add a card or grid relationship field with an Add action to a Creation View. When a user adds the first object, that object is automatically set as the primary parent.

If you want to ensure that a specific object type is set as the parent, set the Required property on the relationship field to True to make the field mandatory.

To have a Creation View take over the parent object from the access point where the user starts, define a rule for the Creation View by setting Parent Types (if known at creation time) on the Rules tab. You can set Parent Types (if known at creation time) to specific parent object types or select Any for any parent object types.

Creation Views might also provide the ability to associate one or more parent objects. To do this, add a card or grid relationship field with an Add action to a Creation View.

If a Creation View allows users to associate both a primary parent object and parent objects, you can define one relationship field with two actions, Set Primary Parent and Add. You can make the relationship field required but you cannot ensure that a user provides a primary parent object. If the user does not explicitly choose a primary parent, the first object that was added as a parent becomes the primary parent when the object is saved.

You can use rules on relationship fields to help a user select the correct associations. You can use the visible and hidden rules on a relationship field to show or hide a relationship field based on the value of another field in the view. For example, if you create an Issue, the issue type that the user chooses can determine the parent object type that is displayed.

For more information about relationship fields, see Adding and configuring relationship fields on views.

Creation Views for adding files

Creation Views for adding files (system and non-system) must provide a means to upload a file. For more information, see Defining Creation Views for file object types.

Fixed UI components in a Creation View

Table 1. Fixed UI components in a Creation View
UI component Description
Work area The work area is always displayed.
Save icon The Save icon is always displayed and cannot be hidden. It is clickable after all required information for an object has been entered.
Cancel icon The Cancel icon is always displayed and cannot be hidden.
Object type and New [object type] The name of the object type is always displayed in the header.
Field guidance icon Field guidance for each section is displayed if at least one field in the section is defined with a field description.
Search button (magnifying glass)
 The search icon is always displayed. Use it to search for fields in the view.

Configurable UI components of a Creation View

Table 2. Configurable UI components in a Creation View
UI component Description
Work area You configure the content of the work area by defining sections and adding fields to each section.
Inline guidance You can add inline guidance.

For information, see Adding inline guidance.

User guidance You can add user guidance that includes information text and a list of key fields.

For information, see Adding user guidance.
Adding fields to sections Fields are organized in sections.

For information, see Adding a section.

Organizing fields into columns You can organize fields in columns.

For information, see Arranging fields in columns.
Defining colors for enumerated field values You can add colors to values in enumerated field values.

For more information about how to apply colors to field values, see Defining enumerated string fields.
Applying color ranges You can apply colors to value ranges for decimal, integer, and currency data types.

For more information about how to apply colors to field value ranges, see Defining fields and adding them to field groups.
Displaying alternate field labels You can change the locale to display alternate field labels.

For information, see Applying alternate field labels.
Associating objects You can add the ability to associate objects, for example, associate a primary parent to a new object.

For information, see Adding a card layout and Adding a grid layout.

Organizing relationship fields in tab groups. Organizing relationship fields in tab groups
Accessing a natural language processing service You can provide the ability to make suggestions by using a natural language processing service.

For information, see Adding a classifier field that makes taxonomy suggestions.

For information, see Adding a classifier field that makes object association suggestions

Adding URL links You can add URL fields that display as buttons or links.

For information, see Displaying a URL launcher field as a button or link.

Uploading files You can add the ability to upload files to Creation Views for file object types.

For information, see Defining Creation Views for file object types.

Defining a Creation View

A Creation View definition contains basic information and rules. When used, a Creation View enables a user to define new objects.

Before you begin

Plan and design the Creation Views. For more information, see Designing a Creation View.

If you define multiple Creation Views for an object type, see Controlling which views are displayed to users.

If you define Creation Views for file object types, see Defining Creation Views for file object types.

Turn on the Display debug info feature. For more information, see Displaying debug information.

About this task

Each object type can have one or more Creation Views that are enabled.

Procedure

  1. Click Open Administration menu Administration menu > Solution Configuration > Views.
  2. Click New View.
  3. Enter a Name. Allowed characters are A-Z, a-z, 0-9, underscore, hyphen, and spaces. Special characters are not allowed.
    The Name that you enter is copied to Label.
  4. Optional: You can either leave the Label as a copy of Name, or you can enter a new Label.
    Click Edit to enter localized values.
  5. Enter a Description.
  6. Select Creation in Type.
  7. Select an object type in Object type.
  8. If you started creating a new view by clicking Copy view in View Designer, Copy from view doesn't appear and you can continue to the next step.
    In Copy from view, click Select a view to start with a base view that you can modify. If you do not select a view to copy from, the new view is empty with just the minimum properties.

    You don't have to copy from the same type of view that you want to create. For example, you can choose to copy from an Admin View even if you want to create a Task View. When you copy from a different view type, only compatible sections are copied to the new view. For example, not all view types have a Parent and child relationships section.

    1. Click the Filter by drop down and select the type of view that you want.
      You can also use the search to find a specific view.
    2. Select the view that you want to copy from.
    3. Click Select.
  9. Leave Enabled selected.
  10. Select Use as default view for this object type for all profiles to make the view the default view for the object type.
  11. If you didn't select Use as default view for this object type for all profiles, you can click Rules and specify the criteria that determines the view that is displayed to a user.
    1. Set View Priority to determine the order in which to display views.
      If multiple views are available for a user after the profile, enumeration, and user rules have been checked, View Priority determines the view that is displayed to the user. The view with the lowest value is displayed first. For example, 0 is displayed first, then 1, then 2.
    2. Optional: In Profiles (if not specified, view is valid for all profiles), select one or more profiles.
    3. Optional: In Parent Types (if known at creation time), select one or more specific parent object types or Any.

      If you use this rule, ensure that you also have a default view. A default view can be used if the parent object type is different than the selected object types or if the parent object type is unknown at creation time. Examples of instances where the parent object type is unknown include when you click Add from a Grid View or dashboard widget.

  12. Click Create.
    The View Designer opens with the Design tab displayed.
  13. Design the view. For more information, see Defining and publishing views with the View Designer.
  14. Click Preview to review the view.
  15. Click Publish.
  16. Test the view. Every time that you change the view or the rules, you must publish it and retest it.

What to do next

If you need to change the rules after a view is saved, click Edit view icon.

Defining Creation Views for file object types

Creation Views are used to add files to the OpenPages file repository.

About this task

A Creation View for the File (SOXDocument) object type is used when users create new files from the following access points:

  • A Task View that contains a grid relationship field for files. In this case, the parent object for the file is the object type of the Task View, for example, a Control or an Issue.

    A Files to add window is shown after you select a file but before you click Upload. Creation Views for files determine the fields that are displayed in the Files to add pop-up window. Only required fields are displayed in the Files to add window.

  • The Primary menu Primary menu icon > Attachments > Files task. In this case, the parent object for the file is a business entity that the user provides. A Files to add window is not displayed.

When you plan Task Views that contain grid relationship fields for files, review the system Creation View for the File object type. You can use it as or create custom views if needed. It might be valuable to use multiple Creation Views for files so that you can control what displays in the Files to add pop-up window. You can define one Creation View for files and use it for all parent object types. Alternatively, define multiple Creation Views for files and use rules to control which Creation View for files is applied based on parent object type. Use the Parent Types (if not specified, view is valid for all parent types) rule on Creation Views to control what fields display in Files to add. For example, files that are added to a Policy object can include fields that support the Policy Import trigger. However, files that are uploaded to all other object types can exclude these fields. For more information, see Designing a Creation View.

Creation Views are also used when users create files from the Primary menu Primary menu icon > Attachments > Files task.

Creation Views are also used when administrators create new system files from the Open Administration menu Administration menu > System Configuration > System Files task. System Creation Views are provided for the objects types for system files.

Procedure

  1. Follow the instructions in Defining a Creation View to define a Creation View.
  2. Select File in Object type (or one of the system file object types).
  3. Add fields to the Creation View.
  4. Drag a File Uploader element to a section. You can use this element to select a file to upload. It is unique to Creation Views for files. It is required.
  5. Add a grid relationship field that contains an action to associate a parent. For more information, see Adding actions to relationship fields. This step is not applicable to Creation Views for system files.
  6. Click Done.