CIMB SMART Versioning Helper

1. Purpose and scope

The Helper versions Gen1 Officeless Studio assets (VP, SEM, MEM, DM) for CIMB SMART, stores working copies in Firestore (per user × environment), and promotes them toward the next gateway target.

2. Architecture overview

Three layers cooperate: the Studio browser tab (session token), the Chrome extension (UI + detection), and the Helper backend (Google session, Firestore, gateway calls).

Figure 1. End-to-end architecture — Studio tab, extension, Helper API, Firestore, and gateways.

2.1 Runtime components

3. Authentication (two layers)

Versioning needs both sessions. Missing either layer causes “unauthorized” or empty catalogs.

Figure 2. Dual authentication — Helper Google session and live Studio bearer token.

Figure 3. Panel when Helper session is missing — Sign in with Google.

Figure 4. Helper signed in (badge shows Helper · user). Studio Token is still required separately.

4. Per-environment Firestore storage

Sync and Rollback histories are isolated per Studio host so UAT2 / UAT / PROD do not overwrite each other.

Figure 5. Isolated Firestore branches per Studio environment.

5. Process flows

5.1 Happy path (UAT2 → UAT → PROD)

1. Open asset on studio-uat2 → Sync a Copy (Firestore …/uat2).
2. Promote to Target → UAT Golden State (preflight: UAT health + Studio UAT sign-in).
3. On studio-uat, Sync again if you edit there (…/uat1 branch).
4. Promote to Target → Production (requires PROD Target settings + Studio PROD session).

Figure 6. Promote ladder — UAT2 Source → Firestore → UAT Target → Production.

6. Sequences

6.1 Sync a Copy

Figure 7. Sync a Copy — download from current gateway and save to Firestore.

6.2 Promote to Target (with preflight)

Figure 8. Promote to Target — diff, preflight, then apply with Target token.

6.3 Rollback from Checkpoint

Figure 9. Rollback from Checkpoint — restore a prior Firestore version (optional redeploy).

7. Installation

1. Open the install page: deployment-helper.smart-cimb.com/docs/studio-chrome-extension/
2. Download officeless-deployment-helper-extension.zip (current pack v1.4.33).
3. Unzip. In Chrome open chrome://extensions, enable Developer mode.
4. Click Load unpacked and select the unzipped folder.
5. Pin the extension. Managed Chrome may use signed CRX via https://deployment-helper.smart-cimb.com/extensions/update.xml.

8. Step-by-step usage

8.1 Sign in (Helper)

1. Open an editor on Studio (example: Visual Programming).
2. In the floating panel, click Sign in with Google.
3. Use a Mekari account (@mekari.com / @aux.mekari.com).
4. Confirm the badge shows Helper · <you>.

Figure 10. Google sign-in for the Deployment Helper session.

8.2 Configure Target (gear)

1. Click the gear icon in the panel footer.
2. On UAT2: enter UAT Staging gateway (gateway-uat.smart-cimb.com) credentials.
3. On UAT: enter Production gateway (gateway.smart-cimb.com) credentials.
4. Use Test connection, then Save Target settings.

Figure 11. Target gateway settings (gear). Required before Promote.

8.3 Sync a Copy

1. Stay logged into the current Studio host (Token present).
2. Open the asset editor (VP / SEM / MEM / DM table).
3. Click Sync a Copy.
4. Confirm status shows a short hash / version id for your env branch.

Figure 12. Versioning actions on a detected Visual Programming asset.

8.4 Promote to Target

1. Click Promote to Target.
2. Review preflight cards: Target health and sign-in.
3. If needed, Open Target & sign in (keep that Studio tab open).
4. Click Refresh statuses until both cards are green.
5. Select synced files → Promote selected.
6. Use summary Open / Rollback, or Target status anytime.

8.5 Rollback from Checkpoint

1. Open the same asset on the same Studio environment you synced from.
2. Click Rollback from Checkpoint.
3. Pick a prior version from history.
4. Optionally redeploy the restored JSON to Source.

8.6 Target status

1. Click Target status.
2. Tabs: On Target, Synced (promote), Recent batches.
3. Open jumps to the Target editor for that kind/id.
4. Rollback selected Target snapshots when available.

9. Gen1 Asset Explorer

Open from the panel (Open Gen1 asset explorer) or the extension side panel. Catalogs load via Helper APIs using your Studio Token from an open Studio tab.

Figure 13. Explorer — UI Single (SEM) catalog.

Figure 14. Explorer — UI Multiple (MEM) catalog.

Figure 15. Explorer — Data Manager tables / groups.

10. Gen1 Execute (VP)

On Visual Programming editors, the Gen1 Execute section can fire the workflow’s api / webhook trigger against the Gen1 gateway using the Studio Token.

Figure 16. Gen1 Execute on a Visual Programming asset.

11. Troubleshooting

Validation checklist

• Helper signed in — email visible; health OK
• Studio Token present with future expire
• Target gateway saved for the current promote ladder
• Extension version ≥ 1.4.33 (check chrome://extensions or install page build-info)