The FileBound native Ad Hoc Route should be disabled but is currently functioning:
If a file is sent to via Adhoc Route to a user in state that does not have interest in the case (for example, a file sent to an OH user where the sending state is AL and the receiving state is TX) the user will not be able to view the file contents or do workflow.
Please contact the helpdesk to remove the assignment.
0 Comments