Improve Web transaction batch user assignment options

Currently batch assignments for web transaction batches allow for multiple users, however this splits the batches in a "round robin" transaction allocation. This is not useful when one user is out of the office and cannot access the other user's batch to process the revenue. Often the "Run as" facility is locked down for all but admin users therefore using this is not a solution. Suggestion would be to assign full batch to multiple users - locking down for user that is not access the batch so only the actively using user can process/commit and/or allow allocation based on users by Site (that have the role permissions to access batch functionality). This would be useful for multisite BBIS clients.
  • Guest
  • Jun 29 2015
  • Attach files
  • +15