Image tagging BUG in 11.100 series

In v11.100 series we made an assumption that the path from workstations can be accessed in read-only mode in order to protect the same. Previously, operators used to delete the files / do whatever they want in the application folder leading to application malfunctioning.

However, by providing a read-only solution, we restricted a functionality from work stations, i.e., image tagging. The image folder currently resides in the application folder itself which is not configurable and hard-coded. Since the folder is in read-only, image tagging has stopped from work stations.

We need to provide a solution to this by providing a non-hardcode configurable image folder path to user.

  • Product Team
  • Apr 6 2016
  • Will not implement
  • Attach files
  • Admin
    Product Team commented
    18 Mar, 2021 01:34pm

    not applicable post v12 release.

Note : Do not post a lengthy title for an Idea. Post your Idea clearly supported by Screenshots, Examples and Case Studies (if possible).