Rule Based Routing Widget - filing validation logic
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Order Fulfillment Widget
- Order Entry Console
- POC Results Entry
Scenario 1: Order Fulfillment widget - "Require Fulfillment" modeled form field validations
Specific Setup:
- Have CWS Modeled form [TestForm], that contains various different field types.
- Have an order code set up in 'Order Code Setup', that has the 'Require Fulfillment' set to "Yes" and [TestForm] selected in the "Fulfillment Form" field
- The 'Order Fulfillment' widget and "Orders" widget exist on the logged in users home view
Steps
- Select a client [TestClient] and navigate the "Order" widget
- Search for the order code you defined in the 'New Order' field.
- Fill out the required fields and click 'Add to Scratchpad', then 'click Sign'.
- Validate a row for the order [TestOrder] is displayed in the widget
- Return to your homeview and
- Refresh the 'Order Fulfillment' widget.
- Validate the widget contains a row for the order entered in step 1
- Select the row and click 'Fulfill Order'.
- Validate [TestForm] is open
- For each field on the form enter a value
- Click [File button].
- Validate when applicable, that an error dialog is displayed indicating fields where an incorrect value was entered.
- Populate each field indicated with a valid value
- Click the [File Button]
- Validate the form submits successfully
- Select client [TestClient]
- Open form [TestForm]
- Validate the row submitted in the widget in step 2, is present
- Select the row
- Validate all fields are populated as expected
Scenario 2: POC Results Entry - "Associated Form" modeled form field validations
Specific Setup:
- Have a non episodic modeled form [TestForm], in application "CWS" that contains a variety of columns types, as well as a multiple iteration section.
- In Order Code setup have "Lab" type order code created [TestCode]
- Have a client [TestClient] with an active order [TestOrder] that uses [TestCode]
- In form 'POC Results Entry Configuration'
- On the 'Observation Definition' section, add a new definition [TestDef] and fill out the required fields
- On the 'Test Definition' page, add a new test
- In the 'Associated Form', select [TestForm]
- Submit the form
- Have the eMAR widget to your homeview.
Steps
- Select [TestClient]
- Navigate to the "Emar" widget
- Validate the order displays in the 'Lab Orders' tab
- Select the order in the widget and click 'Administer'.
- Fill out the required fields and click [OK]
- Open the 'POC Results Entry' form.
- Select [TestOrder] from the 'Order' dropdown.
- Validate the collection data is populated
- Validate the [TestForm] displays in another window.
- Fill out all the fields on the modeled form, including the multiple iteration row, and submit.the form
- Validate when applicable, that an error dialog is displayed indicating fields where an incorrect value was entered.
- Populate each field indicated with a valid value
- Click the [File Button]
- Validate the form submits successfully
- Reopen the 'POC Results Entry' form
- Select [TestOrder].
- Validate the collection is not automatically loaded (as it was already submitted)
- Change 'Include Resulted Collections' to 'Yes'.
- Validate the collection load with the values submitted in step 1.
- Edit some field values
- Submit the form
- Reopen the 'POC Results Entry' form
- Select [TestOrder].
- Select the collection again.
- Validate the changes you made in step 3 are displayed as expected.
|
Topics
• Order Fulfillment
|
