Construction Hive:Construction Hive 1.500.977.0 Release Notes

Bug/CR ID	Customer Code	Customer Reference	Product(s) Modified	Name	Release Notes
Bug#6251	INTERNAL		QESTLab, Construction Hive	Publishing error to Construction Hive: "An invalid character was found in text content"	When publishing reports from QESTLab to Construction Hive, occasional errors have occurred with an error message such as: "AddMetadataFromField: An invalid character was found in text content". While the specific cause of this is unknown, a fix has been applied which will: (a) provide an error message which better identifies the field which caused the issue, and (b) only flag the issue as a warning rather than an error, such that an attempt will be made to publish the report even without the supplied metadata.
CR#3618	USTWI		Construction Hive, QESTLab	Include field technicians on report distributions to Construction Hive	Field technicians may now be added automatically to the distribution list of reports published to Hive. This allows field technicians to access reports even when they may not have been added by the user to the report distribution. The option to control this is available in the QEST Admin Console, Construction Hive > Options: Include field technician in distributions Note that the field technician email will not be visible in the publishing window, but rest assured that it will be included in the generated publish package. In addition, reports published to Construction Hive previously required that all users related to the work order, samples and tests on a report have a company email address (i.e. with the company domain). This has been problematic for cases where such users either do not have an email address, or often in the case of field technicians, they are subcontractors or part-time employees who instead use a personal email address. To alleviate this, additional options have been added which will allow reports to be published without the details of these secondary users - specifically, the tested by, checked by and report signatory users. Two new options have been added to control this: Exclude signed by users Exclude tested by / checked by users These options are pertinent to field technicians insofar as those people may have been not only field technicians but also have been specified as the tester or checker on a test.