{% 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

Custom Workflow Rules

by salespad on October 1, 2014

SalesPad Desktop offers a variety of built-in workflow rules through the Workflow setup module that allows you to create logic and flag documents based on your business needs.

Typically, our customers can meet their needs through one or more of our standard workflow rules; however, there are those certain situations where you may need more flexibility within your process that will require a custom workflow rule.

Our standard workflow rules may not offer that functionality out of the box. That is why we have the ability, with some SQL knowledge, to create your own custom workflow rules. Creating your own custom workflow rules gives you the ability to manipulate how your orders are being processed and can prevent incorrect data entry.

Creating a custom workflow rule does require a customized stored procedure, along with manually adding the rule to our SalesPad table (see more on our documentation link).

You can request the custom stored procedure spcpEvalWfRuleCondition by e-mailing or calling our support team. Once you’ve added this stored procedure, you’ll need to create a condition to add to the "IF" statement that exists within the stored procedure.  Once you’ve made your modifications to the SQL statement and manually updated the SalesPad table, you can add the rule to your workflow just like any other standard SalesPad workflow rule. If this is a rule that you would want to create yourself, SQL experience would be required. If you do not have any SQL knowledge, but can tell us exactly what you’re looking for, this is something our development team would be able to handle creating.

You may be asking yourself, why do I need a custom workflow rule? If you’re using some type of third party software that does not interact with SalesPad but does exist in SQL, that could be a reason to use a custom workflow rule. Maybe you want to check on your warehouse to make sure they are keying in tracking numbers on all orders being shipped? There’s another reason. Anything that you can check or determine within a SQL statement could be created as a custom workflow rule. In your current environment or workflow setup, you may have one or more users in the management role checking numerous orders a day for data entry errors, missing information, even incorrect addresses. Adding a custom workflow rule can help check for these issues, provide information to the user as to what is missing, or move documents to specific workflow batches based on that incorrect information. Workflow as a whole is meant to make order entry and the order flow easier and faster

Brandon Younce

Topics: SalesPad Insights

Get Blog Updates

Recent Posts

Popular Posts