Each stage can have one or more steps that it performs. Typical steps for Microsites are provided out-of-the-box and are associated with the default stages, e.g. load data, save site data, progress action, etc.

A marketing-specific step type is the page. Page steps are quick ways to inject a screen (or page) into the Microsite process. To add a new page, the user can select the +STEP item in the steps area of a stage. After the user specifies the desired page name, the system will automatically create the backing structure (Flow, Flow Action, and Section).

To open the generated Section rule, users can select the page step and click the Configure view button in the right pane. 

A newly created section is shown below.

Users can customize the section content to include any pertinent information to display to or gather from the customer. The Next button in the section can be customized as well. This can be done by overriding the NextButton section in the Microsite class and applying any desired styles to it.

In the Microsite stage view, the X icon on a step facilitates the deletion of the step while the four-directional cursor allows for steps to be moved to their desired position within a stage. When a step is deleted from a stage, the backing artifacts are not deleted and this page step can be added back to the stage at a later point.

For advanced configuration, select the process item (first item) in a stage and then use the Open process link in the right pane to open the backing Flow rule for the selected stage.

• Defining custom fields for microsites

  Users can define custom data fields to use in the pages of the Microsite. Any such field should be defined in the PegaMKT-Data-Microsite class. In the following example, two data fields NewValue and ProspectEmail have been defined in the custom data class.

• Configuring a microsite to display and save custom site data

  The following Microsite serves as a basic example of displaying and saving custom site data. This Microsite is not action- or customer-context aware.

• Configuring a microsite to be aware of customer and action context

  The following Microsite serves as a basic example of utilizing the customer and action context.

• Configuring a microsite to launch a different microsite

  Sometimes, users may wish to launch a different Microsite at a particular stage in their Microsite. This can be done by using either the Redirect Microsite or the Launch Microsite step, as outlined below.