Hoppa till huvudinnehållet

Is it possible to edit the permissions alert in viewer?

Kommentarer

6 kommentarer

  • Tom Neer

    @Valerie Squire? Probably, if you are using the On-Premise version, but you if hunt down the Alert text and change it, you will have to remember to do that with every upgrade.

     

    How about using the Get User Info activity at the beginning of the Workflow and check if the user is "guest/anonymous" and if they are then display a form letting them know that they need to login, then exit?

    0
  • Zack Robison

    I executed a quick search for this text in the viewer language (gvh\Resources\Locales, gvh\resources\compiled) but didn't get any results, though i did find similar text in the ...\Locales\Mapping-en-US.json. This text may be living in the Essentials .dlls.

     

    If that is indeed the case, Tom's solution is probably the least work. You might want to see if anyone in the Essentials forums knows.

    0
  • Permanently deleted user

    @Tom Neer?  @Zack Robison?  thank you for your responses. My issue with adding the get user info activity and sign in alert message at the beginning of workflow is that once the user clicks on the workflow, initially that alert message pops up "You do not have permission to open this workflow" and then the alert message that I created pops up after (because it is tied to that workflow).

     

    I will go check of the Essentials forums, and thank you both again for your help!

    0
  • Stefan Schweigert

    Hi Valerie,

     

    That message originates from within Workflow and cannot be directly updated currently. Please post an Idea if you are interested in the ability to change this warning.

     

    Thanks, Stefan

    0
  • Tom Neer

    @Valerie Squire? Is the permissions restriction in Essentials or Portal? My suggestion moves the permissions checking from Essentials/Portal and places it wholly within the Workflow. If you do not pass the user check, the Workflow just exits.

     

    Alternatively, you could wrap the 5 Workflow in a 4 Workflow then hide on disable so the users would not see the workflow unless they were logged in. And then have a second Workflow that is guest viewable but not when logged in to the public that is just a dialog saying login for this to run.

    0
  • Permanently deleted user

    @Tom Neer? The permissions restriction is in portal. My understanding that since that user does not have access to that workflow (shared only with organization) that they will get immediately blocked (alert message popups) from the workflow before it can start running and check for permissions when they click on it in the I Want To... menu.

     

    Thank you for your suggestion for the alternative solution, I will give that a try.

     

    0

Du måste logga in om du vill lämna en kommentar.