Configurable DHR compilation:

Using the Administration è Archiving menu item, you can now create an individual compilation of content for archiving DHRs. Checkboxes can be used to activate the table of contents, documents, anomalies, forms, the form audit trail, and the status history.

In addition, it is possible to select which types of forms and anomalies should be archived.

All of the above options are also available in the cockpit when you click the Print button to generate a PDF of the current batch.

Improved tablet camera functionality:

An improved functionality is now available for all customers who want to use the tablet or laptop camera function via https://. The previously difficult task of focusing a barcode with the camera has been noticeably simplified.

Customers who still access the browser via http:// can contact our customer service to convert to https:// with the necessary SSL certificates.

Adding Forms:

Under the menu item Administration è Process Management, DOQ now offers two different options for adding additional forms to the documentation process. This can be configured globally or for individual items. One option is the Additional Forms configuration. After the form has been assigned the appropriate time recording and approved, it is available to the user via a button in the cockpit and can be added to the process.

A second option for adding forms is the form field action configuration. Triggers for adding forms are either defined form field contents or Java script-based actions during machine data imports. Anomalies can also be automatically linked to this action.

As a practical example, it is conceivable that when a scrap value greater than zero is entered, a form is included in the documentation in which more detailed information about the reason for the scrap must be entered. For example, if a component test fails, a new form could provide the user with an alternative workflow for replacing an assembly.

Extended maintenance functions:

In maintenance administration, email notifications can now be stored for the various maintenance types, either internally or to external companies. It is possible to send emails at a defined time before maintenance begins or at the time of the upcoming maintenance (or both).

It is also possible to attach documents to a maintenance task as mandatory or optional documents. Photos taken with the tablet camera can also be added to a maintenance task.

Notes on approval procedures:

In the cockpit, the user can now use the Change Status button at any time to find out which conditions still need to be met before a status change of the batch/order is possible. If different status states exist as the desired target status, this can be preset. Information such as forms not completed, mandatory documents not uploaded, inspection not performed, or time recording not completed is displayed.

Other improvements:

There are several other improvements in DOQ 3.8. Photos of anomalies can now be uploaded from files, configuration lists can be copied, and form contents can be printed. The batch overview has been improved in performance, and customer-specific buttons can now be implemented in the form view with significantly less effort.

You are welcome to request the current release notes for DOQ 3.8 as an official document to view all changes.