In this article, you'll find a list of our most impactful new features and enhancements that we have released this month.

Don't worry, for more significant enhancements, you can still check out our blog, as well as read our newsletter. If you have questions about these items, don't hesitate to contact our support team.

Monitor display settings are nearly impossible to standardize, which means pixel-perfect color matching for printed materials in digital review environments was extremely difficult—until this week’s release. With Ziflow’s Color Separations, you can be sure that what you see on your screen is what you'll get in print.

Simply open the menu in Ziflow’s Proof Viewer to get a more accurate view of the specific CMYK and Pantone colors being utilized within the asset. Whether you're creating assets for packaging, outdoor media, brochures, or any other physical material, Color Separations makes color comparison in your proof review process much more precise, so you can ensure that your final designs look their best when printed.

This feature is available today for PDF file types, with more formats (INDDs, PSDs, etc) to be added in future releases.

Administrators and managers can now export their full list of Ziflow users and guests to a CSV file for easy analysis of contact records. The “People'' tab within Ziflow’s dashboard has been updated to include an “Export” button. Either view your portal’s entire set of users (“All contacts”) or filter values using preset or custom settings, then click the button to prompt an export and download flow.

The resultant spreadsheet will include the following fields: “Name,” “Company,” “Group,” “Email Address,” “Role,” and their User Status (“Active/Inactive”), with additional fields to be added to the exported CSV in upcoming releases.

We’ve added a new setting to the “Create Proof” Zibot that enables an Intake Form to respect any settings that have been updated once a new version is added. Admins can toggle this switch to have the proof behave according to the settings and reviewers of the previous version, or leave it untoggled to have new versions use the Zibot proof settings every time.

Here’s an example: a proof that was created with version 1 has since had adjustments made to its settings—folder delivery, reviewers added into the workflow, notification settings, et cetera. With this Zibot setting enabled, any subsequent version uploaded to that proof via an Intake Form will use these updated settings, instead of the settings provided by the Zibot.