- 3,676,726 Users
- 7,521 Discussions
- 12,650 Comments
Forum Stats
Discussions
Conditional Form Processing Steps
In the processing steps for forms, when I select conditionally execute, I can only choose exactly or not exactly. Most filters include other conditions like contains, starts with, ends with, in quicklist, etc... Not having these fields in the conditionally execute step for the form processing is a limitation as I'd like the processing step to execute based on certain criteria. Anyone else having an issue like this?
Comments
-
Yep I agree would be nice to have. In the meantime you can use wildcard characters for contains, begins and ends with.
*contains*
begins*
*ends
-
Agreed, this is often a limiting factor in the solutions that I create.
-
Agreed, this is often a limiting factor in the solutions that I create.
Same here. I think this should be implemented.
-
I'd love it if the "not" option was added too.
-
- OR
- Group
-
... and maths operators for number fields, e.g. Number of days remaining could be >365
-
Yes, I've always wondered why this was missing. Maybe because the processing steps all need to take place before the redirect to thank you page - if you had very complex rules in here, the conditional query might take too long to run, and therefore cause a poor user experience. Just a guess - trying to give Oracle the benefit of the doubt
-
- OR
- Group
Agree, the only AND is really annoying
-
Yep I agree would be nice to have. In the meantime you can use wildcard characters for contains, begins and ends with.
*contains*
begins*
*ends
I have heard from Oracle Support that wildcard patterns on form processing steps tend to work, but are not actually supported by Oracle - meaning they can't guarantee the functionality.
This enhancement would be great.
-
I have heard from Oracle Support that wildcard patterns on form processing steps tend to work, but are not actually supported by Oracle - meaning they can't guarantee the functionality.
This enhancement would be great.
In confirm that. They are working but not 100% accurate.
-
Would really love this as well.
-
Would be nice to have an option to process differently if the field is blank.
-
Would be nice to have an option to process differently if the field is blank.
Yes! This is one we always miss. A lot of the time we set things to always (e.g. Send thank you email based on form value). If the value comes through as blank - it just doesn't send anything. It's one way around it (although it will probably not work in all circumstances).
-
Is there a wildcard setting for blank that I can try? ie, the condition is the field is exactly .... <something>? thx
-
Seems like this function should work - will need to test it a bit - PM me a use case and I can try it out for you.
-
How is this still not implemented? we need all kinds of complex logic we can get here as its the core of the system.
-
100% agree with this! This functionality is available in other Eloqua areas.
-
Is there a timeline for this update to be implemented? Could really use this to perform a split test on two different transactional emails.
-
Also, maybe it's just me, but I don't think picklist options work with conditions either. Only text inputs on the contact record. That issue and the need for contains, starts with, etc is hard to live without.
-
Is there a timeline for this update to be implemented? Could really use this to perform a split test on two different transactional emails.
Any update?
-
No update yet on this feature? I need this today.
-
No update yet on this feature? I need this today.
Release 18D added some more features, but doesn't include "in picklist" or "contains".
-
Agree with @Devon Guerrero, 18D includes the following operators.
Text Field Operators:
- Equals and Not Equals
- Start With
- End With
- Is Blank
Numeric Field Operators.
- Equals and Not Equals.
- Greater than
- Less than
Date Field Operators
- Equals and Not Equals.
- Before
- After
-
I'm trying to set up a rule that if "Country" equals one of 30 countries, it "does something", but it appears as though I need to create 30 separate conditional processing steps.
