Trimble Unity Permit / Cityworks Intra-Application Connector

Cityworks / Trimble Unity Permit Intra-Application connector, automation that works inside the system you already run, picking up where the native Action Manager leaves off. Action Manager can fire the trigger; Velosimo does the rest!

Move data freely across record types. Cityworks / Trimble Unity Permit keeps Service Requests, Work Orders, and Cases in separate silos, and Action Manager can't pass structured data between them. This connector bridges all three directions automatically:

• Service Request → Case: caller and contact details flow straight into the Case's People record.
• Service Request → Work Order: request details populate the Work Order's instructions, so crews get the full story.
• Work Order → Case: Work Order content propagates into the linked Case, keeping the record whole.

Carry attachments and documents with the data. Moving files between record types is one of the biggest gaps in native Cityworks / Trimble Unity Permit, and this connector closes it. It pulls attachments from the source record and reattaches them to the target across every path (Service Request to Case, Service Request to Work Order, Work Order to Case), with built-in deduplication so the same file never lands twice.

Map fields your way, with smart create-or-update logic. The Service Request-to-Case people sync is driven by a configurable, tenant-editable mapping of name, address, every phone type, email, fax, and role, so you can tune it without touching code. It's smart about duplicates, too: it matches on email to update an existing People record or create a new one as needed, instead of the flat, static, single-record copies native Action Manager is limited to.

Calculate fees automatically. For code-enforcement workflows, the connector reviews a Case's violations, counts the open ones, multiplies by the per-violation fee, and writes the recalculated total back to the case—real conditional math across child records with a write-back, something Action Manager simply can't do on its own.

Keep everything in sync as it changes. When source data is updated, the connector re-runs the mapping and refreshes the linked case so records stay current, not just accurate at the moment they were created.

The pattern throughout: native Cityworks / Trimble Unity Permit supplies the trigger; Velosimo supplies the cross-object logic, file movement, and computation that turn a single event into a complete, automated workflow.