The information in this article is the intellectual property of xMatters and is intended only for use with xMatters products by xMatters customers and their employees. Further, this intellectual property is proprietary and must not be reused or resold.
|
Lunar Lander Quarterly Release Details Lunar Lander was released on May 18, 2021. The Lunar Lander release features enhancements to support your incident management processes. Stakeholder updates, real-world incident metrics, easy-to-install workflows, and easier alerting are just some of the highlights. It also includes new ways to collaborate, resolver enhancements, and a redesigned user profile. For all the details, see the Lunar Lander (Apr/May 2021) Release Overview. Next Release: Missile Command (Jul/Aug 2021) We've already started working on our next quarterly release, which we've named Missile Command. Follow the Missile Command Development Highlights & Support Notes page so that you receive updates throughout the quarter on all of the fun and functionality we're working on. |
Introduction
We're hard at work on our next quarterly release, Lunar Lander, which will be rolling out in the Apr/May 2021 timeframe. Please follow this article and its comments to receive updates throughout the quarter about new features and functionality that we're working on for the Lunar Lander release.
Customers interested in previewing new features before they're released can opt into our Early Access Program (EAP), which delivers new features into non-production environments as they're rolled off the assembly line.
We'll also use this document to capture highlights of additions and updates to our mobile platforms and the xMatters REST API.
Deployment Details
For more information on how features in this article work, click the online help links embedded in each topic. As with any of our Community articles, you can click any image or animated GIF to see a larger version.
Support Notes
For a list of additional changes made in each deployment that are not covered in the Development Highlights, see the On-Demand support notes included below each highlight. While most features will be added to production environments as part of our quarterly releases, the support notes typically describe fixes, which can sometimes affect product behavior.
May 24-28, 2021
Simplified flow creation & alerting
The following features from our Lunar Lander release are now available in production environments (click the links for more info):
- Create flow canvases - Easily create canvases where you can build automated flows without having to first add messaging forms to your workflow.
- Create Alert step - Create events and send notifications at any point in your flows without using messaging forms and configuring form properties.
A note about 'events' vs 'alerts'
In the Lunar Lander Release overview, we mentioned that we'll be updating our terminology to use 'alerts' instead of 'events'. The Create Alert step is the first feature to reflect this usage, and over the coming months we'll be updating other features as well, including the Recent Events and All Events reports, event flood control, and event-based rotations in groups. For more information about these changes, see our support article, Automation and terminology updates.
New App triggers
We've added another seven App triggers in Flow Designer! You can take advantage of these new triggers to build your own custom signal handlers in xMatters:
- BigPanda Incidents
- Elastic Alerts
- Honeycomb Alerts
- Panopta Monitors
- Sentry Alerts
- Sumo Logic Alerts
- ThousandEyes Alerts
Support notes (week of May 24-28)
| xMatters Internal Reference No. | Summary |
| COR-37961 | Flow Designer - Merge step: Fixed an issue where users could save the Merge step with empty required fields. |
| COR-37498 | Post-Incident Report - Actions: Corrected an issue where changing the sort order of a column caused all table columns to return to their default order. |
| COR-30871 (SUP-22675) |
Flow Designer - Copy as Custom Step: Fixed an issue that prevented users from saving a copy of a step. |
| COR-38411 (SUP-23101) |
User profile - Groups page (usability fix): Ensured the help link directed users to the correct page in the online help. |
| COR-38409 (SUP-23175) |
Messaging - email template editor (usability fix): Fixed an issue that caused the cursor to return to the beginning of the subject line if the user stopped typing. |
| COR-38294 | Flow Designer - response triggers: Corrected an issue where adding a response trigger to the canvas resulted in users seeing an error message, even though the trigger was successfully added. |
| COR-38233 (SUP-23163) |
Admin menu - security settings: Corrected an issue where renaming the Company Supervisor role prevented users with that role from viewing security settings. |
| COR-38426 (SUP-23103) |
Admin menu - sites: Fixed an issue that caused a column header to have an incorrect name when exporting sites. |
May 17-21, 2021
Lunar Lander Release
The Lunar Lander Release is now available in production environments! For an overview of all the features and enhancements included in the release (and their availability), see our Lunar Lander Release Overview.
Lunar Lander Training Webinars
For a guided tour of the release, including tips and tricks, sign up for one of our free workshops.
xMatters Agent: Version 1.6.11
This latest release improves the ability of the xMatters Agent to handle valid integration requests that don't immediately succeed. Agents will now retry requests with 429 errors until they succeed. They'll also retry requests with network exception errors that have a chance of succeeding (i.e., 4xx/5xx errors) up to three times.
Support notes (week of May 17-21)
| xMatters Internal Reference No. | Summary |
| COR-38405 (SUP-23177) |
User Profile - custom attributes: Adjusted the User Profile screen to ensure all custom attributes are available for each user. |
| COR-37786 | Post-Incident Report (usability fix): Modified the layout of the Actions menu to provide a more consistent user experience. |
| COR-35031 | xMatters REST API - GET /plans?embed=integrations: Fixed an issue where companies with more than 100 integrations had some integrations excluded from the returned response. |
| COR-38120 (SUP-23098) |
Flow Designer - Activity panel: Fixed an issue where opening the Activity panel caused the web browser to crash. |
| COR-38095 (SUP-23147) |
xMatters REST API - GET /events: Fixed an issue to ensure the endpoint to returns accurate user notification counts. |
| COR-38004 | Incident Console - export: Corrected an issue that excluded the Time to Acknowledge time from an exported incident report. |
May 10-14, 2021
Lunar Lander is coming!
We'll be enabling the Lunar Lander release in production environments tomorrow, Tuesday, May 18 at 10:00 am Pacific! If you want to get a head start, the following features are available now in all instances (click the links for more info):
- Incident Commander role - The Resolvers section of the Incident Console includes a permanent 'Incident Commander' role, which you can reassign by dragging someone else into this role.
- Resolver time to acknowledge - The Resolvers tab of the Incident export includes how long it took for each resolver to engage in the incident, providing helpful insight to improve your response process.
- Search for steps in the palette - Quickly and easily hone in on the step you're looking for!
- Initiate flows from Pingdom Server Monitor and Splunk - You can now trigger flows when xMatters receives signals from Pingdom Server Monitor (formerly Scout) and Splunk Infrastructure Monitoring (formerly SignalFx).
New EPIC data sync client version
We've released a new version of the EPIC data sync client! Version 5.5.274 adds some enhancements to the included libraries to address or prevent potential security vulnerabilities. You can get the latest version here.
Include company details in email & app messages
Our Email/App message builder now includes Company Properties that you can use to customize your messages with your company's name and the base URL of your xMatters instance. This is useful if you want to include a link to the login page for your xMatters instance in your emails or to differentiate messages coming from your prod and non-prod instances.
Support notes (week of May 10-14)
| xMatters Internal Reference No. | Summary |
| COR-38036 (SUP-23150) |
User Profile: Fixed an issue that was preventing supervisors from accessing the UUID for a user. |
| COR-38031 (SUP-23142) |
Recent Events report - Properties tab: Corrected an issue that caused users to see an error message instead of report information. |
| COR-37631 | Dashboards - Event by Source widget: Ensured that the Events by Source widget legend displays data in a consistent and expected format. |
| COR-36182 | Incident Console: Fixed an issue that could occur when attempting to adjust times for incident metrics. |
| COR-37952 (SUP-23098) |
Flow Designer - Activity panel: Corrected an issue where attempting to open the activity panel for a specific trigger could cause the browser to crash. |
| COR-37933 | Group Performance report - Export: Updated the headings for some report fields when exporting in French. |
May 3-7, 2021
Lunar Lander Release Overview
The Lunar Lander Release Overview is now available! It's your comprehensive guide to all the great new features and enhancements we've packed into this quarterly release. Lunar Lander is currently live in non-production environments and we'll be toggling the features 'on' in production environments on Tuesday, May 18.
New workflows for Dynatrace & BlazeMeter
We've just released new versions of our Dynatrace and BlazeMeter (formerly Runscope) workflows that you can install directly from xMatters. These workflows include a pre-built flow that creates an event when xMatters receives a signal from the external system. When on-call resources respond to the event notification, they have the option to initiate an incident. For a quick tour, click here.
'Alert Context' property in Event Activity triggers
The 'Alert Context' property in messaging is useful for giving users context about why they're being notified — whether it's because they were targeted directly, as part of a group, or by a subscription. This information is also useful for integrations and sending updates to third-party systems about why a user was notified.
For this purpose, we've updated our Responses and Device Delivery event activity triggers to include a new property with the alerting path followed to notify the recipient:
-
respondedTo.by.alertContextfor Responses triggers -
notification.recipient.alertContextfor Device Delivery triggers
Impact start, end, & duration included in Post-Incident Report exports
To give stakeholders more context as they're reviewing an exported report, we've updated both the DOCX and PDF versions of the report to include the Impact Start, Impact End, and Impact Duration:
Resolver response effort
The recently-added Resolvers tab on the Incident export now includes an 'Engaged Duration (minutes)' column which reports the total number of minutes each resolver was engaged in the incident. Rather than assuming each resolver was engaged for the full period the incident was active, this metric reflects the actual time a resolver became engaged, when they were dismissed, and if they reengaged. This is helpful for compensation purposes and supports a more accurate estimate of the total incident response effort.
Support notes (week of May 3-7)
| xMatters Internal Reference No. | Summary |
| COR-37907 (SUP-23134) |
Flow Designer - step and trigger usage: Fixed an issue that was causing some steps and triggers to be incorrectly labeled as "In Use". |
| COR-37894 | Incident Console - Post Incident Report: Updated the layout and appearance of some items on the Post Incident Report to address issues with some browsers. |
| COR-37759 | All Events report - searching: Fixed an issue where attempting to find events using a single character as the search criteria would cause an error message. |
| COR-37736 | Communication Center - shared dashboards: Fixed an issue that was causing an error message to be displayed when attempting to access shared dashboards. |
| COR-37734 | Conferences report - related events: Updated the Conferences report to address an issue that could occur when viewing related events. |
| COR-37732 | Notifications report - searching by date: Updated the Notifications report to display the correct error message when attempting to apply an invalid date range. |
| COR-37580 (SUP-23083) |
Incident Console - collaboration channels: Fixed an issue where searching for an existing Microsoft Teams channel to add to an incident would sometimes return distribution lists. |
| COR-37758 (SUP-23098) |
Flow Designer - Activity panel: Fixed an issue where attempting to open the Activity panel for a flow with an extremely large payload would cause the browser to crash. |
April 26-30, 2021
Include URLs in incident descriptions
Ever wished you could add a URL to an incident so resolvers could link to another resource for more context? Well, now when you include http:// or https:// web addresses in the description of an incident, they'll appear as clickable links in the Incident Console:
Incident timeline styling update
The incident timeline just got a little easier on the eyes — we've updated entries with icons so it's quicker to identify different types of incident activities as you're scanning through the timeline:
Initiate flows from New Relic and Nagios
We've added another three new App triggers in Flow Designer. You can use these triggers to initiate flows when xMatters receives signals from Nagios Core or Nagios XI, and New Relic:
Support notes (week of April 26-30)
| xMatters Internal Reference No. | Summary |
| COR-37597 | Incident Console - Post Incident Report: Fixed an issue that was causing errors when removing a due data on the Post-Incident Report. |
| COR-37507 | Groups - Adding groups: Updated the Groups page to ensure that the number of groups in the system updates properly after adding a new group. |
| COR-37467 | Communication Center - Event Traffic widget: Updated the layout of the Event Traffic widget to prevent the time from being truncated at certain resolutions. |
| COR-37599 | Workflows - scenarios: Fixed an issue that was causing an incorrect error message to appear when attempting to save a scenario with more than 100 characters in its name. |
| COR-37557 (SUP-23066) |
xMatters REST API - GET /people: Fixed an issue that was causing timeouts when making a request to the GET /people endpoint. |
| COR-37533 (SUP-23068) |
Recent Events - response counts: Fixed an issue that was causing a SQL error when attempting to access response counts on the Recent Events reports. |
| COR-37201 | Flow Designer - step names: Flow Designer will no longer allow users to save a step with only spaces in its name. |
April 19-23, 2021
Lunar Lander Quarterly Release
Fire up the thrusters—we're on the final approach to the quarterly release! Here are the dates to mark on your calendar:
- Non-production environment access: Tuesday, May 4
- Production environment access: Tuesday, May 18 (enabled between 10:00-10:30 am Pacific)
Keep an eye out for the complete Lunar Lander feature overview, coming on Tuesday, May 4!
Trigger flows from Site24x7 and Zabbix
We've added two new triggers to the Apps tab of the Flow Designer palette (click a trigger name below for more info):
You can use these triggers to initiate flows when xMatters receives signals from a Site24x7 Monitor alert or a Zabbix Problem alert.
Support notes (week of April 19-23)
| xMatters Internal Reference No. | Summary |
| COR-37394 | Messaging Page - scenarios (usability fix): Fixed an issue that caused the form description to appear on the scenario page instead of the scenario description. |
| COR-37289 (SUP-22997) |
User devices - escalations: Corrected an issue that caused some users to not receive notifications in the proper escalation order through their devices. |
| COR-37214 | Flow Designer (usability fix): Fixed an issue that caused Flow Designer to not always load properly. |
| COR-37205 (SUP-22814) |
Recent Events report - Response Counts: Corrected an issue that caused Response Counts to incorrectly show an error icon beside the Other Recipients row. |
| COR-37074 | Reports - Notifications (usability fix): Fixed an issue that caused the Device menu to display "Android" no matter what device type was selected. |
| COR-37501 (SUP-23065) |
Workflows - Flow Designer: Corrected an issue that prevented users from saving a step in Flow Designer. |
| COR-37508 (SUP-23064) |
Workflows - Flow Designer: Fixed an issue that prevented Flow Designer from properly displaying connectors between steps. |
April 12-16, 2021
Keep tabs on the status of your Post-Incident Report
You can now see at a glance whether you've completed post-incident reviews for your major incidents. We've added a Post-Incident Report column to the Incidents list which lets you track the statuses of your reports. To view a report's information, simply click its status to link to the Post-Incident Report builder.
More consistent messaging experience between mobile app & web UI
With the latest release of the xMatters app for iOS and Android, any forms or scenarios you 'star' in the app appear as starred in the web user interface (and vice versa):
We've also updated the Forms and Scenarios tabs in the app to match the preferred order of your messages in the web user interface. To see this view, select the 'Default' sort order:
Support notes (week of April 12-16)
| xMatters Internal Reference No. | Summary |
| COR-37221 | Dashboards - Event Traffic widget (cosmetic fix): Minor adjustments to the color of the Search button and the Events by Source display. |
| COR-37104 | Messaging form: Fixed an issue where opening a message form with a valid link caused URI character encoding within the link. The URI encoding made the previously valid link break when the message is saved. |
| COR-36980 | xMatters REST API - GET /device-names?deviceTypes: Ensured the proper error message appears when users request device names without specifying a device type. |
| COR-36954 | Recent Events report: Ensured the proper message is shown in the User Totals screen an event is triggered from a messaging form that does not contain recipients. |
| COR-36935 | Dashboards - Workflow Templates search: Fixed an issue to ensure category searches work as expected. |
| COR-36638 | All Events report - search: Corrected an issue so the source drop-down menu returns all results when multiple searches and sources are selected. |
April 5-9, 2021
Add other collaboration channels from the Incident Console
Want to add a collaboration channel to an incident, but the product your team prefers isn't currently available in the Incident Console? No worries—you can now add Other collaboration channels to an incident:
This new option lets you manually add an existing chatroom, online conference call, or other communication platform to the incident by linking its URL. Once the channel is added, resolvers can easily link to it from the Incident Console.
Post-Incident Report improvements
We've made the following updates to the Post-Incident Report to help improve your postmortem process:
- Contributors: The report now includes a list of people involved in the post-incident review. For convenience, any users engaged in the incident when it was resolved are automatically added to the list of contributors, and you can edit this later to remove or add additional people.
- Status: You can use this new drop-down to set the status of a Post-Incident Report and let resolvers and contributors know how it's progressing through the review and sign-off process.
- Actions: We've moved the 'Add Action' button to the top of the report so you can add action items from any tab of the report. You can also see the report and navigate between tabs as you're adding actions, which makes it easier to reference what you've written in the report and any actions that you've already created or completed.
Trigger flows from BlazeMeter, Dynatrace, and Moogsoft
Another three new app triggers are now available from the Apps tap of the Flow Designer palette (click a trigger name for more info):
You can use these new triggers to initiate flows when xMatters receives signals from a BlazeMeter API Monitoring alert, a Dynatrace problem, or Moogsoft alert.
New workflow for Pingdom
We've just released a new version of our Pingdom workflow that you can install directly from within xMatters! (If you've been following this space, then you know we're updating our workflows so they're easier to install and get started—more info here).
Support notes (week of April 5-9)
| xMatters Internal Reference No. | Summary |
| COR-37052 | Dashboards - Event Traffic widget (usability fix): Ensured the correct error message is displayed when users don't have permission to view the report. |
| COR-36955 (SUP-23006) |
Messaging - Inbox (usability fix): Corrected issues that caused messages to display with improper sizes and scroll bars, and that included parentheses as part of links. |
| COR-36843 (SUP-22996) |
Flow Designer: Fixed an issue that caused warning messages to appear when multiple responses are connected to a single step. |
| COR-36599 (SUP-22946) |
Reporting - xMatters Agent: Fixed an issue that caused disconnected events to appear in the User Performance report. |
| COR-36196 (SUP-23032) |
Voice notifications: Corrected an issue that caused notifications to deliver messages using the incorrect language. |
| COR-36754 | Integration Builder (cosmetic fix): Adjusted the Script Editor parameters so long form titles are not hidden by the page buttons. |
March 29-April 2, 2021
Trigger flows from Grafana
Another new App trigger has hit the Flow Designer palette! You can use the Grafana Alerts trigger to initiate flows when xMatters receives signals from Grafana:
New workflow for Datadog
We've added a new workflow for Datadog—like the two other workflows we released recently, you can install this workflow directly from within xMatters. These workflows include a pre-built flow that creates an event when xMatters receives a signal from the external system. When on-call resources respond to the event notification, they have the option to initiate an incident.
Signals report: Refresh & handling of deleted workflows and triggers
The Signals report now includes a Refresh button that you can use to update the report to see the latest signals received by your xMatters instance:
We've also made it easier to identify signals associated with deleted workflows or triggers. Now when you delete a workflow or trigger, any existing report entries for signals associated with the deleted trigger are grayed out and display the trash can icon:
Support notes (week of March 29-April 2)
| xMatters Internal Reference No. | Summary |
| COR-36685 (SUP-22950) |
Groups - shift-based rotations: Fixed an issue where changing the start time of a shift with a shift-based rotation would not properly reschedule the rotation. |
| COR-35106 | Incident Console (usability fix): Updated the layout and positioning of some UI elements in the Resolvers area to prevent overlaps and address some display issues on some browsers. |
| COR-36701 (SUP-22971) |
Integration Services: Fixed an issue where some users were unable to access the legacy Integration Services pages in the web user interface. |
| COR-36755 (SUP-22975) |
All Events report - messages: Fixed an issue where the notification message was unavailable for some archived events. |
March 22-26, 2021
Trigger flows from AWS Cloudwatch, Prometheus Alertmanager, and AppDynamics
We've just added another three new app triggers to the Flow Designer palette (click a trigger name for more info):
You can use these new triggers to initiate flows when xMatters receives signals from an AWS Cloudwatch alarm, a Prometheus Alertmanager webook, or an AppDynamics webhook.
Filter the All Events report by multiple forms
We've improved the filtering capabilities of the All Events report — you can now use the Form filter to select more than one form at a time. This makes it easier to view event traffic across multiple forms in your organization:
Export the Post-Incident Report as a PDF
The Post-Incident Report export includes a new option to Print to PDF. This saves time if you don't need to make any formatting or styling edits in a word processor before you convert the report to PDF for distribution:
Signals report: View related incidents
The Signals report now includes a Related Incident column to help you better understand which signals initiated incidents in xMatters. The Incident IDs displayed in this column are hyperlinks to the Incident Console, where you can get more context about the incident:
Support notes (week of March 22-26)
| xMatters Internal Reference No. | Summary |
| COR-36612 (SUP-22965) |
Messaging page - scenarios: Fixed an issue that caused the messaging page to cap the number of displayed scenarios per form to 100. |
| COR-35955 | All Events report - date picker: Corrected an issue where an error message was displayed instead of valid data when the date picker was set to 90 days. |
| COR-35215 (SUP-22789) |
Recent Events report - export: Fixed an issue that caused the exported report to display failed SMS notifications as delivered. |
| COR-35003 | Workflows - import (usability fix): Corrected an error that caused imported workflows to have broken breadcrumb links back to the Workflows page. |
| COR-36647 (SUP-22968) |
xMatters REST API - GET /forms: Improved performance when accessing endpoint under certain conditions. |
| COR-36632 (SUP-22966) |
xMatters REST API - POST /integrations: Ensured the proper error message was used to provide valid information on why a submission failed. |
| COR-36168 | Events - processing: Fixed an issue that caused some events to not process correctly, leading to a backlog. |
March 15-19, 2021
New workflows for Microsoft Azure and Google Cloud Operations Suite
We've just added two new workflows for Microsoft Azure Monitor and Google Cloud Operations Suite. Instead of having to download and import a .zip file, you can install these workflows directly from within xMatters — just select the workflow from the list of available templates, and then click "Install"!
To ensure you're up and running quickly, these workflows include a pre-built flow that creates an event when xMatters receives a signal from the external system. When on-call resources respond to the event notification, they have the option to initiate an incident:
You can then use Flow Designer's powerful visual interface to further customize or enhance the workflow's functionality to meet your organization's specific needs.
Trigger flows from Pingdom
We've added another new app trigger to the Flow Designer palette for Pingdom Check Alerts. You can use this trigger to initiate flows when xMatters receives signals from a Pingdom webhook:
Select an existing Slack or Microsoft Teams channel to collaborate on an incident
You can now search and select your existing Slack and Microsoft Teams channels when you add a collaboration channel to the Incident Console. This is handy for connecting to your predefined MIM channels, or for incidents that escalate quickly and already have active chat channels before you get into the Incident Console.
Here's what this looks like for Slack (for Microsoft Teams, you'll need to search for a team and a channel):
Support notes (week of March 15-19)
| xMatters Internal Reference No. | Summary |
| COR-35973 | Incidents - change incident owner: Corrected an issue that restricted changing an incident owner to users with Company Supervisor permissions. |
| COR-35945 (SUP-22916) |
Groups - Group export: Modified report settings to ensure exported results match the filtered results displayed in the web user interface. |
| COR-35751 (SUP-22893) |
Messaging - scenario permissions: Fixed an issue that caused the web user interface to experience delays in displaying the Scenario Permissions window. |
| COR-36018 (SUP-22901) |
Messaging page: Corrected an issue that caused delays in displaying the list of available messaging forms. |
| COR-35873 | All Events report - export: Fixed an issue where the user ID was not displayed properly in the exported report. |
| COR-35868 | Flow Designer - Responses: Corrected an issue that prevented some property information from passing correctly to downstream steps.from |
| COR-35942 | Incident Console - export: Fixed an issue that caused message discrepancies in the Timeline of the exported incident. |
March 8-12, 2021
Add xMatters Conference Bridge collaboration channels from the Incident Console
You can now add xMatters-hosted conference bridges to an incident from the Incident Console. This is useful for workflows that don't automatically create collaboration channels when initiating incidents (such as the default xMatters Incident Management workflow).
You have the option to Create new bridge or to search for and Link existing bridge:
Real-world incident acknowledged times
Wish an incident's 'Time to Acknowledge' metric reflected when the first resolver became engaged? Well, now it does! The Incident Console now sets an incident's acknowledged time to when the first resolver became engaged, or when the incident's status was updated from 'Open' to another value (e.g., 'In Progress')—whichever happens first.
If that doesn't quite match when a resolver first started working the incident in the real world, you now also have the option to update this metric to the exact time you want for your records:
Find events related to an incident
Need to find the events related to particular incident? Don't worry—you won't need to scroll through all of your events. We've added a new Related Incident filter to the All Events report that allows you to easily search for events by their incident ID. You can also sort the table by incident ID by clicking the Related Incident column header.
Support notes (week of March 8-12)
| xMatters Internal Reference No. | Summary |
| COR-35899 | Recent Events report - search and filter: Fixed an issue where where the search bar displayed truncated information, and where the report did not properly apply search filters to returned results. |
| COR-35887 (SUP-22894) |
Subscriptions - Add subscription: Corrected an issue that caused a truncated list of device types to display when expanding the Devices list. |
| COR-35688 (SUP-22882) |
Messages - Create message (usability fix): Updated the behavior of the message editor to improve some functionality and to ensure it identifies the correct default font style. |
| COR-35516 (SUP-2832) |
Integration Builder - inbound integrations: Updated the error message to identify the underlying issue for some authentication problems and assist in troubleshooting. |
| COR-35748 (SUP-22899) |
Flow Designer - Switch step: Corrected an issue where opening a new Switch step caused Flow Designer to return the user to the Workflows page. |
March 1-5, 2021
Automatically kick off Zoom Meetings & Microsoft Teams Online Meetings
We've added new Zoom 'Create Meeting' and Microsoft Teams 'Create Online Meeting' steps to Flow Designer. Include these steps in your flows to automatically create these meetings as part of your workflow processes:
When you configure these steps, you can specify an "Incident ID" to associate the meeting with an incident in xMatters — and add a link to the meeting in the Collaboration section of the Incident Console.
Trigger flows from Datadog
There's a new app trigger in the Flow Designer palette for Datadog Monitor Alerts. You can use this trigger to initiate flows when xMatters receives signals from a Datadog webhook:
Edit an incident's detected time
Want to fine-tune the 'Time to Detect' metric to reflect how long it actually took to detect the incident in the real world? You can now update the default value of this metric by editing the Impact Start time of the incident and when it was Detected:
See who's collaborating on xMatters conference bridges
The Incident Console now includes information about who's collaborating on xMatters conference bridges. The Collaboration section displays how many people are currently on the bridge, and you can click to view more information about who's participating:
We've also added icons to the Resolvers section to indicate which resolvers are currently on a bridge associated with the incident:
Filter Signals by HTTP status
We've added a new filter to the Signals report to view signals based on their HTTP Status Code. For example, you could look up signals with status code values that are "Failures (4xx, 5xx)" to help identify incoming signals that may not be formatted correctly:
Support notes (week of March 1-5)
| xMatters Internal Reference No. | Summary |
| COR-35646 (SUP-22874) |
Reports - Conferences: Fixed an issue where deleting a conference bridge host caused the report to display an error message instead of a list of conference bridges. |
| COR-35617 (SUP-22869) |
Reports - All Events: Corrected an issue that caused the date range to reset to the current date into the "to" field instead of the user selected date. |
| COR-35593 (SUP-22870) |
Messaging - recipients: Fixed an issue that prevented users from adding recipients to their messaging forms in Internet Explorer 11. |
| COR-35564 (SUP-22861) |
Reports - All Events: Corrected an issue where attempting to open an event whose initiator has been deleted resulted in a timeout error. |
| COR-35544 (SUP-22860) |
xMatters REST API - GET /subscription-forms: Fixed an issue where the property definitions were not returned in the order specified in the web user interface. |
| COR-33526 | Incident Console - timeline (cosmetic fix): Modified the spacing around timeline entries to ensure they don't overlap one another. |
| COR-35436 (SUP-22828) |
Messaging: Fixed an error that prevented users from accessing the Messaging page when using certain proxy settings. |
About the early access delivery process
Customers can choose to opt their non-production environments into an Early Access Program (EAP) to see new functionality before it's released. If you're considering signing up for the early access program, there are a couple of important things to know:
- Enrollment in EAP can be turned on any time through a support request.
- Exiting EAP can only be done on quarterly boundaries (you cannot opt in and out between quarterly releases).
For full details, refer to the official On-Demand Deployment Process & Early Access article.
Comments
13 commentsArticle is closed for comments.
Highlights and support notes added for week of March 8-12, 2021:
Updates include:
Highlights and support notes added for week of March 15-19, 2021:
Updates include:
Highlights and support notes added for week of March 22-26, 2021:
Updates include:
Highlights and support notes added for week of March 29-April 2, 2021:
Updates include:
Highlights and support notes added for week of April 5-9, 2021:
Updates include:
Highlights and support notes added for week of April 12-16, 2021:
Updates include:
Highlights and support notes added for week of April 19-23 2021:
Updates include:
Highlights and support notes added for week of April 26-30 2021:
Updates include:
Highlights and support notes added for week of May 3-7, 2021:
Updates include:
Highlights and support notes added for week of May 10-14, 2021:
Updates include:
Highlights and support notes added for week of May 17-21, 2021:
Updates include:
Highlights and support notes added for week of May 24-28 2021:
Updates include:
We've started working on our next quarterly release, which we've code-named Missile Command.
Follow the Missile Command Development Highlights & Support Notes page to receive updates throughout the quarter on all the fun and functionality we're working on!