What Makes A Dataform Required?

Summary

The configurability of ClientSpace allows you to insure specific information is gathered as part of the Pricing process. One way to do so is by requiring the presence of a dataform before submissions can be made - there are several ways this can be configured, all through business rules. This document is designed to provide an overview of common required Table rules and how they can be configured to insure the appropriate infomation is being gathered throughout the sales and pricing process.

So what makes a dataform required anyway?

There are several business rules, both soft and hard error varieties which control this functionality - for purposes of this article we will be looking at the hard errors which stop the workflow process.

HE_RequiredTableEngine

Requires a specific dataform be created for the workspace before allowing the Action to continue - in the example above, in order to submit the deal a Collateral form must be created for the workspace.

HE_RequiredTablePerContractTypeEngine

Requires a specific dataform be created for the workspace before allowing the Action to continue based on Contract type. Specific contract types could require different forms.

HE_RequiredFieldPerContractType

Requires a specific dataform field be completed / filled for the workspace before allowing the Action to continue based on Contract type. Specific contract types could require different dataform fields.

HE_RequiredTablePerCodeEngine

If specific Comp Codes are present in the Pricing Batch (rule accepts a comma separated list - no spaces) require a specific dataform to be created for the workspace before allowing the Action to continue.

Through the use of these configurable rules and others like them, as well a s required field engine rules on the dataform, ClientSpace makes it possible for you to design and create pricing workflows to insure that your sales process is consistent and all required documentation is complete.