•   over 9 years ago

Getting "No valid tabs assigned" message window in CPRS

Hello –

We can connect to each of the VistAs but getting a message box for “No valid tabs assigned” error in CPRS.

We are using:
CPRS Client v1.0.28.24
Enter Access and Verify Code
Get a message window – No valid tabs assigned.
User has Secondary Menus and Security keys as assigned

Looking for assistance on what this error means in CPRS.

  • 4 comments

  •   •   over 9 years ago

    No CPRS tabs are assigned to the user.... try below

    VISTA>D ^XUP
    Setting up programmer environment
    This is a TEST account.
    Terminal Type set to: C-VT100
    Select OPTION NAME: XUSERED
    1 XUSEREDIT Edit an Existing User
    2 XUSEREDITSELF Edit User Characteristics
    CHOOSE 1-2: 1 XUSEREDIT Edit an Existing User
    Edit an Existing User
    Select NEW PERSON NAME: LASTNAME,FIRSTNAME DLC
    NOTE: Editing a user can also be done by editing them in New Person file see below for adding COR tabs.
    Select OPTION: 1 ENTER OR EDIT FILE ENTRIES
    INPUT TO WHAT FILE: DEVICE// NEW
    1 NEW PERSON (16 entries)
    2 NEW WORK ACTION (32 entries)
    CHOOSE 1-2: 1 NEW PERSON (16 entries)
    EDIT WHICH FIELD: ALL//
    Select NEW PERSON NAME: LASTNAME,FIRSTNAME DLC
    NAME: LASTNAME,FIRSTNAME//
    STREET ADDRESS 1:
    STREET ADDRESS 2:
    STREET ADDRESS 3:
    CITY:
    STATE:
    ZIP CODE:
    TEMPORARY ADDRESS 1: ^CPRS TAB
    Select CPRS TAB: COR CPRS GUI "core" tabs.
    Are you adding 'COR' as a new CPRS TAB (the 1ST for this NEW PERSON)? No// Y
    (Yes)
    EFFECTIVE DATE: T (JUN 22, 2007)
    EXPIRATION DATE:
    Select CPRS TAB: ^

  • Manager   •   over 9 years ago

    The CPRS issues can be resolved by reading the instructions. The "VistA users" are only
    created after running the Scenario001. Hence, connections to CPRS can only be done after running the Scenario, not just out of the box when receiving the VMs.

    The ACCESS and VERIFICATION codes needed are available in the VMs themselves in JSON files under the Testing Use Case
    directory.

    Contest Administrator

  •   •   over 9 years ago

    I have looked through all of the JSON files and do not see any variables set for ACCESS or VERIFICATION codes.

  • Manager   •   over 9 years ago

    To find some of the initially created users (Access/Verify Codes) of the provided VistA instances contestants should look under the directory:

    ./OSEHRA/Dashboards/OSEHRA-Automated-Testing/UseCases/

    And specifically the files:

    ● AddDoctors.py.in
    ● ALABAMA/UniqueDoctors.json.in
    ● CALIFORNIA/UniqueDoctors.json.in
    ● CommonDoctors.json.in
    ● GEORGIA/UniqueDoctors.json.in

    These files are used by CMake to generate under the directory:

    ./OSEHRA/Dashboards/OSEHRA-Automated-Testing-build/UseCases/

    The files

    ● AddDoctors.py
    ● CommonDoctors.json
    ● UniqueDoctors.json

    Exploration of the JSON files will reveal the following Access & Verify codes:

    CommonDoctors.json: "Access Code":"fakedoc2",
    UniqueDoctors.json: "Access Code":"fakedoc1",
    UniqueDoctors.json: "Access Code":"mhdoctor1",
    UniqueDoctors.json: "Access Code":"audidoctor1",

    CommonDoctors.json: "Verify Code":"3Car!@#$",
    UniqueDoctors.json: "Verify Code":"2Doc!@#$",
    UniqueDoctors.json: "Verify Code":"2Mhd!@#$",
    UniqueDoctors.json: "Verify Code":"2Aud!@#$",


    The values above are a sample and the contestant should look in their UniqueDoctors.json file as they will vary across the California, Georgia and Alabama VMs.

    Contest Administrator

Comments are closed.