1
0
-1

I have a Maestro 17.10.6 form, which has the online save enabled in the form properties, and the save buttons visible, but after loading the form in TM and clicking the save option returns a HTTP POST error "The form does not support online save".

Being a maestro form, TM does not show any options for online save in the Flow Config tab, and I know I could probably change the form type to Composer to see the online save options, but doing that may also break some of the settings that are configured correctly by default. 

Any ideas how to solve this issue?

  1. Yulius Gita

    Stephen Smith How did you deploy the form to TM? Is that through SDK app deploy or import form in TM?

  2. Stephen Smith

    It's deployed by building in maestro, and then clicking on the upload icon next to the form version number in the form dashboard in TM

CommentAdd your comment...

2 answers

  1.  
    1
    0
    -1

    The standard template code for the save button is "!Form.isFieldWorker() ? Form.showDialog("saveconfirm") : Form.submit("Saved")". It works on other Maestro forms in 17.10.6 from my expericence, bar this one form. 

    1. Trevor Ward

      Does the form have any Form Rules that would have run prior to your page change?  Does the form or any of its' fields (components) have any Script that might do a background save automatically (other than the save button)?

    2. Stephen Smith

      We've tried with background save on and off. the error appears on the first and subsequent page changes.

    CommentAdd your comment...
  2.  
    1
    0
    -1

    (does this happen first time clicking save, or subsequent clicks?  Does the form have any scripted Form.submit calls?  What script is set in the Template for the Save Button?)

    From Product Team on a similar question, might be relevant:

    This happens in forms in 17.10.6 which are doing a Form.submit('Saved', ..., true) where the true is the skipPostSubmit and continuing in the form. This issue has been raised with the product team and the cause has been identified and will be fixed in the 17.10.7 maintenance release. If you contact the Avoka Client Services resource that is working with your team they will be able to help if this is causing issues before the maintenance release.

      CommentAdd your comment...