Frequently asked Questions about CX10


1.    What is CX10?

CX10 is the new user interface for your Jenzabar CX product.  When fully delivered, CX10 will replace all previous interfaces to CX.  This new interface one of the regular enhancements to your system and its costs are included in your annual maintenance.  There is no additional license fee for this interface.

2.    Is the CX10 client a Java-based client?

CX10 client is not a Java-based interface.  It is written in C++ using the Qt tool kit. 

3.    How will we receive CX10?

Jenzabar will be releasing CX10 in software maintenance orders (SMOs) on a module-by-module basis.  As a prerequisite for CX10, you will receive SMO 13074, which contains a new screen compiler for your CX system.  This compiler more stringently imposes good syntax for your screens.  By packaging the compiler with this SMO, you will have the opportunity to not only compile standard Jenzabar screens but also to address any customized screens.  This should give your institution a head start on resolving syntax issues within your custom screens. 

Along with the compiler are a number of screen updates for standard Jenzabar screens, as well as the removal of financial applications no longer supported in the CX system.  These include the original purchasing program (before RPA), the previous payroll system and the notes payable module.

After the preparatory SMO, the CX10 interface will be delivered in a series of SMOs over the course of 2018 and early 2019.  The modules and SMO numbers are:

·         SMO 13041 – CX10 Financial (does not include HR/Payroll)

·         SMO 13071 – CX10 Student (Registration/Advising, Student Services, Placement)

·         SMO 13083 – CX10 Financial Aid

·         SMO 13094 – CX10 Admissions

·         SMO 13095 – CX10 Institutional Advancement

·         SMO 13098 – CX10 Common Module Updates

Because of the technology used in the Human Resources/Payroll interface, the HR modules will require additional work for conversion.  There is currently no targeted release timeframe for this module.

Any future updates to the CX10 client will be included as part of a SMO. Please note that because of the end of platform support for HPUX and AIX systems, the CX10 infrastructure will only be available on Linux systems.

Your institution must install the SMOs in SMO order.  However, installing the SMO does not automatically turn on CX10.  You will need to configure and install the client to make the interface available to your users.  To aid in your transition, we will continue to support the other interfaces for CX (character, JenzaMate, CX 8.1) for 6 months after the GA delivery of all of the SMO’s listed above.  This should give your institution ample time to adopt CX10.

In addition to the CX10 client, CX10 will include on-line documentation.  The on-line documentation installs on a separate web server.  Documentation is tied to each screen through a URL defined in the SCREEN INFO section of each screen. 

4. What about the federal maintenance SMOs during this period?

As indicated above, clients should follow SMO order.  You should install the releases as delivered.  Contents in the SMOs that follow the CX10 module release will be compatible in the character, JenzaMate, and CX8.1 interfaces as well as CX10 during this period.  Federal updates required for CX (FISAP, Need Analysis, 1098Ts w2s, 1099s, etc.) will work for all supported interfaces through this period.

Our goal is to deliver additional updates and functionality to the product built in the new CX10 interface.  During this time of backward compatibility, we will be limited in the new functionality released.  (It has to be compatible in all of the other interfaces.)  To continue to provide the most for your maintenance dollars, we have shortened the dual support period to 6 months after all updates are delivered.  After that period, we will be able to create new features, update workflows, and continue improvements without limitations of the previous interfaces.

5.    What additional services will be necessary to adopt CX10?

The system accesses the screens from their current location on the CX system.  Using Make, the system creates the additional CX10 version of each screen and installs the screens into the appropriate install path.  Using Make is a standard procedure for CX system administration.

Depending upon the level of customization and your resources, the time involved to install SMO 13074 and to address any syntax errors in your screens will differ customer to customer.  After you evaluate your available resources, if you want additional assistance, you can contract through Jenzabar’s Services for assistance in converting your customs.  

In CX10, there is no standard character-based system mail reader.  All e-mails should be forwarded to users from the system to their standard e-mail handler.  If you have not configured your system to forward system mail, you will need to do so.  If you need assistance in getting this set up on your system, you can contract through Jenzabar’s Services for assistance in implementing the change.

6.     Do I have to be using CX8.1 to migrate to CX10?

No.  Your institution does not have to be using CX 8.1 to migrate to CX10.

7.    Is the CX10 client available for both Macs and Windows PCs?

Yes.   The SMO delivers a client for both Macs (El Capitan-10.11, Sierra – 10.12, and High Sierra – 10.13) and Windows PCs.   So far, we have successfully tested the client on Windows 7 and Windows 10.  We are currently evaluating Windows 8 versions.

8.    Is 100% of the communication between the client and the server encrypted in CX10?

Yes.  In CX10, we have introduced a new component in our CX technology stack called CXHub.  CXHub performs two tasks – it multiplexes all TCP connections between the CX10 client and the CX10 backend into a single client-initiated connection.  It also encrypts all data transferred between the client and the server.  This CX10 hub will be required to enable connections between the client and the CX backend.

The CXHub configures using your SSL local certificate and private key.  It listens on a port that will be set in the CX10 client configuration files.  The CXHub is primarily concerned with the switching and shunting of data streams.  It does very little processing of the data beyond what is required for directing it to the correct receiver.  Internally, CXHub uses a single thread to handle all connections and data transfer.  The event-driven architecture easily handles the network throughput (no blocking).  Any processing of data or calls to blocking functions are handled by worker threads to prevent impacting data flow.

The CXHub will be delivered in SMO 13041.

9.     What output viewer is included in CX10?  Can I select a different viewer?

CX10 comes with a standard output viewer.  If the user desires to use a different viewer (for example, Microsoft Word, WordPad, etc.), this can be configured under the personal settings option in the upper right corner of the CX10 menu page.

10.  Will the users be able to see their menu history in CX10?

Yes.  Under personal settings in the upper right corner of the CX10 menu page, the users can select the menu history option and view their menu history for the session.

11.  Is it possible to increase the size of the menu by sliding the screen to the right so that you can see all of the words?

Absolutely. Just grab the right edge of the menu and move it to the right.

12. Do I have to go through the menu and open each level of the menu to find the menu option I want?

While this method is still available, two new features exist in CX10 for locating the desired option.  First, a search box appears just above the menu.  When the user types in the name of the option, the system filters the menu, showing options matching the criteria.  The user can then select from the filtered options.  Second, the CX10 interface contains a “Recent Programs” area that displays the last eight options selected by the user.  The user can click on this list to launch the option.

13.  Are ACE reports going away?

The answer is “No”.  The CX System has over 800 standard reports written in ACE.  These are still available to the user in CX10.

14.  What happens if a user tries to exit the system and still has programs open?

The system will prevent the user from logging off and remind them to close the applications.  If for some reason the user cannot exit the program correctly, then the user can force exit the program and close the client. 

15.  Can you increase the font size in CX10?

Under personal settings, the font size increases up to 200 percent. The font scaling is in addition to your current Window’s setting. 

16. Are you limited to twenty options on the CX10 menu?

No.  However, if you expand your menu to include more than 20 options, your menu will only be available in CX10 – there will be no backward compatibility with prior CX interfaces.

17.  When cutting and pasting text from other applications (like Word) into the blob field, will the field then contain the Microsoft Word special formatting?

The text in blob fields encodes as UTF-8 data when stored in the database.  The editor strips out any special formatting characters like those from Microsoft Word. 

18.  Will I have issues with updating Java for this client?

No.  The client is a C++ application.

19.  Does CX10 have the F5 key capability?  This feature shows the user detail about the field, the database table that contains the field, and a short description.

Yes.  The F5 key feature exists in CX10 also.

20.   Are all of the programs changing?  Will we need to re-train our users in module functionality?

No.  There are minor enhancements to Voucher (journaling) to remove commands that were unneeded at that level of the program but the financial programs are the same as they were in CX.  The CX10 interface however, positions us to continue to improve the workflow for programs after the initial release.

There is also a new version of screens (Perform) in Table Maintenance and Query by Form areas of the system.   This new version operates very similarly to its predecessors. As you implement CX10, user help on the use of these screens will be available through the on-line documentation.

21.  What are the new features of the screen utility that replaces Perform?

We have a new screen utility we named “CX Form”.  In SMO 13041, we included the new utility with support for simple form screens.  Simple screens are screens containing one or more tables on one or more screens that do not have blobs and/or do not have a master/detail relationship between tables on the screen.  Support for the blob and master/detail relationship screens will be included in SMO 13098.  Users receive notification by a popup in CX10 if support for the screen is not yet available. They will need to access the screen through their previous interface until the screen is available.

New feature of CX Form include:

1)    A quick navigation bar for quick movement between screens (where multiple screens apply) and between tables on the screen.

2)    A new result set is available when the query performed by the user matches more than one row.  This result set is accessible from the command menu or from the file folder on the navigation bar.  Data displayed in the result set is sortable.

3)    The navigation bar displays the number of the entry selected of the total number of records in the result set.  The user may use the “<” and “>” signs to move forward or back through the records.

4)    Administrators can configure menu options to run screens as query only.

5)    Lookups are available for fields which reference table and include values.

22.  What are the features of the new file management utility?

With the new file utility, users can:

a.    Quickly access the eight mostly recently updated files in their home directory or open a menu that allows them to browse all files.

b.    Upload and download files to and from their PCs.

c.    View a file in the selected output viewer for the user.

d.    Rename a file.

e.    Copy a file to a new name.

f.     Delete a file.

g.    Print a file.

In addition, institutions can configure the file browser to access more than just the home directory of the user.  An example might be to access the wpvi directory for word processing files.

Please note that the file utility will not allow the user to upload hidden files to their home directory.

23.  We have multiple releases on multiple servers.  Will our users be able to access those releases?

Yes.  Your institution will need to configure the client to know about those releases.  When the users log in, they will need to select the server.  All releases on that server will appear, and the users will then need to select the release and login using their credentials.

24.  Our users navigate through programs with keystrokes – not with the mouse.  Is this possible in CX10?

Yes.  Each command has a keystroke associated to it.

25.  Is it possible to configure the execute key?

Yes.  Under personal setting the user can select the execute key to be either F1 or F9.

26.  We have multiple password-protected menus.  Is this available in CX10?

Yes.  The password protected menu options present with a yellow lock.  Once the user enters the password, the lock turns blue; users can access the option for the time they are connected.  When the contents of password-protected menus appear, the user will have to authenticate to initiate any items under that menu.

27.  We use the privacy feature in CX to indicate items that are private to external constituents.  Does CX10 support this?

Yes.  The privacy feature is a part of CX10.

28.  Some of our users have more than one monitor.  They like to position their monitors with different items on each.  An example would be a financial officer who likes to have Accounting Query, Excel, and Journals all open at once to enable movement between them.  Does this capability exist in CX10?

The answer is “Yes”.  Users can release windows from the CX10 menu frame and move them to multiple monitors by clicking the arrow in the upper right corner of the program screen .  The CX10 menu tracks which items are open and displays them on the task bar.  When you release the window from the CX10 menu, you can <Alt-Tab> through all your open windows.

29.  Have there been improvements in authentication and password management in the CX10 client?

We have exposed the features of PAM (Pluggable Authentication Model) in our CX10 client.  Your setup in PAM will established if the following features exist for your users. The CX10 client supports user notification of the following:


a.    If you are using password aging, then users will be notified when their password is about to expire.

b.    Users will be required to change their password when their passwords expire.

c.    The system notifies users if their account has expired.

Password Management

a.    A dictionary check happens on all proposed password changes to prevent the user from creating passwords that are standard words found in the dictionary.

b.    Password management will support a minimum time between password changes.  If the user tries to change their password again within the minimum time, notification occurs with no change to the password.

c.    The system suspends user access after a defined number of failed attempts.

d.    Password management also disallows the reusing of historical passwords.

If you institution requires additional help in configuring PAM to implement the above options, please contact your Account Manager or Jenzabar Services for assistance.

30.  Does “nomenu” work in CX10 to keep users from using the system?

Yes.  In CX10, the user can login but no menu options launch and the end user sees an alert.  Contents of the “nomenu” file present as dialog to the user within CX10 if they attempt to launch a menu option.

31.  Is it possible in the CX10 menu history files to see the database that the user connected to during the session?

Yes.  The menu history files in CX10 contain the database to which the user connected and the CX environment for the session.

32.  What will be required for Jenzabar support to assist us with CX10 issues?

The standard Jenzabar Connection Requirements as currently published are used.