Automate

 View Only
  • 1.  Tip of the Week - Evolve Web Form Default Buttons

    Employee
    Posted 12-09-2024 12:25

    Every time an Evolve web form view is created, Evolve automatically places default buttons at the bottom of the form.

     

    Examples:

     

     

     

     

    There may be times when the default buttons aren't exactly what you need.  For example, you may want to change the label of a button or use different buttons that perform different actions.

     

    By default, each view you create uses the default buttons.  However, you can choose to use default buttons on No Views, All Views, or specify individual views where the default buttons should be used.

     

    Open the form solution and then go to the first tab in the Workflow section.

     

     

     

    Click on the Properties Window and scroll down to the Form Default Buttons option (close to the bottom).

     

     

     

    Click the box next to the Form Default Buttons option and choose which views to use default buttons.

     

     

     

    In the example below there are five individual views (Submitter, Planning, Accounting, Data Steward, and Resubmit)

     

     

     

     

     

    If you choose All Views, no other action is required.  The default buttons will automatically be used.  However, if you choose No Views, or select any of the individual views, custom buttons need to be added each view where the default buttons are not used. 

     

    Tip:  Don't forget to add the Button Behaviors to each of the custom buttons.

     

    Save and deploy your solution to test custom buttons.



    ------------------------------
    Tammy Lake
    Sales Engineer
    Precisely Software Inc.
    ------------------------------


  • 2.  RE: Tip of the Week - Evolve Web Form Default Buttons

    Employee
    Posted 12-10-2024 12:01

    love it, I learnt something! 

    I was always going to the admin settings to turn off default buttons at the solution level, this approach is so much better and granular. 

    https://help.precisely.com/r/Automate-Evolve/Latest/en-US/Automate-Evolve-User-Guide/Solution-Developer-Help/Workflow-Configuration-Options?tocId=WocPuxnbtshjsi7zstf9Ug

    This is the configuration option : FormDefaultButtons



    ------------------------------
    Jayasri Varyani
    SE
    Precisely Software Inc.
    ------------------------------



  • 3.  RE: Tip of the Week - Evolve Web Form Default Buttons

    Employee
    Posted 12-11-2024 11:15

    That's awesome.  There are so many little, less obvious helpful things you can do to improve the Evolve solution developer and user experience.  I love it when we can help each other find them.



    ------------------------------
    Tammy Lake
    Sales Engineer
    Precisely Software Inc.
    ------------------------------



  • 4.  RE: Tip of the Week - Evolve Web Form Default Buttons

    Employee
    Posted 12-13-2024 09:56

    Thanks, Tammy. 

    I use custom buttons all of the time for the reasons Tammy shared.  There are other reasons to use custom buttons, like checking for various things before the process can move forward, for example:

    • someone has validated their data entries - you can show a custom message instead of the default error
    • someone has filled in a rejection reason prior to rejecting (and yes, you can set this on the workflow node, too)
    • controlling button placement - both order and in relation to a comment field (you may not want to show the process control comments)

    Please remember that status and completion views do not have buttons.

    Happy solution building!

    Sigrid



    ------------------------------
    Sigrid Kok
    Precisely Software Inc.
    ------------------------------