Bentley Communities
Bentley Communities
  • Site
  • User
  • Site
  • Search
  • User
ProjectWise
  • Product Communities
ProjectWise
ProjectWise Design Integration Forum ProjectWise Managed WorkSpace and Predefined variables
    • Sign In

    • State Not Answered
    • Replies 0 replies
    • Subscribers 60 subscribers
    • Views 121 views
    • Users 0 members are here

    ProjectWise Managed WorkSpace and Predefined variables

    Kevin van Haaren
    Offline Kevin van Haaren 4 months ago

    Over the years several predefined variables have been added to the different CADD products but those variables aren't available in ProjectWise Managed workspace when it is copying out files and compiling the config file it hands off to the CADD product.

    ProjectWise's managed workspace is a 2 pass system, first ProjectWise processes all the config files, copies out the files from ProjectWise to the working directory, and builds a config file to hand off to appropriate CADD product when launched. During the copy out phase if you use one of the predefined variables for a path or to make a decision ProjectWise will not copy out the correct files or make a correct decision.

    I'm seeing this with the following variables I use in ORD 10.10

    _USTN_PRODUCT_ONE_GROUPNAME
    _USTN_PRODUCT_ONE_SUBGROUPNAME
    _USTN_PRODUCT_VERSION_BUILD
    _USTN_PRODUCT_VERSION_GENERATION
    _USTN_PRODUCT_VERSION_MAJOR
    _USTN_PRODUCT_VERSION_MINOR
    

    My testing also showed _PLATFORMNAME is missing, but I don't use that variable.

    My use for _USTN_PRODUCT_ONE_GROUPNAME is to have some files in our Organization folder be used with Bentley's Civil products ORD, OBM and OpenRail. To do this I created the folder Civil in our _USTN_ORGANIZATION folder. Inside that folder I put a Civil Standards.cfg file. That cfg file should be automatically loaded by the Connect One Configuration sections of the msconfig.cfg file, but the cfg file is never copied out because during the copy out phase _USTN_PRODUCT_ONE_GROUPNAME is null.

    I worked around the problem by adding the following to our WorkSpaceSetup.cfg file:

    #--- Product variables used in client configurations
    # Because of how ProjectWise Managed Workspaces don't have a full set of the
    # predefined variables until the product actually launches, these are set based
    # on enginename rather than the built-in One Configuration variables
    %if $(_ENGINENAME) == "OpenRoadsDesigner"
    	_USTN_PRODUCT_ONE_GROUPNAME       = Civil
    	_USTN_PRODUCT_ONE_SUBGROUPNAME    = Roads
    %elif $(_ENGINENAME) == "OpenRailDesigner"
    	_USTN_PRODUCT_ONE_GROUPNAME       = Civil
    	_USTN_PRODUCT_ONE_SUBGROUPNAME    = Rail
    %elif $(_ENGINENAME) == "OpenBridgeModeler"
    	_USTN_PRODUCT_ONE_GROUPNAME       = Civil
    	_USTN_PRODUCT_ONE_SUBGROUPNAME    = Bridge
    %endif
    

    Working around the various _USTN_PRODUCT_VERSION_ variables not being available is trickier but you can do it by either reading the value out from the registry (which differs slightly from the actual variables values) or using the _USTN_PRODUCT_FULLMARKETINGNAME variable, which is properly set.

    • Sign in to reply
    • Cancel

    Communities
    • Home
    • Getting Started
    • Community Central
    • Products
    • Support
    • Secure File Upload
    • Feedback
    Support and Services
    • Home
    • Product Support
    • Downloads
    • Subscription Services Portal
    Training and Learning
    • Home
    • About Bentley Institute
    • My Learning History
    • Reference Books
    Social Media
    •    LinkedIn
    •    Facebook
    •    Twitter
    •    YouTube
    •    RSS Feed
    •    Email

    © 2023 Bentley Systems, Incorporated  |  Contact Us  |  Privacy |  Terms of Use  |  Cookies