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.
|
Krull Quarterly Release Details Krull was released on February 23, 2021. The Krull release features a redesigned Messaging screen for both our web and mobile platforms, enhancements for managing incidents, the ability to add collaboration channels to from our incident console, and improvements for getting integrated with xMatters. It also includes a new dashboard widget for monitoring incidents and an export option for the Post-Incident Report. For all the details, see the Krull (Jan/Feb) 2020 Release Overview. Next Release: Lunar Lander (Apr/May 2021) We've already started working on our next quarterly release, which we've named Lunar Lander. Follow the Lunar Lander 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, Krull, which will be rolling out in the Jan/Feb 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 Krull 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.
February 22-26, 2021
Add Microsoft Teams collaboration channels from the Incident Console
Anyone with access to an incident in xMatters can now add new or existing Microsoft Teams channels from the Incident Console. This is useful for workflows that don't automatically create collaboration channels when initiating incidents — like the default xMatters Incident Management workflow.
You have the option to Create a new channel or Link existing channel in Microsoft Teams:
Also, if you provide a link to an existing Microsoft Teams meeting instead of a channel, it'll be added with a different icon so you can easily distinguish your meetings from your channels:
Support notes (week of February 22-26)
| xMatters Internal Reference No. | Summary |
|
COR-35358 |
All Events report - event details: Fixed an issue where clicking on an event caused a timeout error instead of displaying the event details. |
| COR-35348 (SUP-22790) |
Incident Management - Incidents list: Corrected an issue that prevented users from seeing incidents in the list when the corresponding event are deleted. |
| COR-35320 (SUP-22886) |
Groups - Group export: Modified report settings so the export results display in English if the user's instance language is something other than English or French. |
| COR-35319 (SUP-22817) |
All Events report - exporting files: Fixed an issue where exporting an All Events report filtered by Initiator would generate an empty export file. |
| COR-35175 (SUP-22766) |
Shifts - shift escalations: Corrected an issue where the escalation path was not properly followed when a user selected Escalate as a response option. |
| COR-35119 (SUP-22801) |
Devices - voice devices: Fixed an issue where phone numbers were not displayed properly if the first numbers of the phone number were identical to the numbers of the country code. |
| COR-35239 | User profiles - change login: Ensured the appropriate error messages appear if a user tries to save changes when required fields are blank. |
| COR-35007 | Flow Designer - Email trigger: Corrected an issue that prevented the Authenticating Users drop-down list from opening properly. |
| COR-35080 | Flow Designer - Activity stream: Modified the activity stream so it accurately noted whether flows failed or were cancelled. |
February 15-19, 2021
Trigger flows from Google Cloud Monitoring or Microsoft Azure
We've added new app triggers to the Flow Designer palette for Google Cloud Incidents and Microsoft Azure Alerts:
You can use these triggers to initiate flows when xMatters receives signals from Google Cloud Operations Suite or Microsoft Azure webhooks. To get started, drag one of these triggers onto your canvas, copy the URL, and then use it to set up your webhook:
See our online help for more detailed instructions on configuring webhooks for Google Cloud Incidents and Microsoft Azure Alerts.
Support notes (week of February 15-19)
| xMatters Internal Reference No. | Summary |
| COR-34683 | xMatters dashboards - Manage Dashboards (usability fix): Corrected an issue that disabled the Delete Selected and Change Owner buttons when the search field was cleared. |
February 8-12, 2021
Map to xMatters priority values
The Map Event Priority step we told you about in the Krull Release Overview is now available. You can use this step to 'map' values in the signal from an external system to xMatters event priority levels. This means you don't need to worry about the parameters in incoming signals matching the values xMatters expects, and you don't have to write your own custom step to match them up.
When you configure this step, you specify which expected incoming values should correspond to each xMatters priority level and use the output of the step to set the priority in a connected step – such as the xMatters Create Event step.
Edit and remove collaboration channels
During an incident, it's vital that teams know exactly where and how to communicate. If you need to update the name, URL, or details of a collaboration channel, or a channel is no longer relevant and can be removed, you can now do this through the Incident Console.
Click the options drop-down menu next to the channel you want to modify and select Edit or Remove:
Support notes (week of February 8-12)
| xMatters Internal Reference No. | Summary |
| COR-34953 | Device Management - email domains: Fixed an issue where including extra commas in the Allowed Domains field when editing an email device would remove existing domains and disable saving. |
| COR-34933 | Flow Designer - Merge and Switch steps (usability fix): Updated some styling and appearance aspects of the Merge and Switch steps to improve user experience. |
| COR-34835 (SUP-22771) |
Web login - change password: Fixed an issue where repeatedly forcing a password reset would prevent the user from being able to change their own password. |
| COR-34140 | Message designer - image library: Replacing an image in the message designer's image library with an image URL should now properly replace the existing image. |
| COR-31720 | Add Users - translations: Added some missing French translations to the Add Users dialog box. |
| COR-33547 (SUP-22636) |
All Events report - Notification Statistics: Updated the All Events report to count users who have no notifiable devices (as determined by the device filter settings on the event) as 'Failed', which is consistent with the Recent Events report. |
| COR-34771 | Device Management (usability fix): Updated the help button on the Device Management page to open the correct location in the online documentation. |
February 1-5, 2021
Link existing Slack channels from the Incident Console
Ensuring resolvers can easily access collaboration channels is vital for effective incident management. While sometimes you'll want create a new Slack Channel dedicated to an incident, in other cases you might want to link to an existing channel where people are already discussing the issue.
It's now possible to link existing Slack channels to an incident from the Incident Console. When you select to add a Slack collaboration channel, choose Link existing channel and provide the channel's name and URL:
Incident by Severity widget drill-through
The Incidents by Severity widget displays the number and severity of incidents over selected time periods, making it easier to visualize trends and identify potential improvement opportunities:
Now you can easily drill through to the Incidents list to explore a graph's underlying data in more detail. To do this, do one of the the following:
- Click the timeframe summary below the graph's title ('Past 30 days' in the image above) to view the incidents in that timeframe.
- Select an area on the graph and then click View Incidents in the summary pop-up window to view the related incidents for the selected period (alternatively, you can click one of the severity levels to view only the incidents with that severity).
Support notes (week of February 1-5)
| xMatters Internal Reference No. | Summary |
| COR-34610 | Flow Designer (usability changes): Implemented a number of changes to improve the look and feel of Flow Designer. |
| COR-34605 (SUP-22734) |
Admin - Device Management: Fixed an issue where some users could not successfully add a new device type. |
| COR-34231 | Messaging - Scheduled Messages: Changed the button label in the "No Recipients Selected" warning window so it accurately reflects the action that will happen; "Schedule Message" rather than "Send". |
| COR-33998 | Groups - user info card: Ensured the proper error message is displayed to users when they open the info card of a user they don't have permission to view. |
| COR-33141 (SUP-22562) |
Subscription notifications: Fixed an issue that prevented subscription notifications from being sent out for some events. |
| COR-34059 (SUP-22750) |
All Events report - User Delivery tab: Corrected an issue that caused an error to appear on the User Delivery tab instead of valid user information. |
| COR-33995 (SUP-22641) |
xMatters REST API - GET /plans/{planId}/forms: Ensured the endpoint returned the proper error response message for requests where a plan contains no forms. |
| COR-34514 (SUP-22725) |
xMatters Agent: Fixed an issue where an agent could run an integration twice, or multiple agents could process the same update. |
| COR-34622 (SUP-22742) |
Conference Bridges - joining a call: Fixed an issue where some users received an error message when answering a voice notification instead of hearing the actual message with the option to join a conference bridge. |
| COR-34543 (SUP-22700) |
Email notifications (cosmetic fix): Fixed an issue where border and cell padding values were not preserved on messages in Office 365. |
| COR-34452 (SUP-22719) |
xMatters REST API - GET/audits: Corrected an issue where some customers experienced intermittent timeout issues when making requests of the audits endpoint. |
| COR-34422 (SUP-22722) |
Admin - Company Details: Fixed an issue that prevented users from successfully saving changes to the Outgoing Caller ID for their company. |
January 25-29, 2021
Krull Release Overview & feature availability
The Krull release is now live in non-production environments! You can read about all the great new features and enhancements included in the release in our Krull Release Overview, and we'll be toggling the release 'on' in production environments on Tuesday, February 23.
But wait! Some release features are already available in all environments! Click a link to read more:
- Resolver roles - Add labels to your resolvers describing their responsibilities in resolving the incident.
- Manually add Slack channels to an incident - Add existing Slack channels from the Incident Console.
- 'Incidents by Severity' dashboard widget - Monitor trends in the volume of incidents over time.
- Post-Incident Report export - Create documents to share with stakeholders or for your records.
- 'Add Note to Incident' step - Automatically enhance the timeline with information from your flows.
- 'Map Incident Severity' step - Map values from an external system to xMatters severity levels.
- Search for flow variables - Quickly find variables and constants you need when you're configuring a step.
- Updated password policy - Require users' passwords to not contain dictionary words.
Support notes (week of January 25-29)
| xMatters Internal Reference No. | Summary |
| COR-34400 | Communication Center - dashboards (cosmetic fixes): Implemented minor changes to improve the look and feel of dashboard widgets |
| COR-32475 (SUP-22497) |
xMatters Mobile App (Android): Fixed an issue that caused the Android mobile app to occasionally force a logout. |
| COR-30178 | Incident Management - incident export (usability fix): Updated some missing French translations for when an incident is exported. |
| COR-32175 | Groups - shifts: Corrected an issue where a confirmation modal did not close properly when the user navigated away from it. |
| COR-34124 | Groups - add a group (cosmetic fix): Fixed an issue that distorted the size of some items on the Add window. |
| COR-34087 | xMatters login screen: Modified the functionality of some navigation elements to ensure users see the proper login screen. |
| COR-34047 | xMatters REST API - GET /people?embed=devices: Corrected an issue to ensure the request returns the correct number of embedded devices for each user. |
January 18-22, 2021
Krull Quarterly Release Update
Saddle up your fire mare and sharpen your glaive, because the Krull Quarterly Release will be available tomorrow in non-production environments!
We're just putting the finishing touches on some features, which we'll be releasing into non-production environments over the next couple of weeks. To make sure you have enough time to get familiar with all the changes before they go live in production, we've moved the official release date to Tuesday, February 23:
- Non-production environment access: Tuesday, January 26
- Production environment access: Tuesday, February 23 (enabled between 10:00-10:30 am Pacific)
Be sure to check out the Krull Release Overview tomorrow, where we'll give you the full rundown on all the new features and functionality included in this release.
Support notes (week of January 18-22)
| xMatters Internal Reference No. | Summary |
| COR-34048 | Groups - Group performance searches: Fixed an issue where multiple search criteria were incorrectly included in searches resulting in inaccurate results. |
| COR-34004 | xMatters Agent: Corrected an issue that prevented a complete drop-down list of users from expanding in the recipients search field. |
| COR-33992 | xMatters REST API - GET /on-call: Ensured the correct error message is displayed to users when they request the on-call schedule of groups that contain un-encoded special characters. |
| COR-33291 | User profile - Devices: Fixed an issue to ensure the testing status is not altered if devices are re-ordered in the list. |
| COR-33290 | User profile - Devices (cosmetic fix): Updated the layout and positioning of some elements on the Devices tab to provide a smoother user experience. |
| COR-33883 | xMatters REST API - GET /people?embed=roles: Fixed an issue where valid requests for historical data that included embedded roles resulted in an error message. |
| COR-33860 | xMatters REST API - POST /uploads: Ensured the correct error message is displayed to users if they submit a multipart upload form that is not formatted correctly. |
| COR-33763 (SUP-22679) |
Workflows- Flow Trigger step: Fixed an issue that caused a flow trigger and all its connectors to disappear from the canvas, causing the flow to fail. |
| COR-33627 (SUP-22640) |
Flow Designer - Activity Stream: Corrected an issue where the Activity stream does not display the correct steps taken in a switch step. |
| COR-33570 | Flow Designer - Save the flow: Fixed an issue that removed the title of the Unsaved Changes dialog box from appearing when users tried to close a flow without saving changes. |
| COR-28126 | Workflows - Create Event step: Fixed an issue in the Create Event step that prevented the list property from correctly displaying pre-populated values. |
January 11-15, 2021
Krull Quarterly Release
Our next quarterly release is coming up fast! Here are the dates you'll want to mark on your calendar:
- Non-production environment access: Tuesday, January 26
- Production environment access: Tuesday, February 9 (enabled between 10:00-10:30 am Pacific)
Keep an eye out for the complete Krull feature overview, coming on Tuesday, January 26!
Support notes (week of January 11-15)
| xMatters Internal Reference No. | Summary |
| COR-33838 | Workflows - importing: Fixed an issue where importing a workflow that included a conference bridge within one of its forms caused an error on the Messaging tab in Free instances. |
| COR-33734 | Users page - My Profile: Corrected an issue to ensure that users can't see their profiles and devices if they don't have the appropriate permissions. |
| COR-33733 | Subscriptions: Corrected an issue where the "Subscribed" check box was cleared after the user acknowledged a "Cannot Unsubscribe" error message. |
| COR-33698 | Flow Designer - input fields: Fixed an issue to ensure values retain their formatting if they're used within angle brackets. |
| COR-30224 | Users page - Search results: Corrected an issue where users could see incorrect search results if they request a second search result before the first search has completed. |
| COR-33730 (SUP-22677) |
Device management - email domains: Corrected an issue that prevented users from saving changes when they removed all email domains from the Allowed Domains field. |
| COR-33654 | Workflows - delete xMatters Agent: Modified the "Delete xMatters Agent" confirmation window to ensure relevant information is displayed to the user. |
| COR-33632 (SUP-222644) |
xMatters REST API - POST /devices: Corrected an issue so the correct error message displays when attempting to assign an existing externalKey to another device. |
| COR-33445 (SUP-22628) |
Messaging - Message editor styles: Fixed an issue where preset styles were not applied properly and could cause user-specified styles to break. |
January 4-8, 2021
Incident Management: Resolver roles
The Resolvers section of the Incident Console now lets you add labels to each of your resolvers describing their role or responsibilities in resolving the incident. This makes it easy to see what everyone is working on and why they're included in the incident resolution process:
xMatters REST API: Assign users a phone PIN
When you create or modify users with the xMatters REST API, you have the option to programmatically set their phone PIN – that's a number they can enter into their phone to identify themselves when they call into xMatters to retrieve their messages. To do this, include the new phonePin parameter in your request to Post /people.
Support notes (week of January 4-8)
| xMatters Internal Reference No. | Summary |
| COR-33700 | Admin - Device Management: Fixed an issue where the cursor would shift position when attempting to edit a device name. |
| COR-33450 (SUP-22646 |
Web User Interface - Login page - Company logo: Corrected an issue where a company logo appeared properly in the Company Details page, but was distorted on the login page. |
| COR-33440 | Groups - Shifts: Fixed an issue where reverting a modification to a shift occurrence deleted previous occurrences, and applied the modification to the remaining occurrences. |
| COR-32689 | Groups - Shifts: Updated the group calendar page to prevent users from inadvertently moving a shift so it overlaps perfectly with an existing occurrence. |
| COR-30594 | xMatters REST API - POST /events: Corrected an issue so the correct error message displays when submitted events contain a null form ID. |
| COR-33189 | All Events Report - Recipients column: Fixed an issue that caused the All Events reports to repeat user names in the Targeted Recipients column. |
| COR-33184 (SUP-22604) |
Groups - applied filters and file exports: Fixed an issue where filters applied to the Groups page resulted in an empty export file. |
| COR-31690 | Users page - Add Users - Help window: Corrected an issue that caused the xMatters online help to open in a distorted window with no way to maximize it in Internet Explorer 11. |
December 14-18, 2020
Incident Management: Dismiss resolvers
You can now dismiss resolvers from an incident. This is helpful for indicating which resolvers are no longer needed to actively engage in resolving the incident, and for keeping an accurate record of when and how long each resolver was engaged.
To dismiss a resolver, select Dismiss Resolver from the options menu:
And you can optionally add a note explaining why you're dismissing the resolver:
Notes are appended to the timeline record of when the resolver was dismissed:
Dismissed resolvers
You can easily distinguish which resolvers were dismissed because they're greyed out in the console:
Support notes (week of December 14-18)
| xMatters Internal Reference No. | Summary |
| COR-33317 (SUP-22432) |
Integration Builder (performance enhancement): Fixed an issue that potentially caused timeout issues on some Integration Builder requests. |
| COR-33210 (SUP-22618) |
Device Management - email domains: Adjusted the web user interface to automatically convert email domains to lower-case. |
| COR-33180 (SUP-22527) |
Workflows - importing flows: Corrected an issue that prevented workflows that included the Merge step from importing successfully. |
| COR-33083 | Incident Console (cosmetic fix): Fixed an issue where extremely long descriptions or timeline entries were not properly word wrapping within their sections. |
| COR-33063 | Groups - Shifts: Corrected an issue where an unused time zone caused an edited shift to appear at the wrong time in the schedule. |
| COR-33200 (SUP-22603) |
User Import: Fixed an issue that caused errors when the user upload file contained custom attributes. |
| COR-32475 (SUP-22497) |
xMatters Mobile App - Android: Corrected an issue where users were repeatedly logged out of the xMatters mobile app. |
| COR-32612 (SUP-22559) |
Flow Designer - email initiation: Fixed an issue that was causing timeouts when attempting to send POST requests to an email trigger. |
| COR-32329 | Integration Builder - xMatters Agent: Corrected an issue where a messaging loop triggered the creation of a large number of events. |
December 7-11, 2020
Incident Management: Add resolvers without sending notifications
You can now immediately add resolvers to an existing incident without sending them a notification. This is useful when you've already got people working the incident and you simply want to add them to the list of engaged resolvers without making them stop what they're doing to acknowledge a message.
To do this, select the new Mark as Engaged option when you're adding resolvers. You'll then be able to select which users to add to the incident (you can't mark groups or dynamic teams as engaged).
To send a notification inviting users, groups, or dynamic teams to engage in the incident, select Notify to Engage.
Incident Management: Resolvers styling updates
We've streamlined the design of the Resolvers section so it's easier to see which groups are represented and what each user's engagement status is. With this cleaner design, actions to 'Notify' and 'Stop notifying' resolvers are available from an options menu, and you can move your cursor over a resolver's status to see the time they were notified or became engaged:
Flow Designer: New custom step image library
The next time you select an image for one of your custom steps or HTTP triggers, you'll notice we've made the following great improvements to the Image Library:
- Modern, streamlined design with a larger drag-and-drop surface for uploading images
- Custom icons at the top of list, with newest images listed first
- Improved resolution of the default images included in the library
Support notes (week of December 7-11)
| xMatters Internal Reference No. | Summary |
| COR-33073 (SUP-22585) |
Event Traffic widget - All Events report: Corrected an issue that prevented the display of accurate user data when accessing the All Events report notification statistics from the Event Traffic widget. |
| COR-32842 (SUP-22574) |
xMatters REST API - user deliveries: Fixed an edge case issue where attempting to retrieve user deliveries for an event would fail under specific circumstances. |
| COR-32912 (SUP-22583) |
Messaging Forms: Corrected an issue that prevented the Send Message button from being visible at certain zoom levels. |
November 30 - December 4, 2020
Post-Incident Report is now live in production
Advanced plan customers can create a Post-Incident Report in xMatters as part of their postmortem process. On the Incident Console, click Create a Post-Incident Report on a resolved incident to get started:
For details about what's included, see the related entry in the Joust Release Overview, or consult our online help for complete instructions.
Mobile Incident Management (iOS)
It's essential to stay connected when things go wrong so we're happy to announce that you can now manage incidents on the go! This version of the iOS app gives you the ability to view, update, and resolve incidents right from your iOS device.
Use the mobile incident console to update an incident's details, status, and severity by tapping the field:
The resolvers field shows any groups, users, or dynamic teams that are currently engaged. If you need additional resolvers to help with the incident, you can add them by tapping the field and selecting from the People and Groups contact lists:
Read more about how to use the new mobile features in the online help.
Don't use iOS? Don't worry—Mobile Incident Management for Android is coming soon!
Improving All Events report performance
To better support our customers with extensive historical data, we're making some changes to the All Events report. These enhancements will greatly reduce or even eliminate the timeout issues that some customers were experiencing when retrieving larger results sets.
For the full deployment schedule and an explanation of the potential trade-off in overall response times, see our recent Enhancements to the All Events report article.
Support notes (week of November 30 - December 4)
| xMatters Internal Reference No. | Summary |
| COR-32717 (SUP-22569) |
Users - Add Users: Fixed an issue where users without the ability to add users were seeing the Add User button. |
| COR-32714 | Web User interface - translations: Ensured French translations were available for various sections of the user interface. |
| COR-32668 (SUP-22560) |
Workflows - Incident Management: Corrected an issue where users were unable to add resolvers to an existing incident. |
| COR-32602 | User Import: Mobile devices that are part of an import file are ignored by the upload process. As such, we've adjusted the User Import log to display warnings instead of error messages. |
| COR-32447 (SUP-22541) |
User Export: Corrected an issue where some very large user exports experienced timeouts. |
| COR-32424 (SUP-22531) |
Flow Designer - Integrations: Corrected an issue where flow triggers were removed from the canvas when the flow was saved. |
| COR-32419 (SUP-22524) |
Flow Designer - Create Event step: Fixed an issue where deleting an unconnected Create Event step from the canvas caused validation errors for other flow steps. |
| COR-29892 | Conferences - Related Events: Ensured the links on the Related Events page take the user to the tracking report of the event. |
| COR-22712 | All Events report - User Delivery: Fixed an issue where Who Was On Call was not available if group members did not have devices. |
| COR-32651 (SUP-22534) |
Integrations - Microsoft Teams: Corrected an issue where xMatters was unexpectedly disconnected from Microsoft Teams. |
| COR-32364 (SUP-22515) |
All Events report: Fixed an issue that caused poor performance when retrieving event data via the All Events report |
November 16-20, 2020
Initiate incidents from Slack
Does your team live and breathe in Slack? If so, you'll love to hear you can now use the xMatters bot to initiate incidents in xMatters – without leaving Slack!
Use the /xMatters initiate command to provide basic information about the incident and select which Slack conversation to post details about the incident in after it's created:
Once the incident is initiated in xMatters, the bot posts a message with information about the incident to the conversation you selected:
Add an incident to a Microsoft Teams meeting
We've been working closely with Microsoft as it launches its new meeting extensibility capabilities, which add support for apps in online meetings. You can now add an xMatters tab to your meetings to keep your team up to date on incident details and collaborate on incidents without leaving your online meetings:
Update incidents from meetings
When you update the incident's severity, status, or description from your meeting, this information is automatically updated for the incident in xMatters:
Support notes (week of November 16-20)
| xMatters Internal Reference No. | Summary |
| COR-32256 (SUP-22489) |
xMatters REST API - GET /people: Improved performance when requesting a list of users that contains a large number of supervisors. |
| COR-32189 (SUP-22493) |
Messaging - layout formatting: Fixed an issue that removed user-provided formatting from the message form. |
| COR-31338 (SUP-22313) |
xMatters Mobile App (Android/iOS): Corrected an issue that caused some mobile apps to display notification responses twice. |
| COR-32311 (SUP-22507) |
Flow Designer - Activity Stream: Fixed an issue that prevented some users from accessing and using the Activity Stream. |
| COR-32267 (SUP-22504) |
Users - Add Users - Sites: Corrected an issue where only the first 100 sites were displayed in the list of available sites. |
| COR-32060 | Admin - Sites: Fixed an issue that prevented users from being able to delete some sites in their systems. |
November 9-13, 2020
Support notes
| xMatters Internal Reference No. | Summary |
| COR-32147 | Flow Designer - property menu: Fixed an issue to ensure the property menu contained proper object names for connecting triggers. |
| COR-32051 | Groups - updating group name: Corrected an issue where changing the group name caused prevented shift changes from saving. |
| COR-27924 | Dynamic Teams (cosmetic fix): Fixed an issue that caused text to overlap some fields. |
| COR-32063 | Workflows - importing: Corrected an issue where case-sensitivity mismatches prevented a workflow from importing properly. |
| COR-32015 (SUP-22473) |
Flow Designer - custom steps: Ensured that custom steps will not display the Endpoint tab if the "Include Endpoints" check box is left blank when the step is created. |
| COR-32014 (SUP-22463) |
Logging in via SSO/SAML: Fixed an issue that caused some SAML users to see a "Could not generate SAML metadata" error when they attempted to log on to their xMatters instance. |
|
COR-31711 (SUP-22444) |
Flow Designer - Slack steps: Fixed an issue where inputs in configured fields of connected steps were removed after the steps were disconnected from each other. |
| COR-31648 | Groups - filtering: Updated the "With Any Empty Shifts" filter on the Groups page to ensure it will return the expected search results. |
| COR-31483 | Workflows - Activity Updates (cosmetic fix): Adjusted item spacing to ensure a consistent look and feel of the drop-down menus in the Activity Updates window. |
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
14 commentsArticle is closed for comments.
Support notes added for week of November 9-13, 2020.
Highlights and support notes added for week of November 16-20, 2020:
Updates include:
Highlights and support notes added for week of November 30 - December 4, 2020:
Updates include:
Highlights and support notes added for week of December 7-11, 2020:
Updates include:
Highlights and support notes added for week of December 14-18, 2020:
Updates include:
Highlights and support notes added for week of January 4-8 2021:
Updates include:
Highlights and support notes added for week of January 11-15, 2021:
Updates include:
Highlights and support notes added for week of January 18-22, 2021:
Updates include:
Highlights and support notes added for week of January 25-29, 2021:
Updates include:
Highlights and support notes added for week of February 1-5, 2021:
Updates include:
Highlights and support notes added for week of February 8-12, 2021:
Updates include:
Highlights and support notes added for week of February 15-19, 2021:
Updates include:
Highlights and support notes added for week of February 22-26, 2021:
Updates include:
We've started working on our next quarterly release, which we've code-named Lunar Lander.
Follow the Lunar Lander Development Highlights & Support Notes page to receive updates throughout the quarter on all the fun and functionality we're working on!