Quote Type (QTT)
When you create a new quote document, you need to select of which Quote Type the new document will be.
The Quote Type defines:
Logic for building inputs and calculations of the items.
Logic for building inputs and calculation of summaries for the quote header.
Logic for building the approval workflow steps.
Configuration
Quote Types are defined based on project needs and their meta definitions must be stored in the version system together with other configurations.
To configure Quote Types, navigate to page Quoting › Quote Types.
Fields
configuration – Configuration (as JSON string) of the detail page. You can configure e.g. the additional tabs on the Quote detail page, which will show information in the form of a dashboard. See definition of the Dynamic Tabs for more details.
uniqueName – Name used in the quote document as a foreign key, to identify the quote type used.
label – Description to guide users when they select a Quote Type during quote creation.
formulaName – Name of the logic used for calculation of the quote items. Note that this logic is not used for folders; their inputs or results are calculated by the quote header logic.
headerFormulaName – Name of the logic used for building inputs and calculating results for the quote header; it can also manipulate the items and folders.
workflowFormulaName – Name of the approval workflow logic which will build the approval steps for the quote document.
creationWorkflowFormulaName – Name of the creation workflow logic which builds the steps of document creation workflow. (available from version 14.0)
lostReasonCollectionName - Unique name of the loss reason collection, defined at Quote Reasons administration configuration page.
attribute1..30 – These fields are typically used as parameters for the quote logics. For example, if two Quote Types have the same majority of item calculations, you can create a single logic and when this logic is executed, it can read the Quote Type attributes to understand which specific calculations it should do for the current document.
Found an issue in documentation? Write to us.
Â