Operational Guide for GDS Compassionate Engagement Migration

The Operational Guide – GDS Compassionate Engagement Module (APT 2.0), Version 1.0 dated 06.08.2026, provides instructions for processing applications migrated from the Legacy GDS Compassionate Module to APT 2.0.

1. Migration of Applications

  • Migration from the Legacy GDS Compassionate Module to APT 2.0 was completed between 27.07.2026 and 05.08.2026, as per Directorate Letter No. 17-33/2025-GDS dated 21.07.2026.
  • Only applications not pushed to CCE in the Legacy Module were migrated to APT 2.0.
  • Applications already pushed to CCE remain in the Legacy Module and will continue up to DPS Approval.
  • The Legacy Portal will now be used only for CCE/DPS processing; new cases cannot be pushed to CCE.
  • The migration is a one-time activity, and no further migration of pending cases is planned.

2. Missing / Default Data

Several mandatory fields that were unavailable in the Legacy Module have been populated with default values such as “NA”. These include:

  • Employee Reservation Category
  • Case Mark Number
  • Last Office of Working
  • Family Address
  • Applicant Disability Percentage/PwBD Category
  • Parents' / Guardian's Name
  • FIR Number
  • Dependent Mobile Number

The Legacy Online Application Submission Date has been mapped to Manual Application Submitted On. If these details are required, the case can be reverted to the Applicant/Sub-Division/Division for updating.

Any partially completed submission or verification from the Legacy Module has been reset and must be completed afresh in APT 2.0.

3. Cases with Discrepancies

Cases having critical missing or incorrect information are placed under “List of Cases with Discrepancies.”

Examples include:

  • Parent Office details
  • Parent Sub-Division/Division/Region/Circle details
  • Verification Sub-Division details
  • Valid 8-digit Employee ID
  • Other migration-related discrepancies

Such cases will not enter the normal workflow until the concerned Division corrects the discrepancies. Once corrected, they automatically return to the appropriate pending stage.

If the Employee ID is not a valid 8-digit ID, the Division must create a valid Employee ID in the PIS Module and update it in the case.

4. Viewing Migrated Cases

Migrated cases can be viewed by Divisions through “List of Cases Registered.” They can be identified using “Migrated from Legacy to APT” = Yes. The current processing status is displayed in the status column.

Applications already submitted in the Legacy Portal are made available in APT 2.0 at the same processing stage where they were pending.

5. Handling “NA” Fields

During verification, fields that were unavailable in the Legacy system may appear as “NA.”

If correction is required:

  1. Select the relevant field under the Discrepancy dropdown.
  2. Enter appropriate remarks.
  3. Click Add.
  4. Submit the discrepancy.

The application will then be reverted to the appropriate stage for correction.

However, Sub-Division/Division/CCE officials may proceed with verification without marking an “NA” field as a discrepancy if they decide that correction is not necessary. The system will not generate an error.

6. Procedure for Updating Discrepancies

The Division user should:

  1. Log in to the GDS – Compassionate Engagement (CCE) application.
  2. Select “List of Cases with Discrepancies.”
  3. Click the Employee ID of the required case.
  4. Review the fields flagged for discrepancies.
  5. Enter the correct information.
  6. Click Submit.

Only the fields identified as discrepancies are displayed for correction.

After successful submission:

  • A confirmation such as “Discrepancy updated successfully” is displayed.
  • The case is removed from the discrepancy dashboard.
  • It returns to the concerned processing stage.
  • Processing can continue from the same stage at which the case was left in the Legacy Module, without loss of progress. 
Migrated GDS Compassionate Engagement cases should be processed in APT 2.0 from their existing stage. Cases with migration-related discrepancies must be corrected through the dedicated discrepancy dashboard before they can continue in the workflow.

Updates:

Follow us on WhatsApp, Telegram Channel, Twitter and Facebook for all latest updates

Post a Comment

Previous Post Next Post

Most Visited

Follow us on WhatsApp, Telegram Channel, Twitter and Facebook for all latest updates

Search Content of www.potools.blogspot.com @