Managing the Data Management System (DMS)
The TIM intern Data Management System manages the documents, which are attached to processes, activities and tasks. The DMS's functionality can be affected using the following parameters in the tim.properties.
Documents can only be attached to open tasks or rather at the processstart
The parameter dms-user-has-tasks can determine, if documents can only be attached to open tasks or rather to the processstart. The parameter can be set to true or false. (s. example).
dms-user-has-tasks=true
Excluding the processmanager from the regulation It can be useful to exclude processmanagers from this regulation. If the parameter dms-user-check-processmanager is set to true, it is possible for processmanagers to attach documents at any point in time (s. example). Processmanagers can also delete documents at any point in time.
dms-user-check-processmanager=true
Prohibiting the editing of documents The Parameter dms-prevent-docmod-<pd-name>-<activity-name> can prevent the editing of documents at a specific activity. Replace <pd-name> and <activity-name> with the corresponding processdefinition and activity name (s. example). Special characters as well as blanks have to be replaced with a -. <activity-name> can be left out, which leads to preventing the editing for the whole process. (The characters “<” and “>” have to be left out)
dms-prevent-docmod-<process-1>-<activity-1>=true
Setting the DMS Provider The parameter dms-provider refers to the used DMS system (s. example).
dms-provider=sharepoint
The parameter dms-provider-username refers to the user, which is used for signing in into the DMS system.
dms-provider-username=timtim_service
Furthermore the parameter dms-mainprocess-storage and dms-mainprocess-storage-filter determine how the processstorage is accessed and which data is filtered.
dms-mainprocess-storage=read,write
dms-mainprocess-storage-filter=AnyPrefix%
Cache
It is possible to automatically empty the brwoser cache for every login by setting the parameter no-cache to true. If nothing is stated, the cache will not be emptied.
no-cache=true
Standard passwords
It is possible to set and edit the standard password for the Superuser and Client-Administrator
Standard password Superuser The parameter initpass-super-admin is used to set the standard password for the superuser, who can create new clients.
initpass-super-admin=bestAdmin1337
Standard password sys.support The parameter initpass-super-sys.support determines the password for the sys.support user.
Standard password Client-Administrator und User Every Client is created with a user admin. The parameter initpass-x-admin determines the passowrd for that user.
initpass-x-admin=e!|\|*S1cH3r35*|°455w0|27!
The parameter initpass-x-others determines the standard password for all users that are created in that client.
Client language
It is possible to set in which languages the TIM-Clients are available. The parameter available-languages contains all Clientlanguages, seperated with a semicolon (s. example).
available-languages=de-DE,deutsch;en-GB,english (GB);en-US,english (US);es-ES,español;fr-FR,français;nl-NL,nederlands;
Messages in case of external decisions
The setProcessVariableAndSignalProcessinstanceByTransitionName handler allows to make decisions in the process outside of TIM. It can be determined in the tim.properties, which message is displayed in case of a successful or unsuccessful decision.
#signal-succeed-response=Your decision regarding ${SYS.PROCESSDEFINITION_NAME} / ${SYS.PROCESSINSTANCE_NAME} / ${SYS.NODEINSTANCE_NAME} was successfully processed.
#signal-failed-response=Your decision regarding ${SYS.PROCESSDEFINITION_NAME} / ${SYS.PROCESSINSTANCE_NAME} / ${SYS.NODEINSTANCE_NAME} has not been able to be processed.
If the corresponding processinstance was already finished or is not existent, it is possible to set corresponding messages with the parameters signal-failed-pi-ended-response and signal-failed-no-pi-response
Smartform
In the tim-properties it is possible to set, whether the TIM SMartform Suite and the css Framework Bootstrap should be active in the Smartform. This can be set with the parameters form-privder and form-bootstrap respectively.
form-provider=com.dooris.cba.providers.CbaFormProvider
form-bootstrap=false
Notes in the Main- and Subprocess
With the parameter blog-article-inheritance it is possible, that notes from the mainprocess are available in its subprocess. If the parameter is set to read the notes are visible. With write notes from the subprocess are attached to its mainprocess, but not to the subprocess. (s. example)
blog-article-inheritance=write
PDF Conversion
The tim.properties contains multiple parameters meant for controlling conversion of documents into PDFs in TIM.
timPdfConverter
The parameter timPdrfConverter contains, which conversion is used (e.g. aspose).
timPdfConverter=aspose
ooHost
The parameter ooHost contains the host for the OpenOffice Connector.
ooHost=localhost
ooPort
The parameter ooPort contains the port for the OpenOffice Connector.
ooPort=8100
Single Sign On (SSO)
The parameter registrationForm determines the site, which is´displayed, if the signed in user has no access to any client. (s. example)
registrationForm=/loom-portal/super-resource/unauthorized.htm?disposition=inline
