Where does the form reside when a user saves using the Save button?

Comments

6 comments

  • Avatar
    Ron Hall

    If a task is assigned to a user, either through their task list or through a link to anonymous form, the data contained in the controls on the form is held in the AgilePoint schema in the AgilePoint database.  If you have a Save button on the form, the user can add or edit any data on the form and click Save.  If they then close their browser window, the task is still available in the task list or at the link the same as before.  When the user opens the task, regardless of the computer being used, the data they will see in the controls on the form is what was saved.

    In this way, the Save button allows users to enter or edit data on large forms, save what they have done, close the browser and come back to their task at a later time.  This is a very powerful feature for your users.  The only limitation is that it can't be done on the Start task screen since Start task has not yet been submitted, hence the process is not started, so there is no schema for this instance in the AgilePoint database.

    0
    Comment actions Permalink
  • Avatar
    Nik

    This also has a limitation when users may want to work on multiple process instances at the same 'time' yet not submit yet. We have dynamically added a save button to the form with JS to store the value in a radio button. A condition checks that value and loops back to the original task, assigning it to the same user, and resetting the radio button to blank. Then the data is stored in the schema and the user can find it in the task list.

     

    Otherwise the user cannot start on a new process until they finish the first one, and they may not have all the data from the customer, etc. 

    0
    Comment actions Permalink
  • Avatar
    David Moore

    @nik Chaphalkar can you give me some more information on how you use JS to store the value in a radio button? Im using an app for employee evaluations and that would be pretty nice to have users to be able to save information put in on one employee save it start on another one instead of having to finish one employee before starting another. 

    0
    Comment actions Permalink
  • Avatar
    Karl Makatenas

    Remove the Save button and include a Radio button that asks, "Do you want to move this form forward or keep it for editing?"  A Conditional activity will loop back to the task depending on this radio button.

    Nik mentioned he did some JavaScript, but no code is necessary for this base solution; it was likely additional logic within the form to manipulate the "Submit" button and improve the feel of submission.

    1
    Comment actions Permalink
  • Avatar
    David Moore

    Thank you @Karl

    0
    Comment actions Permalink
  • Avatar
    Nik

    Karl is right - we used to have a custom button and it stored the value to a radio button and then triggered 'Submit'

     

    But since then we have simplified and the user simply interacts with the radio button which has the values 'save for later' and 'submit now' and then the user interacts with the native 'Submit' button. Much less to deal with.

    Then there is a condition which takes the process to an activity with the same or similar form based on the radio button.

    0
    Comment actions Permalink

Please sign in to leave a comment.