myEvolv Approver (Doc) Routing

If your note type in myEvolv is configured for Approver (Doc) Routing, Bells will use that configuration for approver routing in Bells. When you go to sign your note in Bells, if the note type selected is configured for approver routing, additional fields show on the sign note display. 

• If the note type is not configured for approver routing, the checkbox for Requires Routing does not display. 
• If the note type is configured but not required for approver routing, the checkbox for Requires Routing shows but is not automatically checked. 
• If the note type is configured and required for approver routing, the checkbox for Requires Routing is checked and is not editable. 
• If the user signing the note has more than 5 approvers available, a search bar will show to help filter out the available approvers to select from.
• If the user signing the note has routed before, the selection will be auto-populated to the previous user(s) selected for routing if available. 

The Approver Routing details selected show on the preview and print preview displays in Bells. 

The document routing functionality has also been added to the Group Note and Bulk Sign workflows. 

myEvolv Routing Configuration Definitions 

• Self-Approval Flow
  • A workflow that transitions from New to Open, and then from Open to another status, without any input fields listed. 
• Supervisor Approval Flow 
  • A workflow that transitions from New to Open, and then from Open to another status, with just one input field listed. 
  • The input field listed must be of type “Only Supervisors” or “Immediate Supervisor”.
• Bells supports two (2) possible routing flows Self Approval and Supervisor Approval. 
  • Bells will present different options in the Sign Note display depending on the compatible transition. 
• Transitions can exist in any Routing Scheme used by the selected service and each supported routing flow can exist in the same or separate Routing Schemes.
• Other transitions may exist in the routing schemes defined within myEvolv.
• Bells will ignore any transition that is not compatible with, such as transitions from “Open to Open”, “Pending Approval to Approved”, etc. 
• Bells is only involved with status transitions from “Open” status transition to another status. 
• Bells is not compatible with any transition that has input fields listed other than the ones described above. If other input fields are listed, the transition is deemed incompatible. 

Custom routes are allowed from myEvolv but the organization must use routing NX and only have a single person that the route can end with.