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.

Frogger Quarterly Release Details Frogger was released on August 13th, 2019. The Frogger release includes inbound triggers for event signal handling, a step to create xMatters events, support for hybrid cloud environments, and step management tools that allow enterprises to run a full development cycle for their steps, and much more. For all the details, see the Frogger (July/Aug) 2019 Release Overview. Next Release: Galaga (Oct/Nov 2019) We've already started working on our next quarterly release, which we've named Galaga. Follow the Galaga Development Highlights & Support Notes page so that you receive updates throughout the quarter on all of the fun and functionality we're working on.

We're hard at work on our next quarterly release, Frogger, which will be rolling out in the Jul/Aug 2019 time frame. 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 Frogger 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 a feature in this article works, 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.

August 12-16, 2019

The Frogger Release is live!

The Frogger Release is now available in production environments. For an overview of all the features and enhancements included in the release, see our Frogger Release Overview.

Here's a quick summary of the new Flow Designer features available this release, with links to resources we've created to help you get up-and-running as quickly as possible:

• Email triggers: Initiate a flow when you send an email to xMatters. Learn more.
  • To take things to the next level, learn how to map email contents to properties in Flow Designer.
  • If you've got existing email integrations, find out how you can convert them to Flow Designer.
• HTTP triggers: Initiate a flow when xMatters receives a POST request to the trigger's URL. Learn more.
• Create events: Create a new event and send notification at any point in a flow. Learn more.
• Run location: Create workflows with steps that execute in different run locations - in the cloud, or locally behind the firewall on an xMatters Agent. Learn more.
• Step Management: Manage permissions, share steps across your organization, and keep your incident resolution workflows running while adapting them to changing requirements.
  • Share - Fine-tune which users or groups can use or edit a step. Learn more.
  • Copy - Use an existing step as a template or starting point for a new step. Learn more.
  • Version - Run a full development cycle for your steps. Learn more.

Join the conversation!
Have any questions or comments about the Frogger Release? Hop on over to the community and let us know what you think!

Integrations: Streamlined ServiceNow setup

Setting up an integration between xMatters and ServiceNow just got more convenient - it's no longer necessary to contact ServiceNow to install the xMatters app into your instance, which means you can get things set up without any delay!

Support notes

xMatters Internal Reference No.	Summary
ACTO-2630, ACTO-2634 (SUP-20141)	xMatters Agent (performance enhancement): Improved performance when switching processing between an agent and the cloud.
COR-16426	All Events report - suppressed events: Updated the information stored for historical events to ensure suppressed events are recorded as suppressed rather than terminated.
COR-17413 (SUP-20145)	Flow Designer - Custom tab (usability): Fixed an issue causing the Custom tab in the palette to display without a scroll bar.
COR-16219	xMatters REST API - people: Updated the GET /people endpoint to refine the permissions around which users could see company administrator.
COR-16746	Integration Builder: Updated the Integration Builder to handle integrations with apostrophes in their name.
COR-17230	Flow Designer - activity (usability): Improved logging so if a flow fails because of a script error in a custom step, the Activity panel shows which custom step caused the issue.
COR-16747 (SUP-20010)	Flow Designer - Email trigger: Confirmed the Email initiation trigger will allow initiation from addresses with BATV tags.
COR-16914	Flow Designer - Responses trigger: Fixed an issue where adding a new Responses trigger to the canvas hid the deprecated Notification Responses trigger.
COR-15074	Integrations - Jira Cloud (usability): Improved the error message displayed when the host could not be found.
COR-15075 (SUP-19474)	Integrations - Sumo Logic: Updated the integration to address an issue causing an error to be returned when using the Test Connection button after setting up the integration in Sumo Logic.
COR-17374 (SUP-20127)	Integrations - Remedyforce: Updated the instructions for the integration to provide a new link to the xMatters installation package in Remedyforce.
COR-16319	Flow Designer (usability): Updated the display of inputs in the step setup screen to maintain the order defined by the step creator.

August 5-9, 2019

July 29-August 2, 2019

Frogger Release Overview

The Frogger (July/Aug) 2019 Release Overview is now available! It's chock-full of eye candy and information for all the great new features and enhancements we've packed into this quarterly release. For a quick run-down on the release, be sure to check out the Frogger Quarterly Release video.

The Frogger release is now live in non-production environments and we'll be toggling the features 'on' in production environments on Tuesday, August 13.

xMatters REST API: ZipSync data imports

In the misty past when you wanted to synchronize user, group, and site data between xMatters and an external system, you'd have to install and run our EPIC client. But now in the clear present you can use the following endpoint to upload an EPIC ZipSync file directly via the xMatters REST API:

• POST /uploads/epic-v1 - uploads an epic_zipsync.zip file.

Mobile: iOS verion 3.24+

The latest version of our iOS app includes the following handy updates:

• Forgot password workflow. Forgot your password? Now you can reset it directly from the mobile app login screen using your email address or phone number (rather than having to access the web user interface through a browser or contacting an administrator):

• More convenient login. Give your thumbs a break! You don’t have to type in the .xmatters.com part of your hostname anymore. All you need to do is type in the name of your company (e.g., "Acme-Corp"), and we'll append the rest of the address:

Support notes

xMatters Internal Reference No.	Summary
COR-16941 (SUP-20016)	Groups - exporting: Fixed an issue where a hard line break (carriage return) would cause a group's description to get divided across multiple lines or cells.
COR-17003 (SUP-20029)	iOS mobile app - login: Fixed an issue where users would be logged out of the mobile app every few days.
COR-16724	Communication plans - properties: Fixed an issue where all of the property types in the selection dialog box would be grayed out and not selectable when attempting to add a new property.
COR-16179 (SUP-19779)	xMatters REST API - subscriptions: Fixed a permissioning issue that was preventing users from being able to add subscriptions to the EPIC Synchronization report via the REST API.
COR-15539 (SUP-19731)	xMatters REST API - on-call: Fixed an issue where the GET /on-call endpoint would sometimes return recently deleted users if the system was under heavy load or if the system failed to correctly remove the deleted user from the shift.
COR-15883	Communication Center dashboards (cosmetic fix): Updated the Choose Sounds dialog box to address an issue where the user interface would get distorted on some browsers.
COR-15594	Flow Designer - Activity panel: Fixed an issue where the Activity panel would sometimes show a blank value for Boolean properties.

July 22-26, 2019

Mobile: Android version 2.18+

We recently released a new version of the Android app that includes the following updates:

• Mobile-only user roles. Some of our customers prefer to contact their users exclusively using push messages on the xMatters mobile app. Whether they have internal policies or just agree with us that our mobile apps are the absolute best way to stay connected, they don't want their users to be able to add other device types to their accounts. To solve this issue, we've made it possible to create a role in xMatters for your mobile users that limits them to the mobile app and prevents them from adding other device types. For help setting this up, contact xMatters Support.
• Android tapjacking protection. As part of our security policy, we disable app interaction when we detect there's another app using the screen overlay feature on your Android device. This prevents other apps from trying to read your input data without you knowing (AKA tapjacking). The xMatters app will warn you when this occurs, and display a message to let you know that you should disable the screen overlay setting for other apps before using xMatters:

Support notes

xMatters Internal Reference No.	Summary
COR-16664 (SUP-19983)	xMatters REST API: Fixed an issue that prevented the return of all devices when there were a large number of users in the system.
COR-16667	All Events report (usability): Fixed an issue that caused data overlapping in the Overview tab.
COR-16391	xMatters REST API: Fixed an issue that caused incorrect pagination of returned results.
COR-15328	Integration Builder - deleting forms: Fixed an issue where outbound integrations were not properly deleted when a form with a flow was deleted.
COR-16392	Flow Designer - switch steps: Improved validation checking for switch steps in Flow Designer.

July 15-19, 2019

xMatters Internal Reference No.	Summary
COR-16186	Flow Designer (performance enhancement): Updated Flow Designer to prevent the creation of circular flows that could result in an infinite loop.
COR-16198	All Events report (usability): Fixed an issue that prevented resizing of columns in the All Events report.
COR-16234	User Profile - Subscriptions (cosmetic fix): Updated the text that appears when hovering over a subscription name to provide more detailed information.
COR-16419 (SUP-19955)	Messaging - recipients: Fixed an issue that caused the list of search results for the Recipients field to become blank when scrolling through the list.

July 8-12, 2019

Flow Designer: Choose a form to create an event

Availability: Frogger Quarterly Release & Early Access Program (available now)

Have you tried the Create Event step in one of your flows? You can use it to create new xMatters events and send new notifications at any point in your flow, using information from previous steps to populate values of your event (like targeted recipients or event details).

Initially, this step allowed you to create an event using the form associated with your Flow Designer canvas. We've now enhanced this feature to allow you to create an event using any of the forms in your communication plan - just select the form that you want to use at the start of the step configuration process:

Support notes

xMatters Internal Reference No.	Summary
COR-15966 (SUP-19798)	Mobile apps - Android: Updated the behavior of the Android version of the mobile app to make sure that users aren't incorrectly presented with the option to add other devices (but can still register their mobile app).
COR-15548	Mobile apps - Android: Improved the log in process for the Android app by automatically trimming whitespace when typing in a hostname.
COR-15578	Mobile apps - Android: Improved the experience when using the mobile app to reply to an event that has already ended.
COR-15560	xMatters Agents - web user interface: Fixed an issue where some types of changes to an xMatters Agent in the web user interface were not being saved after navigating away from the page.
COR-15789	All Events report - selecting dates: Fixed an error in the All Events report where switching the date range from a custom range to a pre-defined range would cause an error.
COR-16078	Recent Events report - search filters: Updated the Recent Events report to fix an issue where some browsers would continue to display or apply a deleted search filter.
COR-15912	Flow Designer - endpoints: Fixed an issue where clearing the "Include Endpoint" check box would prevent any changes from being saved.
COR-15896	All Events report - notification statistics (usability fix): Updated a label in the Notification Statistics to correctly indicate "Pending" notifications (instead of "Not Notified") for events that are active at the time of the report.

July 1-5, 2019

Integrations: Slack endpoint certification

Availability: Now in On-Demand

When you configure a Slack endpoint for a step in Flow Designer or an outbound integration, selecting the Slack authentication method for your endpoint lets you initiate OAuth2 authentication and allow access to your Slack team using the credentials you enter.

However, there was one technical fly in the authentication honey: some of our customers were unable to use this process to connect xMatters to Slack because their Slack workspace allows only certified apps to have access. We're happy to report this is no longer an issue because we've just successfully completed the certification process for our Slack endpoint!

For more information about how to configure a Slack endpoint and the OAuth scopes it requests, see the Slack authentication section for endpoints in our online help.

iOS: View suppressed events

Availability: Now from the App Store

The latest version of the xMatters iOS app extends visibility into our intelligent event management processes to our mobile platform. With the addition of information about suppressed events, you now have insight into when event floods occur in your system, even when you're on-the-go.

View suppressed events

Our event flood control feature compares incoming event requests to recent events and suppresses correlated events that occur in too close succession to one another. When suppression occurs for an event, the Recent Events screen in the mobile app now displays the suppression icon (circled in the screenshot below on the left) and a count of the number of event requests that have been suppressed under this parent event. For events where suppression has occurred, you'll also see a new "Suppression" section when you drill-through to the Event report (shown on the right below):

From here, tap Suppression to view a list of all of the individual suppressed events. You can tap on any suppressed event to view its details, such as the targeted recipients, the event flood control rule that triggered suppression, the event priority, initiator, message content, and any event properties and their values:

Support notes

xMatters Internal Reference No.	Summary
COR-16339 (SUP-19942)	Integrations - Slack: Corrected an issue that prevented Slack from communicating properly with xMatters.

June 24-28, 2019

xMatters REST API: Get a communication plan form

Availability: Now in the xMatters REST API

Communication plan forms define the information contained in messages, how messages are presented to recipients on different devices, and which response options are available. While the xMatters REST API includes an endpoint for looking up all of the forms in a communication plan, you can't look up a specific form. Actually, now you can...

• GET /plans/{planId}/forms/{formId} - Returns a specific form in a communication plan. You can embed the response options available for the form, and include any recipients set in the form.

xMatters REST API: Get form sections

Availability: Now in the xMatters REST API

If you're wanting to know more about a particular communication plan form - like which properties it includes - then you'll be interested in the following endpoint to look up information about the sections in your form layout:

• GET /forms/{formId}/sections - Returns information about the sections in your form layout.

We're building out this endpoint over time, and currently it returns information for the Recipients and Custom sections of your form layout. Since the custom section is how you add communication plan properties to a form, the information returned in the custom section object includes a list of all the properties used on your form.

xMatters REST API: Create & manage communication plans

Availability: Now in the xMatters REST API

Previously, you could use the xMatters REST API to get communications plans. With the following new endpoints, you can now create, modify, and delete them as well:

• POST /plan - Create a communication plan.
• POST /plans/{planId} - Modify the properties of an existing communication plan.
• DELETE /plans/{planId} - Delete a communication plan.

xMatters REST API: Communication plan endpoints

Availability: Now in the xMatters REST API

Communication plan endpoints provide a simple way to define the base URL and authentication credentials to use when making HTTP requests to an application from a transformation script in the Integration Builder - or from a step in Flow Designer. By configuring endpoints separately, you can quickly modify all references to an endpoint across a communication plan rather than editing each instance of the target URL in your scripts.

Previously you had to create and manage endpoints via the xMatters web user interface, but now you can also take these actions programmatically using the following new endpoints in the xMatters REST API:

• GET /plans/{planId}/endpoints - Returns a list of endpoints configured for the specified communication plan or built-in integration.
• POST /plans/{planID}/endpoints - Creates or modifies an endpoint for a communication plan.
• DELETE /plans/{planId}/endpoint/{endpointId} - Deletes a communication plan endpoint.

xMatters REST API: Delete an integration

Availability: Now in the xMatters REST API

We've just added a new endpoint for integrations that you can use to programmatically delete an integration from a communication plan:

• DELETE /plans/{planId}/integrations/{integrationId} - Deletes an integration associated with a communication plan

Support notes

xMatters Internal Reference No.	Summary
RYL-3264	All Events report - User Delivery: Updated the searching feature on the User Delivery tab of the All Events report to prevent free-form text searches when filtering on Delivery Status or Responses.
COR-15753 (SUP-19850, SUP-19866)	All Events report - User Delivery: Fixed an issue that was causing errors when attempting to view some recipient information in the User Delivery section of the All Events report.
YAV-1139	Events reports - system events: Fixed an issue where system events would not display the correct email subject/event title on the Recent Events and All Events reports in trial instances.
COR-15930 (SUP-19791)	Flow Designer - Responses trigger: Updated the Responses trigger in Flow Designer to make sure that flow will properly execute when response options are overridden in an xMatters REST API request.
ACTO-2591 (SUP-19875)	Integration Builder - xMatters Agent: Fixed an issue the Activity Stream in the Integration Builder would not display anything for inbound integrations running on an xMatters Agent if the integration resulted in a large log messages.

June 17-21, 2019

xMatters REST API: Get subscribers

Availability: Now in the xMatters REST API

Need an easy way to find out which of your users are subscribed to a particular subscription? Then you'll be a fan of this new xMatters REST API endpoint that allows you to programmatically look up all the subscribers for a single subscription:

• GET /subscriptions/{subscriptionId}/subscribers - returns a list of all users who subscribe to a subscription.

xMatters REST API: Group observers

Availability: Now in the xMatters REST API

Now when you use the xMatters REST API to retrieve information about groups using the Get a group or Get groups endpoints, you have the option to include information about group observers.

In xMatters, the Group Observers setting controls which roles can notify a group and view its details. By default, all new groups are "Observed by All", but you have the option to grant access only to specific roles (for example, you could provide Supervisors - but not other roles like Standard Users - the ability to contact an Executives group).

To return group observer information in your results, include the ?embed=observers query parameter in your request. If observedByAll=true is returned, then you know all the roles in your company have access to the group. If observedByAll=false is returned, then specific roles have been selected as observers for the group and the return includes a list of these roles.

xMatters REST API: Last login

Availability: Now in the xMatters REST API

It's now possible programmatically to look up the last time a user logged into xMatters. We've updated the Get a person and Get people endpoints to automatically return lastLogin with a user's details.

Support notes

xMatters Internal Reference No.	Summary
COR-15571 (SUP-19823)	xMatters REST API: Corrected an issue where historical data limits were not being properly applied to user requests.
COR-15604 (SUP-19851)	Flow Designer - endpoints: Corrected an issue that prevented older user IDs from creating a Flow Designer endpoint.
COR-15550 (SUP-19822)	xMatters REST API: Corrected an issue where users were required to provide device properties in order to update subscriptions.
COR-15534 (SUP-19845)	Event injection - email initiation: Corrected an issue that was preventing email initiation from processing properly.
COR-15950 (SUP-19871)	User Upload: Fixed an issue where large files with multiple supervisors would not finish processing.
COR-15115 (SUP-19744)	Integrations - Slack: Fixed an issue that prevented Slack from communicating properly with a large enterprise team.
COR-15623 (SUP-19839)	Web user interface - logo placement: Corrected an issue where logos of a specific size were incorrectly showing up underneath the header bar.
ACTO-2587	xMatters Agent: Corrected an issue where the complete version number was not properly displayed in the "Installed" screen of the xMatters Agent.

June 10-14, 2019

Flow Designer: HTTP and Email triggers

Availability: Frogger Quarterly Release & Early Access Program (available now)

If you're enrolled in our Early Access Program, you may have noticed a couple of new additions to the Triggers tab in Flow Designer: Email Initiation and HTTP Request triggers. Previously, the triggers in Flow Designer allowed you to initiate flows when event activities took place within xMatters. These new triggers allow any external system able to send emails or HTTP requests to kick off workflows when something happens outside of xMatters.

Email triggers

You can use an email trigger to inject information into xMatters from any external system capable of sending an email message. When xMatters receives a trigger initiation email from a valid sender (that is, from an email address that's assigned to a user in xMatters who has access permissions to the flow), it initiates the corresponding flow and makes information from the email available as outputs. For example, the message body of the email is assigned to an email.htmlBody output, which you can use as the input value of a property in a later step in your flow, like the description of a service desk ticket.

HTTP triggers

If your external system can send a web request, you can use an HTTP trigger to initiate a flow when xMatters receives a POST request sent to the trigger's URL. The HTTP trigger parses the payload from the incoming HTTP request, extracts information from the payload and maps it to outputs you create, making the data available to later steps in your flow.

Do email and HTTP triggers create an xMatters event?

Good question! The answer is no, email and HTTP triggers do not automatically create an event in xMatters when they're initiated. That's a little bit different than how inbound integrations and our previous email initiation feature worked.

Which leads us nicely into our next highlight...

Flow Designer: xMatters Create Event step

Availability: Frogger Quarterly Release & Early Access Program (available now)

We've added a new xMatters Create Event step to the Tools tab of the Flow Designer palette. Instead of immediately creating an event whenever an external system injects information into Flow Designer, you can use this step to create new xMatters events and send new notifications at any point in your flow. This means you can use information from previous steps to populate values like event details and targeted recipients:

For example, you could use an email or HTTP trigger to kick off a flow in xMatters that first opens a service desk ticket and starts a chat room. You could then map the ticket number and chat room link to the properties of your form so they're included in the event notification.

You can also connect additional steps to your flow after the xMatters event step to extend your workflow and pass information about the event to steps further along in the flow - maybe you'd like to post the conference bridge number for the event into the chat room you created in a previous step and update the service desk ticket.

A couple of important things to note:

• The xMatters event step creates an event using the underlying form of your Flow Designer canvas - make sure that you enable the form for web service.
• To set recipients, use the xMatters target name of the users, groups, or devices you want to target. To target multiple recipients, use a comma between input variables or target names. (Target names that contain commas aren't supported and may result in errors.)
• Properties are based on the form properties, so if you want to include different properties you'll need to add them to the form. To enter the value for a hierarchy property, use an angle bracket ">" between hierarchy levels.

Flow Designer: Flows for built-in integrations

Availability: Frogger Quarterly Release & Early Access Program (available now)

It's now easier to incorporate built-in integrations into your incident resolution workflows using Flow Designer. Once you've created a configuration, a Flows tab appears that displays the triggers for your integration and a link to the Flow Designer canvas:

Click the name of the Flow Designer canvas of your integration ("AutoShare webhook" in this BigPanda example) to link over to Flow Designer to build flows that enrich the information injected by this integration by adding new response options, connecting to other apps, or even creating new xMatters events based on flow activities.

You'll notice that we've added some safeguards along the way so that you can't break the functionality of the built-in integration. For example, you can't modify or delete the built-in responses of the configuration (although you can create new ones):

Flow Designer: Salesforce Service Cloud Add Case Comment

Availability: Now in On-Demand

We just added another step for Salesforce Service Cloud to Flow Designer! You can use the new Add Case Comment step to automatically add a comment to a case, either as an internal comment or a published comment visible to the customer:

Flow Designer: Refresh Activity panel

Availability: Now in On-Demand

Debugging flows just got a little more convenient! The Activity panel now includes a handy Refresh button that you can use to check for any updates in your flow's activity:

Flow Designer: Built-in step help

Availability: Now in On-Demand

Need help configuring one of our built-in steps? We've got your back! Just click the "?" symbol at the top right of the step configuration screen for detailed instructions:

Support notes

xMatters Internal Reference No.	Summary
COR-13388	Flow Designer (cosmetic fix): Updated a label in the web user interface to be consistent with the rest of Flow Designer.
COR-14862 (SUP-19668)	Integrations - Jira Cloud: Fixed an issue where the configuration of the xMatters add-on was getting overwritten when a specific type of update.
COR-15115 (SUP-19744)	Integrations - Slack: Improved how the xMatters bot for Slack handles large enterprise instances.
COR-15315 (SUP-19740)	Custom fields (usability fix): Updated the handling when a custom list field is switched from optional to mandatory: if the "none" option is currently selected, it will now remain set to "none" when the field becomes mandatory, and show a validation error rather than inheriting the default value.
COR-15151	Event Flood Control: Updated the email sent when an event flood is detected to include information on how to view suppressed events.
KAM-5108 (SUP-19798)	Mobile apps - registering: Updated permissions around adding devices to allow users to register their mobile device but not allow them to add a different device.
RYL-3263 (SUP-19764)	All Events report - overview: Refined the logic used by the All Events report to determine response counts so that it matches the Recent Events report.
SCO-11411 (SUP-19725)	Subscriptions (performance enhancement): Improved the efficiency of the query used to search for subscriptions by subscribers.
VOR-4697 (SUP-19793)	Mobile app - messages: Fixed an issue where the Android version of the mobile app was not displaying certain images in messages.

June 3-7, 2019

Flow Designer: Salesforce Service Cloud Update Case

We've added another Salesforce Service Cloud step to Flow Designer! You can use this new Update Case step to automatically update the information in an existing incident in Salesforce Service Cloud:

Support notes

xMatters Internal Reference No.	Summary
COR-14225	Recent Events report - event properties: Updated the Outbound Integrations section so the Trigger column includes the trigger type for Targeted Recipient Failures.
COR-14516, COR-15324	Flow Designer - custom step (usability fix): Made a couple of usability improvements to the custom step creation and setup web user interfaces.
KAM-5088	xMatters REST API - POST /group: Improved the usefulness of the error message returned when an invalid value is submitted for the group supervisor parameter.
RYL-3262 (SUP-19777)	All Events report - User Delivery: Updated the User Delivery tab to use the time zone of the logged in user, matching the other tabs in the report.

May 27-31, 2019

xMatters REST API: Get devices

Have you ever wished there was an easy way to look up all of the devices in your system? Well, today we're in the wish-granting biz! You can now use the following endpoint to do just that (if you have the appropriate permissions, of course):

• GET /devices - returns all of the devices in your system, with the option to include the timeframes during which the devices are scheduled to receive notifications.

While we were at that, we also updated GET /people so you can embed the devices for each user when you're returning a list of all the users in your system.

On-Demand: Deactivating "inefficient" voice devices

In the Enduro release, we introduced behavior into xMatters On-Demand to deactivate "inefficient" SMS devices - that is, any SMS device that xMatters is consistently and repeatedly unable to contact. We've expanded this behavior to include voice devices so that if xMatters On-Demand is unable to successfully contact a user's SMS or voice device 100 times in the same week, it'll be deactivated.

For more information, and for instructions on how to reactivate a device or look up the invalid devices in your system, see Automatic deactivation of inefficient devices in our online help.

On-Demand: SMS best practices

Are you still using SMS? You know that the xMatters mobile app is a much better alternative... right? OK, now that we've got that out of the way... Last week we announced changes to the way xMatters handles longer SMS notifications. If you haven't seen that announcement yet, or read the handy list of SMS tips we've put together, be sure to check out our xMatters and SMS Best Practices.

Support notes

xMatters Internal Reference No.	Summary
KAM-5000	xMatters REST API - POST /integration: Improved the accuracy and usefulness of the error messages returned when submitting an invalid integration script.
RYL-3142	All Events report - User Delivery: Fixed an issue where the User Delivery tab on the All Events report would return an error message if delivery failed to a group member.
SCO-11405 (SUP-19665)	Flow Designer - saving: Fixed an issue where Flow Designer would not save changes when multiple steps were added and edited in a specific order.
UTA-3678 (SUP-19722)	Voice notifications: Fixed an issue where some voice notifications were failing with a "409" error.

May 20-24, 2019

Flow Designer: New built-in steps

Are you a Zendesk, Jira Cloud, or Salesforce Service Cloud user (or maybe you'd like to be)? Then we've got great news! We've just added the following three new built-in steps into Flow Designer, which allow you to easily incorporate these tools into your incident management workflows:

	Zendesk Add Comment - automatically add an internal note or public reply to an existing ticket.
	Jira Cloud Add Comment - add a comment to an existing issue in Jira Cloud.
	Saleforce Service Cloud Create Case - automatically create a new case in Salesforce Service Cloud.

xMatters REST API: Get all groups for a site

Interested in looking up which groups are associated with a specific site? The GET /groups endpoint now includes a ?sites query parameter that you can use to retrieve a list of all the groups for a specified site. For example: GET /groups?sites=(siteId)

xMatters REST API: GET /events exact match search

It's now possible to search for events based on an exact match of a unique property. To do this, use the GET /events endpoint and the new PropertyValueOperator query parameter, in conjunction with the propertyName and propertyValue parameters. For example, here's how you'd search for events with the property 'videoGame' that exactly matched the value "frogger": GET /events?propertyName=videoGame&propertyValue=frogger&propertyValueOperator=EQUALS

For more information about how to use the PropertyValueOperator query parameter, see our online documentation.

xMatters Agent: Better visibility for developers

As a developer, you need visibility into the xMatters Agents in your system. Previously, if you weren't a registered user of an agent, you couldn't see whether a packaged or built-in integration was configured to run on that agent. Now, if you're a developer and you have access permissions to an integration, you'll be able to see which agents it runs on, and whether you're a registered user of those agents.

If you're not a registered user, xMatters will display a read-only view of an integration's configuration screen (and script editor, if applicable), so you'll be able to see the information you need but (obviously!) won't be able to edit what you haven't been granted access to:

Mobile: iOS version 3.22+

We released a new version of the iOS xMatters app last week, which includes the following updates:

• Mobile timeline. Stay up-to-date with your events using the new mobile version of our Event Timeline feature. You can now see at-a-glance who was notified and how people are responding:

• Mobile Device ID. If the xMatters app ever crashes unexpectedly, you can now quote your mobile device ID when you contact Customer Support. Our support engineers can then use it to look up the relevant crash logs and other information to get greater insight into what went wrong and get your app up and running smoothly again as quickly as possible.

Support notes

xMatters Internal Reference No.	Summary
KAM-4991	xMatters REST API - GET /groups: Improved performance of the REST API when retrieving a list of shifts that contain a lot of recipients.
ACTO-2460	Web user interface - scheduled messages: The Schedule Message dialog box will now properly display and save the correct sending time if a previously-created schedule is edited by a user in a different time zone than the message's creator.
KAM-5065	xMatters REST API - permissions: Updated some of the permission checks in the REST API to make sure they are consistent with the permissions granted in the web user interface.
UTA-3600 (SUP-19632)	SMS messages - French characters: Fixed an issue where attempting to send an SMS message that included specific French letters via a specific delivery provider would result in an error message and a failed notification.
COR-14515 (SUP-19602)	Built-in integrations - converting to communication plan: Fixed an issue where, after converting a built-in integration, the Integration Builder configuration was not editable.

May 13-17, 2019

xMatters REST API: Add a member to a shift

We've added a new endpoint to the xMatters REST API that allows you to add a member to a shift:

• POST /groups/{groupID}/shifts/{shiftID}/members - adds a member (group, person, or device) to a shift

You can use this endpoint to specify where to insert the member into the escalation timeline, and whether the member rotates according to the shift rotation rules. If you don't specify a position to insert the member, it's added to the end of the escalation timeline; and, if the group allows duplicates you can add a member to a shift more than once.

Integration Directory: ServiceNow 5.3

A new version of the xMatters application for ServiceNow is available from the ServiceNow Store. This latest release includes the following updates:

• Refined data synchronization scripts to improve performance.
• Values from xMattersConfig script include moved into system properties. If you've customized this script include in the past, there are a few extra steps you'll need to follow as part of the upgrade process.

For upgrade or installation instructions, feature and update descriptions, and a list of issues addressed in recent releases, see the integration guide here.

Support notes

xMatters Internal Reference No.	Summary
ACTO-2569 (SUP-19640)	SOAP web services: Fixed an issue where some SOAP requests were failing with "endpoint not found" or "unbound namespace" errors.
KAM-5068 (SUP-19654)	xMatters REST API - GET /subscriptions-forms: Updated the subscriptions-forms endpoint to properly return all property definitions for any returned subscription forms.
COR-14525 (SUP-19606)	Communication plans - exporting: Fixed an issue where the authentication type option was not editable for imported integrations.

5.5.258

Note: This edition of the development highlights is the last that will be tied to a specific release number. As of March 17, we'll be posting highlights and support notes together as a recap of the bug fixes, issues, and enhancements we've released over the previous week. For more information see this announcement, or check out our updated On-Demand Deployment Process and Early Access article.

Flow Designer: Improved drag & drop precision

We've made it way easier to drag and drop properties exactly where you want them on Flow Designer step input configuration screens. A vertical blue cursor clearly indicates where the property you're adding will be inserted, and you can now add properties anywhere in the input field - at the front, end, or in-between any other properties or text:

Support notes

Production release: May 14, 2019

xMatters Internal Reference No.	Summary
YAV-1104	Groups - Who's On Call (cosmetic fix): Improved the layout of the Who's On Call report to ensure that some elements were not being misaligned in some browsers.
COR-13908	Flow Designer - endpoints: Fixed an issue where some custom steps were not displaying all of the available endpoint types.
COR-14224	Responses - language support: Fixed an issue where a very specific order of operations involving responses of different lengths and languages would cause a processing error.
COR-14454	Flow Designer - event status triggers: Fixed an issue where terminating an event with a fill count required after notification delivery but before responses would not trigger the flow properly.

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.