Skip to main content


         This documentation site is for previous versions. Visit our new documentation site for current releases.      
 

Configuring a work area at run time

Updated on November 15, 2021
Applicable to Theme UI-Kit applications

You can configure the work area of a form as you process a case. The work area includes the content and widgets, but not the header or navigation areas of the case form.

By making changes to regions and fields of a work area in real time, you can develop your application in a dynamic and flexible way.
  1. To create a case, select a case type name from the New menu.
  2. On the lower right corner of the screen, click the Open runtime toolbar icon and then click Turn editing on.
  3. On the toolbar, turn on design mode by clicking the Toggle design mode icon (the square icon) to highlight the work area.
  4. When you reach a page that requires updates, click the Pencil icon in the highlighted work area.
    1. In the right panel, click the gear icon to change the template and reorder sections in the section list. Click Change to switch the existing layout to any of the standard or custom, predefined design templates.
    2. Click the plus icon at the top of the right panel to add one of the available sections or widgets to the work area. Work area widgets are created in Dev Studio and are available for work areas within the same class structure as the widget.
    3. Drag and drop fields to arrange their order.
    4. Optional: Move sections across regions in the work area. If the template has multiple columns, you can move the Action area section to a different region but you cannot remove it.
    5. To modify the properties for a control, click the Pencil icon.
    6. Drag and drop fields to arrange their order.
  5. Click Done.
    Result: The changes that you made are displayed immediately.

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega.com is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us