1. GoCanvas Help Center
  2. Community
  3. Feature Requests

Conditionally Disable User edit to form based on content.

Permanently deleted user

For instance, if said form is a proposal/estimate contract and not yet signed, then the form should be editable.  However, once the form is signed, then it should be immutable.  Perhaps tie to the "Field Conditions".

0

Comments

4 comments
Date Votes

Please sign in to leave a comment.

  • Sara Kaplow, Community Manager

    Hi Jerre,

    I think there might be a way to accomplish this using a combination of conditions and workflow. It's not elegant, but... it could work. Here's what I'd do: 

    1. Create a checkbox for Approved (user would have to manually check this after the signature is collected). 
    2. Create a screen with a condition to only appear if the Approved checkbox is checked (I put some text on it to tell the user that once they execute the handoff, they won't be able to go back and edit the estimate): 

    3. If there are screens that need to come AFTER the work is approved, they'll all need to take the same condition. 
    4. Set up your workflow to appear after your Conditional Screen and have the setting Next user can edit existing data unchecked:

    5. Configure the workflow as needed as far as who the user can handoff to (if it's going to stay with the same person, I'd recommend doing the handoff based off of a field in the app that defaults to the user's email address). 

    So if the estimate is approved, the user will have to handoff, and anyone after that handoff won't be able to edit the previous screens. If they haven't checked that box yet, they'll avoid the handoff all together. 

    Has anyone else done something like this to achieve the same result? 

     

     

    (Edited )
    0
  • Permanently deleted user

    I'll look at the workflow features,

    0
  • Permanently deleted user

    Hello Sara, I'd come up with a satisfactory work-around for this, but either the behavior of GoCanvas has changed, or I have misunderstood the reason the submission number was changing.

    I had thought, each time that a user edited a prior submission and submitted it again, it would generate a new submission number.  I could use this to determine which Estimate was the latest version.  That it is, the most recent submission number would be the prevailing estimate.  As I pulled these in, I would void the prior Estimates and the most recent estimate would be the current binding estimate. 

    This morning as I am retesting and submitting a prior unsold estimate, the submission number stayed the same for a prior submitted estimate.  Is there a switch that controls this behavior?  Perhaps the submission number stays the same unless the app version changes?

     

    0
  • Permanently deleted user

    I think I may have confused myself with the "New" option, which probably won't be used often as it discards, rather than templates the former data.

    Looks like I'll stick with Edit.

     

    0

Didn't find what you were looking for?

New post