For the complete documentation index, see llms.txt. This page is also available as Markdown.
Publish a Module
Publish or schedule a custom module version to make it available to users in PEARS.
Publishing a module version makes it the live version that users interact with. You can publish immediately or schedule a future publish date.
Publish a Version
1
Open the draft version
From the module detail page, click Edit Draft to open the draft version.
2
Navigate to the Publish page
Click Publish in the progress panel to open the publish form.
3
Choose a publish option
Publish now — Leave the date field empty and click Publish to make the version live immediately.
Schedule for later — Enter a future date and time, then click Schedule. The version becomes live automatically at the scheduled time.
Screenshot: The Publish Module page showing the Publish Date field for scheduling and the Publish button
NOTE: Publishing a new version replaces the previous live version. Users who open the module after publishing will see the new version's form. Preview responses created during testing are automatically deleted.
Unpublish a Version
To remove the current live version from user access:
From the module detail page, click Unpublish on the live version.
Confirm the action. The module is no longer available to users until a version is published again.
NOTE: You cannot unpublish a live version if a draft version already exists. Delete the draft first, or publish the draft to replace the live version.
Cancel a Scheduled Publish
If a version is scheduled for future publication, you can cancel the schedule from the module detail page. Click Unpublish to return the version to draft status.
Understanding Live and Draft Versions
A module can have at most two versions at any time:
Live version — The currently published version that users see. Only one version can be live.
Draft version — A work-in-progress version that is not yet visible to users. Only one draft can exist at a time.
When you publish a draft, it becomes the new live version and the previous live version moves to the version history. See Manage Module Versions for details on working with version history.
