Menu Editor for Flat Sets

Using the Menu Editor I can create a custom menu in ProjectWise and when I select Documents everything works fine but not Document Sets.
I am using Command Type: Document Command
Required Mask: 1 (Documents), 2 (Document Sets)

I have tried making the Mask 0 but it makes no difference, I still cannot use my custom menu on Flat Sets.
What am I missing?

ProjectWise 10.00.03.434

Parents
  • ,

    Please post some screenshots of the .MRR properties as well as the code behind the menu commands.

  • Document Command menu items were under a Pull Down Menu.
    That Pull Down Menu had Document Selected as a Required Mask.
    Removing the Document Selected from the pull down has the menu items working correctly.

    I did like how the menu was grayed out when no documents were selected.
    Is there a way to make the Pull Down Menu gray out unless either a Document or Document Set is selected?
    When I check both it's an impossible task.

  • If I understand your problem, it comes done to the "easy to use" filters on the .MRR tool are "hard coded" for AND or OR operations.  In other words, if you require a document to be selected and also require that a flat set is selected, then you have a "catch-22" situation because a document is not a flat set, and a flat set is not a document.

    Without testing, I would think that it would work if you had both a document AND a flat set selected, but I didn't test that.

    Here's what the documentation for Ignore Mask, Required Mask, and State Function says:

    So, the way around this particular problem is to use a "State Function".  A state function can do everything the Required and Ignore Masks can do, but since you define the logic behind what the state function returns, you can introduce whatever logic makes sense for your needs, like if there is at least one document OR flat set selected, then return zero (display the menu item), otherwise return grayed.  

    BTW, AAMS_HIDED doesn't work and hasn't work for years because hiding menu items caused too many calls to user support desks or to Bentley support because, well it was WAD.  For example, a user would report a problem because they could not find the Delete document command, but the reason was because it was hidden (by design) because the user had not selected any documents to delete!  So, the new rule was that ProjectWise Explorer would never hide any menu command, but would only gray them out if they were not available or did not apply.

    Now if you use the API menu functions (see the MYMENU sample), you can control your menus fully, including "hiding" (not displaying) your menu items if your logic dictates that action. 

    HTHs

Reply
  • If I understand your problem, it comes done to the "easy to use" filters on the .MRR tool are "hard coded" for AND or OR operations.  In other words, if you require a document to be selected and also require that a flat set is selected, then you have a "catch-22" situation because a document is not a flat set, and a flat set is not a document.

    Without testing, I would think that it would work if you had both a document AND a flat set selected, but I didn't test that.

    Here's what the documentation for Ignore Mask, Required Mask, and State Function says:

    So, the way around this particular problem is to use a "State Function".  A state function can do everything the Required and Ignore Masks can do, but since you define the logic behind what the state function returns, you can introduce whatever logic makes sense for your needs, like if there is at least one document OR flat set selected, then return zero (display the menu item), otherwise return grayed.  

    BTW, AAMS_HIDED doesn't work and hasn't work for years because hiding menu items caused too many calls to user support desks or to Bentley support because, well it was WAD.  For example, a user would report a problem because they could not find the Delete document command, but the reason was because it was hidden (by design) because the user had not selected any documents to delete!  So, the new rule was that ProjectWise Explorer would never hide any menu command, but would only gray them out if they were not available or did not apply.

    Now if you use the API menu functions (see the MYMENU sample), you can control your menus fully, including "hiding" (not displaying) your menu items if your logic dictates that action. 

    HTHs

Children