Jeff
My feedback
59 results found
-
16 votes
Your idea has been added to our backlog. We are now further investigating the idea.
An error occurred while saving the comment Jeff
supported this idea
·
-
45 votes
Thank you for your idea. We added it to our collection of ideas and features and will further investigate it. We currently cannot say exactly when this idea will be implemented. As soon as we have more information we will update its status.
Jeff
supported this idea
·
-
35 votes
Your idea has been added to our backlog. We are now further investigating the idea.
An error occurred while saving the comment 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.
Jeff
supported this idea
·
-
36 votes
Your idea has been added to our backlog. We are now further investigating the idea.
Jeff
supported this idea
·
-
36 votes
Thank you for your idea. Right now we are focusing on other topics, so we are not considering this idea for future releases. If the demand for this topic increases, we might add it to future plans.
Jeff
supported this idea
·
-
66 votes
Your idea has been added to our backlog. We are now further investigating the idea.
Jeff
supported this idea
·
-
69 votes
Thank you for your idea. We added it to our collection of ideas and features and will further investigate it. We currently cannot say exactly when this idea will be implemented. As soon as we have more information we will update its status.
Jeff
supported this idea
·
-
Restore the ability to drag and drop documents and unstapled pages to reorder them in the web basket
143 votesThank you for your idea.
Right now we are focusing on other topics, so we are not considering this idea for future releases. If the demand for this topic increases, we might add it to future plans.Jeff
supported this idea
·
-
184 votes
Of course the security of our users is important to us.
As you have noticed, this idea still has the same status, but was not declined. That means we evaluate it regularly.One reason why we have decided not to add this security feature yet is that we will first change the authentication flow.
As a first step, we introduced the Identity Service in the DocuWare Cloud with Version 7.3, which allows integration with Azure AD and the use of MFA there.
The next step is to force users to use SSO only. However, to ensure this, we still need to make some changes in our authentication flow.
We are also planning to bring these functions to DocuWare On-Premises.
Afterwards we will evaluate extending the login with DocuWare credentials with MFA/2FA.We are constantly striving to improve our products and appreciate your feedback and contribution.
Jeff
supported this idea
·
-
237 votesJeff
supported this idea
·
-
189 votes
Your idea has been added to our backlog. We are now further investigating the idea.
Jeff
supported this idea
·
-
22 votes
Thank you for your idea. We added it to our collection of ideas and features and will further investigate it. We currently cannot say exactly when this idea will be implemented. As soon as we have more information we will update its status.
Jeff
supported this idea
·
-
97 votes
Thank you for your idea.
We added it to our collection of ideas and features and will further investigate it. We currently cannot say exactly when this idea will be implemented. As soon as we have more information we will update its status.An error occurred while saving the comment Jeff
commented
Just had a customer request this as well. Comma's don't look right in a variety of numeric field applications.
Jeff
supported this idea
·
-
7 votes
An error occurred while saving the comment Jeff
commented
I've had this request come up multiple times from various customers and prospects. Seems like this would be a pretty useful feature, not only for email, but also for downloading as well.
Jeff
supported this idea
·
-
3 votesJeff
shared this idea
·
-
6 votesJeff
supported this idea
·
-
29 votes
Thank you for your idea. We added it to our collection of ideas and features and will further investigate it. We currently cannot say exactly when this idea will be implemented. As soon as we have more information we will update its status.
Jeff
supported this idea
·
-
25 votes
Thank you for your idea. Right now we are focusing on other topics, so we are not considering this idea for future releases. If the demand for this topic increases, we might add it to future plans.
Jeff
supported this idea
·
-
2 votesJeff
supported this idea
·
-
2 votesJeff
supported this idea
·
I demonstrate the Keep Entries feature in almost every single demo when storing documents. In a typical personnel file, we'd normally keep common fields like First Name, Last Name, etc, and those should be brought forward to the next document.
I'll typically additional fields such as Folder, Document type, Document Date, and it keeps the entries from the previous field. You can't replace those index values by simply clicking in the field, or clicking the drop down. You have to click in the field for the X to appear, click the X, and then fill it with the appropriate data.
Put an option in the store dialog configuration screen to "Exclude this field from Keep Entries" so that those fields always show up blank when the new document is being presented to indexing. That way, only the common fields which will not change are brought forward, and then it doesn't require manually clearing out the fields that do need to be changed. This would also help prevent documents being indexed incorrectly should someone forget to clear out a field and simply store the document with the previous documents index information.