What's new

No changes in this release.

No changes in this release.

No changes in this release.

Only selectable and available case groups shown at case creation

When you create cases in WorkZone for Office, you will only be able to see and select case groups that have been made selectable and available for case creation. Case groups that are set up as non-selectable or not available for case creation in WorkZone Configurator will not appear in the Case Group field. See Create a new case.

No changes in this release.

No changes in this release.

No changes in this release.

No changes in this release.

No changes in this release.

No changes in this release.

No changes in this release.

• You can save emails with a digital signature to WorkZone.

WorkZone for Office supports OAuth2 authentication.

• WorkZone Meeting functionality has been deprecated from WorkZone for Office. We have released this functionality as part of our new WorkZone 365 add-in. For more detailed information, see User Guide.
• Export to Microsoft Excel from WorkZone Client is excluded from WorkZone for Officeand, thereby, export no longer depend on the add-in. If you have some files previously exported to Excel, you still needWorkZone for Office to refresh them. See Refresh an exported list from Excel.

No changes in this release.

• The Process overview has been improved. Now you can see all lists on processes in a way they look in WorkZone Client. To do this, click Process Views. For more detailed information, see the WorkZone Process User Guide.
Note: If you used any process lists/folders in the previous version of WorkZone for Office, they will be preserved and will work together with the new process overview.



• A description of how to detect Captia content controls and replace them with the WorkZone content controls is added. See Replace Captia content controls.

• In Outlook, when you save multiple emails on a case, you can now specify the needed classification value for them.
• To start a process from an archived or locked document, you must save the document on case.
• The behavior of starting a process from a document has been enhanced. Now if you start a process from a document that contains unsaved changes, the changes will be saved automatically.
• New fields are available for merging: 
  • Custom fields on case contacts
  • Custom fields on document contacts

  

No changes in this release.

• When creating a new case, you must now select a case category. Case Category is a new mandatory field for the New case dialog, and it aims to ensure improved classification of cases.

• WorkZone for Office now supports multiple databases. It brings a number of benefits such as workload distribution among several databases and possibility to open and view documents from a historical database.
• WorkZone Meeting is now a part of WorkZone for Office documentation. See sections WorkZone Meeting to create new WorkZone meetings, manage agenda items, and generate meeting reports.

• WorkZone's document control has been replaced with Microsoft Office’s document management and co-authoring functionality to manage multiple users editing a document at the same time. Users can now select to work on the same Microsoft Office document (Word, Excel, or PowerPoint) concurrently and merge their changes back into the document.

  The office document is still locked by the first user who opens the document, but when the first user saves and closes the document, the document lock is passed on to the next user who can then save and merge any changes to the document.

  There are no check in/check out procedures and you cannot take over another user's document.

  Users can still select to work on a local copy of the document and either manually merge changes or upload their edited document as a new document.

  For more information, see Document co-authoring.

• Starting with this release, you can open Office documents with the registration pane via WorkZone Explorer and edit Title, Case Handler, and other meta data fields there.

No changes in this release.

EU GDPR requirements

GDPR (General Data Protection Regulation) is the primary law on personal data protection in EU. It unifies data protection, so that each EU member state no longer needs to write its own laws concerning data security. GDPR becomes effective on May 25, 2018.

With this release, WorkZone introduces the following functionality to meet the GDPR requirements:

• Document classification orders and prioritizes data based on its sensitivity. For example, some documents can be available to everybody, while others might contain information that cannot be shared with a wide audience. Starting with this release, document classification code is a required field for each document and it defines its sensitivity level. You can specify the classification code during document registration.
  Note: Documents created in WorkZone for Office 2017 and earlier versions are not classified automatically. You can apply classification codes to them manually.

Other features

• Repeating content controls. You can now create templates that contain repeating sections. Each case or document can have multiple parties with a specific role, for example, Sender or Recipient. If you want to extract information from multiple parties and insert it into a content control, you must use a repeating content control.

• Merge of specific content controls has been adjusted: if you merge contact’s address information, which is protected, the address information will not be inserted into the document.

User interface improvements

• Improved navigation between older and newer versions for Word, Excel, and PowerPoint documents.
• Some fields have been renamed to be compliant with WorkZone Client. Class has been renamed Case group; Sub.No has been renamed Child case group.

• You can search for a party among recent, favorite, and all contacts in the Add/Remove Parties dialog.
• The WorkZone Process add-in has been merged with the WorkZone for Office add-in. If WorkZone Process is not installed on the server, the Process button is disabled.
• You can start a process from a document.
• You can insert content controls for custom fields into templates.