BackgroundStatus Routing allows Power Users to architect various 'states' that an Import Form can inhabit. A primary use case is to allow forms to be reassigned to different teams or people as needed.
As status routing implements business logic, it is important that the Status Routing controls render properly, otherwise the form cannot be rerouted to additional users.
This spec tests the logic that governs the generation and reassignment of a form when Statuses are changed, and ensures that the correct Status Routing buttons are rendered, depending on the current Status. Specification- For each Import Form Template available, the spec ensures that:
- A parent Loan record exists
- A new form can be created
- Form cannot transition from NULL to an invalid Status
- Form in with a status of undefined renders appropriate status buttons
- Form in with a status of Recommend Referral renders appropriate status buttons
- Form in with a status of Approve Referral renders appropriate status buttons
- Form in with a status of Reject Referral renders appropriate status buttons
|