We want to hear from you!

Eliminate Batch ID from Global Search

From an end user point of view there doesn't seem to be any need to search the Batch ID when doing a global search.  Our users are sometimes confused when search results appear to show completely unrelated documents because they've ended up match our job number to a batch ID.

A standard search returns the right results or even clicking one of the correct 'job #" links in the results but people are dumb.  Seems like it just adds confusion where it could be totally avoided.

  • Guest
  • Aug 14 2017
  • Will not implement
  • Attach files
  • Terry Abrams commented
    September 19, 2017 20:22

    I agree, for Global Search, we see Batch ID as useless.

  • Admin
    Mike Morris commented
    November 27, 2017 20:34

    Hey Jason and Terry, 

    Thanks so much for contributing. While BatchID may not be an item used in your day to day operations, there are definitely organizations using DocuPhase that see BatchID as critical, especially for installs that are Document Management heavy, instead of workflow based. I have a feeling that what we should really consider here is allowing your admins to determine what fields have the ability to be searched using a global search. That way, you can maintain fields that this should apply to. 

    I'll go ahead and open another request associated with that idea, and I'll be marking this one as 'Will Not Implement' as I know that it'll have an adverse effect on other users of the software. 


    Mike Morris

    Customer Success Manager. 

  • Guest commented
    November 27, 2017 21:22

    This what I was thinking….I can see it serving a purpose for some but not having the ability to turn it off just adds confusion where it could be avoided.