Construction Hive:Construction Hive 1.200 Release Notes
| Bug/CR ID | Customer Code | Customer Reference | Product(s) Modified | Name | Release Notes |
|---|---|---|---|---|---|
| Bug#2291 | USPSI | Construction Hive | User registration fix for error "(user name) is already a member of (company)" | When an unregistered user is a member of at least 2 subsidiaries in the same company hierarchy, and then the user attempts to register, selecting the second laboratory of which they are already a member no longer gives the error message "(user name) is already a member of (company)". | |
| Bug#4224 | INTERNAL | Construction Hive | Super-administrators - adding new users and controlling registration notifications | Super-administrators can add a user to a company without triggering the generation of an email. The super-administrator does, upon adding the user, have access to a registration link for the user. The super-administrator can also use the "Send Invitation Email" link to send an email to the user. | |
| Bug#5568 | INTERNAL | Construction Hive | Publishing to two users with the same email address no longer causes publish errors | Occasionally, reports published from QESTLab will create a publish package containing two <user> elements referring to the same email address, which would result in the error message: An unexpected error occurred during the import: could not execute batch command.[SQL: SQL not available]". This case will no longer generate an error. | |
| Bug#5726 | INTERNAL | Construction Hive | Exclusion operator in searching now works correctly when coupled with an inclusion term | It is now possible to search for reports which specifically one term but not another e.g. term1 -term2 will find all reports containing the word "term1" but not "term2". This does not currently work with standalone excluded words e.g. -term1, it must always be used in conjunction with another word. | |
| Bug#5736 | INTERNAL | Construction Hive | More detailed publish response error messages | Publish Responses for xml imports now include a "violation" at info level that specifies which Construction Hive service was being used - request Host or System Hostname, and the machine name - to better assist with support requests. Responses for publishing that failed because of a mismatch with a recent transaction now include the ID of the conflicting transaction. | |
| CR#1277 | INTERNAL | Construction Hive | Construction Hive Welcome Email | An email is sent to new users after registering. Apart from being a friendly gesture, this is additionally useful as a security feature, as there are occasions in which users forward their report notifications to others by email, and the recipients of those emails then register the original user. This email would alert the user that someone has registered using their email address. | |
| CR#1810 | INTERNAL | Construction Hive | Download link on documents in s3 | The Download link now causes a web browser to download a document that is stored on amazon s3 rather than opening it.
| |
| CR#2328 | INTERNAL | Construction Hive | Construction Hive password hash storage | Password hashes now stored in a more secure form. | |
| CR#2588 | INTERNAL | Construction Hive | Construction Hive Password Change Notification | Users receive an email after their password is changed to notify them that their password has been changed. | |
| CR#2589 | INTERNAL | Construction Hive | Verification for Adding Email Adresses and Merging Accounts. | The UI for merging accounts has been subsumed by the add email address functionality.
| |
| CR#2590 | INTERNAL | Construction Hive | Construction Hive Tokens use random data | To improve security, access tokens now contain no encrypted information. This ensures it is not possible to determine information about an access token without access to the Construction Hive database. | |
| CR#2608 | GLFUG | Construction Hive | User Memberships and Roles Management UI | The interface for managing users and their roles and memberships has been overhauled.
| |
| CR#2708 | INTERNAL | Construction Hive | Placeholder company for unregistered users | When publishing a report to Construction Hive, the users included in the report (typically as recipients) sometimes need to be created in a company hierarchy due to the domain name of their email address e.g. user1@cmtesting.com needs to be added to the CM Testing company. Previously, these users were added to the root company. This was not the most logically correct place for them, as they could see project names and, if granted a role without moving the user, would have all the permissions of that role at all companies in the heirarchy.
| |
| CR#2929 | INTERNAL | Construction Hive | Files delivered to users direct from Amazon S3 where possible | Unless we want to use the file data, it is never retrieved from the database when available on s3 and the browser is provided with a url / redirect for s3. | |
| CR#2986 | INTERNAL | Construction Hive | Home Page / Login Form | The home page no longer has the register interest form.
| |
| CR#3031 | INTERNAL | Construction Hive | Construction Hive Email Headers | Emails sent from Construction Hive no longer use the Sender header to indicate which Construction Hive user distributed a document. Instead, when listing a Construction Hive user, the From header will be set to "[Name] via Construction Hive" <member@constructionhive.com>. | |
| CR#3082 | INTERNAL | Construction Hive | Reset Password and Register Account pages now require not being logged in. | Reset password redirects to the home page if logged in. Register Account provides reasonable options. |