Skip to main content

DupliCat Changelog

Last updated: February 23, 2026 (America/Los_Angeles)

Applies to version/build: DupliCat v0.1.6 (released February 16, 2026)

Small changes, fewer surprises.

Boundaries

  • This changelog tracks public docs updates and operator-facing release notes.
  • It is not a roadmap.

Support intake checklist

If you’re reporting a regression to support, include:

  • Portal ID
  • Object type + source record URL
  • Template name (or “Use effective default”)
  • Number of duplicates value
  • Timestamp with timezone

2026-02-23 - Docs refresh (operator-first, boundary-first)

Changed

  • Rewrote DupliCat docs for clearer operator boundaries and rollout-safe checklists.
  • Avoided adding new capability claims; tightened wording to match the companion DupliCat runtime repo.

v0.1.6 - Workflow + advanced template controls

Released: February 16, 2026

Added

  • Workflow action support documentation for DupliCat: Clone through workflow, including setup and run outcomes.
  • Card duplicate count control documentation for Number of duplicates (1-10) with sequential clone creation and per-duplicate links.
  • Enhanced override documentation covering date shift, owner rules, and pipeline/stage mapping behavior.

Changed

  • Template default docs now reflect both portal defaults and personal defaults (“my default”) per object type.
  • Public naming language now uses prefix semantics ([Duplicate]) instead of suffix wording.
  • Scopes documentation now reflects 15 required scopes, including automation.

v0.1.5 - Duplication templates

Released: February 16, 2026

Added

  • Duplication Templates: save reusable clone presets per object type.
  • Default template selection per object type so template config auto-loads in the card.
  • Card-level template selector to switch template per clone run or use portal default behavior.

Changed

  • Setup docs now document template creation, default-template behavior, and runtime fallback rules.
  • Public capability docs now include template usage and object-type template scope boundaries.

v0.1.4 - Preview card entry support

Released: February 16, 2026

Added

  • DupliCat can now be used from HubSpot record preview cards, in addition to record tab and sidebar cards.
  • Setup documentation now includes preview-card placement steps per supported object type.

Changed

  • Public capability docs now describe all three entry surfaces (tab, sidebar, preview).

v0.1.3 - Source-reference note on cloned records

Released: February 15, 2026

Added

  • Cloned records now receive a DupliCat note with a link back to the source record.
  • Setup docs now include validation for source-reference note behavior.

Changed

  • Known limitations now clarify that source activities are not cloned, while one new traceability note is added to cloned records.

v0.1.2 - Ticket object support

Released: February 15, 2026

Added

  • Ticket record cloning support from DupliCat tab and sidebar cards.
  • Ticket workflows documented in setup, scopes, and known limitations pages.

Changed

  • Support now includes deals, contacts, companies, and tickets.
  • Setup and limitations docs now include ticket-specific guidance.

v0.1.1 - Clarity and trust updates

Released: February 13, 2026

Added

  • App-scoped permissions documentation at https://clevercat.app/apps/duplicat/docs/scopes.
  • Data deletion guidance via support.

Changed

  • Setup guidance clarified for card placement and first clone validation.
  • Capability docs now clearly distinguish association re-linking from deep-cloned deal line items.
  • Trust and support pages now provide clearer storage and deletion expectations.

v0.1.0 - Initial release

Released: February 13, 2026

Added

  • DupliCat record cloning for deals, contacts, and companies.
  • Optional deep-clone line item behavior for deals when line_items is selected.
  • Public docs for setup, changelog, scopes, and limitations.
  • Trust pages for privacy, security, and support.

Changed

  • Setup and docs coverage expanded for launch usability.

Format

Future entries follow:

  • Date in YYYY-MM-DD
  • Added / Changed / Fixed bullets
  • Links to docs or support pages when relevant