{% set baseFontFamily = "Roboto" %} /* Add the font family you wish to use. You may need to import it above. */

{% set headerFontFamily = "Montserrat" %} /* This affects only headers on the site. Add the font family you wish to use. You may need to import it above. */

{% set textColor = "#565656" %} /* This sets the universal color of dark text on the site */

{% set pageCenter = "1100px" %} /* This sets the width of the website */

{% set headerType = "fixed" %} /* To make this a fixed header, change the value to "fixed" - otherwise, set it to "static" */

{% set lightGreyColor = "#f7f7f7" %} /* This affects all grey background sections */

{% set baseFontWeight = "normal" %} /* More than likely, you will use one of these values (higher = bolder): 300, 400, 700, 900 */

{% set headerFontWeight = "bold" %} /* For Headers; More than likely, you will use one of these values (higher = bolder): 300, 400, 700, 900 */

{% set buttonRadius = '40px' %} /* "0" for square edges, "10px" for rounded edges, "40px" for pill shape; This will change all buttons */

After you have updated your stylesheet, make sure you turn this module off

Workflow Rules — Sequence Matters

by salespad on October 7, 2014

workflow rules - sequence matters.jpg

If you've ever been in the workflow setup in SalesPad Desktop, you have likely seen that there are two sections you spend the most of your time in; the workflow queues section in the top half of the screen and the workflow rules in the bottom half.

One thing both sections share is the Seq column, which allows you to set the sequence of the queues and rules. These sections differ in that queue sequence is for aesthetic purposes, while the rule sequence actually means something.

When you create your workflow rules and you setup multiple rules to evaluate when they are in the same queue, you need to sequence them in such a way so that the most important rules trigger first.

SCENARIO
  1. You create a rule to place a document into a Backorder/Needs Purchasing queue if there are back ordered items on the document.
  2. You create a second rule to place a credit hold on a document and place it in an A/R review queue if the customer has an outstanding balance over 90 days.

Both of these rules are evaluating when the document is in the new order queue.

When you release a document that matches both of these scenarios, the first rule in the sequence that evaluates true is going to be the one that takes effect. So, in this case the document would be moved to Backorder/Needs Purchasing.

This scenario is not ideal, since you would not want to purchase inventory for a customer that hasn't paid in 90 days. To correct this, you would change the rule sequencing so that the credit rule is applied first.

This way, if the customer hasn't paid, it will be caught first. If the customer's credit is fine, the next rule to be evaluated will be checked.

For more information regarding SalesPad Desktop Workflow and workflow rules, check out the documentation here. The rest of SalesPad Desktop support documentation can be found here.

— Brandon Bollenbach

 

 

Topics: SalesPad Insights

Get Blog Updates

Recent Posts

Popular Posts