DEV Community: Query Filter

gradle-118

Query Filter — Tue, 29 Sep 2026 15:52:54 +0000

In your TeamCity build log snippet, the 1406 value inside GCometUI_1406.xml represents the unique Application Version ID (or Atom ID / Version Item ID) generated by the internal Citi Atom / Husky deployment framework.

Here is the breakdown of how that value is generated and used in this log sequence:

1. Context from the Log Lines

ArtifactVersionCreationResultSaver:SaveToFile: The deployment runner calls a method passing the DTO Citi.Atom.Husky.Contracts.Dtos.VersionItemViewDto alongside the component name GCometUI.
FullPathGenerator:GetFullPath: The process dynamically constructs the filename using the returned metadata: "GCometUI_1406.xml".
D:\TeamCity\...\GCometUI_1406.xml: The file saved at this location contains the serialized deployment metadata / manifest for GCometUI version item 1406.

2. What `1406` Represents

Atom Version Item ID / Release Identifier: In the Citi Atom / Husky framework, each registered build artifact or deployment manifest is assigned an auto-incrementing integer key (here, 1406).
Deployment Wiring: This XML file holds the specific stream configuration, binary references, and entitlement parameters required for downstream release steps (e.g., uDeploy / App Directory registration / Deployment Portal wiring).

gradle-117

Query Filter — Tue, 29 Sep 2026 14:20:12 +0000

flowchart LR
subgraph STEP1 ["Step 1"]
S1["⚙️ Build & Publish
TeamCity / uDeploy"]
end

subgraph STEP2 ["Step 2"]
    S2["🔌 <b>Stream Update</b><br/>Deployment Portal"]
end

subgraph STEP3 ["Step 3"]
    S3["🔒 <b>Approval & Promo</b><br/>AppD Portal"]
end

subgraph STEP4 ["Step 4"]
    S4["🖥️ <b>Client Sync</b><br/>Citi Desktop"]
end

STEP1 --> STEP2 --> STEP3 --> STEP4

%% Styling
style S1 fill:#1A1D20,stroke:#2080F0,stroke-width:2px,color:#fff
style S2 fill:#1A1D20,stroke:#8E24AA,stroke-width:2px,color:#fff
style S3 fill:#1A1D20,stroke:#FB8C00,stroke-width:2px,color:#fff
style S4 fill:#000000,stroke:#1E88E5,stroke-width:2px,color:#fff

gradle-116

Query Filter — Tue, 29 Sep 2026 14:12:32 +0000

flowchart LR
%% Node Definitions
subgraph CI_CD ["1. CI/CD & Artifact Management"]
TC["⚙️ TeamCity CI
Build & Automate"]
ART["📦 JFrog Artifactory
Artifact Storage"]
end

subgraph DEPLOYMENT ["2. Release & Provisioning"]
    UD["🚀 uDeploy<br/><b>Version Tracking</b>"]
    DP["🔌 Deployment Portal<br/><b>Stream Wiring</b>"]
end

subgraph ACCESS ["3. Security & Access"]
    AD["🔒 App Directory<br/><b>Access Control</b>"]
end

subgraph CLIENT ["4. Client Environment"]
    BA["🤖 Background Agent<br/><b>(runApp.bat Auto)</b>"]
    CD["🖥️ Citi Desktop<br/><b>User Execution</b>"]
end

%% Flow Connections
TC --> ART
ART --> UD
UD --> DP
DP --> AD
AD --> BA
BA --> CD

%% Styling
style TC fill:#000000,stroke:#2080F0,stroke-width:2px,color:#fff
style ART fill:#1A1D20,stroke:#43A047,stroke-width:2px,color:#fff
style UD fill:#1A1D20,stroke:#00ACC1,stroke-width:2px,color:#fff
style DP fill:#1A1D20,stroke:#8E24AA,stroke-width:2px,color:#fff
style AD fill:#1A1D20,stroke:#FB8C00,stroke-width:2px,color:#fff
style BA fill:#1A1D20,stroke:#E53935,stroke-width:2px,color:#fff
style CD fill:#000000,stroke:#1E88E5,stroke-width:2px,color:#fff

gradle-115

Query Filter — Tue, 29 Sep 2026 14:10:28 +0000

gradle-114

Query Filter — Mon, 28 Sep 2026 15:04:52 +0000

Here is the updated, complete slide-by-slide text formatted for your presentation, now including the introductory overview slide at the beginning.

Slide 1: Introduction to Citi Desktop & COMET-NAM GUI

Slide Title: Citi Desktop & COMET-NAM GUI Overview

Subtitle: "Next-generation application delivery and access control"

Key Features & Access Model

Modern Delivery Platform: Citi Desktop introduces a unified mechanism for launching CITI enterprise applications, including COMET-NAM GUI.
Flexible Launch Options: Users can launch Citi Desktop directly through the Windows Start menu or via Atom.
Role-Based Entitlement:
Each COMET-NAM GUI application and its specific version is directly associated with an Atom security group.
Access is strictly controlled: users can only see and launch COMET-NAM GUI applications authorized for their assigned Atom group.

Slide 2: End-to-End Provisioning Architecture Overview

Slide Title: COMET-NAM GUI: Provisioning & Integration Workflow

Subtitle: Streamlined application delivery through interconnected Citi platform dependencies

Core Architecture Concept

Provisioning COMET-NAM GUI via Citi Desktop relies on relational "wiring" between enterprise systems—similar to database referential integrity. Each system validates dependencies downstream before final promotion.

+-------------------+      +--------------------+      +-------------------+      +------------------+
|    Jenkins CI     | ---> |  JFrog Artifactory | ---> |      uDeploy      | ---> | Deployment Portal|
| Build & Automate  |      | Artifact Storage   |      | Version Tracking  |      | Stream Wiring    |
+-------------------+      +--------------------+      +-------------------+      +------------------+
                                                                                       |
                                                                                       v
+-------------------+      +--------------------+                               +------------------+
|   Citi Desktop    | <--- |   Background Agent | <---------------------------- |    App Directory |
| User Execution    |      | (runApp.bat Auto)  |                               | Access Control   |
+-------------------+      +--------------------+                               +------------------+

Slide 3: Pipeline & Environment Dependencies

Slide Title: System Components & Relational Wiring

1. Build & Release Management (CI/CD Pipeline)

Jenkins CI/CD compiles code and publishes build artifacts.
JFrog Artifactory securely stores versioned binaries.
uDeploy captures release versions, build parameters, and deployment packages.

2. Deployment Portal (Resource & Stream Configuration)

Stream Definition: Connects build artifacts to execution resources.
Resource Binding: Links specific uDeploy application versions, runtime JDKs, and auxiliary dependencies.
Access Mapping: Associates the stream with authorized Atom Groups and their assigned users.

3. App Directory (AppD Portal) (Access Control & Promotion)

One-Time Application Setup: Wires the application, stream configuration, and Atom group affiliations.
Visibility Control: Sets user entitlement and UI display rules.
Environment Promotion: Manages governed workflow approvals for UAT and PROD releases.

Slide 4: Release Management Lifecycle

Slide Title: Step-by-Step Release & Promotion Workflow

[ Step 1: Build Publish ] ---> [ Step 2: Stream Update ] ---> [ Step 3: Approval & Promo ] ---> [ Step 4: Client Sync ]
Jenkins / uDeploy               Deployment Portal               AppD Portal                      Citi Desktop

Operational Steps

Step 1: Build & Publish
Developer pushes changes; Jenkins builds and registers new version numbers in uDeploy.
Step 2: Deployment Portal Update
Deployment Portal Admin updates the target stream with the latest (or selected) version from uDeploy.
Step 3: AppD Portal Governance
AppD Portal Admin submits promotion requests and obtains required approvals for UAT / PROD.
Step 4: User Entitlement & Execution
Authorized Atom group members gain access to launch or update the application.

Slide 5: Client Execution & Background Deployment

Slide Title: Silent Client Updates & Background Execution

Automated Client Lifecycle

Seamless Launch: Users launch COMET-NAM GUI directly from Citi Desktop or Atom.
Zero-Touch Background Installation:
Re-installations and updates execute automatically in the background upon relaunch.
Driven by the custom runApp.bat agent defined within the AppD Portal.
Enterprise Security Benefits:
Eliminates manual installation steps for end users.
Guarantees strict version control and security alignment across all client environments.

gradle-113

Query Filter — Mon, 28 Sep 2026 15:01:19 +0000

Here is the complete slide-by-slide text formatted for your presentation.

Slide 1: End-to-End Provisioning Architecture Overview

Slide Title: COMET-NAM GUI: Provisioning & Integration Workflow

Subtitle: "Streamlined application delivery through interconnected Citi platform dependencies"

Core Architecture Concept

+-------------------+      +--------------------+      +-------------------+      +------------------+
|    Jenkins CI     | ---> |  JFrog Artifactory | ---> |      uDeploy      | ---> | Deployment Portal|
| Build & Automate  |      | Artifact Storage   |      | Version Tracking  |      | Stream Wiring    |
+-------------------+      +--------------------+      +-------------------+      +------------------+
                                                                                       |
                                                                                       v
+-------------------+      +--------------------+                               +------------------+
|   Citi Desktop    | <--- |   Background Agent | <---------------------------- |    App Directory |
| User Execution    |      | (runApp.bat Auto)  |                               | Access Control   |
+-------------------+      +--------------------+                               +------------------+

Slide 2: Pipeline & Environment Dependencies

Slide Title: System Components & Relational Wiring

1. Build & Release Management (CI/CD Pipeline)

Jenkins CI/CD compiles code and publishes build artifacts.
JFrog Artifactory securely stores versioned binaries.
uDeploy captures release versions, build parameters, and deployment packages.

2. Deployment Portal (Resource & Stream Configuration)

Stream Definition: Connects build artifacts to execution resources.
Resource Binding: Links specific uDeploy application versions, runtime JDKs, and auxiliary dependencies.
Access Mapping: Associates the stream with authorized Atom Groups and their assigned users.

3. App Directory (AppD Portal) (Access Control & Promotion)

One-Time Application Setup: Wires the application, stream configuration, and Atom group affiliations.
Visibility Control: Sets user entitlement and UI display rules.
Environment Promotion: Manages governed workflow approvals for UAT and PROD releases.

Slide 3: Release Management Lifecycle

Slide Title: Step-by-Step Release & Promotion Workflow

[ Step 1: Build Publish ] ---> [ Step 2: Stream Update ] ---> [ Step 3: Approval & Promo ] ---> [ Step 4: Client Sync ]
Jenkins / uDeploy               Deployment Portal               AppD Portal                      Citi Desktop

Operational Steps

Step 1: Build & Publish
Developer pushes changes; Jenkins builds and registers new version numbers in uDeploy.
Step 2: Deployment Portal Update
Deployment Portal Admin updates the target stream with the latest (or selected) version from uDeploy.
Step 3: AppD Portal Governance
AppD Portal Admin submits promotion requests and obtains required approvals for UAT / PROD.
Step 4: User Entitlement & Execution
Authorized Atom group members gain access to launch or update the application.

Slide 4: Client Execution & Background Deployment

Slide Title: Silent Client Updates & Background Execution

Automated Client Lifecycle

Seamless Launch: Users launch COMET-NAM GUI directly from Citi Desktop or Atom.
Zero-Touch Background Installation:
Re-installations and updates execute automatically in the background upon relaunch.
Driven by the custom runApp.bat agent defined within the AppD Portal.
Enterprise Security Benefits:
Eliminates manual installation steps for end users.
Guarantees strict version control and security alignment across all client environments.

gradle-112

Query Filter — Mon, 28 Sep 2026 14:48:30 +0000

Slide 1: End-to-End Provisioning Architecture Overview
Slide Title: COMET-NAM GUI: Provisioning & Integration Workflow
Subtitle: Streamlined application delivery through interconnected Citi platform dependencies
Core Architecture Concept
Provisioning COMET-NAM GUI via Citi Desktop relies on relational "wiring" between enterprise systems—similar to database referential integrity. Each system validates dependencies downstream before final promotion.
+-------------------+ +--------------------+ +-------------------+ +------------------+
| Jenkins CI | ---> | JFrog Artifactory | ---> | uDeploy | ---> | Deployment Portal|
| Build & Automate | | Artifact Storage | | Version Tracking | | Stream Wiring |
+-------------------+ +--------------------+ +-------------------+ +------------------+
|
v
+-------------------+ +--------------------+ +------------------+
| Citi Desktop | <--- | Background Agent | <---------------------------- | App Directory |
| User Execution | | (runApp.bat Auto) | | Access Control |

Slide 2: Pipeline & Environment Dependencies
Slide Title: System Components & Relational Wiring

Build & Release Management (CI/CD Pipeline) • Jenkins CI/CD compiles code and publishes build artifacts. • JFrog Artifactory securely stores versioned binaries. • uDeploy captures release versions, build parameters, and deployment packages.
Deployment Portal (Resource & Stream Configuration) • Stream Definition: Connects build artifacts to execution resources. • Resource Binding: Links specific uDeploy application versions, runtime JDKs, and auxiliary dependencies. • Access Mapping: Associates the stream with authorized Atom Groups and their assigned users.
App Directory (AppD Portal) (Access Control & Promotion) • One-Time Application Setup: Wires the application, stream configuration, and Atom group affiliations. • Visibility Control: Sets user entitlement and UI display rules. • Environment Promotion: Manages governed workflow approvals for UAT and PROD releases. Slide 3: Release Management Lifecycle Slide Title: Step-by-Step Release & Promotion Workflow [ Step 1: Build Publish ] ---> [ Step 2: Stream Update ] ---> [ Step 3: Approval & Promo ] ---> [ Step 4: Client Sync ] Jenkins / uDeploy Deployment Portal AppD Portal Citi Desktop Operational Steps • Step 1: Build & Publish o Developer pushes changes; Jenkins builds and registers new version numbers in uDeploy. • Step 2: Deployment Portal Update o Deployment Portal Admin updates the target stream with the latest (or selected) version from uDeploy. • Step 3: AppD Portal Governance o AppD Portal Admin submits promotion requests and obtains required approvals for UAT / PROD. • Step 4: User Entitlement & Execution o Authorized Atom group members gain access to launch or update the application. Slide 4: Client Execution & Background Deployment Slide Title: Silent Client Updates & Background Execution Automated Client Lifecycle • Seamless Launch: Users launch COMET-NAM GUI directly from Citi Desktop or Atom. • Zero-Touch Background Installation: o Re-installations and updates execute automatically in the background upon relaunch. o Driven by the custom runApp.bat agent defined within the AppD Portal. • Enterprise Security Benefits: o Eliminates manual installation steps for end users. o Guarantees strict version control and security alignment across all client environments.

gradle-110

Query Filter — Mon, 28 Sep 2026 13:57:37 +0000

taskkill /F /IM SearchHost.exe
rd /s /q "%localappdata%\Packages\MicrosoftWindows.Client.CBS_cw5n1h2txyewy\LocalCache"

gradle-109

Query Filter — Mon, 28 Sep 2026 13:55:20 +0000

taskkill /F /IM SearchHost.exe
rd /s /q "%localappdata%\Packages\Microsoft.Windows.Search_cw5n1h2txyewy\LocalState"

gradle-97

Query Filter — Tue, 22 Sep 2026 16:23:22 +0000

ere is the list of official statutory holidays and recognized public holidays in Ontario for the summer and fall of 2026:

Summer 2026
Canada Day

Date: Wednesday, July 1, 2026

Type: Official Ontario Statutory Holiday

Civic Holiday (frequently referred to as Simcoe Day)

Date: Monday, August 3, 2026

Type: Public / Civic Holiday (Widely observed across municipalities and employers, though not legally classified as a mandatory statutory holiday under the Ontario Employment Standards Act).

Labour Day

Date: Monday, September 7, 2026

Type: Official Ontario Statutory Holiday

Fall 2026
National Day for Truth and Reconciliation

Date: Wednesday, September 30, 2026

Type: Federal Statutory Holiday (Mandatory day off for federal public sector employees, federally regulated businesses, and banks; optional for non-regulated private employers in Ontario).

Thanksgiving Day

Date: Monday, October 12, 2026

Type: Official Ontario Statutory Holiday

Remembrance Day

Date: Wednesday, November 11, 2026

Type: Commemorative / Federal Holiday (Observed by federal workers and financial institutions; not a statutory public holiday under Ontario provincial labor law).

gradle-95

Query Filter — Mon, 21 Sep 2026 19:51:30 +0000

When a GUI user triggers an action (specifically LinkRepOrderAction.getFxRate), the backend calls reference data services to fetch product details:

Trigger: GetProductBySymbolAltIdAssetClass.getCachedObjectImpl

Log Level: SEVERE / WARNING

Exception:

Plaintext
com.citigroup.equities.comet.framework.util.DuplicateProductException: Multiple Products for: ...
Cause: The reference data lookup query returned more than one matching product record for the given symbol/alternative ID asset class mapping (NTR / NTR.TO).

gradle-94

Query Filter — Mon, 21 Sep 2026 14:17:25 +0000

Get-AppxPackage -AllUsers -Name MicrosoftWindows.Client.CBS | Foreach {Add-AppxPackage -DisableDevelopmentMode -Register "$($_.InstallLocation)\AppXManifest.xml"}

DEV Community: Query Filter

gradle-118

1. Context from the Log Lines

2. What 1406 Represents

gradle-117

gradle-116

gradle-115

gradle-114

Slide 1: Introduction to Citi Desktop & COMET-NAM GUI

Slide Title: Citi Desktop & COMET-NAM GUI Overview

Subtitle: "Next-generation application delivery and access control"

Key Features & Access Model

Slide 2: End-to-End Provisioning Architecture Overview

Slide Title: COMET-NAM GUI: Provisioning & Integration Workflow

Subtitle: Streamlined application delivery through interconnected Citi platform dependencies

Core Architecture Concept

Slide 3: Pipeline & Environment Dependencies

Slide Title: System Components & Relational Wiring

1. Build & Release Management (CI/CD Pipeline)

2. Deployment Portal (Resource & Stream Configuration)

3. App Directory (AppD Portal) (Access Control & Promotion)

Slide 4: Release Management Lifecycle

Slide Title: Step-by-Step Release & Promotion Workflow

Operational Steps

Slide 5: Client Execution & Background Deployment

Slide Title: Silent Client Updates & Background Execution

Automated Client Lifecycle

gradle-113

Slide 1: End-to-End Provisioning Architecture Overview

Slide Title: COMET-NAM GUI: Provisioning & Integration Workflow

Subtitle: "Streamlined application delivery through interconnected Citi platform dependencies"

Core Architecture Concept

Slide 2: Pipeline & Environment Dependencies

Slide Title: System Components & Relational Wiring

1. Build & Release Management (CI/CD Pipeline)

2. Deployment Portal (Resource & Stream Configuration)

3. App Directory (AppD Portal) (Access Control & Promotion)

Slide 3: Release Management Lifecycle

Slide Title: Step-by-Step Release & Promotion Workflow

Operational Steps

Slide 4: Client Execution & Background Deployment

Slide Title: Silent Client Updates & Background Execution

Automated Client Lifecycle

gradle-112

gradle-110

gradle-109

gradle-97

gradle-95

gradle-94

2. What `1406` Represents