DEV Community: Query Filter

exec-11

Query Filter — Wed, 19 Aug 2026 18:34:29 +0000


// For Junit5 conflicting tests  are resolved using a ResourceLock

import org.junit.jupiter.api.Test;
import org.junit.jupiter.api.parallel.ResourceLock;
import org.junit.jupiter.api.parallel.Resources;

class LegacyServiceTest {

    @Test
    @ResourceLock("SHARED_CONFIG_FILE") // Use any unique string key
    void testFirstConflictingOperation() {
        // Modifies shared file/state
    }

    @Test
    @ResourceLock("SHARED_CONFIG_FILE") // Matches the key above
    void testSecondConflictingOperation() {
        // Reads/Modifies same shared file/state
    }
}

// For Junit4 use name ordering

Java
import org.junit.Test;
import org.junit.FixMethodOrder;
import org.junit.runners.MethodSorters;

@FixMethodOrder(MethodSorters.NAME_ASCENDING)
public class LegacyIntegrationTest {

    @Test
    public void test01_firstOperation() {
        // Executes first alphabetically
    }

    @Test
    public void test02_secondOperation() {
        // Executes second alphabetically
    }
}

exec-10

Query Filter — Wed, 19 Aug 2026 15:04:38 +0000

plugins {
    id 'java'
    id 'distribution'
    id 'maven-publish'
}

group = 'com.example'
version = '1.0.0'

java {
    toolchain {
        languageVersion = JavaLanguageVersion.of(21)
    }
}

repositories {
    mavenCentral()
}

dependencies {
    // Add runtime dependencies here
    // implementation 'org.springframework.boot:spring-boot-starter:3.2.0'
}

// -----------------------------------------------------------------------------
// 1. Distribution Configuration
// -----------------------------------------------------------------------------
distributions {
    main {
        distributionBaseName = project.name
        contents {
            // Package compiled JAR into lib/
            into('lib') {
                from tasks.named('jar')
                from configurations.runtimeClasspath
            }
            // Include resources or configuration files into config/
            into('config') {
                from 'src/main/resources'
            }
        }
    }
}

// Ensure the TAR task produces a compressed .tar.gz archive
tasks.named('distTar', Tar) {
    compression = Compression.GZIP
    archiveExtension = 'tar.gz'
}

// Disable ZIP archive creation completely across build lifecycle
tasks.named('distZip') {
    enabled = false
}

// -----------------------------------------------------------------------------
// 2. Manifest Generation Task
// -----------------------------------------------------------------------------
def manifestFile = layout.buildDirectory.file("reports/manifest.json")

tasks.register('generateManifest') {
    outputs.file(manifestFile)
    doLast {
        def manifestContent = """{
  "appName": "${project.name}",
  "version": "${project.version}",
  "buildTime": "${new Date().format("yyyy-MM-dd'T'HH:mm:ss'Z'")}",
  "archive": "${project.name}-${project.version}.tar.gz"
}"""
        manifestFile.get().asFile.parentFile.mkdirs()
        manifestFile.get().asFile.text = manifestContent
    }
}

// Guarantee manifest is generated during assembly
tasks.named('assemble') {
    dependsOn tasks.named('generateManifest')
}

// -----------------------------------------------------------------------------
// 3. Artifactory Publishing (Maven Publish Plugin)
// -----------------------------------------------------------------------------
publishing {
    publications {
        mavenTar(MavenPublication) {
            groupId = project.group
            artifactId = project.name
            version = project.version

            // Publish the .tar.gz distribution file
            artifact(tasks.named('distTar')) {
                extension 'tar.gz'
            }

            // Publish the manifest as an auxiliary artifact
            artifact(manifestFile) {
                classifier 'manifest'
                extension 'json'
                builtBy tasks.named('generateManifest')
            }
        }
    }

    repositories {
        maven {
            name = "artifactory"
            // Replace with your Artifactory repository URL
            url = uri("${artifactory_contextUrl}/libs-release-local")
            credentials {
                username = project.findProperty('artifactory_user') ?: System.getenv('ARTIFACTORY_USER')
                password = project.findProperty('artifactory_password') ?: System.getenv('ARTIFACTORY_PASSWORD')
            }
        }
    }
}

exec-9

Query Filter — Wed, 19 Aug 2026 14:44:52 +0000

How to Trigger Each Option

Option 1: Using the `distribution` Plugin

Applying id 'distribution' (or id 'application') automatically hooks tasks into your project lifecycle.

Triggering explicitly:
./gradlew distTar (generates only the .tar / .tar.gz)
./gradlew distZip (generates only the .zip)
./gradlew assembleDist (generates both zip and tar)
Does ./gradlew build create it by default?
Yes, indirectly. ./gradlew build triggers assemble, which depends on assembleDist. This will automatically generate both a .zip and a .tar under build/distributions/.
Note: If you only want a TAR and want to disable the ZIP output during standard builds, you can add this to your build.gradle:

tasks.named('distZip') { enabled = false }

Option 2: Standalone `tasks.register('buildAppTar', Tar)`

Because this is a custom-registered task, Gradle treats it as an opt-in task.

Triggering explicitly:
./gradlew buildAppTar
Does ./gradlew build create it by default?
No. Custom tasks do not run during standard ./gradlew build execution unless you explicitly wire them into the build lifecycle:

// Wire it so ./gradlew build or ./gradlew assemble triggers it
tasks.named('assemble') {
    dependsOn tasks.named('buildAppTar')
}

Which Option Should You Choose?

Feature / Aspect	Option 1: `distribution` Plugin	Option 2: Standalone `Tar` Task
Setup Complexity	Very Low (Idiomatic Gradle)	Low to Medium
Convention Support	Auto-includes `./src/main/dist` content	You must manually define every path
Publishing Integration	Built-in integration with `maven-publish` (`components.java` or `distTar` artifact)	Requires manually attaching the output file to `publishing`
Granular Control	Opinionated defaults	Full control over compression, permissions, and paths

Recommendation

Choose Option 1 (distribution plugin) if your project is a standard Java/Kotlin application or microservice. It is the Gradle standard, simplifies publishing configurations, and handles file permission metadata (0755 for executables vs. 0644 for configs) out of the box.
Choose Option 2 (Custom Tar task) if you have strict, non-standard directory packaging requirements that conflict with Gradle's conventions, or if you want absolute control over when and how the archive is assembled.

For a walkthrough on creating zip/tar archives and managing tasks, see the Gradle Distribution Plugin tutorial.

exec-8

Query Filter — Wed, 19 Aug 2026 14:38:20 +0000

Transitioning from an RPM workflow to a .tar (or .tar.gz) distribution simplifies build pipelines and decouples deployment from host-level package managers (rpm/yum).

The breakdown below details the modifications required for both your Gradle build and your Ansible deployment step.

1. Gradle Project Changes

What to Remove:

RPM Plugins: Remove any OS packaging plugins (e.g., id 'nebula.ospackage', com.netflix.nebula.ospackage).
RPM Configuration Tasks: Delete all ospackage, buildRpm, or rpm tasks from build.gradle.
Artifactory RPM Publications: Remove the RPM artifact publishing configuration inside your publishing block.

What to Add:

Apply Gradle’s native distribution plugin or use a standard Tar task, and update the Artifactory maven-publish or ivy publishing setup.

Example build.gradle snippet:

plugins {
    id 'java'
    id 'distribution'    // Generates .tar and .zip distribution archives
    id 'maven-publish'   // For pushing to Artifactory
}

// Option A: Configure standard distribution structure
distributions {
    main {
        distributionBaseName = 'my-app'
        contents {
            into('lib') {
                from configurations.runtimeClasspath
                from tasks.named('jar')
            }
            into('resources') {
                from 'src/main/resources'
            }
        }
    }
}

// Option B: Custom Tar Task (if you prefer explicit naming/compression)
tasks.register('buildAppTar', Tar) {
    archiveBaseName = 'my-app'
    archiveVersion  = project.version.toString()
    archiveExtension = 'tar.gz'
    compression      = Compression.GZIP

    into('lib') {
        from configurations.runtimeClasspath
        from tasks.named('jar')
    }
    into('resources') {
        from 'src/main/resources'
    }
}

// Update Artifactory publishing to push the TAR and Manifest
publishing {
    publications {
        mavenTar(MavenPublication) {
            // Attach the TAR archive generated by distribution or custom task
            artifact(tasks.named('distTar')) {
                extension 'tar.gz'
            }

            // Attach your manifest file artifact if generated separately
            artifact(file("${buildDir}/reports/manifest.json")) {
                classifier 'manifest'
                extension 'json'
            }
        }
    }
}

2. Ansible Playbook Changes

What to Remove:

RPM Installation Tasks: Remove tasks using ansible.builtin.yum, ansible.builtin.dnf, or ansible.builtin.package to install the .rpm file.
RPM Query / Cleanup Steps: Remove tasks checking rpm -qa or removing old package versions via package managers.

What to Add:

Use ansible.builtin.unarchive to fetch or unpack the .tar.gz directly into the target application path.

- name: Ensure application target directory exists
  ansible.builtin.file:
    path: /opt/my-app
    state: directory
    owner: appuser
    group: appuser
    mode: '0755'

- name: Retrieve Manifest from Artifactory
  ansible.builtin.get_url:
    url: "{{ artifactory_url }}/my-app-{{ app_version }}-manifest.json"
    dest: /opt/my-app/manifest.json
    url_username: "{{ artifactory_user }}"
    url_password: "{{ artifactory_password }}"
    mode: '0644'

- name: Download and unpack TAR directly onto host
  ansible.builtin.unarchive:
    src: "{{ artifactory_url }}/my-app-{{ app_version }}.tar.gz"
    dest: /opt/my-app/
    remote_src: yes  # Downloads directly from Artifactory URL on target host
    owner: appuser
    group: appuser
    mode: '0755'

Key Operational Differences

Permissions & Ownership: RPM automatically handles system permissions during installation via the RPM spec. With .tar, explicitly pass owner, group, and mode attributes in the Ansible unarchive and file tasks.
Symlinking / Versioning: Because .tar extraction overrides or adds to target directories rather than replacing a package database entry, consider extracting each deployment into a versioned folder (e.g., /opt/my-app/releases/1.2.3/) and swapping a symlink (/opt/my-app/current) for atomic rollbacks.

exec-7

Query Filter — Tue, 18 Aug 2026 17:12:06 +0000

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>COMET-EMEA Migration Plan</title>
    <style>
        * {
            box-sizing: border-box;
            font-family: 'Segoe UI', Roboto, system-ui, sans-serif;
        }
        body {
            background: #f4f7fc;
            display: flex;
            justify-content: center;
            padding: 2rem 1rem;
            margin: 0;
        }
        .table-wrapper {
            max-width: 1400px;
            width: 100%;
            background: white;
            border-radius: 20px;
            box-shadow: 0 12px 30px rgba(0,0,0,0.08);
            overflow: hidden;
            padding: 1.5rem 1rem 1rem 1rem;
        }
        h2 {
            margin: 0 0 0.25rem 0;
            font-weight: 600;
            font-size: 1.6rem;
            color: #0b2b4a;
            letter-spacing: -0.3px;
            padding-left: 4px;
        }
        .sub-note {
            color: #2c5778;
            margin: 0 0 1.25rem 0;
            padding-left: 4px;
            font-size: 0.95rem;
            border-left: 4px solid #2b7bb6;
            padding-left: 14px;
            background: #f0f6fe;
            border-radius: 0 8px 8px 0;
            line-height: 1.5;
        }
        .sub-note strong {
            color: #003b6f;
        }
        table {
            width: 100%;
            border-collapse: collapse;
            font-size: 0.9rem;
            background: white;
            border-radius: 14px;
            overflow: hidden;
            box-shadow: 0 2px 8px rgba(0, 20, 40, 0.04);
        }
        th {
            background: #1d3b5c;
            color: white;
            font-weight: 600;
            padding: 14px 10px;
            text-align: left;
            white-space: nowrap;
            font-size: 0.8rem;
            letter-spacing: 0.3px;
            text-transform: uppercase;
        }
        td {
            padding: 12px 10px;
            border-bottom: 1px solid #e9edf4;
            vertical-align: middle;
            background-color: white;
        }
        tr:last-child td {
            border-bottom: none;
        }
        tr:hover td {
            background-color: #f8faff;
        }
        .phase-badge {
            display: inline-block;
            background: #e5eef9;
            color: #00407a;
            font-weight: 600;
            font-size: 0.7rem;
            padding: 4px 10px;
            border-radius: 30px;
            letter-spacing: 0.2px;
            white-space: nowrap;
        }
        .task-id {
            font-weight: 600;
            color: #1a3e62;
            font-size: 0.85rem;
        }
        .task-name {
            font-weight: 500;
            color: #0b2a44;
        }
        .desc {
            color: #2a4058;
            font-size: 0.85rem;
            line-height: 1.4;
            min-width: 220px;
        }
        .date {
            white-space: nowrap;
            font-size: 0.8rem;
            color: #1a405e;
        }
        .duration {
            text-align: center;
            font-weight: 600;
            color: #004b87;
            background: #ecf3fa;
            border-radius: 30px;
            padding: 3px 6px;
            display: inline-block;
            min-width: 40px;
            font-size: 0.8rem;
        }
        .phase-row td:first-child {
            width: 18%;
        }
        .phase-row td:nth-child(2) { width: 8%; }
        .phase-row td:nth-child(3) { width: 18%; }
        .phase-row td:nth-child(4) { width: 30%; }
        .phase-row td:nth-child(5) { width: 11%; }
        .phase-row td:nth-child(6) { width: 11%; }
        .phase-row td:last-child { width: 8%; text-align: center; }

        /* user note at bottom */
        .user-note {
            margin-top: 1.8rem;
            background: #f2f6fd;
            border-radius: 16px;
            padding: 1rem 1.4rem;
            border: 1px solid #d6e3f2;
            display: flex;
            flex-wrap: wrap;
            align-items: center;
            gap: 0.8rem 1.5rem;
        }
        .user-note .label {
            font-weight: 600;
            color: #003e77;
            font-size: 0.95rem;
        }
        .user-note .question {
            background: white;
            padding: 6px 18px;
            border-radius: 40px;
            box-shadow: 0 1px 4px rgba(0,0,0,0.02);
            font-weight: 500;
            color: #003366;
            border: 1px solid #c8d9ef;
        }
        .user-note .pill-group {
            display: flex;
            gap: 0.8rem;
            flex-wrap: wrap;
        }
        .user-note .pill {
            background: #1d3b5c;
            color: white;
            padding: 5px 16px;
            border-radius: 50px;
            font-size: 0.8rem;
            font-weight: 500;
            letter-spacing: 0.2px;
        }
        .user-note .pill-light {
            background: #dce6f3;
            color: #003163;
        }

        @media (max-width: 850px) {
            .table-wrapper {
                padding: 0.5rem;
            }
            table, thead, tbody, th, td, tr {
                display: block;
            }
            thead tr {
                display: none;
            }
            tr {
                margin-bottom: 1rem;
                border: 1px solid #dde5ef;
                border-radius: 14px;
                padding: 0.8rem 0.6rem;
                background: white;
                box-shadow: 0 2px 6px rgba(0,0,0,0.02);
            }
            td {
                border: none;
                padding: 5px 6px;
                display: flex;
                flex-wrap: wrap;
                align-items: baseline;
                gap: 0.2rem 0.5rem;
                background: transparent !important;
            }
            td:before {
                content: attr(data-label);
                font-weight: 600;
                color: #1f4870;
                min-width: 90px;
                font-size: 0.75rem;
                text-transform: uppercase;
                letter-spacing: 0.3px;
            }
            .duration {
                display: inline-block;
            }
            .phase-badge {
                font-size: 0.65rem;
            }
            .desc {
                min-width: unset;
            }
        }
    </style>
</head>
<body>
<div class="table-wrapper">
    <h2>📋 COMET-EMEA · Citi Desktop Migration</h2>
    <div class="sub-note">
        <strong>3 groups defined:</strong> &nbsp; PROD · PILOT · SUPPORT &nbsp; (see note below)
    </div>

    <table>
        <thead>
            <tr>
                <th>Phase</th>
                <th>Task ID</th>
                <th>Task Name</th>
                <th>Description</th>
                <th>Start Date</th>
                <th>End Date</th>
                <th>Duration (h)</th>
            </tr>
        </thead>
        <tbody>
            <!-- Phase 1 -->
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 1: IAM & Group Setup</span></td>
                <td data-label="Task ID"><span class="task-id">1.1</span></td>
                <td data-label="Task Name"><span class="task-name">Define the Pilot Group</span></td>
                <td data-label="Description" class="desc">Identify specific users to participate in the initial production pilot (onshore/offshore support & existing pilots users).</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/21/2026</td>
                <td data-label="Duration"><span class="duration">1</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 1: IAM & Group Setup</span></td>
                <td data-label="Task ID"><span class="task-id">1.2</span></td>
                <td data-label="Task Name"><span class="task-name">Create AD Groups</span></td>
                <td data-label="Description" class="desc">Submit requests to IAM/Directory Services to create SG-COMET-EMEA-Dev-CitiDesktop and SG-COMET-EMEA-Support-CitiDesktop.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/25/2026</td>
                <td data-label="Duration"><span class="duration">1.5</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 1: IAM & Group Setup</span></td>
                <td data-label="Task ID"><span class="task-id">1.3</span></td>
                <td data-label="Task Name"><span class="task-name">Create New Atom Groups</span></td>
                <td data-label="Description" class="desc">Define COMET-EMEA-Pilot and COMET-EMEA-Prov user groups within the Atom deployment console.</td>
                <td data-label="Start Date" class="date">8/21/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">1</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 1: IAM & Group Setup</span></td>
                <td data-label="Task ID"><span class="task-id">1.4</span></td>
                <td data-label="Task Name"><span class="task-name">Consult with OneTouch Team</span></td>
                <td data-label="Description" class="desc">Reach out to the OneTouch team for knowledge sharing and lessons learned from their successful migration.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2</span></td>
            </tr>

            <!-- Phase 2 -->
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 2: Prod Config & Portal Setup</span></td>
                <td data-label="Task ID"><span class="task-id">2.1</span></td>
                <td data-label="Task Name"><span class="task-name">Create AppD Portal Configurations</span></td>
                <td data-label="Description" class="desc">Configure application profiles on the AppD portal for Prod and Pilot environments (Launch Info, atom stream, toggles).</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">1</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 2: Prod Config & Portal Setup</span></td>
                <td data-label="Task ID"><span class="task-id">2.2</span></td>
                <td data-label="Task Name"><span class="task-name">Merge Atom Users into Prod/Pilot Groups</span></td>
                <td data-label="Description" class="desc">Consolidate and map all existing legacy Atom users into the newly created COMET-EMEA-Pilot and COMET-EMEA-Prov groups.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 2: Prod Config & Portal Setup</span></td>
                <td data-label="Task ID"><span class="task-id">2.3</span></td>
                <td data-label="Task Name"><span class="task-name">Sync AD Groups with AppD Portal</span></td>
                <td data-label="Description" class="desc">Map the newly created AD groups to their respective roles and permissions within the AppD portal.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2</span></td>
            </tr>

            <!-- Phase 3 -->
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 3: Pilot & Communication</span></td>
                <td data-label="Task ID"><span class="task-id">3.1</span></td>
                <td data-label="Task Name"><span class="task-name">Launch Pilot Phase</span></td>
                <td data-label="Description" class="desc">Enable the Citi Desktop application profile for the COMET-EMEA-Pilot group to validate stability in Prod.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 3: Pilot & Communication</span></td>
                <td data-label="Task ID"><span class="task-id">3.2</span></td>
                <td data-label="Task Name"><span class="task-name">Send Retirement & Access Notices</span></td>
                <td data-label="Description" class="desc">Broadcast official retirement notices to all COMET-EMEA Prod users with instructions to request Citi Desktop & EEMS access.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2</span></td>
            </tr>

            <!-- Phase 4 -->
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 4: Prod Rollout & Handover</span></td>
                <td data-label="Task ID"><span class="task-id">4.1</span></td>
                <td data-label="Task Name"><span class="task-name">Resolve Pilot Feedback</span></td>
                <td data-label="Description" class="desc">Address any bugs, configuration mismatches or performance issues identified by the Pilot group.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 4: Prod Rollout & Handover</span></td>
                <td data-label="Task ID"><span class="task-id">4.2</span></td>
                <td data-label="Task Name"><span class="task-name">Phased Production Migration</span></td>
                <td data-label="Description" class="desc">Gradually enable the Citi Desktop production profile for batches of COMET-EMEA production users.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2.5</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 4: Prod Rollout & Handover</span></td>
                <td data-label="Task ID"><span class="task-id">4.3</span></td>
                <td data-label="Task Name"><span class="task-name">Hypercare Support</span></td>
                <td data-label="Description" class="desc">Provide dedicated support via the new SG-COMET-EMEA-Support-CitiDesktop AD group.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2.5</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 4: Prod Rollout & Handover</span></td>
                <td data-label="Task ID"><span class="task-id">4.4</span></td>
                <td data-label="Task Name"><span class="task-name">Handover to Decommissioning Team</span></td>
                <td data-label="Description" class="desc">Compile migration sign-off report and hand over to the external team responsible for decommissioning legacy Atom.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">0.1</span></td>
            </tr>
        </tbody>
    </table>

    <!-- user note at bottom (exactly as in the original) -->
    <div class="user-note">
        <span class="label">📌 User note:</span>
        <span class="question">“Do we want support and pilot to be the same group?”</span>
        <span style="color:#1f3b57; font-weight:400; margin-left:0.2rem;">—</span>
        <div class="pill-group">
            <span class="pill">prod</span>
            <span class="pill" style="background:#2a6b96;">pilot</span>
            <span class="pill" style="background:#1f8b4c;">support</span>
            <span class="pill pill-light" style="background:#e5edf8; color:#004a7a;">✅ 3 groups – keep separate</span>
        </div>
    </div>
</div>
</body>
</html>

exec-6

Query Filter — Tue, 18 Aug 2026 17:10:34 +0000

<!DOCTYPE html>

COMET-EMEA Migration Plan
 * { box-sizing: border-box; font-family: 'Segoe UI', Roboto, system-ui, sans-serif; } body { background: #f4f7fc; display: flex; justify-content: center; padding: 2rem 1rem; margin: 0; } .table-wrapper { max-width: 1400px; width: 100%; background: white; border-radius: 20px; box-shadow: 0 12px 30px rgba(0,0,0,0.08); overflow: hidden; padding: 1.5rem 1rem 1rem 1rem; } h2 { margin: 0 0 0.25rem 0; font-weight: 600; font-size: 1.6rem; color: #0b2b4a; letter-spacing: -0.3px; padding-left: 4px; } .sub-note { color: #2c5778; margin: 0 0 1.25rem 0; padding-left: 4px; font-size: 0.95rem; border-left: 4px solid #2b7bb6; padding-left: 14px; background: #f0f6fe; border-radius: 0 8px 8px 0; line-height: 1.5; } .sub-note strong { color: #003b6f; } table { width: 100%; border-collapse: collapse; font-size: 0.9rem; background: white; border-radius: 14px; overflow: hidden; box-shadow: 0 2px 8px rgba(0, 20, 40, 0.04); } th { background: #1d3b5c; color: white; font-weight: 600; padding: 14px 10px; text-align: left; white-space: nowrap; font-size: 0.8rem; letter-spacing: 0.3px; text-transform: uppercase; } td { padding: 12px 10px; border-bottom: 1px solid #e9edf4; vertical-align: middle; background-color: white; } tr:last-child td { border-bottom: none; } tr:hover td { background-color: #f8faff; } .phase-badge { display: inline-block; background: #e5eef9; color: #00407a; font-weight: 600; font-size: 0.7rem; padding: 4px 10px; border-radius: 30px; letter-spacing: 0.2px; white-space: nowrap; } .task-id { font-weight: 600; color: #1a3e62; font-size: 0.85rem; } .task-name { font-weight: 500; color: #0b2a44; } .desc { color: #2a4058; font-size: 0.85rem; line-height: 1.4; min-width: 220px; } .date { white-space: nowrap; font-size: 0.8rem; color: #1a405e; } .duration { text-align: center; font-weight: 600; color: #004b87; background: #ecf3fa; border-radius: 30px; padding: 3px 6px; display: inline-block; min-width: 40px; font-size: 0.8rem; } .phase-row td:first-child { width: 18%; } .phase-row td:nth-child(2) { width: 8%; } .phase-row td:nth-child(3) { width: 18%; } .phase-row td:nth-child(4) { width: 30%; } .phase-row td:nth-child(5) { width: 11%; } .phase-row td:nth-child(6) { width: 11%; } .phase-row td:last-child { width: 8%; text-align: center; } <div class="highlight"><pre class="highlight plaintext"><code> /* user note at bottom */ .user-note { margin-top: 1.8rem; background: #f2f6fd; border-radius: 16px; padding: 1rem 1.4rem; border: 1px solid #d6e3f2; display: flex; flex-wrap: wrap; align-items: center; gap: 0.8rem 1.5rem; } .user-note .label { font-weight: 600; color: #003e77; font-size: 0.95rem; } .user-note .question { background: white; padding: 6px 18px; border-radius: 40px; box-shadow: 0 1px 4px rgba(0,0,0,0.02); font-weight: 500; color: #003366; border: 1px solid #c8d9ef; } .user-note .pill-group { display: flex; gap: 0.8rem; flex-wrap: wrap; } .user-note .pill { background: #1d3b5c; color: white; padding: 5px 16px; border-radius: 50px; font-size: 0.8rem; font-weight: 500; letter-spacing: 0.2px; } .user-note .pill-light { background: #dce6f3; color: #003163; } @media (max-width: 850px) { .table-wrapper { padding: 0.5rem; } table, thead, tbody, th, td, tr { display: block; } thead tr { display: none; } tr { margin-bottom: 1rem; border: 1px solid #dde5ef; border-radius: 14px; padding: 0.8rem 0.6rem; background: white; box-shadow: 0 2px 6px rgba(0,0,0,0.02); } td { border: none; padding: 5px 6px; display: flex; flex-wrap: wrap; align-items: baseline; gap: 0.2rem 0.5rem; background: transparent !important; } td:before { content: attr(data-label); font-weight: 600; color: #1f4870; min-width: 90px; font-size: 0.75rem; text-transform: uppercase; letter-spacing: 0.3px; } .duration { display: inline-block; } .phase-badge { font-size: 0.65rem; } .desc { min-width: unset; } } </style> </code></pre></div> </head> <body> <div class="table-wrapper"> <h2>📋 COMET-EMEA · Citi Desktop Migration</h2> <div class="sub-note"> 3 groups defined:   PROD · PILOT · SUPPORT   (see note below) </div> <table> <thead> <tr> <th>Phase</th> <th>Task ID</th> <th>Task Name</th> <th>Description</th> <th>Start Date</th> <th>End Date</th> <th>Duration (h)</th> </tr> </thead> <tbody>  <tr class="phase-row"> <td data-label="Phase">Phase 1: IAM & Group Setup</td> <td data-label="Task ID">1.1</td> <td data-label="Task Name">Define the Pilot Group</td> <td data-label="Description" class="desc">Identify specific users to participate in the initial production pilot (onshore/offshore support & existing pilots users).</td> <td data-label="Start Date" class="date">8/14/2026</td> <td data-label="End Date" class="date">8/21/2026</td> <td data-label="Duration">1</td> </tr> <tr class="phase-row"> <td data-label="Phase">Phase 1: IAM & Group Setup</td> <td data-label="Task ID">1.2</td> <td data-label="Task Name">Create AD Groups</td> <td data-label="Description" class="desc">Submit requests to IAM/Directory Services to create SG-COMET-EMEA-Dev-CitiDesktop and SG-COMET-EMEA-Support-CitiDesktop.</td> <td data-label="Start Date" class="date">8/14/2026</td> <td data-label="End Date" class="date">8/25/2026</td> <td data-label="Duration">1.5</td> </tr> <tr class="phase-row"> <td data-label="Phase">Phase 1: IAM & Group Setup</td> <td data-label="Task ID">1.3</td> <td data-label="Task Name">Create New Atom Groups</td> <td data-label="Description" class="desc">Define COMET-EMEA-Pilot and COMET-EMEA-Prov user groups within the Atom deployment console.</td> <td data-label="Start Date" class="date">8/21/2026</td> <td data-label="End Date" class="date">8/28/2026</td> <td data-label="Duration">1</td> </tr> <tr class="phase-row"> <td data-label="Phase">Phase 1: IAM & Group Setup</td> <td data-label="Task ID">1.4</td> <td data-label="Task Name">Consult with OneTouch Team</td> <td data-label="Description" class="desc">Reach out to the OneTouch team for knowledge sharing and lessons learned from their successful migration.</td> <td data-label="Start Date" class="date">8/14/2026</td> <td data-label="End Date" class="date">8/28/2026</td> <td data-label="Duration">2</td> </tr>  <tr class="phase-row"> <td data-label="Phase">Phase 2: Prod Config & Portal Setup</td> <td data-label="Task ID">2.1</td> <td data-label="Task Name">Create AppD Portal Configurations</td> <td data-label="Description" class="desc">Configure application profiles on the AppD portal for Prod and Pilot environments (Launch Info, atom stream, toggles).</td> <td data-label="Start Date" class="date">8/14/2026</td> <td data-label="End Date" class="date">8/28/2026</td> <td data-label="Duration">1</td> </tr> <tr class="phase-row"> <td data-label="Phase">Phase 2: Prod Config & Portal Setup</td> <td data-label="Task ID">2.2</td> <td data-label="Task Name">Merge Atom Users into Prod/Pilot Groups</td> <td data-label="Description" class="desc">Consolidate and map all existing legacy Atom users into the newly created COMET-EMEA-Pilot and COMET-EMEA-Prov groups.</td> <td data-label="Start Date" class="date">8/14/2026</td> <td data-label="End Date" class="date">8/28/2026</td> <td data-label="Duration">2</td> </tr> <tr class="phase-row"> <td data-label="Phase">Phase 2: Prod Config & Portal Setup</td> <td data-label="Task ID">2.3</td> <td data-label="Task Name">Sync AD Groups with AppD Portal</td> <td data-label="Description" class="desc">Map the newly created AD groups to their respective roles and permissions within the AppD portal.</td> <td data-label="Start Date" class="date">8/14/2026</td> <td data-label="End Date" class="date">8/28/2026</td> <td data-label="Duration">2</td> </tr>  <tr class="phase-row"> <td data-label="Phase">Phase 3: Pilot & Communication</td> <td data-label="Task ID">3.1</td> <td data-label="Task Name">Launch Pilot Phase</td> <td data-label="Description" class="desc">Enable the Citi Desktop application profile for the COMET-EMEA-Pilot group to validate stability in Prod.</td> <td data-label="Start Date" class="date">8/14/2026</td> <td data-label="End Date" class="date">8/28/2026</td> <td data-label="Duration">2</td> </tr> <tr class="phase-row"> <td data-label="Phase">Phase 3: Pilot & Communication</td> <td data-label="Task ID">3.2</td> <td data-label="Task Name">Send Retirement & Access Notices</td> <td data-label="Description" class="desc">Broadcast official retirement notices to all COMET-EMEA Prod users with instructions to request Citi Desktop & EEMS access.</td> <td data-label="Start Date" class="date">8/14/2026</td> <td data-label="End Date" class="date">8/28/2026</td> <td data-label="Duration">2</td> </tr>  <tr class="phase-row"> <td data-label="Phase">Phase 4: Prod Rollout & Handover</td> <td data-label="Task ID">4.1</td> <td data-label="Task Name">Resolve Pilot Feedback</td> <td data-label="Description" class="desc">Address any bugs, configuration mismatches or performance issues identified by the Pilot group.</td> <td data-label="Start Date" class="date">8/14/2026</td> <td data-label="End Date" class="date">8/28/2026</td> <td data-label="Duration">2</td> </tr> <tr class="phase-row"> <td data-label="Phase">Phase 4: Prod Rollout & Handover</td> <td data-label="Task ID">4.2</td> <td data-label="Task Name">Phased Production Migration</td> <td data-label="Description" class="desc">Gradually enable the Citi Desktop production profile for batches of COMET-EMEA production users.</td> <td data-label="Start Date" class="date">8/14/2026</td> <td data-label="End Date" class="date">8/28/2026</td> <td data-label="Duration">2.5</td> </tr> <tr class="phase-row"> <td data-label="Phase">Phase 4: Prod Rollout & Handover</td> <td data-label="Task ID">4.3</td> <td data-label="Task Name">Hypercare Support</td> <td data-label="Description" class="desc">Provide dedicated support via the new SG-COMET-EMEA-Support-CitiDesktop AD group.</td> <td data-label="Start Date" class="date">8/14/2026</td> <td data-label="End Date" class="date">8/28/2026</td> <td data-label="Duration">2.5</td> </tr> <tr class="phase-row"> <td data-label="Phase">Phase 4: Prod Rollout & Handover</td> <td data-label="Task ID">4.4</td> <td data-label="Task Name">Handover to Decommissioning Team</td> <td data-label="Description" class="desc">Compile migration sign-off report and hand over to the external team responsible for decommissioning legacy Atom.</td> <td data-label="Start Date" class="date">8/14/2026</td> <td data-label="End Date" class="date">8/28/2026</td> <td data-label="Duration">0.1</td> </tr> </tbody> </table>  <div class="user-note"> 📌 User note: “Do we want support and pilot to be the same group?” — <div class="pill-group"> prod pilot support ✅ 3 groups – keep separate </div> </div> </div> </body> </html>

eec-5

Query Filter — Tue, 18 Aug 2026 17:09:01 +0000

<!DOCTYPE html>
<html lang="en">
<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>COMET-EMEA Migration Plan</title>
    <style>
        * {
            box-sizing: border-box;
            font-family: 'Segoe UI', Roboto, system-ui, sans-serif;
        }
        body {
            background: #f4f7fc;
            display: flex;
            justify-content: center;
            padding: 2rem 1rem;
            margin: 0;
        }
        .table-wrapper {
            max-width: 1400px;
            width: 100%;
            background: white;
            border-radius: 20px;
            box-shadow: 0 12px 30px rgba(0,0,0,0.08);
            overflow: hidden;
            padding: 1.5rem 1rem 1rem 1rem;
        }
        h2 {
            margin: 0 0 0.25rem 0;
            font-weight: 600;
            font-size: 1.6rem;
            color: #0b2b4a;
            letter-spacing: -0.3px;
            padding-left: 4px;
        }
        .sub-note {
            color: #2c5778;
            margin: 0 0 1.25rem 0;
            padding-left: 4px;
            font-size: 0.95rem;
            border-left: 4px solid #2b7bb6;
            padding-left: 14px;
            background: #f0f6fe;
            border-radius: 0 8px 8px 0;
            line-height: 1.5;
        }
        .sub-note strong {
            color: #003b6f;
        }
        table {
            width: 100%;
            border-collapse: collapse;
            font-size: 0.9rem;
            background: white;
            border-radius: 14px;
            overflow: hidden;
            box-shadow: 0 2px 8px rgba(0, 20, 40, 0.04);
        }
        th {
            background: #1d3b5c;
            color: white;
            font-weight: 600;
            padding: 14px 10px;
            text-align: left;
            white-space: nowrap;
            font-size: 0.8rem;
            letter-spacing: 0.3px;
            text-transform: uppercase;
        }
        td {
            padding: 12px 10px;
            border-bottom: 1px solid #e9edf4;
            vertical-align: middle;
            background-color: white;
        }
        tr:last-child td {
            border-bottom: none;
        }
        tr:hover td {
            background-color: #f8faff;
        }
        .phase-badge {
            display: inline-block;
            background: #e5eef9;
            color: #00407a;
            font-weight: 600;
            font-size: 0.7rem;
            padding: 4px 10px;
            border-radius: 30px;
            letter-spacing: 0.2px;
            white-space: nowrap;
        }
        .task-id {
            font-weight: 600;
            color: #1a3e62;
            font-size: 0.85rem;
        }
        .task-name {
            font-weight: 500;
            color: #0b2a44;
        }
        .desc {
            color: #2a4058;
            font-size: 0.85rem;
            line-height: 1.4;
            min-width: 220px;
        }
        .date {
            white-space: nowrap;
            font-size: 0.8rem;
            color: #1a405e;
        }
        .duration {
            text-align: center;
            font-weight: 600;
            color: #004b87;
            background: #ecf3fa;
            border-radius: 30px;
            padding: 3px 6px;
            display: inline-block;
            min-width: 40px;
            font-size: 0.8rem;
        }
        .phase-row td:first-child {
            width: 18%;
        }
        .phase-row td:nth-child(2) { width: 8%; }
        .phase-row td:nth-child(3) { width: 18%; }
        .phase-row td:nth-child(4) { width: 30%; }
        .phase-row td:nth-child(5) { width: 11%; }
        .phase-row td:nth-child(6) { width: 11%; }
        .phase-row td:last-child { width: 8%; text-align: center; }

        /* user note at bottom */
        .user-note {
            margin-top: 1.8rem;
            background: #f2f6fd;
            border-radius: 16px;
            padding: 1rem 1.4rem;
            border: 1px solid #d6e3f2;
            display: flex;
            flex-wrap: wrap;
            align-items: center;
            gap: 0.8rem 1.5rem;
        }
        .user-note .label {
            font-weight: 600;
            color: #003e77;
            font-size: 0.95rem;
        }
        .user-note .question {
            background: white;
            padding: 6px 18px;
            border-radius: 40px;
            box-shadow: 0 1px 4px rgba(0,0,0,0.02);
            font-weight: 500;
            color: #003366;
            border: 1px solid #c8d9ef;
        }
        .user-note .pill-group {
            display: flex;
            gap: 0.8rem;
            flex-wrap: wrap;
        }
        .user-note .pill {
            background: #1d3b5c;
            color: white;
            padding: 5px 16px;
            border-radius: 50px;
            font-size: 0.8rem;
            font-weight: 500;
            letter-spacing: 0.2px;
        }
        .user-note .pill-light {
            background: #dce6f3;
            color: #003163;
        }

        @media (max-width: 850px) {
            .table-wrapper {
                padding: 0.5rem;
            }
            table, thead, tbody, th, td, tr {
                display: block;
            }
            thead tr {
                display: none;
            }
            tr {
                margin-bottom: 1rem;
                border: 1px solid #dde5ef;
                border-radius: 14px;
                padding: 0.8rem 0.6rem;
                background: white;
                box-shadow: 0 2px 6px rgba(0,0,0,0.02);
            }
            td {
                border: none;
                padding: 5px 6px;
                display: flex;
                flex-wrap: wrap;
                align-items: baseline;
                gap: 0.2rem 0.5rem;
                background: transparent !important;
            }
            td:before {
                content: attr(data-label);
                font-weight: 600;
                color: #1f4870;
                min-width: 90px;
                font-size: 0.75rem;
                text-transform: uppercase;
                letter-spacing: 0.3px;
            }
            .duration {
                display: inline-block;
            }
            .phase-badge {
                font-size: 0.65rem;
            }
            .desc {
                min-width: unset;
            }
        }
    </style>
</head>
<body>
<div class="table-wrapper">
    <h2>📋 COMET-EMEA · Citi Desktop Migration</h2>
    <div class="sub-note">
        <strong>3 groups defined:</strong> &nbsp; PROD · PILOT · SUPPORT &nbsp; (see note below)
    </div>

    <table>
        <thead>
            <tr>
                <th>Phase</th>
                <th>Task ID</th>
                <th>Task Name</th>
                <th>Description</th>
                <th>Start Date</th>
                <th>End Date</th>
                <th>Duration (h)</th>
            </tr>
        </thead>
        <tbody>
            <!-- Phase 1 -->
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 1: IAM & Group Setup</span></td>
                <td data-label="Task ID"><span class="task-id">1.1</span></td>
                <td data-label="Task Name"><span class="task-name">Define the Pilot Group</span></td>
                <td data-label="Description" class="desc">Identify specific users to participate in the initial production pilot (onshore/offshore support & existing pilots users).</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/21/2026</td>
                <td data-label="Duration"><span class="duration">1</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 1: IAM & Group Setup</span></td>
                <td data-label="Task ID"><span class="task-id">1.2</span></td>
                <td data-label="Task Name"><span class="task-name">Create AD Groups</span></td>
                <td data-label="Description" class="desc">Submit requests to IAM/Directory Services to create SG-COMET-EMEA-Dev-CitiDesktop and SG-COMET-EMEA-Support-CitiDesktop.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/25/2026</td>
                <td data-label="Duration"><span class="duration">1.5</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 1: IAM & Group Setup</span></td>
                <td data-label="Task ID"><span class="task-id">1.3</span></td>
                <td data-label="Task Name"><span class="task-name">Create New Atom Groups</span></td>
                <td data-label="Description" class="desc">Define COMET-EMEA-Pilot and COMET-EMEA-Prov user groups within the Atom deployment console.</td>
                <td data-label="Start Date" class="date">8/21/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">1</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 1: IAM & Group Setup</span></td>
                <td data-label="Task ID"><span class="task-id">1.4</span></td>
                <td data-label="Task Name"><span class="task-name">Consult with OneTouch Team</span></td>
                <td data-label="Description" class="desc">Reach out to the OneTouch team for knowledge sharing and lessons learned from their successful migration.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2</span></td>
            </tr>

            <!-- Phase 2 -->
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 2: Prod Config & Portal Setup</span></td>
                <td data-label="Task ID"><span class="task-id">2.1</span></td>
                <td data-label="Task Name"><span class="task-name">Create AppD Portal Configurations</span></td>
                <td data-label="Description" class="desc">Configure application profiles on the AppD portal for Prod and Pilot environments (Launch Info, atom stream, toggles).</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">1</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 2: Prod Config & Portal Setup</span></td>
                <td data-label="Task ID"><span class="task-id">2.2</span></td>
                <td data-label="Task Name"><span class="task-name">Merge Atom Users into Prod/Pilot Groups</span></td>
                <td data-label="Description" class="desc">Consolidate and map all existing legacy Atom users into the newly created COMET-EMEA-Pilot and COMET-EMEA-Prov groups.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 2: Prod Config & Portal Setup</span></td>
                <td data-label="Task ID"><span class="task-id">2.3</span></td>
                <td data-label="Task Name"><span class="task-name">Sync AD Groups with AppD Portal</span></td>
                <td data-label="Description" class="desc">Map the newly created AD groups to their respective roles and permissions within the AppD portal.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2</span></td>
            </tr>

            <!-- Phase 3 -->
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 3: Pilot & Communication</span></td>
                <td data-label="Task ID"><span class="task-id">3.1</span></td>
                <td data-label="Task Name"><span class="task-name">Launch Pilot Phase</span></td>
                <td data-label="Description" class="desc">Enable the Citi Desktop application profile for the COMET-EMEA-Pilot group to validate stability in Prod.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 3: Pilot & Communication</span></td>
                <td data-label="Task ID"><span class="task-id">3.2</span></td>
                <td data-label="Task Name"><span class="task-name">Send Retirement & Access Notices</span></td>
                <td data-label="Description" class="desc">Broadcast official retirement notices to all COMET-EMEA Prod users with instructions to request Citi Desktop & EEMS access.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2</span></td>
            </tr>

            <!-- Phase 4 -->
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 4: Prod Rollout & Handover</span></td>
                <td data-label="Task ID"><span class="task-id">4.1</span></td>
                <td data-label="Task Name"><span class="task-name">Resolve Pilot Feedback</span></td>
                <td data-label="Description" class="desc">Address any bugs, configuration mismatches or performance issues identified by the Pilot group.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 4: Prod Rollout & Handover</span></td>
                <td data-label="Task ID"><span class="task-id">4.2</span></td>
                <td data-label="Task Name"><span class="task-name">Phased Production Migration</span></td>
                <td data-label="Description" class="desc">Gradually enable the Citi Desktop production profile for batches of COMET-EMEA production users.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2.5</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 4: Prod Rollout & Handover</span></td>
                <td data-label="Task ID"><span class="task-id">4.3</span></td>
                <td data-label="Task Name"><span class="task-name">Hypercare Support</span></td>
                <td data-label="Description" class="desc">Provide dedicated support via the new SG-COMET-EMEA-Support-CitiDesktop AD group.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">2.5</span></td>
            </tr>
            <tr class="phase-row">
                <td data-label="Phase"><span class="phase-badge">Phase 4: Prod Rollout & Handover</span></td>
                <td data-label="Task ID"><span class="task-id">4.4</span></td>
                <td data-label="Task Name"><span class="task-name">Handover to Decommissioning Team</span></td>
                <td data-label="Description" class="desc">Compile migration sign-off report and hand over to the external team responsible for decommissioning legacy Atom.</td>
                <td data-label="Start Date" class="date">8/14/2026</td>
                <td data-label="End Date" class="date">8/28/2026</td>
                <td data-label="Duration"><span class="duration">0.1</span></td>
            </tr>
        </tbody>
    </table>

    <!-- user note at bottom (exactly as in the original) -->
    <div class="user-note">
        <span class="label">📌 User note:</span>
        <span class="question">“Do we want support and pilot to be the same group?”</span>
        <span style="color:#1f3b57; font-weight:400; margin-left:0.2rem;">—</span>
        <div class="pill-group">
            <span class="pill">prod</span>
            <span class="pill" style="background:#2a6b96;">pilot</span>
            <span class="pill" style="background:#1f8b4c;">support</span>
            <span class="pill pill-light" style="background:#e5edf8; color:#004a7a;">✅ 3 groups – keep separate</span>
        </div>
    </div>
</div>
</body>
</html>

exec-4

Query Filter — Tue, 18 Aug 2026 17:02:47 +0000

Area	EMEA Choice	NAM Decision Needed
Number of groups	3 separate: Prod, Pilot, Support	Does NAM want the same, or combine Pilot & Support?
Pilot group composition	Onshore/offshore support + existing pilot users	Who will NAM include?
AD group naming	SG‑COMET‑EMEA‑...	Use SG‑COMET‑NAM‑...
Atom group naming	COMET‑EMEA‑Pilot / COMET‑EMEA‑Prov	Use COMET‑NAM‑Pilot / COMET‑NAM‑Prov
Consultation	Consulted OneTouch team	Consult EMEA team (just finished)
Hypercare support	Dedicated Support AD group	Dedicated or combined?
Decommissioning	External team	External or internal?

exec-4

Query Filter — Tue, 18 Aug 2026 16:44:26 +0000

Phase	Task ID	Task Name	Description (NAM version)	Start Date	End Date	Duration (Hrs)
Phase 1: IAM & Group Setup	1.1	Define the Pilot Group	Identify NAM users for the initial production pilot (consider onshore/offshore support + existing pilot users).	TBD	TBD	1
	1.2	Create AD Groups	Submit requests to IAM/Directory Services to create NAM‑specific AD groups (e.g., SG‑COMET‑NAM‑Dev‑CitiDesktop and SG‑COMET‑NAM‑Support‑CitiDesktop).	TBD	TBD	1.5
	1.3	Create New Atom Groups	Define NAM‑specific user groups within the Atom deployment console (e.g., COMET‑NAM‑Pilot and COMET‑NAM‑Prov).	TBD	TBD	1
	1.4	Consult with EMEA Team	Reach out to the EMEA team (who just completed their pilot) for lessons learned, pitfalls, and best practices.	TBD	TBD	2
Phase 2: Prod Config & Portal Setup	2.1	Create AppD Portal Configurations	Configure AppD portal profiles for NAM Prod and Pilot environments (Launch Info, atom stream, toggles).	TBD	TBD	1
	2.2	Merge Atom Users into Prod/Pilot Groups	Consolidate and map all existing legacy Atom users in NAM into the newly created COMET‑NAM‑Pilot and COMET‑NAM‑Prov groups.	TBD	TBD	2
	2.3	Sync AD Groups with AppD Portal	Map the newly created NAM AD groups to their respective roles/permissions within the AppD portal.	TBD	TBD	2
Phase 3: Pilot & Communication	3.1	Launch Pilot Phase	Enable Citi Desktop for the COMET‑NAM‑Pilot group to validate stability in Prod.	TBD	TBD	2
	3.2	Send Retirement & Access Notices	Broadcast retirement notices to all COMET‑NAM Prod users with instructions to request Citi Desktop & EEMS access.	TBD	TBD	2
Phase 4: Prod Rollout & Handover	4.1	Resolve Pilot Feedback	Address any bugs, config mismatches, or performance issues identified by the NAM Pilot group.	TBD	TBD	2
	4.2	Phased Production Migration	Gradually enable Citi Desktop for batches of COMET‑NAM production users.	TBD	TBD	2.5
	4.3	Hypercare Support	Provide dedicated support via the new NAM Support AD group (e.g., SG‑COMET‑NAM‑Support‑CitiDesktop).	TBD	TBD	2.5
	4.4	Handover to Decommissioning Team	Compile migration sign‑off report and hand over to the team responsible for decommissioning legacy Atom in NAM.	TBD	TBD	0.1

exec-4

Query Filter — Tue, 18 Aug 2026 16:37:05 +0000

To transfer this plan into **Word** while preserving formatting, here are the best approaches. I'll give you **3 options** (ranked from best to quickest), and I've also prepared a **ready-to-copy Word-friendly version** below.

---

## Option 1: Copy as Rich Text (Best for Word)

I've prepared a **clean, Word-optimized table** below. Just **copy the entire table** and paste it directly into Word. It will retain:
- Bold headers
- Column alignment
- Clean spacing
- Color coding (if you paste with "Keep Source Formatting")

---

### COMET-NAM Migration Plan (Adapted from EMEA Template)

| **Phase** | **Task ID** | **Task Name** | **Description (NAM version)** | **Start Date** | **End Date** | **Duration (Hrs)** |
|-----------|-------------|---------------|-------------------------------|----------------|--------------|-------------------|
| **Phase 1: IAM & Group Setup** | 1.1 | Define the Pilot Group | Identify NAM users for the initial production pilot (consider onshore/offshore support + existing pilot users). | TBD | TBD | 1 |
| | 1.2 | Create AD Groups | Submit requests to IAM/Directory Services to create NAM-specific AD groups (e.g., SG-COMET-NAM-Dev-CitiDesktop and SG-COMET-NAM-Support-CitiDesktop). | TBD | TBD | 1.5 |
| | 1.3 | Create New Atom Groups | Define NAM-specific user groups within the Atom deployment console (e.g., COMET-NAM-Pilot and COMET-NAM-Prov). | TBD | TBD | 1 |
| | 1.4 | Consult with EMEA Team | Reach out to the EMEA team (who just completed their pilot) for lessons learned, pitfalls, and best practices. | TBD | TBD | 2 |
| **Phase 2: Prod Config & Portal Setup** | 2.1 | Create AppD Portal Configurations | Configure AppD portal profiles for NAM Prod and Pilot environments (Launch Info, atom stream, toggles). | TBD | TBD | 1 |
| | 2.2 | Merge Atom Users into Prod/Pilot Groups | Consolidate and map all existing legacy Atom users in NAM into the newly created COMET-NAM-Pilot and COMET-NAM-Prov groups. | TBD | TBD | 2 |
| | 2.3 | Sync AD Groups with AppD Portal | Map the newly created NAM AD groups to their respective roles/permissions within the AppD portal. | TBD | TBD | 2 |
| **Phase 3: Pilot & Communication** | 3.1 | Launch Pilot Phase | Enable Citi Desktop for the COMET-NAM-Pilot group to validate stability in Prod. | TBD | TBD | 2 |
| | 3.2 | Send Retirement & Access Notices | Broadcast retirement notices to all COMET-NAM Prod users with instructions to request Citi Desktop & EEMS access. | TBD | TBD | 2 |
| **Phase 4: Prod Rollout & Handover** | 4.1 | Resolve Pilot Feedback | Address any bugs, config mismatches, or performance issues identified by the NAM Pilot group. | TBD | TBD | 2 |
| | 4.2 | Phased Production Migration | Gradually enable Citi Desktop for batches of COMET-NAM production users. | TBD | TBD | 2.5 |
| | 4.3 | Hypercare Support | Provide dedicated support via the new NAM Support AD group (e.g., SG-COMET-NAM-Support-CitiDesktop). | TBD | TBD | 2.5 |
| | 4.4 | Handover to Decommissioning Team | Compile migration sign-off report and hand over to the team responsible for decommissioning legacy Atom in NAM. | TBD | TBD | 0.1 |

---

### Decision Points for COMET-NAM

| **Area** | **EMEA Choice** | **NAM Decision Needed** |
|----------|----------------|--------------------------|
| Number of groups | 3 separate: Prod, Pilot, Support | Does NAM want the same, or combine Pilot & Support? |
| Pilot group composition | Onshore/offshore support + existing pilot users | Who will NAM include? |
| AD group naming | SG-COMET-EMEA-... | Use SG-COMET-NAM-... |
| Atom group naming | COMET-EMEA-Pilot / COMET-EMEA-Prov | Use COMET-NAM-Pilot / COMET-NAM-Prov |
| Consultation | Consulted OneTouch team | Consult EMEA team (just finished) |
| Hypercare support | Dedicated Support AD group | Dedicated or combined? |
| Decommissioning | External team | External or internal? |

---

## Option 2: Export as HTML → Open in Word

1. Copy the **HTML code** I provided in my previous response.
2. Save it as a `.html` file.
3. Right-click → **Open with Word**.
4. Word will render the table with all styling intact.
5. Save as `.docx`.

---

## Option 3: Paste into Google Docs → Download as Word

1. Paste the plain table into Google Docs.
2. Use **Table → Table properties** to adjust borders and shading.
3. Download as `.docx` — formatting is usually preserved well.

---

## Quick Tip for Word

After pasting into Word:
- Go to **Paste Options** → choose **Keep Source Formatting** (or **Merge Formatting**).
- If the table looks off, click **Layout** → **AutoFit** → **AutoFit Window** to stretch it cleanly.

---

Would you like me to:
- **Generate a plain-text version** (no markup) for easier copy-paste?
- **Provide an HTML file** you can save and open directly in Word?
- **Adjust any columns** (e.g., add a "Status" or "Owner" column) before you export?

exec-3

Query Filter — Mon, 17 Aug 2026 15:48:14 +0000

Subject: Proposal & Alignment Request: COMET-NAM PROD Promotion & AD Group Structure

Hi team,

We are initiating the planning phase for the comet-nam PROD promotion. The overarching roadmap includes customer coordination, Atom retirement, and Citi Desktop training sessions.

Before we finalize the execution steps, we need your guidance on the Active Directory (AD) group setup to ensure full alignment with team standards:

Dev Team Separation: Should we proceed with provisioning a dedicated AD group for the NAM dev team to keep permissions distinct from the existing LightSpeed dev group?

Support Team Provisioning: Should we also set up a new AD group for the NAM support team, or does an existing NAM support AD group already cover this requirement?

Please let us know your recommendation on how best to structure these groups so we can finalize the access request path and proceed with the promotion setup.

exec-2

Query Filter — Thu, 13 Aug 2026 13:26:32 +0000

(() => {
  // Capture the full live DOM including html tag and doctype
  const doctype = document.doctype 
    ? new XMLSerializer().serializeToString(document.doctype) + '\n' 
    : '';
  const fullHTML = doctype + document.documentElement.outerHTML;

  // Create a blob and trigger a direct file download
  const blob = new Blob([fullHTML], { type: 'text/html' });
  const url = URL.createObjectURL(blob);
  const a = document.createElement('a');
  a.href = url;
  a.download = `live_page_${new Date().toISOString().slice(0,10)}.html`;
  document.body.appendChild(a);
  a.click();

  // Cleanup object URL and temporary node
  document.body.removeChild(a);
  URL.revokeObjectURL(url);
  console.log('Live DOM successfully exported!');
})();

DEV Community: Query Filter

exec-11

exec-10

exec-9

How to Trigger Each Option

Option 1: Using the distribution Plugin

Option 2: Standalone `tasks.register('buildAppTar', Tar)`

Which Option Should You Choose?

Recommendation

exec-8

1. Gradle Project Changes

What to Remove:

What to Add:

2. Ansible Playbook Changes

What to Remove:

What to Add:

Key Operational Differences

exec-7

exec-6

eec-5

exec-4

exec-4

exec-4

exec-3

exec-2

Option 1: Using the `distribution` Plugin