Wheelhouse®
Shopping Cart
QuickBooks Online Integration
QuickBooks Online Integration Setup and Troubleshooting
QuickBooks Online (QBO) Integration Overview
Custom Fields and Forms
System Administration
Troubleshooting Checklist
Document Auto Number Format
Sale Shipment Records and Tracking Information Emails
Peripherals and Equipment Requirements
Navigation and Definitions
Logging In and Getting Started
Understanding Order Flow in Wheelhouse
Document Categories
Understanding People and Organizations in Wheelhouse
Admin List Views and Single Record Views
Left Menu Navigation
Advanced Search Techniques
User Administration
User Management: Adding, Editing, and Revoking Access
Defining or Adjusting Teams
User Profiles and Roles in Wheelhouse
Choosing a User Profile
Understanding Wheelhouse Login Types
Reports, Import, Exports, and Document Templates
Report Manager Guide
How to Modify Document Templates
Preparing Excel and Word Templates for Data Merge
Running Reports
Creating Reports on Quotes, Sales, and Outside Reps
Exporting to Excel
Quality Mangement
Adding QCIR Templates
QC Non Conformance Reports (NCRs)
Adding Quality Control Inspection Records (QCIR) in Shop Work
Order Management
Using Order Flags and the Flag First Configs Option
Order Management Guide
Creating customers, quotes and sales
Adding Dealer and Outside Rep Logins
Closing a Sale
External Agent Access Levels
Printing and Emailing Quotes and Sales
Production Routing and Tracking
Shop Work and QR Scanning
Merge Line Items at a Certain Step (Stash & Merge Functionality)
Bin Locations
Shop Work: Priority Flags and Fixed Position
Stopping Work Center or All Running Operations at the End of the Shift
Shop Work
Viewing/Adding/Resolving Work Order Issues
Production Scheduling
Job Manager Guide: Creating Jobs and Work Orders
Workflow Guide: Completing Work Order Operations
The Gantt View
Job Scheduler
Labor Routings
Production Definitions
External Connections - API
Items and Configurators
Product Configuration in Wheelhouse
Item Types
Build Types
Item Overrides: Name, Pricing, and Discounts
Public Item Selector AKA Public Display Categories
Deploying A Configurator to Another Environment
Item and BOM Import Action
Introduction to Kanban Inventory Management
Setting Up Inventory Replenishment and Purchasing
Inventory Hub Guide
Can I use Wheelhouse as my CRM?
Wheelhouse Change Log
Table of Contents
Dino Script® Language Reference
Appendix A: Trestle®/Dino Script® Integration
A: Returning JSON Data
A: Host and Target
A: Running SQL Queries
A: Table of Contents
A: Commands
A: Dynamic and DynamicProxy
A: Advanced Command Arguments
A: Introduction
A: Files
A: Direct Links - URLs and Downloads
A: NPOI and Excel, DocX and Word
A: Embedded Apps with MS Access Files
A: Command Arguments
Style Guidelines
Adding New Functionality with Dino Script XCommand™
Introduction
Dino Script™ Table of Contents
Operators
Concepts
Syntax
Expression Types
Keywords
Variables
Blocks and Scopes
Built-In Functions
Custom Functions (defs)
Anonymous Functions
Conditional Statements
The Context Object
FAQ
Dino Cookbook
Sandbox In-Depth
Functions as Delegates
Native Types
Aliasing
Other Dino Scripts
A: Introduction
Dino is not intended as a standalone language; rather it is a "script-integrated" system. This appendix will consider how Dino integrates into the Trestle framework. Trestle is an ORM (object-relatio…
Dino is not intended as a standalone language; rather it is a "script-integrated" system. This appendix will consider how Dino integrates into the Trestle framework.
Trestle is an ORM (object-relational mapping) and repository framework used to build the DTO (data-transfer objects) and middleware for communication with a relational database. For our purposes though, the ORM parts of Trestle are not as important. The most important thing to get up to speed is to see how Dino integrates as "data as code".
Data as Code
Dino scripts are stored in a data store along with any other record. Depending on the system, these records may fall under various names, usually Business Rule or Rule Script. Also depending on the system (whether it is multi-tenant) there may be records that apply to only a single tenant, and/or there may be global scripts that can apply to any or all tenants. To avoid getting into the weeds on tenancy, we will focus only on the definitions of the fields and scripts of these objects, rather than whether they are single- or multi-tenant. The same rules apply whether the scripts are applicable to one or any number of tenants.
Anatomy of a Rule Script
Now that we know what to look for, we can cover the anatomy of a rule script record.
Note: the examples presented here will use function local imports, so we can see outside dependencies directly in the function that needs them. This is not the recommended approach: it is more efficient to import outside dependencies at the top of the script, at the script root level.
// standard import
from System import DateTime;
// use DateTime anywhere in this script...
// function local import
def myFunction() {
from System import DateTime;
// use DateTime...
}
How did we do?
A: Advanced Command Arguments
A: Files