Configuration Finish

A configuration can be explicitly finished, which marks it as complete and triggers a number of user-defined actions such as sending mails, creating a quote, pushing data to 3rd party applications (such as ERPs) or adding an item to an ecommerce shopping cart.

On Checkout

The process of completing a configuration was previously known as Checkout, which is still available and fully functional.
We are currently in the procress of rolling out the new Finish experience.

Finish Actions

Everything that happens when a configuration is finished is defined by so-called finish actions. These are defined in the FinishActions rule.

You can define different sets of actions based on the current user, configurator stage or any other characteristic you like.
When a configuration is finished, you can view the results of all action on the Insights page.
You can optionally assign a custom actionName to each of your finish actions, if you plan to access their results later on.

Checkout interaction: if your configurator contains a CheckoutComponent, then its Shop and Insights will be automatically converted into finish actions.
You can keep using the CheckoutComponent and define additional finish actions – but be aware that certain actions can only be used once per configuration.

Example FinishActions rule:

[
  OnFinish.SendMail(new {
    from: new { mail: "test@example.com", name: "Test Inc." },
    to: [ new { mail: "user@example.com" } ],
    subject: "Test Mail",
    message: "Example content",
    CC:[],BCC:[],cfgnFiles:[]
  }),

  OnFinish.CreateQuote(MyQuote),

  OnFinish.SetOutput({
    color: SelectedColor,
    price: unitPrice * Amount
  })
]