We need the possibility to hide "Send to Meridian Portal" in specific context

We seem to miss the functionality the hide the "Send to Meridian Portal" command in the PowerWeb client and or the functionality to catch the event in the Configurator.

We need to block this functionality in case the document is in the wrong context, has invalid property values, wrong status, wrong location (not a ProjectCopy), etc.

Can this be made possible because now the command can be started from anywhere in the Meridian vault.

Kind regards

  • Ronald Kock
  • Mar 12 2020
  • Future consideration
Meridian Server
  • Attach files
  • Marco Russian commented
    26 May, 2021 10:01pm

    HI Rudi,


    I agree with Hans, we need a way of controlling the event. Something like SendToPortal_IsVisible and/or BeforeSendToPortal event would be very useful to extend the cabability of the command.


    Attachments Open full size
  • Hans van Koelen commented
    23 Mar, 2020 11:55am

    Hi Rudi,

    This depends if you want to have the document send out in a workflow. Issue are still the unchanged documents returned from the Portal. When they are automatic revoked i can work. In our use case we have a property that should control the availability of "Send to Portal", the best way to deal with this is to have a script event so we can abort the command.

    Attachments Open full size
  • Admin
    Rudi Pieters commented
    23 Mar, 2020 11:14am

    Upcoming in Meridian 2020 R2: the ability to send a document to Portal on a workflow transition. Then you could hide the Send to Portal command in a Scope and control the visibility of the workflow transition. Would this address the use case?

    Attachments Open full size

Related ideas