Module Templates

Create and use reusable module templates in the PEARS Module Builder.

Module templates are reusable module designs that serve as starting points when creating new modules. Templates contain predefined sections, fields, and options that can be copied into a new module, saving time when your organization frequently creates modules with similar structures.

Templates do not appear in the Plan, Engage, or Reflect navigation menus and are not available for end users to fill out.

View Templates

On the Module Builder list page, templates are displayed in a separate Your Organization's Templates section below the list of active modules.

Create a Template

There are two ways to create a template:

From the Module Builder List

1

Click Add Template

On the Module Builder list page, click the Add Template button.

2

Enter template details

Enter a Module Name and Module Identifier for the template. The menu location is automatically set to Template.

3

Build the template

Click Create to create the template. Use the form builder to design the template's sections, fields, and options.

4

Publish the template

Publish the template to make it available for use when creating new modules.

circle-info

TIP: A template must be published before it appears in the Start with Template dropdown when creating a new module.

From an Existing Module

You can also create a template by copying an existing module. See Copy a Module and check the Create as Template option during the copy process.

Use a Template

When creating a new module, select a template from the Start with Template dropdown. The template's sections, fields, and options are copied into the new module as a starting point. You can then modify the copied structure in the form builder without affecting the original template.

Edit a Template

Templates follow the same versioning workflow as regular modules. To update a template, create a new draft version, make your changes in the form builder, and publish the updated version. Changes to a template do not affect modules that were previously created from it.

Last updated