Microsystems.config filesIf you are using DocXtools, you have a Microsystems.config file. But what does it do? If we think of DocXtools like a restaurant, the database is the chef. It is capable of providing you with the Microsystems Ribbons and tools with which you want to work. The config file is the waiter; its job is to tell the database what specific items to serve up to the user.
How can it be altered?The config file, which rests in the C:\Users\%Username%\AppData\Roaming\Microsystems folder, can be edited with a text program. Customer Support typically uses NotePad. We highly recommend contacting your DocXtools specialist or Customer Support before making changes to this file.
All these keys, what do they do?Here are the keys that can be customized:Let's break them down one by one:
- Administrator key: This key controls a user's ability to create enterprise sets for Numbering and Comparison. If this key is set to 'True,' it allows the user to save these sets to the enterprise database and from there it can be distributed to other users as a firm set. This folder is denoted with a star. If the user has this key set to 'False,' they are only able to create personal sets for their own use, which will not be distributed.
- Role key: The most frequently changed key, the role key determines which DocXtools Ribbon will load for each user. This key is case sensitive. To load the roles below, the key would need to read 'Test' or 'Test 2'. If the key is misspelled, left blank, or refers to a role not present in the database it will load the Default role instead.
- networkDirectory key: This key affects the location from which users automatically acquire updated Databases. The location should include the server name and folder within which the database is stored. For example, if you directed it to '\\servername\folder,' DocXtools looks for a file within on the designated server in the named folder.
- distributeDirectory key: Administrator's installation only. This key is set in the Microsystems Administrator to designate the network location to place a custom configuration for distribution to the users. This location can vary by user group if there are different custom configurations for different users.
- lastupdatedMicrosystemsconfig key: This key works the same as previous key, but works to change the config file to the most up to date.
- lastupdatedMicrosystemsDataEnterprisemdxt key: This is the key that keeps your database up to date. It works by comparing the date in the key against the time stamp associated with the Microsystems.Enterprise.mdxt on the network. If the time in this key is older than the time stamp associated with the database, it will copy the new database into the correct location so that it is used. After that it will change the time on the key to the time that the updated database was pulled for use and the old database is replaced. It does not change the displayed time to match the database.