# System Operations, Configurations, and Preferences

## Where do I find information about which studies have been accessed and which processes have run?

Whenever a user runs a report, metadata about the execution is captured. The location for these metadata are controlled by a path setting in the installation.path.preferences file. The value of the /user/lifesciences/processresults key defines the location. By default, that value is <userLifeSciencesRoot>\ProcessResults\<USER>. For the Default configuration, that will resolve to: <DOCUMENTS>\JMPClinical\Configurations\Default\ProcessResults\<USER>.

Within that folder, each study has its own subfolder. Within each study subfolder, there are three files: _processinfo.sas7bdat, _processinfo2.sas7bdat, and StudyLog.txt. These file contain the execution details for each report the user ran.

## How does JMP Clinical know where to find my studies?

There are two files in your JMP Clinical installation folder (normally C:\Program Files\SASHome\JMPClinical\12\LifeSciences) that tell JMP Clinical where to look for your studies and where the output data, reports, notes, and so on, are to be placed.

The first of these files, installation.path.preferences tells JMP Clinical where to find the file paths to the locations of all of your studies and other need information. A portion of the default installation.path.preferences file is shown below:

Note the lines highlighted in blue. These define the user root, preferences, and output locations.

The second file, installation.configuration.preferences is shown below:

This file tells JMP Clinical where to find installation.path.preferences file for each of the locations configured for your JMP Clinical installation.

Note: There is a separate installation.path.preferences file for each local and shared configuration for JMP Clinical. Conversely, there is only one installation.configuration.preferences file.

## How can I change the location of and share my studies with other users?

To set up a shared location for your studies, you must first map a location on a shared drive and then modify the installation.configuration.preferences file that is installed with JMP Clinical.

Examine the installation.configuration.file shown below:

The key statement in this file is:

[“name” => “Local”, “installationconfigurationroot” => “$LS_HOME”]

This line defines both the name and location of the default configuration. In this case, the name of the configuration is Local and it is located in the $LS_HOME, which in the default installation is set to C:\Program Files\SASHome\JMPClinical\12\LifeSciences\. This is the location shown on the JMP Clinical Settings tab, as shown below:

To add a new or existing shared location, you must copy and modify this key statement so that in defines both the name and the location of the new shared location.

| 8 | Use OS commands to map the drive where the new share is to reside. In this example, the shared drive is defined as drive S:.

| 8 | Navigate to the JMP Clinical installation folder (normally C:\Program Files\SASHome\JMPClinical\12\LifeSciences) on your local machine and open the installation.configuration.preferences file with a text editor.

| 8 | Copy the key statement, including the square brackets. Enter a comma (“,“) directly after the key statement and then paste the copy directly after the comma. It should appear as shown below:

[“name” => “Local”, “installationconfigurationroot” => “$LS_HOME”],[“name” => “Local”, “installationconfigurationroot” => “$LS_HOME”]

| 8 | Change the name and location in the pasted copy to the name and location of the share. In this case the name is Share and the location is S:\Clinical Share\FullShare_20160328. Your name and location must be enclosed by the quotation marks. The modified statement should appear as shown below:

[“name” => “Share”, “installationconfigurationroot” => “S:\Clinical Share\FullShare_20160328”]

Note: Entries are case-sensitive.

Caution: In the example shown here, the location is specified using a mapped drive path. Locations should contain mapped drive paths only if your organization's setup guarantees that all users have the same mapped drives. If you are unsure, you should use the UNC path instead.

The modified file is shown below:

| 8 | Save and close the file.

You must exit out and reopen JMP Clinical before the changes take effect.

| 8 | Close and then reopen JMP Clinical.

| 8 | Click the Settings tab and then on the Configuration drop-down menu.

The new “Share” configuration is now shown as an option.

| 8 | Select Share.

You must close and reopen JMP Clinical before the new selection takes effect. If the new Share folder is an existing shared folder, studies contained within the folder are displayed on the Studies tab. If this is a new shared folder, JMP Clinical adds the necessary components for the folder to function as a shared studies folder.

Note: Anyone with Read/Write privileges on the shared drive has access to a new shared folder. As the creator of this folder you can control level of access by changing the permissions using WinO/S commands.

## I have just re-installed JMP Clinical and my configuration settings are gone. How do I restore my previous configuration settings?

JMP Clinical saves and stores all of your configuration variations in a file called installation.configuration.preferences. This file is located in your product home directory (typically C:\Program Files\SASHome\JMPClinical\12\LifeSciences).

When you open JMP Clinical for the first time, the software generates a backup copy of the installation.configuration.preferences file, called installation.configuration.preferences.backup, and saves it in your Documents folder (C:\Users\username\Documents\JMPClinical). Every time, thereafter, that you open JMP Clinical, the software compares the date-time stamps of the installation.configuration.preferences file and the installation.configuration.preferences.backup file. If it finds them to be different, such as would occur when you add or modify configurations, JMP Clinical immediately generates a backup copy of the installation.configuration.preferences.backup file, naming it installation.configuration.preferences.previousbackup, and stores it in the same location. It then overwrites the existing installation.configuration.preferences.backup file with one that is identical to the installation.configuration.preferences file. The installation.configuration.preferences.previousbackup file is always a copy of the penultimate version of the installation.configuration.preferences file.

When you re-install JMP Clinical or update to a newer version, you also install a new copy of the installation.configuration.preferences file containing only the default configuration. To restore your previous configurations, delete the new installation.configuration.preferences file, copy, and paste the installation.configuration.preferences.previousbackup file into the C:\Program Files\SASHome\JMPClinical\12\LifeSciences directory and rename it installation.configuration.preferences. Close and reopen JMP Clinical and you should find that your configurations have been restored.

## How do I access basic JMP functions?

Refer to Working with JMP for information about accessing basic JMP functionality.

## How do I view Action Button labels in addition to icons?

By default, JMP Clinical represent action buttons using icons. You can view the button label by positioning your pointer over the icon. You can change this display if you would prefer to display the label in place of or in addition to the icon. To make this change, you must modify the system.clinical.preferences file (the default local location for this file is the C:\Program Files\SASHome\JMPClinical\12\LifeSciences directory).

| 8 | Open the system.clinical.preferences file with a text editor.

The file shown below opens. The text to be modified is highlighted.

By default, the ButtonLabelOption is set to “1” to display icons only, as shown below:

| 8 | To view button labels in place of icons, change the text {“ButtonLabelOption”, 1} to {“ButtonLabelOption”, 2}. The buttons appear as shown below:

| 8 | To view button labels and icons, change the text {“ButtonLabelOption”, 1} to {“ButtonLabelOption”, 3}. The buttons appear as shown below:

Note: You must include the quotation marks as shown in the text above. Entries are case-sensitive.

| 8 | Save and close the system.clinical.prefereneces file.

| 8 | You must exit and reopen JMP Clinical in order for these changes to be registered.

## How do I change the page threshold for splitting narratives?

The Adverse Events Narrative report generates an rtf copy of the narrative. These narratives can be quite extensive and so run up against Microsoft Words page limit of 32,000 pages. Because of this, we have set JMP Clinical to split the narratives, by subject, into multiple documents when a threshold of 10,00 pages is reached. The document is split every time the threshold is reached. For example, a narrative of 32.000 pages is split first at 10,000, a second time at 20,000, and a third time at 30,000 resulting in 4 documents.

This feature is hidden but you can change the threshold by the following steps:

| 1 | Navigate into the JMP Clinical ProcessLibrary folder (default location: C:\Program Files\SASHome\JMPClinical\15\Clinical\ProcessLibrary) and open the AENarrative.xml file using a text editor.

| 2 | Scan down to line 30 to see the following code:

<input name="EVTSPRFL" type="slider" label="Maximum number of subjects to include in a single file" required="false" value="10000" hidden="true">

| 3 | Change the word "true" (highlighted in the line above) to "false" and save the file.

| 4 | Close and reopen JMP Clinical.

| 5 | When you open the AE Narrative report, you will see a new option in the General section, circled in the figure below:

| 6 | Either enter the desired value in the text box or use the slider to set the desired value.

JMP Clinical will use this new threshold to determine where to split the narrative document.

## How do I view JMP Clinical in a language other than English?

JMP Clinical supports use of either both English and Chinese languages, as well as partially supporting Japanese.

| 8 | Use the Switch to Language drop-down menu to change language usage by JMP Clinical.

| 8 | You must exit and relaunch JMP Clinical in order for the language change to take effect.

If you do not see all three languages in the drop-down menu, you probably need to rerun the original JMP Clinical installer to add them to your JMP Clinical installation.

### Adding Additional Language Support for JMP Clinical

| 8 | Exit and close JMP Clinical.

| 8 | Navigate to your SAS Software Depot (typically found at C:\SAS Software Depot) and double-click to open the SAS Deployment Wizard.

| 8 | Select Install SAS Software and click .

| 8 | Select Install Additional Software and click

| 8 | Select both JMP Clinical and SAS Foundation and click .

| 8 | Click on the next few windows.

| 8 | Make sure all of the languages are checked on the Select Language Support , as shown below.

| 8 | Click .

| 8 | Click on the next few windows.

| 8 | Review the Deployment Summary (shown below) and click .

| 8 | When all components have been successfully installed, click and/or in this and all subsequent s to complete and exit the installer.

| 8 | Reopen JMP Clinical. Options for selecting English, Japanese, and Chinese should now be available in the Switch to Language drop-down menu.

## How is JMP Clinical affected by localization-specification?

Data used in JMP Clinical must comply with local CDISC standards for variables and values. Certain values have been hardcoded in JMP Clinical software and must be specified exactly as listed below. The following table lists the English specification for these values and their equivalents in additional languages supported by JMP Clinical software:

Available options are described in the table below:

Values That Must Be Specified Exactly as Written
English String | Domain | Variable(s) | Report Affected | (Chinese) | (Japanese)
Screen Failure | DM, ADSL | ARM, TRT01P, ACTARM | Time to Event |  |
Mild | AE | AESEV | Patient Profile |  |
Moderate | AE | AESEV | Patient Profile |  |
Severe | AE | AESEV | Patient Profile |  |
Life Threatening | AE | AESEV | Patient Profile |  |
High | EG, LB, VS | --NRIND | Patient Profile |  |
Normal | EG, LB, VS | --NRIND | Patient Profile |  |
Low | EG, LB, VS | --NRIND | Patient Profile |  |
Complete | DS | DSDECOD, DSTECRM | Time to Event |  |
Completed | DS | DSDECOD, DSTERM | Time to Event |  |
Death | DS | DSDECOD, DSTERM | Time to Event |  |
Died | DS | DSDECOD, DSTERM | Time to Event |  |
Dead | DS | DSDECOD, DSTERM | Time to Event |  |
Disposition Event | DS |  | Time to Event |  |
Y | AE | AESER | Adverse Events Distribution, The value for AESER in ad.sas7bdat. |  |
N | AE | AESER | Adverse Events Distribution, The value for AESER in ad.sas7bdat. |  |
F | DM, ADSL | SEX |  |  |
M | DM, ADSL | SEX |  |  |
Drug Withdrawn | AE | AEACN | TEAE |  |
Fatal | AE | AESEV | Patient Profile |  |