We could reproduce the problem described by Thilo Meier. That's of course not the intended behavior of the cascading select lists.

We will fix the issue asap and roll it out using our standard procedures. We are sorry for any inconvenience caused by this.

For more details, please contact our Support Department.

And since completion with an error which makes it kind of useless.

Following example: (Used from the "Client(Deutsch)")
We have a HR table with the following fields: "first name" and "last name"
DocuWare Storage mask with fields: "first name" and "last name"

HR table contains the following data:
First name/ last name
Max / Muster
Thilo / Meier

In the storage mask you now fill the first name with "Max".
The DocuWare select list proposes "Muster" like expected and correct.
But if you now type manually "Meier" into the "last name" field DocuWare accepts this values while storing.

So it is still possible to enter "wrong" data like in this example "Thilo Muster".

I needed this feature to make some simple validation of the data which is entrered.
Because of this error the feature failed my expectations completly.

PS: DocuWare is aware of this error since 6.9 and in 6.10 this is still not fixed...

Possible with 6.9
http://help.docuware.com/en/#b57860t62404n68975

Any update? Even any activity regarding cascading fields and linked drop downs sourced by external data lists / SQL?

I think that the communication and release planning by Docuware regarding this high voted issue is not really understandable for the involved audience. :S

...but I do not give up hope that someone at Docuware will recognize this sooner or later and that they will change the priority of this. The mentioned issue is so important and so common in other ECM solutions that - this is well known - in some cases potential contracts and customers were lost to other competitors when this came up... :(

Sad story at all as we see that there is still not any progress to be communicated although this issue is urgently needed, highly voted and asked since 2014 (minimum! ).

As Thilo Meier (ALOS AG) already said:

"This feature is so common-place that users expect it in DW and are surprised that it's not there."

In case you are working on it. Please keep in mind to implement kind of "database variables". We are using a CRM system with the feasability to access the tables directly. There we are looking at a first step for the company name and for the ID.
Means: We use two fields in docuware: one for company name, one for ID. Both are filled via SQL statement. To find the right ID, a variable is needed.

Updates? We really need this.

Any updates regarding this feature request?
It is now ranked highest in Client (English) and Client (Deutsch)

I am sorry to contradict you but this functionality was never available as discussed here. It was and still is however possible to get a similar behavior as described below by Mr. Hartmann.

This was a feature that worked in 6.0 and is now not available in 6.6.

Selective select lists are still available through activating the "Filtering" checkbox in the according dropdowns. What is not yet possible and what this idea is about is to pre-define cascading drop-down entries without having documents with this index information already stored in DocuWare.

This used to be an option where you right click in a field and it would bring up "Select Selective List." I would like to see this feature reinstalled. It's is easier and quicker this way v. the way it is now. Now, I have to scroll down my options, which include ALL categories!

The problem is, that if the entrys are not allready in DocuWare you have to make some AutoIndex Jobs just to create the dummy data in the archive... Also if the document and sub types change the storage dialouge will always show the old data because there are still documents with the old index entries.
And since the user still can chose the wrong index entry out of the select list (if you have no validation) this could "pollute" your index data.
I am very glad that DocuWare considers implementing this feature

You can already achieve this by implementing a custom validation. Just create a database table with two columns: column one contains your document types and column two the corresponding sub types. Than you have to check in your validation if there is a row with the combination. If not simply deny storing the document.

This, however, doesn't solve the problem that a user sees all entries in a select list.

"This feature is so common-place that users expect it in DW and are surprised that it's not there."
I think that as well, this feature would greatly enhance the usability of DocuWare when it comes down to manually storing documents with Connect-to-Outlook or the Windows Explorer Client or the normal storage dialogue.
I guess an extended select list would help to solve this problem.
If it would be possible to use variables like already filled fields in the storage dialogue, the logged on user or the current date you could use this variables to filter the select list of a field on external data.
And if the select list would only return one value it fills this value already in the field.
That would not only help the user to manually store documents more structured but also fill in needed fields faster.
For example if the company name is already selected you could use this filled in value to fill in the company number which comes out of an external data base.
If you open the storage dialogue, the select list behind the field “department” looks up the logged in user and fill in his department. (SQL Example for select list: “SELECT department FROM tableUserDeparement WHERE User = CURRENTUSERLONGNAME()” ).
If the user is in more than one department he would get a select list the departments he is in.
Afterwards the user would be just able to store documents of a special document type because the department he is working in is just allowed to store certain document types. (SQL Example for select list: “SELECT documentType FROM departmentDocuments WHERE department = DWFIELD_DEPARTEMENT” )
And it goes even further, if he selects one document type you could say that this document gets automatically the status "NEW" or something and triggers a workflow...
Together with the already existing feature that a user is just allowed to store entries out of a select list this would greatly help to ensure the user enters exactly the data he is allowed to enter.
Also the filling in of storage dialogues would go faster because of the automated filling of index fields.
This looks like a very nice feature and I look forward if this will get implemented!