Catalog View Configuration (Storefront 2.0 only)
Pepperi Web Admin V8.71 introduces a major new feature: New and Improved Workflows
We are very excited to introduce an enhanced, advanced, yet simple method of configuring your Workflows.
Workflows have now become completely flexible, with branches, actions and custom forms. You can configure the Workflows to carry out many more types of actions triggered by the status changes of a Transaction, Activity or even an Account (NEW!).
Actions can now be triggered for any combination of status changes, not only the three previously supported (Submitted, Revised, Awaiting approval).
For example, set different actions for Orders changing from New to In Creation (Draft), and then from In Creation to Submitted, and then from Submitted to ERP, and then from Submitted to Revised, and then back to Submitted. Each one of those status changes can trigger the actions.
This provides you with unlimited flexibility in defining exactly what happens at every point in your business process.
New Actions include:
- Webhooks (web services)
- Conditional alerts
- Branch to another step in the workflow
- More... (full list of Workflow actions are detailed below)
Please note that the Workflows configured via the Pepperi Web Admin are currently partially supported on the mobile app. They will be fully supported on the iOS and Android mobile apps in their respective upcoming versions.
Contact us if you wish to activate the new Workflows.
We are also introducing Workflows for Accounts. You can now trigger actions such as notification, rule validation, Email, alerts, and more when a new Account (customer) is created by a user on the iPad.
For example, trigger an address verification form to pop up when a user creates a new Account that verifies address fields such as City, State, Street against a predefined list.
A detailed lists of the actions available for Accounts is in the table below.
The new Workflow creation has an easy-to-follow visual representation. Workflows are still located in the same place in the Workflows tab of the Transaction, Account or Activity.
Each status change defined in the Workflow may have one or more Actions associated with it.
To Add a step, click "+Step" and give the Step a name. The step name will be used as the text on the "Submit" or "Done" button on the Transaction, Activity or Account creation form.
In the example below the name "Validate order" will appear instead of the text "Submit" on the shopping cart.
The actions defined in this step will be executed when the Transaction changes status from In creation to Submitted.
Building a workflow like the one shown above requires you to add steps for each of the required status changes, and the diagram above will be automatically generated.
Actions are divided into "Actions and Branches" and "Post Actions"
The list of all actions shown here is explained in detail in the table below.
"Actions and Branches" are executed upon tapping the "Submit" button in the shopping cart in the case of a Transaction, or the "Done" button in the case of an Activity or Account.
Once the "Actions and Branches" are completed, the "Post Actions" will be executed.
|Action name||Action description||Type||Available for|
|Alert||This action displays an alert message in a dialog box with the option to Cancel or Continue. Cancel - dismisses the dialog and returns the user to what she was working on. Continue - continues to the next action or step in the workflow.||Action/Branch||All (Account, Activity, Trans)|
|Alert on Condition||This action displays an alert message in a dialog box on the condition that the selected rule is evaluated to the indicated value (true/false). Cancel - dismisses the dialog and returns the user to what she was working on. Continue - continues to the next action or step in the workflow.||Action/Branch||Activity, Transactions|
|Notification||This action displays a notification message in a dialog box. The user clicks OK and the workflow continues to the next action or step.||Action/Branch||All (Account, Activity, Trans)|
|Webhook||This action executes an asynchronous Webhook (web service) and continues the workflow||Action/Branch + Post||All (Account, Activity, Trans)|
|Stop condition||The Workflow will be stopped on the condition that the selected rule is evaluated to the indicated value (true/false). A message will be displayed to the user, allowing them to go back and modify the workflow accordingly.||Action/Branch||Activity, Transactions|
|Webhook Stop Condition||The Workflow will be stopped on the condition that the Webhook (web service) is evaluated to true. A message will be displayed to the user, allowing them to go back and modify the workflow accordingly.||Action/Branch||All (Account, Activity, Trans)|
|Custom Form||Open Client WEB customized form (coming soon)||Action/Branch||*COMING SOON|
|Branch Condition||This action evaluates a Boolean rule and branches the workflow to another step based on the status selected in case of failure. Select from a list of Boolean rules created in Advanced Custom Fields. Select the status in case the rule fails to evaluate.||Action/Branch||Activity, Transactions|
|Webhook Branch||This action executes a Webhook (web service) and branches the workflow to another step based on the status selected in case of failure.||Action/Branch||All (Account, Activity, Trans)|
|Open Form||This action allows you to select a form that will be opened for the user to fill in. If the form does not contain fields marked as mandatory it will not be opened. Selecting \'Force always open\' will open the form even if does not contain mandatory fields.||*COMING SOON|
|Force Sync||This action forces the mobile app to sync.||Action/Branch||*COMING SOON|
|Split Order||This action splits the order among multiple locations (ie chains) and creates a separate Transaction for each location. Select the Transaction Type for the newly created orders.||Post||Transaction|
|Send email||Send configurable email||Post||Activity, Transactions|
|Export File to FTP||This action will post an XML file to the Pepperi secure FTP server. This file can then be imported to any ERP/CRM or other system.||Post||All (Account, Activity, Trans)|
|Distribute Activity||This action duplicates the Activity for multiple Accounts. Select the type for the newly created Activities.||Post||Activity|
|Navigate to||After the Actions in this step are completed, the user will be redirected to the page they were on previously, an Activity List of your choice, or stay on the same page. Select from the options below.||Post||*COMING SOON|
Later this quarter we'll be releasing a new version of our Web Storefront - Storefront 2.0
In preparation, we are releasing a feature in this Web Admin version that will allow you to configure the Catalog thumbnail view your buyers use to select a catalog.
You can now add fields from the Catalog Form or Custom Fields, just like any other Pepperi from layout configuration. (This is relevant only if you are using the Multiple Catalogs feature.)
You can position the fields and change their title, as well as add custom fields: