Organization settings

For organization settings that override the configuration storage file (in which only one property ConfigurationFile is specified), there is a locking system that works according to the following scheme:

1. A user who initially has access to edit a configuration file launches the plugin

2. The configuration file is locked, i.e. no other users are allowed to make changes to it

3. Next to the configuration file is a text file (if it isn't created) created or updated with a name like PluginName.lock.txt, in which the system name of the user who locked the configuration file is written

4. When closing the plugin, the configuration file is released and the system name is deleted from the text file.

That is, the configuration file becomes user-occupied until the plugin is closed.

While the configuration file is occupied, other users who originally have access to edit the configuration file will have the name of the user that the configuration file is currently occupied displayed in the plugin.

The organization settings for the menus allow you to override the menus on the ribbon in AutoCAD or Revit, and to interrupt ModPlus loading in AutoCAD, Revit, or Renga.

The node should be named - Menu.

The node can contain AutoCAD and/or Revit properties. Each property specifies the path to an xml file containing the instructions for building the menu.

If you specify the path to a menu file stored on a network drive on your local network, the path must be in UNC format!

To create a menu file, use the Configurator: on the "Adaptation" tab, create a menu and export it to an xml file using the appropriate  button.

Important! Do not create or edit the menu file manually, it might cause errors when launching AutoCAD, Revit!

If the user has an overridden menu with Organization Settings, the user will not be able to edit the corresponding menu in the Configurator.

A node can contain the following properties to interrupt ModPlus loading:

If any of the properties is not specified or is specified incorrectly, but the Menu node exists, the default settings will be used.

Example of settings:

Set all settings for the auto update module.

The node should be named – AutoUpdater.

Node may contain the following properties:

If any of the properties is not specified or is specified incorrectly, but the AutoUpdater node exists, the default settings will be used.

The auto update module has a check for enabling/disabling the organization settings every 30 minutes, which allows you to enable/disable the organization settings without restarting the module.

Example of settings:

Result:

The License Server settings allow you to set the address of the LAN License Server or a unique key of the Web License Server, as well as to specify which server is active.

The zone node must be named – LicenseServer.

The settings for the LAN License Server consist of three properties:

The settings for the Web License Server consist of two properties:

It is sufficient to add to the node the settings of only the license server which is used in the organization.

In the case of the Web License Server, the email for user identification is not specified by the organization settings!

Example of LAN License Server settings:

Result:

Example of the Web License Server settings:

Result:

Set the settings for the autosave service.

The node should be named – AutoSaveService.

Organization settings for the autosave service are taken into account when Revit is loaded!

Node may contain the following properties:

The BackupDirectory property supports the use of Windows environment variables. For example, %appdata%, %homedrive%, %temp%, etc. If the folder specified in the BackupDirectory property does not exist and there is a CreateBackupDirectory property with a True value, an attempt to create the folder will be made. Errors that occur while trying to create the folder are ignored.

If a property is not specified or is specified incorrectly, the user settings will be used.

Example of settings:

Example of the "Autosaver" tab in the settings window:

The organization settings for the Base level plugin allows to override the path to the configuration storage file. By default, user configuration settings are stored in %appdata%\ModPlus Data\UserData\mprBaseLevel.xml file.

The node should be named - mprBaseLevel.

The node can contain the following properties:

If specifying the path to a file or folder stored on a network drive on the local network, the path must be in UNC format!

Properties can be combined. If using the properties (ConfigurationsFolder or ConfigurationsFolder + ConfigurationFile or ConfigurationFile + CanUseUserConfigurationFile or ConfigurationFile + ConfigurationsFolder + CanUseUserConfigurationFile) results in multiple configuration files, a drop-down list with configuration file selection appears in the information box. If the CanUseUserConfigurationFile property is set to True, the "User configuration file" position will be added to the list of configuration files.

The files located in the folder specified in the ConfigurationsFolder property must contain valid data for the plugin. Files are not checked for content! Incorrect xml files can lead to errors!

Example of settings:

An example of plugin window with these settings:

It is possible to differentiate access to the configuration files using Active Directory service. If a user has no access to edit a configuration file, he will be notified accordingly in the plugin window, and all configuration editing functionality will be disabled. That is, the configuration file will be read-only.

The organization settings for the Parametrization plugin allows to override the path to the configuration storage file. By default, user configuration settings are stored in %appdata%\ModPlus Data\UserData\mprColorizer.xml file.

The node should be named - mprColorizer.

The node can contain the following properties:

If specifying the path to a file or folder stored on a network drive on the local network, the path must be in UNC format!

Properties can be combined. If using the properties (ConfigurationsFolder or ConfigurationsFolder + ConfigurationFile or ConfigurationFile + CanUseUserConfigurationFile or ConfigurationFile + ConfigurationsFolder + CanUseUserConfigurationFile) results in multiple configuration files, a drop-down list with configuration file selection appears in the information box. If the CanUseUserConfigurationFile property is set to True, the "User configuration file" position will be added to the list of configuration files.

The files located in the folder specified in the ConfigurationsFolder property must contain valid data for the plugin. Files are not checked for content! Incorrect xml files can lead to errors!

Example of settings:

An example of plugin window with these settings:

It is possible to differentiate access to the configuration files using Active Directory service. If a user has no access to edit a configuration file, he will be notified accordingly in the plugin window, and all configuration editing functionality will be disabled. That is, the configuration file will be read-only.

The organization settings for the Copy values plugin allows to override the path to the configuration storage directory. By default, user configuration settings are stored in %appdata%\ModPlus Data\UserData\CopyParameterConfigurations file.

The node should be named - mprCopyParameterValues.

The settings consist of one property - ConfigurationDirectory - in the value of which the path to the configuration storage directory is specified. The path must point to the existing configuration storage directory.

If specifying the path to the configuration storage directory located on a network drive on the local network, the path must be in UNC format!

Example of settings:

An example of plugin window with these settings:

It is possible to differentiate access to the configuration files using Active Directory service. If a user has no access to edit a configuration files, he will be notified accordingly in the plugin window, and all configuration editing functionality will be disabled. That is, the configurations will be read-only.

The organization settings for the Dimensions by line plugin allows to override the path to the configuration storage file. By default, user configuration settings are stored in %appdata%\ModPlus Data\UserData\mprDimByLine.xml file.

The node should be named - mprDimByLine.

The node can contain the following properties:

If specifying the path to a file or folder stored on a network drive on the local network, the path must be in UNC format!

Properties can be combined. If using the properties (ConfigurationsFolder or ConfigurationsFolder + ConfigurationFile or ConfigurationFile + CanUseUserConfigurationFile or ConfigurationFile + ConfigurationsFolder + CanUseUserConfigurationFile) results in multiple configuration files, a drop-down list with configuration file selection appears in the information box. If the CanUseUserConfigurationFile property is set to True, the "User configuration file" position will be added to the list of configuration files.

The files located in the folder specified in the ConfigurationsFolder property must contain valid data for the plugin. Files are not checked for content! Incorrect xml files can lead to errors!

Example of settings:

An example of plugin window with these settings:

It is possible to differentiate access to the configuration files using Active Directory service. If a user has no access to edit a configuration file, he will be notified accordingly in the plugin window, and all configuration editing functionality will be disabled. That is, the configuration file will be read-only.

The organization settings for the Elements join plugin allows to override the path to the configuration storage file. By default, user configuration settings are stored in %appdata%\ModPlus Data\UserData\mprJoin.xml file.

The node should be named - mprJoin.

The node can contain the following properties:

If specifying the path to a file or folder stored on a network drive on the local network, the path must be in UNC format!

Properties can be combined. If using the properties (ConfigurationsFolder or ConfigurationsFolder + ConfigurationFile or ConfigurationFile + CanUseUserConfigurationFile or ConfigurationFile + ConfigurationsFolder + CanUseUserConfigurationFile) results in multiple configuration files, a drop-down list with configuration file selection appears in the information box. If the CanUseUserConfigurationFile property is set to True, the "User configuration file" position will be added to the list of configuration files.

The files located in the folder specified in the ConfigurationsFolder property must contain valid data for the plugin. Files are not checked for content! Incorrect xml files can lead to errors!

Example of settings:

An example of plugin window with these settings:

It is possible to differentiate access to the configuration files using Active Directory service. If a user has no access to edit a configuration file, he will be notified accordingly in the plugin window, and all configuration editing functionality will be disabled. That is, the configuration file will be read-only.

The organization settings for the Filter selection plugin allows to override the path to the configuration storage file. By default, user configuration settings are stored in %appdata%\ModPlus Data\UserData\mprFilterSelection.xml file.

The node should be named - mprFilterSelection.

The settings consist of one property - ConfigurationFile - in the value of which the path to the configuration storage file is specified. The path must point to the existing configuration storage file, which can even be empty (you can create an empty text file and change the extension from .txt to .xml).

If specifying the path to a configuration file stored on a network drive on the local network, the path must be in UNC format!

Example of settings:

An example of plugin window with these settings:

It is possible to differentiate access to the configuration file using Active Directory service. If a user has no access to edit a configuration file, he will be notified accordingly in the plugin window, and all configuration editing functionality will be disabled. That is, the configuration file will be read-only.

The organization settings for the Floor by Room plugin allows to override the path to the configuration storage file. By default, user configuration settings are stored in %appdata%\ModPlus Data\UserData\mprFloorByRoom.xml file.

The node should be named - mprFloorByRoom.

The settings consist of one property - ConfigurationFile - in the value of which the path to the configuration storage file is specified. The path must point to the existing configuration storage file, which can even be empty (you can create an empty text file and change the extension from .txt to .xml).

If specifying the path to a configuration file stored on a network drive on the local network, the path must be in UNC format!

Example of settings:

An example of plugin window with these settings:

It is possible to differentiate access to the configuration file using Active Directory service. If a user has no access to edit a configuration file, he will be notified accordingly in the plugin window, and all configuration editing functionality will be disabled. That is, the configuration file will be read-only.

The organization settings for the Parametrization plugin allows to override the path to the configuration storage file. By default, user configuration settings are stored in %appdata%\ModPlus Data\UserData\mprParametrization.xml file.

The node should be named - mprParametrization.

The node can contain the following properties:

If specifying the path to a file or folder stored on a network drive on the local network, the path must be in UNC format!

Properties can be combined. If using the properties (ConfigurationsFolder or ConfigurationsFolder + ConfigurationFile or ConfigurationFile + CanUseUserConfigurationFile or ConfigurationFile + ConfigurationsFolder + CanUseUserConfigurationFile) results in multiple configuration files, a drop-down list with configuration file selection appears in the information box. If the CanUseUserConfigurationFile property is set to True, the "User configuration file" position will be added to the list of configuration files.

The files located in the folder specified in the ConfigurationsFolder property must contain valid data for the plugin. Files are not checked for content! Incorrect xml files can lead to errors!

Example of settings:

An example of plugin window with these settings:

It is possible to differentiate access to the configuration files using Active Directory service. If a user has no access to edit a configuration file, he will be notified accordingly in the plugin window, and all configuration editing functionality will be disabled. That is, the configuration file will be read-only.

The organization settings for the Section annotation plugin allows to override the path to the configuration storage file. By default, user configuration settings are stored in %appdata%\ModPlus Data\UserData\mprSectionAnnotation.xml file.

The node should be named - mprSectionAnnotation.

The settings consist of one property - ConfigurationFile - in the value of which the path to the configuration storage file is specified. The path must point to the existing configuration storage file, which can even be empty (you can create an empty text file and change the extension from .txt to .xml).

If specifying the path to a configuration file stored on a network drive on the local network, the path must be in UNC format!

Example of settings:

An example of plugin window with these settings:

It is possible to differentiate access to the configuration file using Active Directory service. If a user has no access to edit a configuration file, he will be notified accordingly in the plugin window, and all configuration editing functionality will be disabled. That is, the configuration file will be read-only.

Organization settings for the Sheet export plugin allow you to set the rules for watermarking when exporting to PDF.

The node should be named – mprSheetExport.

The settings consist of 4 obligatory properties:

Example of settings:

The exclusions file (WatermarkExclude property) specifies the names of documents that do not require a watermark to be added, even if watermarking is enabled (Watermark = True). Each value must be specified on a new line in the file. Only part of the name can be specified in the file. For example, if a document in Revit is named RAC_basic_sample_project and the file has the value RAC_ or the value _sample_, the document will not add a watermark when exported to PDF.

In the rules file (WatermarkRules property) you add watermark rules. Each rule must be placed on a new line. If a line in the file starts with a # character, the line will not be processed by the plugin. Each rule consists of 7 properties, separated by a comma. The start and end spaces of each property are ignored by the plugin. Properties in a string must be arranged in the following order:

If no rule from the file matches the name of the Title Block (or there are no rules in the file), the plugin will use a rule with the values ",185,65,0,RED,5,isocpeur.ttf".

Example of filling out a rules file:

The organization settings for the Parametrization plugin allows to override the path to the configuration storage file. By default, user configuration settings are stored in %appdata%\ModPlus Data\UserData\mprWorksets.xml file.

The node should be named - mprWorksets.

The node can contain the following properties:

If specifying the path to a file or folder stored on a network drive on the local network, the path must be in UNC format!

Properties can be combined. If using the properties (ConfigurationsFolder or ConfigurationsFolder + ConfigurationFile or ConfigurationFile + CanUseUserConfigurationFile or ConfigurationFile + ConfigurationsFolder + CanUseUserConfigurationFile) results in multiple configuration files, a drop-down list with configuration file selection appears in the information box. If the CanUseUserConfigurationFile property is set to True, the "User configuration file" position will be added to the list of configuration files.

The files located in the folder specified in the ConfigurationsFolder property must contain valid data for the plugin. Files are not checked for content! Incorrect xml files can lead to errors!

Example of settings:

An example of plugin window with these settings:

It is possible to differentiate access to the configuration files using Active Directory service. If a user has no access to edit a configuration file, he will be notified accordingly in the plugin window, and all configuration editing functionality will be disabled. That is, the configuration file will be read-only.