Harness and Section forms: Help — Client Event Editor

Use the Client Event Editor to identify a non-auto-generated control that, when a user interface event is performed on it, dynamically submits elements within a work item or flow action form and re-renders the display.

To access the Client Event Editor, in the Cell Properties panel for the control select the gear icon next to the Behavior field. For client events configured before PRPC Version 6.3, the Behavior field displays for both auto-generated controls and controls that are not auto-generated.

To configure dynamic behavior for an auto-generated control, select the gear icon that is next to the Control field in the Cell Properties panel for the control. Configure behaviors using the Control Parameters (Behavior) dialog. See Control form — Completing the Control tab.

Choosing the Event

Consider the control that is to be used to present the controlling property. This rule may be identified in the Control field of the cell properties panel.

Select a value for the Event field based on the runtime presentation of the property:

Choosing the Action

Select an Action:

• Refresh This Section — When the event is performed on the property, the system submits the elements to the server in a single section. The Pega Platform uses AJAX technology to communicate between the browser client and the server. The section is then redrawn dynamically, based on the value of this controlling property. The updated form may contain different values supplied by an activity or a data transform.

For greater design flexibility, such as the ability to refresh sections anywhere on a form, you can use:

— A Refresh When condition on an included section. See Working with the Condition Builder.

— A Refresh Section action in a control such as pxButton, pxLink, or pxIcon. See Control form — Completing the Control tab.

• Post Value — Posts the property value to the clipboard and refreshes the cell's contents. Post Value is triggered by OnChange or OnBlur of the field and prior to any other event (such as a click action) initiated from a control, or from the calculation of expressions. For example: a pxButton control refreshes another section using an activity that requires three updated properties before the control can update the target section. When the user clicks the button, the properties are posted to the clipboard and are synchronized with the activity.The properties are already on the clipboard, in most cases, when the button is clicked.

Activity and Transform Data fields

If you selected Refresh This Section for the Action field, the Activity and Data Transform fields appear. You can use either or both options. If used together, the data transform processes first. To find the activity or data transform at run time, rule resolution uses the rule's Applies To class. Where possible, use a data transform rather than an activity to effect the refresh process.

• Data Transform — Optional. Enter the Name key part of a data transform that may affect the content of the section to be redrawn. Click Params to display the parameters specified on the Data Transform form's Parameters tab. Enter the values you want to pass to this data transform. See About Data Transforms.
• Activity — Optional. Enter the Activity Name of an activity that performs only computations and does not send HTML or XML code to the workstation. Click Params to display the parameters listed on the Activity rule form's Parameters tab. Enter the values you want to pass to this activity.

Click Save to exit the Client Event Editor.

Open topic with navigation