Patch Notes
| App version | Change/Issue description | Supported Planon version | Comments |
|---|---|---|---|
| 1.11.0 | Delete Mobiess Inspection on cancelling order | L100 and higher | When an order is cancelled in Planon, the corresponding inspection in Mobiess will be deleted. A new setting orderCancelStates is introduced to configure cancel status based on order type. |
| 1.11.0 | Change in Reassigning of Oder | L100 and higher | Previously if an order is reassigned in Planon, the owner of the corresponding inspection in Mobiess is changed. From now, the existing inspection is deleted, and a new inspection is created. |
| 1.12.0 | Handle Data Driven questions as Planon questions | L100 and higher | Previously all Mobiess questions of type Data driven are skipped and considered as fields on Assessment BO only if code matches with Planon system name. From now, these data driven questions are also created as Planon questions if Mobiess question code is empty or doesn’t match with any of the fields on the Assessment BO. |
| 1.12.0 | Issue while update PPM Orders | L100 and higher | An errors “FieldNotFound” occurs while updating a PPM Order if none of the corresponding maintenance activities have Assessment Definition. This is now fixed |
| 1.13.0 | Handling Hidden questions | L105 and higher | Along with the existing conditions, now a new setting prefixToSkipHiddenQuestions is introduced to decide if hidden question needs to be created in Planon. Under following conditions hidden questions are created: 1. Question Code is empty 2. Question Code doesn’t match with any of the system name of Assessment BO Fields 3. prefixToSkipHiddenQuestions is empty 4. Question code doesn’t start with value of the setting prefixToSkipHiddenQuestions |
| 1.13.0 | Handle multiple scorings of same topic for an observation | L105 and higher | Previously all scorings are created in Planon but Planon restricts one score per topic for an observation. Now similar logic is implemented in the connector. Only the latest score per topic based on the index from Mobiess is created. |
| 1.13.1 | Fix bug in error handling in case of failed status transitions for orders and maintenance activities | L105 and higher | We have identified a bug in the error handling part for failed status transitions of orders and maintenance activities. This is now fixed. |
| 1.14.0 | Improvements in Answer Line Observation feature | L109 and higher | Now Assessment Answer is filled on the Observation based on the question code of the corresponding answer. If no question found in Planon, existing way is used |
| 1.14.0 | Fix issue with empty log message in Log viewer | L109 and higher | Error message on Log viewer is empty in some cases. This is now handled |
| 1.15.0 | UI Improvements | L110 and higher | When Link action is selected, it now shows the current selected template. Add filtering options on Description & Date |
| 1.15.1 | Trim string fields based on field length instead always trimming to 250 characters | L110 and higher | Previously all the answers for Strings fields are trimmed to 250 characters on Communication logs, Observations, Follow-up Actions and Scoring Bos. This is now changed, and trim is done based on field length. |
| 1.16.0 | Add feature of relinking the definition | L111 and higher | Now users will be given an option to relink the already linked template to the selected Assessment Definition |
| 1.16.1 | Keep App Inactive after a restart in non-prod environment | L113 and Higher | Previously app was always activated after a restart or copy down of a non-prod environment, now the app will remain inactive. |
| 1.17.0 | Add feature to fetch missing answers | L126 and higher | Now users can use the new feature to fetch the missing answers for the assessments |
| 1.18.0 | Extend fetch missing feature with observations and its details | L126 and higher | The feature introduced in 1.17.0 is now extended to fetch observations, scores, follow up actions and comlogs |
| 1.18.1 | Fix issue with creating property observations | L129 and higher | There is technical issue which caused problem with creating property observation using the Fetch Missing answers feature. |
| 1.18.2 | Handle changes in question config from Mobiess | L129 and higher | With new Mobiess setup, there are some changes in the way question configuration is returned. This is leading to some issues during the synchronization of assessments. Changes are made in the app such it works independant of changes in the configuration |
| 1.18.3 | Fix issue in handling lookup questions from Mobiess | L129 and higher | Fix issue with validation of question if it based on lookup table in Mobiess which led to synchronization issues |
| 1.18.4 | Fix issue in handling Multiselect questions from Mobiess | L129 and higher | Fix issue with sync of multi select questions |