Web forms sometimes need to be able to handle complex issues. The Formprocessor extension could already handle a lot of situations. Sometimes, however, CiviRules also still proved necessary to handle all variants coming in through a web form. While that worked well, it also made it cluttered and complex. Therefore, much more extensive conditions functionality has been added to the form processor. You can find them in the latest release of the formprocessor: 3.0
An example of a complex form, would be that when a participant registers, the following should happen:
- it needs to check whether the employer exists in the database based on a unique attribute, e.g. VAT number
- it should check whether that employer is a member so that costs can be based on the benefits offered by membership
- the participant must be able to indicate preferences for participation in sessions whose costs can be added up
- the preferred language should be specified
- the participant should be able to indicate whether they want to receive the newsletter
- the data must be processed in CiviCRM
- the billing address for this invoice should be defined
- a variety of confirmation e-mail should be sent with the right information and in the right language
With the new functionality of conditions in the formprocessor, you work through every variant that can be submitted within the formprocessor. Each variant forms its own rule in the formprocessor, with its own multiple conditions and actions that can be executed based on them. It looks like much of the functionality of CiviRules is available within the formprocessor.
Used CiviCRM extensions
Drupal modules