Previously, route instances that were created by an administrator or a user in Rounds Pro Mobile were removed when you previewed a route master. This issue has been resolved. | 1018162 |
Previously, when you migrated Steps that have Conditional Steps using the Migration Tool, then the values did not get displayed in the Assets, Operator, Conditions fields. This issue has been resolved. Now, the values in the specified fields are loaded successfully and appear correctly. | 996684 |
Previously, the Migration Tool migrated a Lubrication Step to Global site, even though the Legacy Lubrication Requirement belonged to an actual site. This issue has been resolved. Now, the Lubrication Step will have the same site as the Legacy Lubrication Requirement. | 974099 |
Previously, the Next Date field on the Route Master grid is not populated, even though the Route Master has a schedule. This issue has been resolved. Now, the Next Date field gets populated based on the Schedule defined in the Route Master. | 956794 |
Previously, when you attempted to print a Route Instance, an error occurred if the Route Instance was created from a Schedule. This issue has been resolved. | 949743 |
Previously, when you selected the Manage picklist option in Rounds Designer page, a 502 bad gateway error appeared and the picklists were not loaded. This issue has been resolved. Now, the picklists are displayed without any error. | 949740 |
Previously, the Migration Tool job status remained at In Progress. This issue has been resolved. | 945119 |
Previously, the Migration Tool created duplicate Readings if you selected the Readings option and ran the tool again for the same route. This issue has been resolved, | 945119 |
Previously, if the Migration Tool was run for steps that had a schedule type set to selected days of a month, the migration failed for those steps. This issue has been resolved. Now, the Migration Tool will migrate those steps also. | 916936 |
Previously, the Route Master Grid displayed duplicate records when you set Rows per page to 100 or more. This issue has been resolved. Now, the Route Master Grid no longer shows duplicate records regardless of the Rows per page setting. | 875879 |
Previously, the Step Reading Data Loader returned an Asset not found error even when valid asset information was provided. This issue has been resolved. Now, the Step Reading Data Loader accepts Step Name, Asset, and CMMS System data to uniquely identify the step and associate a reading. | 720225 |
Previously, the Step Readings Data Loader returned a Step not found error occasionally. This issue has been resolved. Now, the Step Readings Data Loader will use the Asset ID instead of ENTITY ID. | 720225 |