How are default WorkSet Properties modified

When a workset is created, there is an option to create new WorkSet Properties.  These can be added and edited later from the workset menu.

There are also default Workset Properties such as Project Name, Project Number, etc.  Where can these properties be modified?  The workset menu only shows the properties I created.  Under the File Properties within a DGN there is a section called WorkSet Properties where I can see both the default and user added properties (all properly greyed out since they shouldn't be edited within the file).  But I can only edit the ones I added.  How do I edit the default Workset Properties?

I'm investigating using the workset properties to populate sheet number block items such as the "Project Number" that will go on all sheets.  Once the Workset Properties are set and all the pertinent properties can be edited; is it possible to save that as a workset template (to be used on all projects)?

(I've also tested using properties within the Sheet Index properties, and have the same question about having a DGNWS template.)

Using OpenRoads Designer Version 10.04.00

Parents
  • The answer to your first question is that the properties are stored in the worksets DGNws file. You can open the DGNws file and edit any of the properties, they are stored on the file header. Any changes will be written to files opened with that workset active.

    You can have a workset template or a DGNws seed for creating new workset. There are configuration variables to set this up and you can create a base workset to work as a template if you want. A workset template is more detailed than a DGNws seed, the workset template also contains the dgnws but also folders and other files can be included.  There are several TR's on this concept so tread where you want with caution.

    Regarding Sheet indexing note that the Workset custom properties and sheet indexing properties and custom properties are somewhat different. Text fields, reporting, etc. can use either. One set is stored on the model (sheet models inparticular) the other is stored on the file.

    HTH

    ~HTH

    John.

    yep

    Answer Verified By: Stephen Chapman 

  • How do I change the default properties on the file header?  When I go to the Edit WorkSet area I can change the default "Description" variable and the variables I added.  The other default variables are not available here.

    Then when I go to the File Properties of a DGN in the WorkSet I can see both the "default" properties and the ones I could edit in the above screen.  How can these circled attributes be edited?

    When I used this DGNWS as a seed (either on the use template option on the create workset dialog OR in the configuration variables) my added workset variables do not come across.

    I fared better using the Sheet Index variables.  I added three subfolders to the Sheet Index, each with their own sheet numbering rules, plus I added some Sheet Index variables.  These all came over when using the DGNWS as a seed.  However they came across as a group with the seed DGNWS name.  A second empty group with the active DGNWS name was also included.  This seems rather awkward; I'd rather have the seed group renamed to the new DGNWS name - I think I saw another thread about that.

    One other oddity is that the Sheet Index variables do not show up in the Manage Sheet Index dialog.  They can be seen and modified in the Properties tab, but not in the dialog.

    SCC.dgnws

    For my application I think I'd rather use the workset properties than the Sheet Index properties since, as you point out, they are more universally available.  But at the moment the Sheet Index variables seem to work better.

    ORD-2018 Release 2 Update 4 - Version 10.04.00.48

  • I don't know or see why those wouldn't be copied forward. In my quick test I created a WorkSet "Testing" with a custom property "test" = "this is a test". I then created a new workset "blueZoo" and used "Test" as my template. The blueZoo workset has a custom property on it set as "test" = "this is a test"

    I then copied test.dgnlib to my templates folder and renamed it to "WorkSetTemplate.dgnws". I created a new workset "redZoo" with template = none. This new workset did not contain the custom property. I would of thought it should. I believe this is a bug from my limited testing. Maybe Bentley could look at it further.

    ~HTH

    John.

    yep

  • HI all, I see the same issues with the DGNWS not copying the custom properties from the defined _USTN_WORKSETDGNWS cfg.  The template has custom properties, the new workset gets created, with the new dgnws, named to match the workset, but no custom properties.  Is appears to be a bug?  CE Update 10 and ORD 3 both show the same results, no custom properties on the copy of the template dgnws.

    Thanks

    Craig

  • Hi All,

    I have followed John Frampton's advice below to modify the defualt WorkSet properties. I have made these changes within AECOsim CEU4 (in Microstation mode), I then saved settings, closed the file and open a dgn file associated to the same Workset all works fine and i can see the properties have been carreid across to the other files. See below.

    However as soon as I closed down AECOsim and restarted, the properties get wiped.

    What could be doing this? Is there something in the config at Local / Organisational level that could be wiping these? It doesnt matter if i reopen in Microstation or AECOsim mode, the properties keep getting deleted.

    Appreciate any help.

     

    AECOsim SS6 + CONNECT U4, Windows 7 Pro, 64Bit, Intel Xeon E3-1275 v5 @ 3.6GHz, 32GB RAM, NVIDIA Quadro P1000

  • I tired to enter values for those properties also and they where wiped out as soon as I did a save or save settings or the application saved. I believe that set of properties is reserved for CONNECTED projects and it is syncing the values from there and since you may not have a connected project then the values are null and it syncs them to null. Oddly enough I created my own property value set and they are un-editable from the properties dialog, the value change back to my original values when I do a save. The only place I can edit my property value is from the Work Page.  This I would consider a bug as the values if un-editable should be ghosted/locked.

    ~HTH

    John.

    yep

  • Please see screengrabs below for sources of the WorkSet properties.

    Those preceded by Project are populated by a CONNECTED Project (note the screen grabs are not from a CONNECTED Project, I don't have a suitable one to hand at this minute).

    I see that an edit made to a custom property from the File Properties within the DGNWS is not retained, I suspect the defect is that these fields have been left editable in this context.
    We recommend only editing custom WorkSet properties from the BackStage WorkSet Properties dialog.

    It also appears that the WorkSpace property is editable when file properties are shown in a DGNWS, which is definitely a defect!

    I have filed Defect 1007045:
    "When the File Properties dialog is opened in a DGNWS, WorkSet Properties can be edited which a) should not be possible b) conflicts with other inputs. Make then read-only."

    Marc

Reply
  • Please see screengrabs below for sources of the WorkSet properties.

    Those preceded by Project are populated by a CONNECTED Project (note the screen grabs are not from a CONNECTED Project, I don't have a suitable one to hand at this minute).

    I see that an edit made to a custom property from the File Properties within the DGNWS is not retained, I suspect the defect is that these fields have been left editable in this context.
    We recommend only editing custom WorkSet properties from the BackStage WorkSet Properties dialog.

    It also appears that the WorkSpace property is editable when file properties are shown in a DGNWS, which is definitely a defect!

    I have filed Defect 1007045:
    "When the File Properties dialog is opened in a DGNWS, WorkSet Properties can be edited which a) should not be possible b) conflicts with other inputs. Make then read-only."

    Marc

Children
  • "When the File Properties dialog is opened in a DGNWS, WorkSet Properties can be edited which a) should not be possible b) conflicts with other inputs. Make then read-only."

    Not sure I agree with your logic here. A property should be able to be edited in many ways, when and were the user needs to edit them. Tool in MSTN edit properties all the time, eg change attributes tool. Maybe the CONNECT project Properties and WorkSpace shouldn't be able to be edited but a property that a user defines or the description should be able to be edited in either the WorkPage or file properties of the DGNws.

    After looking at this a bit more I only see the values reset when using ORD. In MSTNCE.11 the vales are all editable and hold the values. When the WorkSpace value is edited things go awry.

    ~HTH

    John.

    yep

  • I tend to agree with John Frampton; there should be more than one way to edit these properties.  But I see that editing them in the DGNWS properties window is not very elegant.  It would be nice to be able to edit those properties (the default properties and the user added properties) in the backstage area on the Edit Workset dialog.  Editing the properties on the Connected Project window above is problematic for this office since we are not allowed to use that feature (cloud storage) in our security environment.  

  • The 'Project *' properties were all created specifically for use by CONNECTED Projects so we won't make them available for free editing. The custom properties are available for that purpose, so where cloud services are unavailable appropriate custom WorkSet properties can be created. The WorkSet Properties dialog is designed for that enabling adding, editing and deleting custom properties. The general Properties dialog is only designed to allow values to be edited.

    I can see a workflow where it would sometimes be time-saving for someone working in a DGNWS to quickly edit a property via the Properties panel. On the other hand we are often criticised for failing to consolidate settings in single locations, so I would suggest that we stick to the WorkSet Properties dialog for this with its UI designed for that purpose.

    Does editing custom WorkSet properties occur with such frequency that we need to add a mechanism to the general Properties dialog that can write to the DGNWS?

    Marc

  • Does editing custom WorkSet properties occur with such frequency that we need to add a mechanism to the general Properties dialog that can write to the DGNWS?

    Editing them from the Work page or when in the DGNws from the properties works fine, if it works correctly. In my case there seems to be a bug in ORD regarding editing these from Properties as it is not possible.  In MSTN the bug as far as I can see is that WorkSpace is editable. The "Project" properties are fine with be editable if they sync to the CONNECTed project if/when it is made CONNECTed.

    ~HTH

    John.

    yep