Skip to content
Permalink
master
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Go to file
 
 
Cannot retrieve contributors at this time

Output Workflows

image

The Output Workflows allows you to define powerful finishing workflows, after a form has been successfully submitted. To give you a slight overview of the idea behind all this, we'll show you some scenarios you may want to achieve:

Default Scenario

You simply want to send all the form data as email to a given admin and to the user for confirmation.

  • Create Output Workflow
    • Add a new Email-Channel and select a valid pimcore mail template
    • Add another Email-Channel and select a valid pimcore mail template
      • Note: Using the %FIELD_NAME% placeholders in the to field for example is still valid!)

Extended Scenario I

You want to offer an event registration form. After a client has submitted the form, you want to send him a confirmation email and store the data in a structured DataObject called Event.

  • Create Output Workflow
    • Add a new Email-Channel and select a valid pimcore mail template
    • Add a new Object-Channel and select the resolver strategy
    • Map your form fields with all the object fields of Event

Extended Scenario II

You want to offer an event registration form. After a client has submitted the form, you want to send him a confirmation email and submit all the data to some external services via API.

  • Create Output Workflow
    • Add a new Email-Channel and select a valid pimcore mail template
    • Create a Custom Channel

As you can see, these are powerful tools which allows you to define workflows without writing a single line of code. Want to learn more? Let's start with the Email Channel.

Output Workflow Topics