Skip to main content

This content has been archived and is no longer being updated.

Links may not function; however, this content may be relevant to outdated versions of the product.

Utilizing the Action Form for Harnesses and Sections

Suggest edit Updated on September 13, 2021

This presentation is part of the Advanced UI Techniques Self-Study Course.

Transcript

Traditionally, a button or icon with a custom activity was used to invoke and follow a new process from the middle of an existing process. This is fine for some situations but does not work well when the activity in question creates a new work object and displays an assignment on that new work object.

The CPM Framework takes advantage of a minimal change to the Action form on the Perform Harness to solve this requirement while still being guardrail compliant.

For example, we are interacting with a customer and attempting to search for the customer record.  When the customer record is not found, we are required to register the customer.  Interacting with the customer and creating a new customer are two separate processes. 

By changing the target of the Action form, you can direct the submission of the form to submit the entire form rather than just the Action form. This can be achieved by embedding a fragment with a small piece of JavaScript that modifies the target attribute of the form.

Did you find this content helpful? YesNo

Have a question? Get answers now.

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

Ready to crush complexity?

Experience the benefits of Pega Community when you log in.

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