To create a new Microsite, use the Create button on the Microsites landing page.
Provide a name and description for the Microsite. Users can also utilize the Advanced Settings section to configure advanced options, such as inheritance and ruleset information.
To nest the new Microsite under an existing one, select the existing Microsite in the Derives From (Pattern) field (under Advanced Settings).
Upon clicking Submit, the system creates a new class for the Microsite (with class name PegaMKT-Work-Microsite-<MicrositeName>). The system also creates starter rules for the Microsite in this class and then presents the stage-based Microsite view.
A newly created Microsite starts out with the following stages:
In this stage, customer and action data (if available) is loaded so that it can be used by later stages. For this data to be loaded, at runtime, the Microsite must be launched from a customer and/or action-aware context. An example of such a context would be an action email that was sent to a customer with a link to the Microsite.
In this stage, the Microsite is displayed to the customer. A new Microsite starts with a single page, titled Page 1. Behind the scenes, the system has automatically generated corresponding Flow, Flow Action, and Section rules to support this page. Primarily, users should only modify the section to specify the contents of the Microsite. To do so, click the step in the stage to select it. Then, click the Configure view button in the right pane to open the backing Section rule.
In this stage, values entered by the customer on Microsite pages are saved. This stage saves two types of data:
- Action data – These values can later be used in the progressed flow.
- Custom Site data – These values are custom fields created and specified by the users. See Defining and Using Custom Data Fields for details.
In this stage, the action that initiated the Microsite (e.g. via an email containing a link to the Microsite) will be progressed along the ResponseReceived path. By default, the response value is set to Accepted.
In this stage, a confirmation page is displayed to the customer. The identifier of the out-of-the-box generated confirmation page Section rule is Confirm.