TOSCACommander.exe.config

This setting specifies the number of objects to be processed simultaneously when projects are synchronized and saved. If this setting is not specified, the value is 100000 by default. This value can be decreased if an OutOfMemoryException occurs while projects are either synchronized or saved. In this case, the synchronize or save processes are delayed. This setting is also used if a new workspace is created for an existing repository.

Name of the project to which settings and repository refer

Directory in which data of the workspaces are stored

Enable/Disable: Undo function for Tosca Commander

This setting can be added if a healthcheck should be performed on a common repository (see chapter "HealthCheck").

Directory to store workspaces

Directory to store Common Repositories

The font used in Tosca Commander

Font size of the font used in Tosca Commander in points

This setting specifies whether the statistics of the LogInfo column should be displayed for directories in ExecutionLists.

Define the time in milliseconds that Tosca tries to contact Tricentis File Service. The default value is 5000.

Enable/Disable: obtain temporary write access without checkout

Enable/Disable: linking files in the files system to selected objects in the workspace (file references)

Sets the maximum waiting time on the availability of the CommonRepository in seconds

If enabled (True), user group hierarchies can be managed (see chapter " Use hierarchical user groups").

If enabled (True), you can include a whole tree for synchronization (see chapter "Enable synchronization of excluded items").

Enable/Disable: selective check-in on object level (see chapter "Synchronization - Using specific functions")

Enable/Disable: selective workspace update on object level (see chapter "Synchronization - Using specific functions")

Enable/Disable: only the element itself and its direct child elements are updated

Steering to handle IndividualCheckIn concerning those objects that are (directly or indirectly) used by the objects to be checked in and are still checked out themselves.

AlwaysAdd: the used objects are always checked in (without asking the user)

Ignore: the used objects are not checked in (without asking the user)

AskUser: The user can decide if all depending objects or none of these objects should be checked in.

Default setting: AskUser

Steering to handle IndividualUpdate concerning those objects that are (directly or indirectly) used by the objects to be updated and are also modified.

AlwaysAdd: the used objects are always updated (without asking the user)

Ignore: the used objects are not updated (without asking the user)

AskUser: The user can decide if all depending objects or none of these objects should be updated.

Default setting: AlwaysAdd

Define the maximum allowed file size for embedded files, or disable embedding.

As the value, enter one of the following:

• A positive integer to indicate the allowed file size in megabytes.

• 0 if you want to disable embedding.

When this setting is enabled (True), a multi-user workspace only contains the project object when it is initially created. During the process to create a workspace no update from the Common Repository is carried out.

Specify that Tricentis Tosca should display a warning message whenever users embed files of a certain size or larger.

The message informs users that large files may slow down the workspace over time. Additionally, it offers to create a file reference instead.

As the value, enter a positive integer to indicate the file size in megabytes.

This setting activates the option Revoke all my Checkouts in other Workspaces.

This setting allows to enable or disable the option Revert local. This setting must be added and it is enabled by default.

This setting allows to enable or disable the option Revert to Revision. This setting must be added and it is enabled by default.

This setting specifies whether all the required objects should be included in the synchronization prior to execution.

This setting only applies if the value of the setting AutoIncludeNecessaryItemsBeforeExecution is set to True. This setting specifies whether a warning should appear prior to including objects automatically into synchronization. If this warning appears, the user will be prompted again whether the objects should be included or not.

This setting enables you to automatically create reports via the TC-Shell without any user interactions (see chapter "Print reports").

ExecutionLists and ExecutionList folders cannot be rearranged manually by default. ExecutionLists are sorted by Type and Name.

This setting must be created with the value True in order to change the behavior. ExecutionLists are initially sorted according to the UniqueID and can then be manually rearranged.

Modules and Module folders can be rearranged manually by default. Modules are initially sorted according to the UniqueID.

This setting must be created with the value False in order to change the behavior. Modules are sorted by Type and Name.

If enabled, a TestCase can be repeatedly used in one ExecutionList.

The options Synchronize and Search all...->Synchronized Folder are always displayed by default. If this setting is enabled, these options are only displayed if synchronous ExecutionEntryFolders are available.

This setting specifies whether a warning notice including a cancel option should be displayed when large amounts of data are checked in (Checkin all). The specified value indicates the number of modified Tosca Commander™ objects to be checked in (cumulative). This setting affects the performance of the Repository (Performance).

If this setting is enabled, the common repository is compressed when saving. Please consult Tricentis Support before modifying this setting.

This setting allows to specify for a certain object type that the property SynchronisationPolicy has the default value CustomizableDefaultIsOff (TestCase, ExecutionLog, etc.) while it is created.

If enabled, more than one object is copied to the database at once when the operation Checkin All is performed. If this setting is disabled, the objects are written to the database one by one. This setting is used for DB2 databases. The setting DB2ObjectStorageChunkSize specifies the number of objects to be transferred at the same time. These settings have an influence on the performance of the Checkin All function.

This setting specifies the number of objects to be copied to the DB2 database at once when the operation Checkin All is performed and if DB2UseBulkInserts is enabled. If the value of this setting is less than 2, the objects are copied to the database one by one.

If enabled, more than one object is copied to the database at once when the operation Checkin All is performed. If this setting is disabled, the objects are written to the database one by one. This setting is used for MS SQL server databases. The settingMSSQLServerObjectStorageChunkSize specifies the number of objects to be transferred at the same time. These settings have an influence on the performance of the Checkin All function.

This setting specifies the number of objects to be copied to the MS SQL server database at once when the operation Checkin All is performed and if SQLServerUseBulkInserts is enabled. If the value of this setting is less than 2, the objects are copied to the database one by one.

If enabled, more than one object is copied to the database at once when the operation Checkin All is performed. If this setting is disabled, the objects are written to the database one by one. This setting is used for Oracle databases. The setting ORACLEObjectStorageChunkSize specifies the number of objects to be transferred at the same time. These settings have an influence on the performance of the Checkin All function.

This setting specifies the number of objects to be copied to the Oracle database at once when the operation Checkin All is performed and if OracleUseBulkInserts is enabled. If the value of this setting is less than 2, the objects are copied to the database one by one.

This setting is required for synchronizing objects in multi-user workspaces. Objects that are excluded from synchronization are included into the synchronization again by expanding them. This behavior can be changed by disabling this setting.

This setting enables the option to modify ModuleAttributes via the context menu of Modules.

This setting allows to specify how values are copied from Excel cells. If this setting is True, the value is read as text (i.e. how it is displayed). If this setting is False, the value is read as Value (i.e. how it has been entered earlier).