Using a default human service page layout

Edit online
Draft comment:
This topic is shared by BAW, CP4BA. Last updated on 2025-03-13 12:15
You can create your case user interface by using default page layouts. To use client-side human services to create your page, you must change the default widget-based page layouts to human service-based page layouts.

Before you begin

Start with a case solution that has the required roles, case types, and properties. See Adding a solution.

About this task

A page contains the user interface elements that are required to complete an activity. Case Builder provides different default page layouts for an action, for example, Add Case that is widget-based and Add Case Default (Human Service) that is human service-based. Set your default page layouts to human service-based pages.

The case toolbar widget displays the toolbar, and the client-side human service viewer displays the human service. After you create your case page, you can test it in the development environment, then deploy your case solution to a production environment.

In the Case Client, the case details human service adapter page includes a case widget and a client-side human service viewer stacked vertically.

Procedure

To create a case page by using the default human service page layout:

  1. Open your case solution and case type.
  2. Under Case Type, change the default widget-based Case Details page layout to Case Details Default (Human Service).
  3. Deploy and run the case solution, which takes you to the Case Client.
    Note: You must be assigned to the role associated with the case solution to proceed. If not, request your administrator to assign you to the appropriate role.
  4. From the Cases page, add a case to the solution.
  5. From the cases list, open the case that you have added.
    Your case page might look similar to the following example,

    Example of a default human service-based case page, with two areas stacked vertically: area 1 is a toolbar that includes the header and some default buttons, and area 2 is an iFrame with client-side human service views that contains the Overview, Properties, Documents, Activities, and History tabs.
    Where area 1 is the toolbar that contains the header and some default buttons, and area 2 is an iFrame that includes human service views that are laid out as tabs (similar to the layout of a process instance).