Not signed in (Sign In)

Vanilla 1.1.5a is a product of Lussumo. More Information: Documentation, Community Support.

  1.  
    I want to set up a form that would allow a user to validate some information, and then update the SFDC object with the validated data. After the validation however, I do not want them to be able to change the data again without contacting our offices directly because the validation will initiate some internal workflows that could be disrupted by silently updating the record again.

    There are a couple of ways I can think of flagging a new update after the workflow has begun, but my preference would be to "disable" the form after it has been submitted.

    Any suggestions on how I might make something like this work with FormAssembly?
    • CommentAuthordbuschho
    • CommentTimeAug 3rd 2010
     
    Hello,

    There isn't a good way to do this with FormAssembly directly. My advice would be to place a notice up on the form reminding people to only submit once, and to contact you directly ( give them a mailto link ) if they need to update further.

    Beyond that, you could add a one-time code to their object in SF, and validate against that code. Once they submit an update, then you change that code with a trigger, and future updates won't succeed. That would probably *greatly* annoy your users though.

    You might also check with your Salesforce tech support rep, and see if there is a clever way to do this with VisualForce, maybe embedding the form on a VisualForce site that is only visible to users who haven't already updated?

    Happy to help,
    Drew.
    FA Support.
  2.  
    Embedding it on a visual force page only if the record has not been updated is a great idea, and shouldn't be too difficult to implement. Thanks for the suggestion.
    • CommentAuthordbuschho
    • CommentTimeAug 3rd 2010
     
    Cool. If you get it working, let us know, we're tossing around the idea of writing up some FA-VF-sites documentation, but Salesforce has been a pain about getting it rolled out to our dev instances. If it's anything to sensitive for public consumption, fire it to drew AT formassembly.com