Body
Contents
Logging in to CX10
If CX10 does not show for you when following the below steps, please contact the Help Desk at X3500.
- On your computer, press the Windows Key and type "CX" and click on JenzabarCX 10.
- In the resulting window, type in your CX login credentials, choose your database ("CX: carsi" = LIVE; "CX: carstrain" = TRAIN), and click Login.
- Select CARS database and then Select.
- You will now be logged into your CX menu and can operate as normally.
Logging out of CX10
Logging out of CX10 is a bit different than in previous interfaces.
Before closing out of CX10, make sure that there are not any programs running. This is evident by nothing underneath the large "J" on the left hand side.
Example of CX10 with programs running:
Example of CX10 without programs running:
Once all programs are closed out, click on the "X" in the top right corner to close out of CX10:
Setting up external viewer in CX10
Due to the limited capability of the CX printers, it is sometimes recommended change the Output Viewer to a Windows WordPad or NotePad utility.
- Open up and log in to CX10 using the steps above.
- In the upper right-hand corner, click on your username and then on Settings:
- In the window that pops up, click on Viewers. Check the box for "Use an external text viewer" and click on the ellipses ("...") to find the program you would like to output to. Recommended programs and their probably directories are:
Notepad:C:\WINDOWS\system32\notepad.exe
Notepad++:C:\Program Files\Notepad++\notepad++.exe
- Click on OK to save your selection.
CX10 Documentation
With the move to CX10, Jenzabar moved all of their documentation accessible from inside of the interface. Any of the screens that include a Question Mark
link to this online documentation. Clicking on the icon will open a browser with the documentation for the corresponding screen:
Documentation can also be searched by clicking on the magnifying glass once a browser has been opened. Please note: at this time, Chrome is the best browser to open documentation with.
This documentation is maintained by Jenzabar and is updated by SMOs.