Gavin.schultz at 02:58, 10 June 2016

2016-06-10T02:58:16Z

New page

{|class="wikitable"
|- valign="top"
!Bug/CR ID
!Customer Code
!Customer Reference
!Product(s) Modified
!Name
!Release Notes

|- valign="top"
|style="background:white;"|Bug#2291
|style="background:white;"|USPSI
|style="background:white;"|
|style="background:white;"|Construction Hive
|style="background:white;"|User registration fix for error "(user name) is already a member of (company)"
|style="background:white;"|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)".
|- valign="top"
|style="background:white smoke;"|Bug#4224
|style="background:white smoke;"|INTERNAL
|style="background:white smoke;"|
|style="background:white smoke;"|Construction Hive
|style="background:white smoke;"|Super-administrators - adding new users and controlling registration notifications
|style="background:white smoke;"|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.
|- valign="top"
|style="background:white;"|Bug#5568
|style="background:white;"|INTERNAL
|style="background:white;"|
|style="background:white;"|Construction Hive
|style="background:white;"|Publishing to two users with the same email address no longer causes publish errors
|style="background:white;"|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.
|- valign="top"
|style="background:white smoke;"|Bug#5726
|style="background:white smoke;"|INTERNAL
|style="background:white smoke;"|
|style="background:white smoke;"|Construction Hive
|style="background:white smoke;"|Exclusion operator in searching now works correctly when coupled with an inclusion term
|style="background:white smoke;"|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.
|- valign="top"
|style="background:white;"|Bug#5736
|style="background:white;"|INTERNAL
|style="background:white;"|
|style="background:white;"|Construction Hive
|style="background:white;"|More detailed publish response error messages
|style="background:white;"|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.
|- valign="top"
|style="background:white smoke;"|CR#1277
|style="background:white smoke;"|INTERNAL
|style="background:white smoke;"|
|style="background:white smoke;"|Construction Hive
|style="background:white smoke;"|Construction Hive Welcome Email
|style="background:white smoke;"|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.
|- valign="top"
|style="background:white;"|CR#1810
|style="background:white;"|INTERNAL
|style="background:white;"|
|style="background:white;"|Construction Hive
|style="background:white;"|Download link on documents in s3
|style="background:white;"|The Download link now causes a web browser to download a document that is stored on amazon s3 rather than opening it. 
 
Clicking the preview image will still open the document.
|- valign="top"
|style="background:white smoke;"|CR#2328
|style="background:white smoke;"|INTERNAL
|style="background:white smoke;"|
|style="background:white smoke;"|Construction Hive
|style="background:white smoke;"|Construction Hive password hash storage
|style="background:white smoke;"|Password hashes now stored in a more secure form.
|- valign="top"
|style="background:white;"|CR#2588
|style="background:white;"|INTERNAL
|style="background:white;"|
|style="background:white;"|Construction Hive
|style="background:white;"|Construction Hive Password Change Notification
|style="background:white;"|Users receive an email after their password is changed to notify them that their password has been changed.
|- valign="top"
|style="background:white smoke;"|CR#2589
|style="background:white smoke;"|INTERNAL
|style="background:white smoke;"|
|style="background:white smoke;"|Construction Hive
|style="background:white smoke;"|Verification for Adding Email Adresses and Merging Accounts.
|style="background:white smoke;"|The UI for merging accounts has been subsumed by the add email address functionality. 
 
Adding an email address or merging an account requires a token, sent to the email to be added / merged in (for adding this isn't really a change). 
 
Administrator accounts can not be merged into other accounts.
|- valign="top"
|style="background:white;"|CR#2590
|style="background:white;"|INTERNAL
|style="background:white;"|
|style="background:white;"|Construction Hive
|style="background:white;"|Construction Hive Tokens use random data
|style="background:white;"|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.
|- valign="top"
|style="background:white;"|CR#2608
|style="background:white;"|GLFUG
|style="background:white;"|
|style="background:white;"|Construction Hive
|style="background:white;"|User Memberships and Roles Management UI
|style="background:white;"|<div>
The interface for managing users and their roles and memberships has been overhauled.
</div>
 
The interface now shows (and enables editing of) either 
 - All users in one company (the old company roles page) 
   - Access via company management page -> 'User Roles' link. 
 - All companies (within your company group) for one user 
   - Access via company management page -> 'Company Members' link -> 'Edit Permissions' link. 
 
There are now three actions for user memberships: 
 - Add (only available on the single-user all-companies view). This grants a new membership with default roles in a company. 
 - Remove: This removes a user's membership from a single company, and can be used to completely remove them from an entire company group. As long as they are still members of another company in the same group, they will still have permission to view documents that were sent to them. 
 - Transfer: This removes a user's membership from a single company and adds it to another company, with the same set of roles as they had in the company they were moved from.
|- valign="top"
|style="background:white smoke;"|CR#2708
|style="background:white smoke;"|INTERNAL
|style="background:white smoke;"|
|style="background:white smoke;"|Construction Hive
|style="background:white smoke;"|Placeholder company for unregistered users
|style="background:white smoke;"|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. 
 
Instead, these users are now placed in a "holding" company, if there is no other information to determine which specific company to put them in. The holding company has limited permissions and does not contain any projects or documents. Users within a holding company generally only have the ability to access reports that they have published or received. 
 
Administrators can move users out of the holding company and into a more specific company at any time using the standard user management tools.
|- valign="top"
|style="background:white;"|CR#2929
|style="background:white;"|INTERNAL
|style="background:white;"|
|style="background:white;"|Construction Hive
|style="background:white;"|Files delivered to users direct from Amazon S3 where possible
|style="background:white;"|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.
|- valign="top"
|style="background:white smoke;"|CR#2986
|style="background:white smoke;"|INTERNAL
|style="background:white smoke;"|
|style="background:white smoke;"|Construction Hive
|style="background:white smoke;"|Home Page / Login Form
|style="background:white smoke;"|The home page no longer has the register interest form. 
 
A login form has been added to the page header while not logged in.
|- valign="top"
|style="background:white;"|CR#3031
|style="background:white;"|INTERNAL
|style="background:white;"|
|style="background:white;"|Construction Hive
|style="background:white;"|Construction Hive Email Headers
|style="background:white;"|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>. 
This change is being made bring Construction Hive up to speed with current best-practice use of these mail headers.
|- valign="top"
|style="background:white smoke;"|CR#3082
|style="background:white smoke;"|INTERNAL
|style="background:white smoke;"|
|style="background:white smoke;"|Construction Hive
|style="background:white smoke;"|Reset Password and Register Account pages now require not being logged in.
|style="background:white smoke;"|Reset password redirects to the home page if logged in. Register Account provides reasonable options.

|}

Construction Hive:Construction Hive 1.200 Release Notes - Revision history

Gavin.schultz at 02:58, 10 June 2016