Customize a default setup for Organizer
You can customize Organizer by creating a setup that opens the same templates and categories in all new models. A customized setup is useful if you have templates and categories you want to use in all models. Then you do not need to create or import the templates and categories for each model separately. The customized setup is used when you open Organizer in a model for the first time.
To make the customized property templates and categories available in all models, store the templates in the \ProjectOrganizerData\PropertyTemplates folder and the categories in the \ProjectOrganizerData\DefaultCategoryTrees folder. The templates and categories are stored as in the xml format. Property templatedefinition of object property layout for the property table in object browser
The property template is saved in an .xml file or in the Organizer database.
files have the .propertytemplate file extension and categories have the .category file extension.
The defined location categories are automatically imported but they behave like manually created categories. Automatic categories need to be defined in each model separately.
You can have the folders under any or all of the following folders:
Current modelmodel that is active in Tekla Structures
The current model can be a single-user model, a shared model or a working model.
Project folderfolder that is used for storing Tekla Structures-related files customized for a particular project
, defined in the XS_PROJECT advanced option
Firm folderfolder that is used for storing Tekla Structures-related files customized for a particular organization
A Tekla Structures user can, for example, customize a company’s cloning templates and save them in a sub-folder located under the firm folder. After this, the customized cloning templates can be used in all projects carried out for the company.
, defined in the XS_FIRM advanced option
System folderfolder that is used for storing files that define default settings
, defined in the XS_SYSTEM advanced option
Example of the \system folder:
All templates and categories in these folders are loaded to Organizer when you open it for the first time in a model. If there are many files with the same file name in several different folders, the first file found is loaded and the other files with the same file name are ignored. The search order is always: model, project, firm, system. The roles.ini does not affect this order.
For example, if you have rebar.category , category.category and material.category in the \system\ProjectOrganizerData\DefaultCategoryTrees folder, these files will all be loaded automatically to the categories. If you also have a rebar.category file in the \PROJECT\ProjectOrganizerData\DefaultCategoryTrees folder and in the \model\ProjectOrganizerData\DefaultCategoryTrees folder, only the first rebar.category file found is used. In this case, the file under the model folderfolder that is used for storing files associated with a model
Tekla Structures stores all files associated with a model in a folder it creates with the same name as the model database (.db1).
In multi-user mode all users access the same model folder.
would be the first one found.
You can use the roles.ini files to control multiple setups. For example, create a \Concrete\ProjectOrganizerData folder and a \Steel\ProjectOrganizerData folder under the firm folder. Then define in the roles.ini file which of these folders is read and/or in which order the folders are read. This way you can read only the \Concrete folder files, or read the \Concrete folder first. In this case, the files with the same name in the steel folder are ignored.
The loaded templates and categories are saved in the ProjOrg.db in the \ProjectOrganizer folder under the model folder. When you open Organizer for the first time, the ProjOrg.db is created and the files are read in from the model, project, firm and system folders. The ProjOrg.db database stores all template and category information used in the model. When you make changes to the templates and categories in the folders, they are not automatically updated in ProjOrg.db. The database will not read in the template and category xml files again, so updates to the files will not be automatically applied.
If you want to apply the changed templates and categories to the ProjOrg database, you have two options:
Delete the old templates and categories in Organizer and import the changed templates and categories. We recommend that you use this option.
Export from Organizer all the templates and categories that you want to keep and close the model. Delete the ProjOrg.db database from the \ProjectOrganizer folder under the model folder, and re-open the model. Import the exported templates and categories back to Organizer.Note:
The second option will reset Organizer completely. All data will be lost if not exported.
Excluding object types from Organizer
Some object types can be excluded from Organizer. These object types are listed in the ExcludedTypesFromOrganizer.xaml file that is by default located in the \system\ProjectOrganizerData folder in the Common environmentTekla Structures environment that forms a basis for other environments
The common environment is included in the software installation and includes the global settings, macros, symbols, items, and fonts, for example. The common environment and global settings form the basis for all other environments.
. The location may vary depending on your environment. Excluded object types are not displayed in Object Browser and they are not included in categories, even if you select in the category rules to include a model and all its objects to a category. For example, loads, cuts and fittings are listed in the ExcludedTypesFromOrganizer.xaml file and excluded from Organizer.
You can modify the ExcludedTypesFromOrganizer.xaml file to either include or exclude the object types. Before you modify the file, we recommend that you copy it to the \ProjectOrganizerData folder that is under the model folder. You may need to create the \ProjectOrganizerData folder as it does not by default exist in the model folder.
For example, to exclude fittings, change the value as follows:
<Fitting>true</Fitting> to <Fitting>false</Fitting>
To include fittings again, change the value false back to true.
To apply the changes, clickin Categories to fully synchronize Organizer with the model.
Do not add or remove any lines from the ExcludedTypesFromOrganizer.xaml file, otherwise Organizer will not be able to use the file.