Design communication plan forms
A communication plan form defines the information contained in a message, how the message is presented to a recipient in a way that best suits their device, and which response options are available. The Forms tab of the communication plan editor allows you to create forms, build out form content, configure delivery options, and define who has permission to use it. Once you have created a form, you must deploy it before it can be used to send notifications.
The Forms tab allows you to create an empty form and add it to the communication plan.
- On the Forms tab, click Create Form.
- In the Create a New Form dialog box, specify a Name and optional Description.
- The name you give the form is inherited by the Flow Designer canvas associated with the form.
- Click Create Form.
Once you have created an empty form, you can build out the form content, configure delivery options and permissions, create flows, and deploy the form. For an overview of the steps required to build out your form, see Building and deploying forms.
When you delete a form, any flows, subscription forms or subscriptions that are based off the form are also deleted. If the form is associated with an active event then you will no longer be able to view the message content from the xMatters web user interface or mobile apps.
To delete a form:
- Locate the form on the Forms tab.
- Click the X icon next to the form name.
By giving forms accurate names and descriptions you can easily locate and manage them. The order of forms within each communication plan on the Messaging tab is the same as their order on the Forms tab of the communication plan builder.
- To rename a form, click the form name and then type a new name when the cursor appears.
- To edit the form description, click the description and then type a new description when the cursor appears.
- To reorder the forms on the page, click the form's handle icon and drag it to a new position.
Once you've created an empty form, you still have some work to do. The following sections provide an overview of the steps you'll need to take to create the message content, define who has permission to send messages using the form, and configure advanced notification and handling options.
Once you have created an empty form, you can create the content of the messages and define message delivery options.
The form's Layout tab allows you to configure the default recipients and message handling options and specify which properties are available to be included in messages. This tab also defines whether sending the form initiates a conference bridge. For more information about working with the form layout, see Design your form's layout.
The form's Messages tab defines the content of the email, SMS (text), and voice notifications. You can include properties in the messages if the properties included on the form's Layout tab. For more information about creating message content for email, SMS (text) and voice notifications, see Define message content.
The form's Responses tab defines the response choices that are presented to message recipients and defines the action xMatters takes when each response is selected. These actions may include escalating the event, terminating the event, or connecting the recipient to a conference bridge. For more information about defining response choices, see Define response options.
You can create multiple flows for each form. Use Flow Designer to connect the tools you use into orchestrated, fully automated toolchains to help you reduce the complexity of your incident management workflows.
You can make it easier for message senders to quickly send notifications by creating pre-populated forms called scenarios. By anticipating common situations and creating scenarios that are already filled in with the appropriate values, you can reduce the number of choices a message sender must make when sending an urgent notification. For more information about creating scenarios, Access scenarios.
For the form and its scenarios to be accessible to other users, you must configure permissions. For more information about setting form and scenario permissions, see Configure form sender and scenario management permissions.
If you would like to allow users to voluntarily receive notifications even when they aren't targeted by the event, you can create a subscription form. Subscription notifications can be configured so that they are "information-only" and do not include the ability to respond or take ownership of the event. Then can also be configures so that they are generated after an event has been open for a certain length of time.
For more information about creating subscription forms, see Subscription forms.
You can notify specific users, groups, or dynamic teams when an event based off the form is initiated or concluded. For more information about setting activity updates, see Configure activity updates.
You can also create outbound integrations that send webhooks when a message is delivered, a user responds to a notification or an event is initiated, paused, or terminated. For more information, see Outbound integrations.
Before you can send notifications with your form, you must deploy it. Deploying a form defines how and where it can be accessed by message senders. Forms can be deployed for access by the web user interface, mobile apps, REST API, or email initiation. For more information about deploying a form, see Deploy a form.