Hi
How do I export drawing rules made in a workset? I've created some structural rules, and now I want to distribute them to my organization. Do the rules get stored in the dgn-file? In that case, how do I extract them to a .rul-file?
Regards,
Robert
Hi Robert,
Rules are stored in the location pointed to by STFFILE_DRAWINGRULES. The Swedish default location is C:\ProgramData\Bentley\OpenBuildings CONNECT Edition\Configuration\Datasets\Dataset_SE\Rules.
The changes that you have made will be in the current STFFILE_DRAWINGRULES location. You can find this in the Configuration variables dialog or with the key-in expand echo $(STFFILE_DRAWINGRULES) which will show the currnet value of STFFILE_DRAWINGRULES in the Message Center. (this works for any variable, just insert the variable that you want to find out about into the key-in.)
STFFILE_DRAWINGRULES can be set at Organization, WorkSpace or WorkSet levels as required to deploy one or multiple versions of Structural Rules as required.
Marc
Answer Verified By: Robert Högberg
A related question. You say I can set drawing rules at different levels. I had the variable set at organization level at first. But when a append or prepend a rule-file at workset level too, all rules at organization level disappears. The only visible rule is "No display". (Which is not visible when I only have the organization rules).
Am I only allowed to have one rule-file? I want the possibility to add rules for everyone in my organization. But they can't write to that file, so for their own rules, they need to read/write to a workset level rule file.
Robert, this has been discussed on and off over the years, but I assume things haven't changed and you can only configure to a single rule file.
Seems really limiting. Guess I'll file a request for that!
Depends on how you do your rule files. I tend to find I have a separate one from Company down to each client as the levels each client has varies. If it does come to needing different rules for different projects (within the same client or company build), then I tend to have one main rule file and set the seed rules that users can load, that way I have the rules for each discipline drawing on the project pre-defined. It cuts many of the issues down with users picking the wrong rule files. I have a button for each discipline that the users click to load the seed extractions. You could do the same, though a little more long winded, for dynamic views. Perhanps a dgnlib per project (if required) with the rules set for the views.
Ok. But I don't know. I find it easier that I manage a rule-file on organization level, and the users manage the one on workset level if there's some special rules that project requires. Don't see why .rul can work just like all .dgnlib .cel and so on does.
I suppose that's where we differ, we tend to lock things down when it comes to rule files. Tend to find people always reinventing the wheel, but I get when you mean.