If you want to view document history by clicking on it in tasks, you will only see history for that particular workflow. It would be great to see whole document history even if I want to watch it in tasks.

Please can you allow folders and lists to be controlled in the same way as normal searches - for example being able to remove the ability to edit without checking a document out first (currently, you have to remember to check it out and back in again when you upload a document to stop this) or allow the search to exclude files based on a field value such as retired documents.

Hello,

We have a problem when storing documents when documents are copied from filecabinet to basket and than stored.

Docuware stores index entries event if fields are not on Store dialog.
Prefiling with empty would clear unwanted index fields.

Best regards

Have the ability to create a List from multiple file cabinets

On on premice version, index profile can be defined with an SQL command allowing to write complex sql command
this option is disable on cloud version

I think will be great if in DocuWare cloud we could have the way to see the status of fulltext tasks, like how many documents are indexed and how many are missing for being indexed. Sometimes we have had to reset fulltext index for some file cabinets due to some problems with full text but we don't know when this process will finish and also we don't know if something will fail.

To be able to indicate in the filing cabinet a maximum size of document that can be archived, we would like to be able to control the size of the documents that are inside the filing cabinets.

There is no way tell what changes were made when an Index Entry has been edited (e.g. If someone modifies an Index Entry, the system only lets you know who modified entry, but it doesn't outline modifications that were made.)

If a select list is narrowed down to only one remaining option by the other field(s) that it's filtered by, we need an option to automatically select this item. Why do users need to perform 2 additional mouse clicks or several keystrokes to accomplish this?

Ability to have multiple content conditions for identifying and splitting documents with AND & OR operators.

Abitily to index fields in the document processing module, even if the store dialog chosen has them hidden. This works perfectly like this when indexing forms.

Have the ability to make validations and rules to a store dialog. It is important to prevent storing duplicated invoices for example.

The REQUIRED or not field is very basic validation. Forms already has field validation.

Ability to change the store dialog dynamically based on the fields. For example the document type. Forms already has some dynamic fields based on others, and is very helpful. This would reduce the need to have many different store dialogs for each type of document.

Abitily to have a Result Dialog or another, BASED ON RULES. This would display the necessary metadata for different document types. Contracts, Invoices...

Abitily to ASSIGN a specific result list to a LIST DIALOG to show the results instead of customizing every single time

You should allow the selection of dialogs and profiles when creating a new field. The field being only assigned to the standard dialogs it's not enough when costumers have 30+ profiles, 30+ dialogs and 50+ tasklists.
Thank you.

Currently, when you change the name of a database field, the dialogs all keep the old field name as a "Label". This forces me to go into every dialog (including result list and index dialogs) and erase the label so that it matches the new field name.

When I'm changing a database field name, it is because a customer wants the field name to change everywhere.

I set a multicolumn select list to a field and added a filter to another field that has a fixed value.
it would be nice if, hiding the fixed field, the filter continued to work.

Debería existir un método de migración de Archivos .XML de los Archivadores masivo, es decir, permitir seleccionar archivos específicos o todos y exportarlos, creando un archivo .XML para su importación posterior.

También un método de importación masivo, permitiendo que se creen más de un Archivador de forma simultánea.