Your InVision experience is improving as we work to squash bugs and release new features. Here’s an account of the improvements you’ll find in the latest releases.
What's fixed or improved?
These issues were fixed or improved in InVision Cloud during August:
Sample projects: After clicking the pink + icon to create a new project, if you then opt to open a sample project instead, you may notice the updated copy and design on the Sample Project page.
Studio sharing: When sharing a Studio prototype via InVision Cloud, members of Enterprise teams now have two sharing options in the prototype Share module:
Private link: Allow anyone with the link to view, comment, and inspect the prototype.
Public link: Restrict the share link recipient's access to viewing the prototype.
Let's sort this out, team: On the Teams tab (after clicking People in the main navigation), Enterprise teams are now sorted alphabetically.
Step right in: Enterprise account owners who are not already collaborating on a prototype can now accept requests to join the team and prototype, as expected.
Loading screen improvements: When accessing InVision Cloud, you should now see an updated loading screen while everything loads.
There was one new release for Craft Manager (1.0.86) and one new release for Craft Data (1.0.39) last month—both released on August 27th.
Remember, Craft Manager is a separate tool that you use to manage the Craft plugin suite; therefore, the version number is different than what you see when clicking Manage plugins in the Sketch Plugins menu.
Light the way: To reduce any potential confusion their team members may have when signing in to Craft, Enterprise account admins can now configure Craft Manager to start on the Sign in using your team domain screen rather than the screen with the Email address and Password fields.
There were two big bug fixes during August:
One of a kind: When duplicating a layer with text content populated from Craft Data, each new layer should now be unique, as expected. Previously, duplicating such layers would also assign the original layer's value to the duplicate.
Do you validate?: Now you won't encounter the "Invalid Inspect JSON" error, which was caused by a bug that had been preventing Craft Sync from uploading all the data needed for Inspect on InVision Cloud.
Design System Manager (DSM)
This new feature was released in the DSM Web view during August:
Flip the switch: To help avoid the confusion mismatched versioning causes, developers can now use Live Components version switching when viewing component pages in the DSM Web view. The new feature lets developers easily match any version of a component's documentation with the version used in the current code.
In addition to numerous platform stability and security improvements, the following security measure was taken during August:
TLS Upgrade: To align with current industry best practices for Transport Layer Security (TLS), InVision has disabled TLS 1.1 and enabled TLS 1.3. We currently support TLS 1.2 and 1.3.
InVision Cloud V7
The following release notes apply to InVision Cloud V7 only; these do not apply to InVision V6.
What's new in Cloud V7?
The following new feature—a notice-able improvement, wink wink—was released in InVision Cloud V7 during August:
Put on notice: If you mention one or more people in a comment (using the @ key followed by their name), they will receive a notification email to ensure they see the comment.
You can mention yourself in a comment to receive a notification email.
You can also edit an existing comment to mention someone, and they will receive a notification email.
What's fixed in Cloud V7?
These issue were addressed in InVision Cloud V7 during August:
Improved commenting experience: In addition to the new commenting features described above, you may notice the UX improvements when leaving a comment on a document.
Message received: You should now receive email notifications as expected when others leave comments on documents, whether or not you were mentioned in the comment. Previously, an issue was preventing the notification emails from being sent unless the intended recipient was explicitly mentioned in a comment.