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.
We're celebrating this release with Atari's racing video game Enduro, where players race day and night, avoiding other cars and inclement weather (look out for that fog!). It's taken the same type of endurance to bring you all the great new features, enhancements, and multiple sneak peeks that we've packed into this release!
While Flow Designer changes everything for building incident management workflows, this release also includes big enhancements for Intelligent Event Management, with the ability to create your own event flood control rules, new mobile app event management capabilities, and sound alerts for event feeds on our Communication Center dashboards. But those are just some of the highlights - so buckle up, put on your helmets, and let's get this epic race started!
Before you dive in to learn about all the improvements, here are some important dates:
- Non-production environment access: Tuesday, April 30
- Production environment access: Tuesday, May 14 (triggered between 10-10:30am Pacific)
Sneak Peek
As a special bonus we'll also give you a sneak peek at enhancements we're working on for a future release:
- Flow Designer updates - extend built-in integrations, add external triggers, create an xMatters event in your flow, share & version steps, and run steps on xMatters Agents
- Developer tab reorganization - a more intuitive way to build your workflows
Jump ahead
In a hurry? Here's an overview of this doc if you want to skip ahead to something awesome:
- Flow Designer
- Intelligent Event Management
- Reporting
- Data Management
- Integrations & Development
- Mobile
- Other Product Updates
- Even More Flow Designer
- Early Access Program & Feature Delivery Update
Flow Designer
We just recently announced a game-changer for incident management: Flow Designer, a stunningly simple, visual workflow builder that’s as easy as drag, drop, and done. Flow Designer manages the complexity of synchronizing the data and tools used in incident management, so you can focus on resolving incidents.
Flow Designer offers:
- Codeless design with built-in steps for the most requested apps to flatten the learning curve for integrated toolchains.
- A visual designer for at-a-glance analysis of workflows that lets you focus on incident response orchestration.
- Enhancement of your existing communication plans to extend your current process.
- A toolkit for building custom steps to support any business process.
For more details about Flow Designer, see our introductory overview. Then when you're ready to dive in, be sure to check out our comprehensive documentation for how-to guides, and lots of helpful tips and tricks.
This is just the beginning
While we officially launched Flow Designer on April 9, that was just the initial roll out. We've got a long list of enhancements that we're working on to continue to evolve this latest innovation in our integration platform. Read on for more information about the updates that are already available, and for a whole bunch of sneak peeks at the exciting things coming up in our Frogger release, and beyond.
Usability Enhancements
We're constantly incorporating feedback to improve the overall experience of using Flow Designer. This includes things like improved drag-and-drop targeting on the step configuration screen when adding properties to step input values, and mini-icons to easily identify outputs from prior steps that can be mapped to inputs. For the latter, this makes it much easier to tell if the "Create Incident" outputs in the sidebar are from Statuspage or ServiceNow:
Got an idea?
If you've got any great suggestions of what you'd like to see in Flow Designer, or how we could make it better, please drop us a line in the online community!
New built-in steps
Flow Designer includes built-in steps for many of the common tools used in incident management workflows, and we're adding new steps all the time. In this release, we added a Zendesk Create Ticket step to the Apps tab in the Flow Designer palette:
Other steps that are coming soon:
- Zendesk Update Ticket
Sneak peek: Create xMatters Event
A new xMatters Event step will soon be available from the Tools tab of the Flow Designer palette. This step allows you to trigger a new xMatters event as one of the steps in your flow, using one of the forms in your communication plan (for example, maybe at some point in your flow you want to start a new event with a conference bridge).
The configuration for this step includes providing the targeted recipients for the form, and any requested property values:
More Flow Designer sneak peeks
We have so many other sneak peeks to share with you about what's coming next for Flow Designer, but we're supposed to be talking about the Enduro release .... so, we've created a designated section for them later on in this document! If you'd like to read about them now, follow this detour.
- Developer tab reorganization - a more intuitive way to build your workflows
- Extension of built-in integrations - use Flow Designer to add steps to your built-in integrations
- External triggers - start flows using an HTTP request
- Step management - share, duplicate, and version your steps
- Select run location - run steps in the cloud or on an xMatters Agent
Intelligent Event Management
A major theme of our last few quarterly releases is the continued evolution of our Intelligent Event Management processes. That theme continues this release with the ability to create and edit your own flood control rules, enhancements to our mobile platform that allow you to manage and comment on events when you're on-the-go, and new sound alerts for the web user interface to quickly alert you that new events and other types of event activity have occurred.
Create and edit event flood control rules
As promised, in this quarterly release we enhanced the Flood Control interface with functionality to create and edit event flood control rules for your inbound integrations.
This means that if the default Event Rate Filter we implemented in the Defender release doesn't suit your needs, you now have the option to create your own rules. This allows you to customize the event properties and trigger conditions used for event suppression, as well as the settings for event flood control notifications.
For example, maybe you'd like to do more granular filtering and suppression, such as by alert type (e.g., network issues) or sub-system (e.g., to differentiate between Nagios and Zenoss alerts being fed into your Moogsoft monitoring system). Or perhaps you'd like to define different flood threshold parameters, such as >10 events with the same priority every three minutes for a specific communication plan. Or maybe you'd like to notify recipients every 10 minutes or 500 events that a flood is ongoing.
Required permissions
To create and edit event flood control rules for a communication plan or built-in integration, you'll need the following:
- A role with permission to manage event flood control settings (this includes Company Supervisors, Full Access Users, and REST Web Service Users).
- Access permissions to the relevant or built-in integration.
Create a rule
To create a new event flood control rule, click the new + Create Rule button in the top right corner of the Flood Control page:
This opens a new configuration screen:
From here, you can define the details for your rule, including:
- Source. The communication plan or built-in integration you want the filter to apply to, and whether the rule applies to all the integrations in the plan, or to just a specific integration.
- Event properties. The properties xMatters uses to determine if incoming event requests are correlated. If incoming requests have matching values for the selected properties, the rule will be triggered.
- Trigger conditions. The rate you consider a flood, which is a rolling window of the number of events per time period (for example, 4 events within 60 seconds).
- Notification interval. How often you'd like to remind recipients that an event flood is occurring, by time period or after a certain number of events - xMatters will automatically send the notification for whichever occurs first.
Edit a rule
If you need to tweak the settings of an existing event flood control rule and you have the required permissions, you can edit its configuration settings by clicking the name of the rule on the main Event Flood Control page:
If you don't have permissions to manage a rule, you'll see the rule listed on this screen, but you won't be able to access its configuration or enable, disable, or delete it.
Manage events from the mobile app (iOS)
Need to manage events when you're on-the-go? No problem! We've made a bunch of enhancements and improvements to our iOS app this release that make it easy for you to manage events when it's inconvenient to log into the xMatters web user interface from your computer.
The biggest update to the app is a new option for events that allows you to terminate, suspend, or resume a single event - or perform the same action on multiple events. For single events, either swipe left on an event on the Recent Events screen, or select the new 'Manage' option when you're on the Event report:
To manage multiple events in bulk, tap Manage on the Recent Events screen. You have the option to 'Select All' events, or just the particular events you'd like to suspend, resume, or terminate:
Tracking report design updates
We’ve also improved the experience you’ll have when you drill into an event by introducing a new streamlined Event tracking report design (say goodbye to those over-sized colored squares!). This update also makes room on the Event report for the new Comments and Timeline capabilities we're adding to the app this release.
Other updates
Finally, these small but handy updates will also help to improve your overall event management experience using the mobile app:
- Email subject as event title. The app now displays the email subject as the title for each event (previously it displayed the form and communication plan names). This tweak is useful because the email subject is often customized with event-specific information (priority, system, location, etc.) that can give you greater insight into the type of action that's required.
- Name of initiator. The report now displays an event initiator's full name, instead of their username (and if you've configured an override display name, the report will display that instead). This takes the guesswork out of determining who the initiator might be, so now there's no more head-scratching about whether "jsmith" is John or Jennifer Smith!
- Styling updates. We've made a number of minor but eye-pleasing styling updates, such as better use of spacing and icons, to improve your overall experience using the report.
View and add comments from the mobile app (iOS)
Wish you could easily stay updated on what people are saying about an event or join the conversation yourself - even when you're not at your desk? Now you can, because we've just added the ability to view and add comments to an event from the mobile app. The following screenshot shows what the new Comments screen looks like in the iOS mobile app. For more eye-candy and a deeper look into how this new feature works, click here.
Event timeline (iOS)
Availability: This feature is scheduled to be available for the iOS app in May 2019.
In this release, we bring the Event Timeline to our mobile platform. If you're familiar with our timeline feature, you'll know how handy it is during an active event to quickly gain insights into the way an incident is progressing and to see who is working to resolve the issue. You can also review the timeline after an event has completed to make improvements to your incident management processes.
To view the timeline in the mobile app, tap the Timeline section on the Recent Events report. The timeline displays the following information in chronological order:
- Each user that was targeted, the device they were notified on, and the status of the notification (whether it was delivered or if it failed).
- How users responded, and the device they responded from.
- Any comments that were submitted by a user, either with their response or via the Tracking report.
Communication Center sounds options for events
Do you work in a network operations center where several large screens display all kinds of system monitoring feeds, including xMatters events? Do you wish there was a way you could make it more obvious when an xMatters event comes in? If so, then you'll be happy to hear that we've enhanced the Events widget on the Communication Center dashboard with sounds.
You can now configure xMatters to play a sound whenever a new event is created, when a comment is added, or when an Event Flood Control rule is triggered to suppress events. To manage your sound settings, select Choose Sounds from the events widget settings menu. This brings up the following screen where you can select a sound for each different event activity, and customize the number of times you'd like each sound to loop:
Reporting
Whether it's a customer-facing incident, digital service downtime, or unmanaged responses to critical issues, the reporting capabilities of xMatters provides insights and visibility across your business. In this release, we make additional enhancements to the All Events report.
All Events report updates
Now that extended data retention and the All Events report are in place, we can continue to focus on enhancing our reporting mechanisms to give you greater insights into your past events. In this release we made several updates to the All Events report, including the addition of response highlights and statistics, user delivery information, and new search filters for quickly finding the data that you need.
Response highlights and statistics
In addition to information about who was notified for an event, the overview tab of the All Events report now also includes Response Highlights and Response Statistics. These sections provide incident managers the information they need about response rates. This includes highlights about how many people responded, who was first to respond and how quickly they did so, the number of users for which no response was received, and a breakdown of response counts for each response option:
User Delivery information
We've added a new User Delivery tab to the All Events report that you can use to see who received notifications for an event. The report includes a list of users that were notified for the event, and the delivery status of the notification. If the event was used to notify a large number of users, you can use the User filter in the search bar to find a particular recipient.
Over time we'll be adding additional information to the User Delivery tab, such as the groups a user was targeted through, how users responded, which devices were notified, as well as enhancing the report with additional sorting capabilities and filters to make your historical event information more accessible. Here's what this might look like:
Enhanced Report Filtering
We've added two new filters to the All Events report: Source and Form. These new filters allow you to narrow down your list by the source of the event (communication plan or built-in integration name), or the name of the form used to create the event.
Data Management
A critical step to managing data in any system is being able to successfully get your data into the system, which may or may not be an easy task. In our last quarterly release, we completely redesigned how user data is uploaded into xMatters On-Demand, with a goal of making the upload process of your data management as pain-free as possible. That theme continues this release, with additional improvements to our user upload process.
User Upload updates
Have you had a chance to try our new User Upload feature yet? It makes it easier than ever to perform bulk uploads or updates of user information in xMatters, especially with the additional enhancements we added this release, which include job status notifications, user and device summary statistics, and improvements to the import process when using an exported user list.
Job status notifications
You now have the option to subscribe to User Upload job status alerts so you'll always know when your upload jobs completed successfully (or not!). Here's an example of what these alerts look like:
Sign me up!
From the Subscriptions tab in your user profile, simply select the User Upload: Job Processed subscription and choose what you'd like to be notified about. You can subscribe to all or only specific upload jobs, and you can be notified when jobs complete successfully and/or when they fail. For more information see Subscribe to User Upload alerts.
User and device summary statistics
We've added summary statistics and a new Report tab to the upload results that provides more detailed information about the number of users processed (added, deleted, or updated) as part of your upload job. This makes it easier to see your job results at-a-glance, and to confirm the upload job performed as expected.
Easier importing
We've eased up a little on the header validation for the User Upload so it'll still process your job if there's a column it doesn't recognize, or if your columns are in an unexpected order. This means you can now straight-up use an exported list of users as a template file, without modifying any columns before you import it.
Integrations & Development
Flow Designer was the major enhancement to our integration platform this release, and it's a testament to how much we love providing our customers with the tools they need to maintain the availability of their digital services. We made some other great updates too though, including enhancements to the xMatters REST API and to two of our existing integrations.
xMatters REST API
We continually enhance our xMatters REST API calls to replace existing SOAP and older REST methods. These calls not only support customer integration needs, they're also the foundation for data access by our mobile clients, the web user interface, and other key xMatters services.
xMatters REST API enhancements
In this release, we've enhanced the xMatters REST API with new endpoints that provide access to more information about communication plans, like form scenarios and properties, as well as endpoints for creating integrations, and getting and managing subscriptions. Read on for more details about these new endpoints, and for information about some other important updates we've made related to the xMatters REST API.
New endpoints
Get form scenarios
Scenarios are versions of a communication plan form that have property values predefined for different situations. In this release, we enhanced the xMatters REST API with two new endpoints that you can use to programmatically look up the scenarios that are available for a communication plan form, and retrieve information about a specific scenario:
- GET /plans/{planId}/forms/{formId}/scenarios - returns the scenarios for a form.
- GET /scenarios/{scenarioId} - returns a specific scenario.
We've also updated an existing endpoint with the option to embed scenario data when you retrieve forms for a communication plan:
Get properties for a communication plan
We've also added an endpoint for looking up the properties defined for a communication plan:
- GET /plans/{planId}/property-definitions - returns the properties for a specific communication plan.
You can also use these existing endpoints to embed property data when you retrieve the communication plans in your system, or a specific communication plan:
Create an integration
You can use the following endpoint to programmatically create or modify inbound or outbound integrations in your communication plan, without having to log into the xMatters web user interface. If your integration includes a script, you can update that too.
- POST /plans/{planId}/integrations - creates or updates an integration for a communication plan.
Get user subscriptions
We've added two new endpoints to the xMatters REST API to let you look up information about user subscriptions:
- GET /subscriptions/{subscriptionId} - returns information for a specific subscription.
- GET /subscriptions - returns a list of subscriptions.
The subscriptions endpoint includes query parameters that you can use to filter your results. Here are some examples of how you might narrow down your request:
- All subscriptions Mary McBride owns
- Subscriptions Mary manages but others own
- Subscriptions that are shared with Mary
- Subscription names containing "ITSM"
- Subscription descriptions containing "DBA Team"
Manage subscriptions
We've also added several new endpoints that allow you to manage subscriptions. You can use these endpoints to create, edit, or delete your users' subscriptions the same way you're able to in the xMatters web user interface:
- GET /subscriptions - returns a list of the subscriptions in your system.
- GET /subscriptions/{subscriptionId} - returns a specific subscription.
- POST /subscriptions - creates or updates an existing subscription.
- DELETE /subscriptions/{subscriptionId} - deletes a subscription.
- DELETE /subscriptions/{subscriptionId}/subscribers/{personId} - unsubscribes a user from a subscription.
Other Updates
Get historical information for communication plans
It's now possible to use the xMatters REST API to search for historical data about the communication plans in your system. We've enhanced the GET /plans and GET /plans/{planId} endpoints with the at parameter, which you can use to retrieve information about a communication plan at a point in time in the past. For more information about historical data access and permissions, see Accessing Data in the online documentation.
Annotations now trigger outbound integrations
We've updated the Event Comments trigger to include annotations (comments) added to an event using the xMatters REST API. Previously, outbound integrations using this trigger would only fire when comments were added via the mobile app, xMatters Inbox, email, and Tracking report.
Now, comments added to an event using the POST /event/{eventId}/annotations endpoint will trigger any new or existing outbound integrations using the Event Comments trigger. For more information about this trigger and what's included in the payload, see Event Comment webhooks.
Ability to edit or delete any group
We've added two new permissions to the REST Web Service User role in xMatters On-Demand, to give users with this role greater control to manage groups using the xMatters REST API. These permissions allow a user to edit or delete any group, even if they're not a supervisor of the group. This is handy, because it means you won't need to add a REST Web Service User as a supervisor to a group every time they want to update or delete it via the xMatters REST API.
What's next?
Over the next quarter you can expect to see new REST web services that provide the ability to create or modify information about communication plans. We'll also be adding a number of rest services based on user feedback, including endpoints to retrieve a list of all user devices, and for viewing large lists of subscribers for single subscriptions. Finally, we'll continue to expose more historical event and system information through existing endpoints to support new features related to the All Events report.
You can learn more about the xMatters REST API in our online help.
Integration Directory
The Integration Directory streamlines the work required to integrate your tools with pre-built integrations that are easy to find, configure, and manage. The main enhancements to the Integration Directory includes updates to two of our existing integrations: ServiceNow and Runscope.
New and updated integrations
 |
ServiceNow |
 |
Runscope |
Mobile
The major themes for our mobile platform this release included bringing event management capabilities to the mobile app (including the ability to view and add comments to events), and enhanced mobile reporting with the event timeline. We made a couple of other small updates that we think you'll find handy though, including enhanced logging to help with technical support, and a sweet calendar shortcut to refocus you to today's on-call schedule.
Enhanced logging for improved technical support (Android & iOS)
We've added your Mobile Device ID to the xMatters Android and iOS apps. If the xMatters app ever crashes unexpectedly, you can quote your mobile device ID when you contact Client Assistance. Our support engineers can use it to look up 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.
To locate your mobile device ID, go to setting in the mobile app and tap About xMatters:
My Schedule shortcut to "Today" (iOS)
We added a handy "Today" shortcut in the My Schedule monthly and weekly views in the iOS xMatters app that quickly returns you to today's on-call schedule:
Other Product Updates
This section includes a couple of other updates that didn't quite fit in the previous sections - but, we think you'll still find them useful.
Deactivating inefficient SMS devices
What the heck is an "inefficient" device? Basically it's a device that xMatters is consistently and repeatedly unable to contact. For example, a device might not work because someone typed in the number incorrectly. Or, a device could be outdated because the owner got a new number and never updated their settings. These 'bad' devices have a couple of trickle-down effects on everyone:
- If xMatters is trying to send you a high-priority notification and can't get through to your device, you're not being notified as quickly as you should.
- When attempting to contact a non-working device, xMatters uses time and resources better spent placing calls to working devices - and getting stuff resolved
What's the solution?
If xMatters On-Demand is unable to successfully contact a user's SMS device 100 times in the same week, it'll be deactivated. (In an upcoming release, this will apply to voice devices, too - but, we'll give you a heads-up when that happens.)
Obviously, we want to be careful not to delete any devices from the system that are actively in use and are just sometimes hard to contact. But if we fail to reach a device - say, 100 times in the same week - it's probably safe to say there's a problem. (And by fail, we mean all attempts to connect to the device fail; attempts that don't connect at first but succeed on a retry attempt are not considered failures.)
If we deactivate your device, its information will stay on the Devices page in xMatters, but it'll be marked as "Inactive" and xMatters will not attempt to contact it again. If you have an email device, you'll receive an email explaining the problem. You can then log into xMatters to check your device details. If you identify and correct the problem, you can reactivate your device and make a test call to ensure that notifications can now get through.
These inactive devices are also marked as "Invalid" in xMatters. The Users page includes a handy search filter that you can use to find all the users in your system with invalid devices:
New in-country SMS number
We've identified an additional 'hot spot' and have added an in-country SMS code for Macedonia... Здраво! This brings our grand total to 36 countries. See the complete list of countries that we currently support.
Configure an "emergency-only" device
We've heard from customers that users (or their supervisors) often use the Device Timeframe feature to create "emergency-only" devices. By setting the timeframe for a device to 00:00, they're telling xMatters that they don't want their device to be notifiable except under emergency situations.
To help support this use case, we've updated the behavior so that devices with a timeframe of zero hours and minutes will only be notified when:
- The message sender selects the "Override Device Restrictions" option (essentially declaring that this message is an emergency).
- The device is targeted directly (because directly targeting a device always ignores any timeframes or other user-specified options).
- The device is marked as "Failsafe", and a notification sent to the user's group triggers the failsafe conditions.
Even more Flow Designer
Congratulations Roadbuster, you've made it to the end! We know we already gave you a sneak peek at the new Create xMatters Event step... but to sweeten the pot, here are a whopping five more sneak peeks at some amazing new enhancements we're currently working on for an upcoming release.
Sneak peek: Developer tab reorganization
The release of Flow Designer sets a new standard for how our customers build automated workflows. To support this, we're in the beginning stages of redesigning the Developer tab in xMatters to make it more intuitive for users to work with the underlying components of Flow Designer, such as communication plans and custom or built-in integrations.
As you can see from one of our very early designs, we're planning to rename the Developer tab (terminology still to be determined!) and combine communication plans and integrations in a single, cohesive interface that makes it easier for anyone - not just developers - to work with and conceptualize the purpose and capabilities of these different components:
Sneak peek: Extension of built-in integrations
Until our overhaul of the Developer tab comes to fruition, we'd like it to be easier for our customers to extend their built-in integrations with Flow Designer. To support this, we're adding a new Flows tab to our built-in integration configurations. This tab includes links to the Flow Designer canvases for each of the underlying forms that make up the built-in integration. The tab also includes icons that indicate the triggers associated with each form, as well as the form description for added context:
If you click through to a canvas, you'll see the triggers associated with that form. While you can't edit or delete these triggers without first converting your built-in integration to a communication plan, you can add additional steps to extend your built-in's flows. The following example shows the triggers that you'd find on Datadog's "Conference Bridge" canvas, and how you could connect additional steps to this integration's status updates trigger:
Sneak peek: External triggers
The triggers included in the initial release of Flow Designer all use activities that occur within xMatters (such as an event status change, a specific response, or an added comment) to kick off a series of actions and pass incident resolution information along the toolchain. But, what if you wanted to kick off a flow when something happens in another system? With this enhancement, you'll be able to trigger flows when information is sent to xMatters by an external system.
We're in the process of adding a new Create HTTP Trigger option to Flow Designer that you can use to catch webhooks from your other applications and use them to start flows. Like custom steps, you'll have the ability to build your own custom triggers, which you can then reuse in any flow.
Here's an example of what this might look like:
In this mockup, you can see there are now different categories of triggers, including Event Activity (the pre-existing triggers) and the new HTTP Request trigger type. In this example, the Stackdriver and Pingdom triggers have been dragged onto the canvas and connected to other steps to create flows that will kick off when the trigger receives an HTTP request.
Here's the plan
We're starting by giving you a toolkit that you can use to start building your own custom triggers. After this is in place, we'll then start creating pre-built trigger steps (like our built-in app steps) that use simple drag-drop-configure models to define inbound flows.
Sneak peek: Step management (sharing, duplication, versioning)
Have you built a custom step that you'd like to share with others? Or, maybe you want to share but don't want others to edit the step's underlying logic. Wish that you could tweak a built-in app step or a custom step to better suit your organization's specific processes? We thought you might! We're working on the following step management enhancements that will allow you to do all of these things, and more.
Step sharing
When you create a custom step, you'll soon be able to specify its usage permissions from the step's settings menu:
This allows you to select exactly how and who you'd like to share your step with (or if you'd like to keep it all to yourself). If you're choosing to share, you can give all users blanket permission to only use the step, or if they're also able to edit it (which means they can use and edit it). Or, you can get more granular and specify specific users, groups, or roles that you want to share it with, and what permission level (use or edit) each of those entities have:
Once step sharing is in place, the Custom tab of the palette will display filters that you can use to show the steps that you own, any steps that were created by someone else and shared with you, or all the steps that you have access to:
Copy a step
Want to duplicate a built-in step so that you can extend or otherwise customize it? For example, maybe you're using the ServiceNow Create Incident step, but you'd really like to be able to add some additional input fields. Custom and built-in steps will soon have an option that you can use to copy the step, so you can customize it however you like without changing the functionality of the existing steps:
Step versioning
We're also introducing the ability to version your steps. Using ServiceNow as an example, you could use this feature to label your London vs Madrid versions and support your steps through a full life-cycle:
- In Development - only available for use by step owners and may not be fully functional.
- Deployed - up-to-date and available for use.
- Deprecated - still available for use but have been scheduled for withdrawal. The planned withdrawal date is displayed as a warning to users on the step configuration screen.
- Withdrawn - no longer available and will cause errors when the step executes.
Sneak peek: Select run location
Want to run a flow step on an xMatters Agent so that your flow can include behind-the-firewall systems? Then you'll like the new Run Location logic we're adding to the custom step configuration, which allows you to specify where you'd like the step to be able to run - either in the Cloud, or on an xMatters Agent:
Early Access Program & feature delivery update
The goal of our current delivery model for xMatters On-Demand is to balance feature delivery with customer change management processes. This means providing visibility into upcoming changes for customers that want it, while allowing other customers to have a more standard non-production environment that matches production.
If you aren't familiar with the current model, we release features only visible to admins/developers at a faster pace than the quarterly release process. These features should not impact end users until a customer provisions them into their communication plan. Customers can opt their non-production environments into the Early Access Program to see features and functionality enhancements that impact end users before they're released on a quarterly basis. All customer non-production environments are updated two weeks prior to official quarterly production release to allow for testing and training on new features.
We regularly reevaluate and improve our deployment processes to ensure they reflect industry best practices and customer feedback. For more information about our deployment process, see our On-Demand Deployment Process and Early Access article. We'll update that document whenever we make a change, and let you know about the change through other appropriate channels.
Comments
1 commentArticle is closed for comments.
The Enduro Quarterly Release is now available in all production environments.