Jump to content

jfishcasselsbrock.com

Members
  • Posts

    373
  • Joined

  • Days Won

    5

Everything posted by jfishcasselsbrock.com

  1. We are currently using Allegro and the language identification field lists languages by percentage. eCapture uses flags. Can we have this functionality in eCapture and ADD. We don't want to change our workflow when we move to ADD.
  2. We are currently using Allegro and the language identification field lists languages by percentage. eCapture uses flags. Can we have this functionality in eCapture and ADD. We don't want to change our workflow when we move to ADD.
  3. We are currently using Allegro and the language identification field lists languages by percentage. eCapture uses flags. Can we have this functionality in eCapture and ADD. We don't want to change our workflow when we move to ADD.
  4. If we switch over to ADD, (currently using Allegro), I would like the metadata fields to be the same so that our workflow does not have to change. The OCR confidence level in Allegro was a percentage, whereas the field in eCapture is a flag if the level is below a certain amount. When will this feature be available in eCapture an/or ADD.
  5. If we switch over to ADD, (currently using Allegro), I would like the metadata fields to be the same so that our workflow does not have to change. The OCR confidence level in Allegro was a percentage, whereas the field in eCapture is a flag if the level is below a certain amount. When will this feature be available in eCapture an/or ADD.
  6. If we switch over to ADD, (currently using Allegro), I would like the metadata fields to be the same so that our workflow does not have to change. The OCR confidence level in Allegro was a percentage, whereas the field in eCapture is a flag if the level is below a certain amount. When will this feature be available in eCapture an/or ADD.
  7. If we switch over to ADD, (currently using Allegro), I would like the metadata fields to be the same so that our workflow does not have to change. The OCR confidence level in Allegro was a percentage, whereas the field in eCapture is a flag if the level is below a certain amount. When will this feature be available in eCapture an/or ADD.
  8. If we switch over to ADD, (currently using Allegro), I would like the metadata fields to be the same so that our workflow does not have to change. The OCR confidence level in Allegro was a percentage, whereas the field in eCapture is a flag if the level is below a certain amount. When will this feature be available in eCapture an/or ADD.
  9. If we switch over to ADD, (currently using Allegro), I would like the metadata fields to be the same so that our workflow does not have to change. The OCR confidence level in Allegro was a percentage, whereas the field in eCapture is a flag if the level is below a certain amount. When will this feature be available in eCapture an/or ADD.
  10. If we switch over to ADD, (currently using Allegro), I would like the metadata fields to be the same so that our workflow does not have to change. The OCR confidence level in Allegro was a percentage, whereas the field in eCapture is a flag if the level is below a certain amount. When will this feature be available in eCapture an/or ADD.
  11. I know about the create new numbers option. I want to be able to create new numbers from an existing field in the database. SE allows you to do this. Also, if the production is native only, exporting to PDF is not an option. We use publish in order for the client to review and make comments in an editable field. we even give them tags to use.
  12. I know about the create new numbers option. I want to be able to create new numbers from an existing field in the database. SE allows you to do this. Also, if the production is native only, exporting to PDF is not an option. We use publish in order for the client to review and make comments in an editable field. we even give them tags to use.
  13. I know about the create new numbers option. I want to be able to create new numbers from an existing field in the database. SE allows you to do this. Also, if the production is native only, exporting to PDF is not an option. We use publish in order for the client to review and make comments in an editable field. we even give them tags to use.
  14. I know about the create new numbers option. I want to be able to create new numbers from an existing field in the database. SE allows you to do this. Also, if the production is native only, exporting to PDF is not an option. We use publish in order for the client to review and make comments in an editable field. we even give them tags to use.
  15. I know about the create new numbers option. I want to be able to create new numbers from an existing field in the database. SE allows you to do this. Also, if the production is native only, exporting to PDF is not an option. We use publish in order for the client to review and make comments in an editable field. we even give them tags to use.
  16. I know about the create new numbers option. I want to be able to create new numbers from an existing field in the database. SE allows you to do this. Also, if the production is native only, exporting to PDF is not an option. We use publish in order for the client to review and make comments in an editable field. we even give them tags to use.
  17. I know about the create new numbers option. I want to be able to create new numbers from an existing field in the database. SE allows you to do this. Also, if the production is native only, exporting to PDF is not an option. We use publish in order for the client to review and make comments in an editable field. we even give them tags to use.
  18. When will we have the ability in the GUI to bulk update the Review status of documents when a reviewer mass tags documents
  19. When will we have the ability in the GUI to bulk update the Review status of documents when a reviewer mass tags documents
  20. When will we have the ability in the GUI to bulk update the Review status of documents when a reviewer mass tags documents
  21. When will we have the ability in the GUI to bulk update the Review status of documents when a reviewer mass tags documents
  22. When will we have the ability in the GUI to bulk update the Review status of documents when a reviewer mass tags documents
  23. When will we have the ability in the GUI to bulk update the Review status of documents when a reviewer mass tags documents
  24. When will we have the ability in the GUI to bulk update the Review status of documents when a reviewer mass tags documents
  25. when will we be able to search for Annotations using the advanced search and the document viewer
×
×
  • Create New...