Root System Code - creation
Note - These testing guidelines assume the user is skilled in the use of, at a minimum, the following:
- Data Trail Configuration
- Document Management Definition
- Form Bundler (PM)
- Launch RxConnect
- Registry Settings (PM)
- User Role Definition
Scenario 1: New "Root" System Code - Data Validations after root system code creation
Specific Setup:
- Have a system with a root system code defined [RootA]
- [RootA] has Avatar "PM", "CWS", "MSO" and "CFMS" installed
- In addition, [RootA] is configured with the following:
- "Avatar Identity Manager" is installed
- The 'Enable Avatar Identity Manager' registry setting is not set to 'Y
- "RXConnect" installed and configured
- [UserA] has permissions in form "User Definition" to "RxConnect" to login to the application
- "Avatar Order Entry" is installed
- In form 'Ask on Order Entry Definition' form, two questions are defined [TestA] and [TestB]
- Have a report or query to display data in the "OrderEntry.index_order_code" table [OrderRptA]
- "Avatar Data Trail" is installed
- Open form "Data Trail Configuration" and run the report by "Option"
- Expand the group tree for each namespace on left side panel and make a note of the forms listed under each namespace
- In form "Document Management Definition" a form name is defined [FormA] with a "Form Type" [FTypeA] that has two categories [CatA] and [CatB], selected in the "Categories" field
- In each namespace ("PM", "CWS", "MSO" and "CFMS") a form bundle [BundleA] has been created in form "Form Bundler", that contains two forms, [BformA] and [BformB].
- In each namespace a modeled form [FormA] has been created using form "Form Definition"
- In each namespace a report definition [ReportA] has been created using form "Report Definition"
- A user role [RoleA] has been created in form "User Role Definition"
- Netsmart has created a new root system code, using [RootA] to copy data from. For this example [RootB] with Facility [5] assigned is used
- [UserA] has been assigned full form and table access in [RootA] and [RootB]
- Log in to [RootB] as [UserA]
Steps
- Open form "Registry Settings"
- Search for setting 'Enable Avatar Identity Manager'
- Validate the setting is found, as the module is installed
- Validate the setting is set to "N", as the module has not been enabled and configured yet in the new root system code
- Close the form
- Open form "'Ask on Order Entry Definition'"
- Click the "Edit" radio button
- In the "AOE to Edit" search field, enter [TestA]
- Validate the question is found, and results are as expected
- In the "AOE to Edit" search field, enter [TestB]
- Validate the question is found, and results are as expected
- Run the "OrderEntry.index_order_code" table report [OrderRptA]
- Validate a row is present with the "Order Code" column populated with [TestA] and the "Facility" column contains "7" the new facility number for [RootB]
- Validate a row is present with the "Order Code" column populated with [TestB] and the "Facility" column contains "7" the new facility number for [RootB]
- Close the report
- Close the form
- Open form "Document Management Definition"
- Click [Select Form]
- Select [FormA]
- Select [FTypeA] in the "Form Type" field
- Click [Select Categories]
- Validate categories [CatA] and [CatB] are displayed
- Close the form
- Open form "Form Bundler" in "PM"
- Click [Edit Existing]
- Validate [BundleA] is present in the list and click [OK] to select the bundle
- Click [Included Forms]
- Validate [BformA] and [BformB] are listed, as expected
- Close the form
- Open form "Form Bundler" in each of the child namespaces
- Repeat steps 4 a and b
- Validate results are as expected
- Close the form
- From the "Search Forms" field on the home view, search for the "Report Definition" form [ReportA] in "PM"
- Select the form
- Validates the form opens successfully
- Close the form
- Repeat step 6 opening [ReportA] in each of the child namespaces
- Validate results are as expected
- From the "Search Forms" field on the home view, search for the "Modeled" form [FormA] in "PM"
- Select the form
- Validate the form opens successfully
- Close the form
- Repeat step 8, searching for the modeled [FormA] in each of the child namespaces
- Validate results are as expected
- Open form "User Role Definition"
- Click [Select User Role]
- Validate [RoleA] is present in the results
- Click to open the role
- Validate data is populated as expected
- Close the form
- Open form "Data Trail Configuration"
- Select "Option" in the "Sort Report By" field
- Click [Run Report]
- Expand the group tree for each namespace on left side panel
- Compare the forms listed under each namespace with ones noted in the set up
- Validate the forms listed are the same in both root system codes
- At the home screen, search for form "Launch RXConnect"
- Click [Launch RXConnect]
- Validate the "RXConnect" application is launched in separate window
- Validate the user is automatically logged in
- Click logout
- At the login screen, enter the Avatar user name and password
- Click login
- Validate the user is logged in successfully
- Click [Logout]
- In Avatar, close the form
|
Topics
• Forms
• NX
|
