autocomplete a field based on another field
autocomplete a field based on another field
when storing in storage dialog box, to add a field, automatically extract the value of a second field from a table or list selection
Example identification number autocomplete the name of a person
Your idea has been added to our backlog. We are now further investigating the idea.
-
Chris McFarland commented
I see what you're describing in Forms, but not for a store dialog. I have a lot of processes where there will be one single row of data matching on the first field that we'll populate. What I'm seeing is that in a store dialog there is no automatic population at all. The ticket refers to store dialog specifically, and for me that's where I'd most like to see it. If you're seeing any kind of automatic population in a store dialog then I'm interested. Maybe there is a way.
-
Jeff commented
This functionality does now work, however, if you go back and change a selection that it's using to filter, it does not update the subsequent fields. So, if column A and column B produce a result in column C, this works the first time. If I go back and change the combination of column A and column B, then column C does not automatically adjust to account for this change. A user filling the form would need to know to manually clear out the field being populated by column C and adjust column A and/or column B to get the field for column C to update with the correct information.
This is not intuitive for users not familiar with filling out DocuWare forms, and would likely view this as a bug.
Any field that is being populated based on filtering previous field(s) should automatically update if the fields being used for the filter are updated.
-
Jon Weston commented
To add to Mark Smith's comment (from 5 years ago), this behaviour is almost universally expected among the userbase now so it's seen as a deficiency when they see that DocuWare can't do it. This is the feedback I've received repeatedly from clients over the past few years and heard it again today while doing training on a project that's about to go live.
-
Jon Weston commented
or allow it to trigger a single run of an AutoIndex job for just that one document. This would leverage the power of AutoIndex without the horrible inefficiency of having it run every 10 seconds to update any incoming documents.
-
Mark Smith commented
When an index field is filled in to the point where there is only a single candidate in the corresponding select list, the remaining text should be automatically filled in (auto-completed). This is a very intuitively - obvious basic standard development practice/implementation used in most applications, including Oracle Capture, which our main scan operator has used for many years. However Capture implements the DocuWare toolkit, which is no longer available after version 6.7. So I’m trying to get her to switch over to the DocuWare web client. But having to do the additional steps of going into the select list really “trips up” her “rhythm” when indexing/storing the large number of documents that she processes daily.
When the time comes that we upgrade DocuWare past version 6.7 (Oracle Capture goes away), I don’t believe that she will be willing to use it unless the auto-complete functionality is implemented into the DocuWare web client. At that point we may be compelled to switch to another product, such as Laserfiche.