Settings
The Runner has a few settings you can adjust.
Startup module
The startup module is the path to the model which the Runner will use to start a case. This is the full name of the model without the extension. In this example the model is in folder E:\data\testing, the model is dateinttexts.
Auto start-up
If the Runner is started, it will automatically start with the case found in startup module.
Save case on exit
A case is saved is the Runner is closed. If so, the latest input of the user is saved as well. If you turn this off, all information is lost if you close the Runner. The case is stored as [modelname].[ID].cas. The case id is a random hexadecimal string of thirty-two characters. An example is newmodel.652A189B-82A8-4803-809D-054A54FC06FE.cas
Save last start-up
The Runner is started from the Studio. The Runner will remember the last model where it is called from, and set this value in Startup module.
Detailed log
The Runner is capable of logging when it is running a model. This can provide valuable information, but, especially with text production, this can result in a lot of data.
Log to file
The log is sent to a window that can be opened with File > Log. It is also possible to send the log to a file. This way you can see all the logging (the log window only holds a limited amount of logging). In case of a problem, you can also send this log files to Berkeley Bridge. With the log at hand we can better understand what is going on. A new log file will be created when reaching a limit of 5MB. Each time the Runner has to create a new log file, it will delete log files older than fourteen days. This prevents your hard drive from getting filled up. The log files are stored in the folder C:/Users/[Your Name]/AppData/Roaming/BerkeleyRunner/BBRunner.log, (substitute your own user name for [Your Name]).
Reference check text production
Enables numbering in text productions. Because calculating this is quite expensive, you can disable this if you do not use numbering.
Auto generate jumplist
Tries to create a jumplist up front. This is not always possible, as the Berkeley Runner has no way of knowing the path a user will take, but for some straightforward models this option can be useful.
Use persistent jumplist
Leaves items on the jumplist when a user jumps back into the model, so the user can jump forward again. If on the other hand she changes the input and so changes the path, the jumplist items ‘ahead of’ the change will be deleted.
Use all startup-parameters (not safe)
Parameters can be passed to the Runner that can be used inside the model. In case of the Berkeley Webserver the username and password have to be passed to provide access to the model. All these parameters can be retrieved in the model with the function getparambyname() (See Functions: advanced).
The parameters are stored in the case. Because saving sensitive data such as credentials always implies a security risk, the following parameters are excluded from saving: username, password, sessionid, caseindex, modelname, dbname, uniqueid, fmt and templateindex. This information is neither stored, nor is it available in the model.
If you check the option ‘use all startup parameters’ this information will be treated as normal. This is to say it will be available in the model and stored in the case. For obvious reasons you should not use this option unless it is absolutely vital.
Path to persistent documents
If you need to reference documents that are not produced by the model, you can store them in this folder. You can use ‘linked text’ to reference them.
Library folder
All library files are stored in a single folder. This folder should be the same as the one you have selected in the Studio.
Test folder
If you create your own regression tests (optional), which are stored in this folder
There are settings for four different PDF creators. One is used for HTML files (Web), one for DocX (Word), one is for PptX (Powerpoint) and the last one for RTF (old Word, and deprecated).
All four PDF creators have similar options:
Location of PDF Creator
The location of the convert executable. The Runner will call this converter through a command line, making the use parameters possible.
PDF creator parameters
The command line arguments for the program you have chosen to convert documents to PDF. Use %s for source and %t for target.
Uses target folder
Some PDF creators put the result in a single output folder, instead of in the folder specified by the target (%t). If so, turn this option on, and the Runner will move the file from that folder to the output folder of the case.