7 results found

1. Autoindex monitor should show updated documents

   The Auto Index monitor in DocuWare 6.11 shows the number of documents processed, not the number of documents updated. I like that it now shows how many documents were processed. It would be nice if it showed both the documents processed and the number that were updated.

   5 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Autoindex  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close
   Added to Ideas Backlog  ·  AdminDocuWare Product Management (Product Owner, DocuWare) responded

   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.

2. Could we get an email alert when one of the autoindexing jobs errors out?

   Could we get an email alert when one of the autoindexing jobs errors out? It would be nice to be proactive in fixing these issues without waiting for users to report.

   4 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   1 comment  ·  Autoindex  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

3. Increasing Automatic Intelligent Index fields

   To be able to increase the amount of index that can be automatically indexed when configuring the Intelligent indexing fields. We have a use case where we need 260 index fields but are only able to auto index 14 custom text fields. So wouldn't it be better to be able to increase this amount.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Autoindex  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

4. Add refresh button to Autoindex Configuration page to better monitor status

   Add a refresh button to Autoindex Configuration page. On-the-fly updates are not consistent and monitoring for extended period of time. Refreshing web page brings you back to the start of the configurations page.

   2 votes

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Autoindex  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

5. Keywords should be fully supported in autoindexing and document relations -- "Contained by" operator

   As of writing, keyword fields seem to only be half-heartedly supported by DocuWare.

   One of the biggest issues with keyword fields is that we have a "Contains" operator that can be used in autoindexing and document relations, yet we don't have a "Contained by" operator. This means that while we can include a related document that has a keyword which contains a text field in our starting document, it is impossible to make the inverse document relation, where a starting document matches its keyword field against other documents' text fields. Document relations should let users navigate in both directions, not just one-way.

   One would imagine a workaround for the above problem is to add a new index field to refer to the document that has the keyword field from the documents that the keyword field refers to. This would change the scenario from a one-to-many matching to a many-to-one matching, which is currently supported by document relations. Unfortunately, autoindex matchcodes can only be configured to match using the "is equal to" or "is not equal to" operators; keyword fields are completely unusable. This means that it is impossible to go from one-to-many to many-to-one using autoindexing.

   Proposed solution:
   It would be an ideal fix if keyword fields could be used in matchcodes with "is equal to" and "is not equal to" operators for comparing a keyword field to a keyword field (using set equality rules) and "contains" and "contained by" operators for comparing a keyword to a text field. This fix would also allow for a simple workaround to the document relation issue.

   One-to-many relationships in documents are commonplace, so DocuWare should be able to handle these scenarios without complex workarounds.

   As of writing, keyword fields seem to only be half-heartedly supported by DocuWare.

   One of the biggest issues with keyword fields is that we have a "Contains" operator that can be used in autoindexing and document relations, yet we don't have a "Contained by" operator. This means that while we can include a related document that has a keyword which contains a text field in our starting document, it is impossible to make the inverse document relation, where a starting document matches its keyword field against other documents' text fields. Document relations should let users navigate in both directions, not… more

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Autoindex  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

6. Enable AutoIndex To Write Back To CSV Files Without A Header Row

   AutoIndex will write back to CSV files with a header row. It also writes back to CSV files without a header row; however, it writes back row 1's data to row 2, row 2 to row 3, etc. Then it doesn't write back the last row.

   AutoIndex can support a CSV without a header row. Therefore, AutoIndex should be able to properly write back to a CSV file that doesn't have a header row. Since AutoIndex doesn't properly write back to CSV files without a header, this is one way the configuration of DocuWare can be improved.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Autoindex  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

7. Set datetime filed in the condition of much code of autoindex.

   We can't select the datetime field in the autoindex much code. Currently only date field is available.

   1 vote

   Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   0 comments  ·  Autoindex  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close