I have two questions regarding the FormCurrentVersion.
This is for a global form.
1. Is there a way not have FormCurrentVersion in the email when using ${avform_contents}
if not then.
2. Is there a way to define where it shows in the email.
Form is configured with two fields each having a select box.
The debug option shows Variable1 and Variable2 as it should.
However, the approval email shows:
Variable1
FormCurrentVersion
Variable2
Thank you
Not sure if it's possible to customize the avform_contents attribute.
I suggest you reference the relevant form variables explicitly in the email instead of using avform_contents
Boris,
I went through all the items, I do not see a "variables" field.
How do I just add the variable names?
In the runtime of the workflow, you can see the available variables under the Variables section (screenshot below)
To reference the form variables in an email, you can use this pattern:
${jobUserData_PublicData_test_to_delete_stattext1}
test_to_delete - is the workflow variable prefix as configured in the form
statictext1 - is the name of the field
Configuration of my form:
Thank you.
I am working on different variations to get it to work.
As I finally believe what I was missing, the final save gives me the error:
Workpoint Architect
Hello Boris,
It appears that I need to add the variables to match your screen shot above (with my particular workflow/data variables).
My current challenge is, the value of ${jobUserData_form_request_app_stattext1} is only what I put in the name field and not the actual inputted value of the form variable example: static text 1
So my first question is: Do I need to use the actual verbiage of _PublicData_
if not
what I am I missing?
Yes, give it a try with PublicData
${jobUserData_PublicData_form_request_app_stattext1}
If doesn't work, I suggest you add some screenshot to clarify
Yes, give it a try with PublicData
${jobUserData_PublicData_form_request_app_stattext1}
If doesn't work, I suggest you add some screenshot to clarify