Qualer Update Version 2.5
Go-Live Date: Sep 3, 2018
Access to Validation Site: Aug 20, 2018
Access to Preview: Aug 13, 2018
Announcement: July 31, 2018
A planned release will be made to the Qualer platform on September 3rd, 2018. This release will include various bug fixes, and added functionality to improve your overall experience with the Qualer system. A summary of the functionality included in this release, and an impact assessment for each feature is listed below:
| ID | Feature Description | Relevant Module(s) | Risk |
| 35292 | Extended uncertainty budgets | Service Administration, Fulfillment Interface, Service Manager | 03 - Medium |
| 35511 | Extended custom fields | Service Administration, Fulfillment Interface | 01 - Low |
| 35514 | Data only entry mode | Fulfillment Interface | 01 - Low |
| 35515 | Display key work order milestones | Service Manager | 01 - Low |
| 35519 | Additional measurement form options | Service Administration, Fulfillment Interface | 01 - Low |
| 35520 | Improvements to price lists and charges | Service Administration, Fulfillment Interface, Service Manager | 03 - Medium |
| 35521 | New service capability view | Service Administration | 01 - Low |
| 35523 | Tracking asset received date and acclimation time | Service Manager | 01 - Low |
| 35525 | Survey module improvements | Surveys Module | 01 - Low |
| 36167 | Asset Information Improvements | Fulfillment Interface | 01 - Low |
Overview of Qualer's Risk Assessment Procedure
Risk is defined as Low, Moderate, or High based on the criteria identified in the following table:
| Consequence | Likelihood Based on the Frequency of Use | |||
Low | Medium (credible/not likely) | High (credible/likely) | ||
| Low (Unregulated environment) | Low | Low or Medium | Medium | |
| Medium (Business operations) | Low or Medium | Medium | Medium or High | |
| High (IS0 9000/GxP environment) | Medium | Medium or High | High | |
Controls will be tested, as indicated:
| Risk | Level of Testing |
| Low | Significant controls and functions will be tested for correct function. Invalid inputs and/or usage will not be tested, but will be noted if found. |
| Medium | All controls and functions will be tested for correct function. Invalid inputs and/or usage will not be tested, but will be noted if found. |
| High | All controls and functions will be tested for correct function. Where possible, invalid inputs and/or invalid usage will be tested to verify appropriate failure conditions. |