Defining a Task View

A Task View definition contains basic information and rules. When used, a Task View enables a user to complete work that is assigned to them.

Before you begin

Plan and design the Task Views. For information, see Planning the Task Views.

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

If you define Task Views that allow users to add file attachments, see Defining Task Views for file object types.

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

About this task

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

Custom views can be edited. System views open in read-only mode and the Design tab is hidden.

Procedure

  1. Click Settings menu > Solution Configuration > Views.
  2. Click Add New.
  3. Leave Enabled selected.
  4. Select Use as default view for this object type for all profiles to make the view the default task view for the object type. If Use as default view for this object type for all profiles is cleared, you can click Rules and build the criteria that determines the Task View that is displayed to a user.
  5. Select an object type in Object type.
  6. Enter a Name. Allowed characters are A-Z, a-z, 0-9, underscore, hyphen, and spaces. Special characters are not allowed.
  7. Select Task in View Type.
  8. Select a source view in Copy from view (Optional) to start with a base view that you can then modify. Choose a system Task View, a published custom Task View, or a Detail view from the Standard UI.

    If you do not select a view to copy from, the new view is empty (minimum properties). You must design a new view.

  9. Enter a Description.
  10. If Use as default view for this object type for all profiles is cleared, you can click Rules and build the criteria that determines the Task View that is displayed to a user.
  11. Set View Priority to a numeric value, for example, 0, 1, or 2. It establishes the display priority of a Task View compared to other Task Views for the same object type. If multiple Task Views match for a user after the profile, enumeration, and user rules have been checked, View Priority determines the view that is displayed to the user. A Task View with the lowest value 0 is displayed first, then 1, then 2, and so on.
  12. Set Rule Operator to one of the following options:
    • Logical AND of all rules

      All of the rules (profile, enumeration rules, and user rules) must be met for the view to be shown to a user.

    • Logical OR of all rules

      Any one of the rules (profile, enumeration rules, and user rules) must be met for the view to be shown to a user.

  13. Optional: In Profiles (if not specified, view is valid for all profiles) select one or more profiles.
  14. In Enumeration rule you can set a view to display if the value of an enumeration field on the object is a specific value.
    1. In Rule Field select the field that the rule is based on.
    2. In Rule Condition select the condition, for example, equal (=) or not equal to (<>).
    3. In Rule Value select the value that the rule tests against.
    4. Click Enumerated Rule Plus icon to add more enumeration rules.
  15. In User rule you can set a view to display if the signed on user has the role of the value selected, for example, is the owner or assignee of the object.
    1. In Rule Field select the field that the rule is based on, for example, assignee or <object> owner.
    2. Click User Rule Plus icon to add more user rules.
  16. Click Add.
    The View Designer opens with the Design tab displayed.
  17. Design the view.
  18. Click Preview to review the view.
  19. Click Publish.
  20. Test the view. Each time you change the view or the rules, you need to publish it and re-test it.

What to do next

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