For MicroStation V8i SS releases it is not uncommon for me to have 20 or more different MicroStation startup icons on my Windows desktop, each launching MicroStation with a different client workspace.
In MicroStation CONNECT I started down the path of configuring WorkSpaces and WorkSets to eliminate the need for all of those different icons. I did have some initial success in accomplishing this goal, but alas was foiled again, and I am back to having different MicroStation CONNECT startup icons for different client configurations.
The roadblock I've come across is branded dgn files and conflicting WorkSpace names.
As a Consultant you want to use the same WorkSpace and WorkSet names as the Client is using so nobody has to rebrand the hundreds of dgn files when the project dgn's are handed over. Not only can you have duplicate WorkSpace names from multiple clients, but mixing different terminology. One client might use the WorkSpace name Bridge, another might use the name Structures, even more confusing one client might use the term Electric for a WorkSpace name and another might use Electrical. Having all of those mixed into a single WorkSpace listing is just one big mess. That is why I've had to revert back to the different startup icons for different configurations to segregate the different WorkSpace names.
I think a possible solution would be a selectable _USTN_ORGANIZATION level, under which you would have a unique set of WorkSpaces available.
So to summarize:
The current design assumes a single organization, you would like to have multiple organizations available?
Marc
Yes, I think that would alleviate this problem.
That not only solves the issue I referenced above, but also reduces the amount of configuration file gymnastics you have to through to remap each client's _USTN_ORGANIZATION definition.
Rod WingSenior Systems Analyst
OK, and just to clarify the use case, this in the context of providing consultancy; once a configuration is delivered the end user will only have one organization?
Most likely, yes.
It would probably be best if the Organization was not branded to the dgn file like the WorkSpace and WorkSet are. That gives the consultant flexibility in changing the name to better fit the individual client.
Rod,
I used to be like you years ago. The biggest thing that changed the way I deliver builds was finding a way I could use variables to deliver our company and client builds at the touch of a button. It's well worth having a look at the hta interface, it's just basically a html way to run scripts and set variables, but becomes a very powerful tool once you get your head around a few things.
Have a look at:
I'll have some updated blogs soon on using the CE variables, but it's pretty easy to translate across what I've done here. Feel free to check out my other blogs on the subject as well.