Can Process Data Fields be Updated From a Form?

Comments

3 comments

  • Avatar
    Casey Kolowinski

    What's the use case? I would think you shouldn't need to do that because the Process Fields are typically utilized within the workflow, so if you needed to wait until then anyways, then it wouldn't be an issue? I would ask how you're using the process fields within the form that make you need them updated that can't be mimicked with normal form fields?

    NOTE: I haven't tried accessing them, so don't know if it's possible, just thinking out loud.

    Casey

    0
    Comment actions Permalink
  • Avatar
    Loren Bratzler

    I have a task that sends reminder emails to an outside vendor.  The email address that the reminders are sent to are currently stored in a Process Data field.  There are two email address fields on my eForm.  Depending on what type of data is in the process, one of the email addresses from the eForm is loaded to the process field email address in an earlier step.

    The users want to be able to update the email address on the eForm and save the change without submitting and completing the task.  If they do this, they want to have future reminder emails sent to the updated email address.  So that is why I was wondering if I could update a Process Data field from within an eForm.

    But now I realize that I would probably be better off to just create a hidden email field on the eForm that is updated with the proper email address and use that for the reminder emails.  Then if they change the email on the form, I can use JS or a rule to update the hidden field.

    0
    Comment actions Permalink
  • Avatar
    Casey Kolowinski

    The use case makes sense but yeah, I think it makes the most sense to have the field hidden on the form that's calculated and use that in the email instead of that process field. Small difference but opens up your flexibility. Hope it works for you. Have a good day!

    0
    Comment actions Permalink

Please sign in to leave a comment.