Using Variables Examples

You can combine some of the variables to achieve more complex results. See the examples of using variables in different scenarios organized by complexity and use case.

In this article:

• Quick Reference
• Basic Variable Usage
  • How can I add a table with variables?
  • How to display default values for blank variables?
• Document-Specific Examples
  • Payment Applications
    • How to remove empty line items from a payment application?
    • How can I only show costs on scheduled items and not show subtotal amounts in payment applications?
    • How can I configure the budget payment application spreadsheet to split change orders by type?
    • How can I add a new tab without subtotals to the cost payment application spreadsheet?
    • How can I add a grouped COR tab to the budget payment application spreadsheet?
  • Change Orders
    • How can I add the content from the comments section to change order documents?
    • How can I organize upstream change orders by the main contract SOV?
    • How can I add work items subtotals and markup subtotals for cost items?
    • How can I show associated COR and OCO numbers when splitting change orders by type?
  • Contracts
    • How can I only show costs on scheduled items and not show subtotal amounts in contract SOV?
    • How can I refer to the budget code and name in contract document templates?
• Advanced Techniques
  • Filtering and Conditional Logic
    • How to use filter functionality on document generation?
    • How can I hide the contingency cost in generated documents?
  • Data Aggregation
    • Using sumBy for Data Aggregation

Quick Reference

Common variable patterns and their use cases:

Basic Variable Usage

Start here if you're new to using variables in document templates. These examples cover fundamental concepts that apply to all document types.

How can I add a table with variables?

You can use variables and present your data in the form of a table with columns and headers. Here's an example of syntax:

Use the opening section variable, starting with # (for example, {#markups}) and closing one with / (for example, {/markups}).

Wrong usage:

Correct usage:

Between opening and closing variables, you can list all the necessary data, like {name} or {description}.

The result in generated document:

How to display default values for blank variables?

Scenario: You're using variables like {previousAmount} and {materialsStored} in your document template, but when generating documents, some columns show blank instead of displaying "$0" values.

To display a default value when a variable is empty or blank, use conditional expressions with the following pattern:

{#variableName} {variableName} {/}{#!variableName}default_value{/}

For example, to show "0" when {previousAmount} is blank:

{#previousAmount} {previousAmount} {/}{#!previousAmount}0{/}

This conditional expression works as follows:

• {#previousAmount} - If previousAmount has a value, display it
• {previousAmount} - The actual variable value
• {/} - Close the first condition
• {#!previousAmount} - If previousAmount does NOT have a value (is blank/empty)
• 0 - Display "0" as the default value
• {/} - Close the second condition

You can apply this pattern to any variable where you want to show a default value instead of blank cells, such as:

• {#materialsStored} {materialsStored} {/}{#!materialsStored}$0.00{/}
• {#currentAmount} {currentAmount} {/}{#!currentAmount}0{/}

Document-Specific Examples

These examples are organized by document type to help you find relevant solutions for your specific use case.

Payment Applications

Examples for customizing payment application documents and spreadsheets.

How to remove empty line items from a payment application?

To remove empty line items from a payment application use the conditional expression {#amount!="0.00"} at the beginning of a table and {/} at the end of the line. For example:

How can I only show costs on scheduled items and not show subtotal amounts in payment applications?

To eliminate subtotals from payment applications or contracts, you can enter your payment line items with {#children.length===0}{xxx}{/}. For example:

How can I configure the budget payment application spreadsheet to split change orders by type?

Scenario: You have created a change order type called "Allowance Transfers".

And want to see the approved owner changes for these allowances in the Excel spreadsheet. How to do that?

1. List "Owner Change Order" for the column in the Excel spreadsheet.

   

2. Apply the new type to an OCO.

   

3. Match the name to the type in the Excel spreadsheet.

   

How can I add a new tab without subtotals to the cost payment application spreadsheet?

Scenario: You want to create a new tab in the default cost payment application spreadsheet template that shows only scheduled items without displaying subtotal amounts.

To add a new tab without subtotal to your cost payment application spreadsheet template, use the following variable pattern:

{#children.length===0}{xxx}{/}

This conditional expression ensures that only line items without subtotals are displayed in the generated spreadsheet tab. The {xxx} represents the specific data fields you want to include for each line item.

Use case: This is particularly useful when you want to provide subcontractors with a clean view of individual work items without the complexity of subtotal calculations.

How can I add a grouped COR tab to the budget payment application spreadsheet?

Scenario: You want to create a new tab in the default budget payment application spreadsheet template that groups items by COR (Change Order Request) without showing individual cost item details.

To add a new tab, called "Optional details grouped by COR" for example, to your budget payment application spreadsheet template, use the following variable pattern:

{#payment.lineView.rootItems|groupItemsByXCO: 'COR'}{number}{/payment.lineView.rootItems|groupItemsByXCO: 'COR'}

This variable groups payment line items by their associated COR and displays only the COR numbers without the underlying cost item details.

Key features:

• Groups items by COR for better organization
• Excludes detailed cost item information for a cleaner view
• Useful for high-level budget tracking and reporting
• Helps project managers quickly identify COR-related costs

Change Orders

Examples for customizing change order documents including RFQs, CORs, and OCOs.

How can I add the content from the comments section to change order documents?

Scenario: You want to create a document containing the comments added throughout the lifetime of a change order.

The example shows {#rfq.comments} as the opening tag for the variables and {/rfq.comments} as the closing tag. The other related variables must be between these two variables.

For example, an RFQ with the following comments section:

Adding a table into a Word document with the following:

Results in:

Only one line of a table needs to be filled out in the document template. The software builds the table with the specified information based on the data in Cost Management.

How can I organize upstream change orders by the main contract SOV?

To organize CORs or OCOs by the main contract's Schedule of Values in your document template. For CORs, use this pattern:

And for OCOs, replace rco with oco.

How can I add work items subtotals and markup subtotals for cost items?

Scenario: You're creating a change order document (for example, OCO) and want to have two separate tables within. One for regular cost items with a subtotal and the second for markup cost items. You want to add total change order pricing as well. How to do that? Here's an example of used variables in a document:

How can I show associated COR and OCO numbers when splitting change orders by type?

To show associated COR and OCO number use the following variables:

• COR: {this.costItem.corNumber}
• OCO: {this.costItem.ocoNumber}

The result:

Contracts

Examples for customizing contract documents and Schedule of Values displays.

How can I only show costs on scheduled items and not show subtotal amounts in contract SOV?

Scenario: You want to create a contract with only the subtotal of SOV subitems displayed. You don't want a parent item to be visible to a subcontractor. To do that, use these variables from the document template:

Also, you don't want to show the Unit Cost and Amount values as $0. You can replace $0 with the word "Included". How to do that? Enrich already used variables:

The outcome in the generated contract will look like this:

How can I refer to the budget code and name in contract document templates?

To refer to a budget code and name in the document template, use this formula:

For example, when the Schedule of Values for the contract looks like this:

The presented formula generates this:

Advanced Techniques

These examples demonstrate sophisticated variable usage for complex document customization requirements.

Filtering and Conditional Logic

Advanced filtering techniques to show or hide specific data in your documents.

How to use filter functionality on document generation?

You can use filter functionality on document generation. For example, to only show the Risk Contingency item, use {#payment.columnView.rootItems | filter:"name":"Risk Contingency"} variable:

Result:

Members can also separate original Schedule of Values with all approved SCOs into two separate worksheets.

To generate a worksheet that includes only the Original SOVs, use the following variable:

{#payment.lineView.rootItems | filter:"associationType":"SOV"} {/payment.lineView.rootItems | filter:"associationType":"SOV"}

To generate a worksheet that includes only the approved SCOs, use the following variable:

{#payment.lineView.rootItems | filter:"number":"Change Orders"} {/payment.lineView.rootItems | filter:"number":"Change Orders"}

How can I hide the contingency cost in generated documents?

In situations where administrators don't want to make contingency cost visible in the generated document, filters can be used:

The result:

Data Aggregation

Advanced techniques for calculating totals and performing data aggregation in your documents.

Using sumBy for Data Aggregation

The sumBy function helps to aggregate values within your data set.

Example 1: Calculate the subtotal of each PCO's regular cost items' approved values.

{#oco.pco}{regular | sumBy:'approved'}{/oco.pco}

Example 2: Calculate the total of each PCO's all cost items' approved values.

{#oco.pco}{this | getAll: "costItems" | sumBy: "approved"}{/oco.pco}