Fourth Quarter of 2021
Release Date: December 17, 2021
This topic provides a list of product changes released for this module on this date.
| Description | Tracking ID |
|---|---|
|
When you schedule a route to end after a specific time, you are unable to save the route if you have set up the schedule with some occurrences in the past. You must set up the schedule so that all new scheduled occurrences are created in the future. | DE172400 |
| When you attempt to filter the Assigned To column data in the Open Instances, or the Instance History pages, an error occurs if you are a secure user. | DE172186 |
| Currently, you cannot use picklists that contain special characters in their name on steps and steps templates. To work around this issue, you must modify the picklist name to exclude the special character. | DE172183 |
| When you attempt to re-sequence steps within a route, the performance may degrade when you move steps when there are more than 200 steps under a given asset node on the route. Though the re-sequencing action does not fail, the action does not complete within optimal performance expectations. | DE172180 |
| When you delete a route master, the confirmation message that the delete was successful does not appear and the deleted route master still appears in the list of route masters. Close the Route Details page and refresh the list of route masters, to verify that the route master has been successfully deleted. | DE172179 |
| When you copy and rename a step with associated conditional steps, the mappings on the conditions records are not retained. | DE172127 |
| If you are not operating the mobile device on a reliably fast network, you may encounter delays and errors. In this case, move to a better network and use the mobile device. Code and network optimizations are continuing to be worked and will be delivered in future patches. | DE172059 |
| In the Rounds Designer page, if you add a nested Conditional Step to a Step that is already specified as a Conditional Step on a Primary Step, then the nested Conditional Step will not be available when the Primary Step is included on a Route. | DE171733 |
| In the Rounds Designer page, if you add a step that contains a hashtag (#) in the name, an error message appears indicating that the Asset Key is not passed in the request. Close the error message window and save the step. | DE171246 |
| Site functionality is not fully supported within Rounds Pro. Steps inherit the site for the Asset or FLOC that they are created under. If you do not have access to the assets due to a site access restriction, then any instances that you create from the web or from the mobile application will not contain those steps that exist under the specific assets. If you have a broader site access and create the instance, the steps will be part of the instance and all users will be able to see and update those steps in the Rounds Pro mobile app. | DE170565 |
| When you attempt to create a Health Indicator using the Generate Health Indicators section while creating a step, the health indicator creation may fail, and an error message appears indicating that the action has failed. In this case, you need to create a new step. | DE170265 |
When you modify a step template to use a new picklist and picklist values, the save button ( ) does not get enabled with the changes. A work around for this issue is to modify the step description also to enable the save button (). | DE168473 |
| You cannot add a primary step as a condition to itself in the first level. However, you can add the primary step as a condition at the second or later levels. | DE158339 |