🪄 Dynamic Forms

Rootly comes pre-configured with a set of Default Forms used to collect key information to help you track incident data at the time of incident creation, resolution, and more. You can customize these forms by adding or changing the custom fields within them, or create your own forms from scratch. Fields refer to the individual sections within each form — Rootly also provides a large selection of fields to choose from and the ability to create your own.

Now, we’ve introduced even more flexibility into forms with the ability to create Dynamic Forms! Dynamic Forms allow you to configure separate versions of your forms that apply under certain conditions—for example, a specific incident type. If none of your conditions apply, the default version of the form will be used.

Some benefits of using Dynamic Forms:

• Only collect the data that matters for each specific incident
• You can reduce the amount of form fields to make data collection more efficient 
• Set clearer parameters among teams for which fields are optional or required 
• More control for teams to choose the data they want to collect

In this demo, Ashley walks you through a quick use case creating a dynamic incident creation form for security incidents:

Learn more about Dynamic forms in our Help Docs.

Ready to start using Dynamic Forms? Reach out to Rootly Support today to request enablement of this feature! 

🌝 New & Improved

🆕 Sub-incidents can now be referenced through the {{ incident.sub_incidents }} liquid variable from the parent incident. Teams can now configure workflows to update or send messages to the child incident(s) when the parent incident status changes.

🆕 Multiple alerts can now be systematically attached to an incident via Alert Workflows.

💅 Bulk editing capabilities are now available on the Alerts page of the Rootly web dashboard.

💅 Resolution and mitigation messages are now configurable fields that can be included built-in and custom forms.

🐛 Fixed intermittent issue with teams unable to receive Slack messages when multiple team channels are targeted in the Send Slack Message and Send Slack Block workflow actions.

🐛 Fixed issue with non-users being able to be added to Rootly On-Call rotations.

‍