Bug #17355 Nexus Integration Missing Mandatory Request Header

Summary

After analyzing the bug system information and conducting an investigation, it has been identified that the Nexus integration is missing a required request header called {x-ctx-type: PROJECT}.  

This request header is essential for the appropriate project record creation process in the custom module (Village Information). The absence of this header causes the system to select the highest sequence number among all project records associated with the custom module. 

Step 1: Analyzed bug system information to understand the reported issue

Step 2: Examined the integration between Nexus and the custom module

Step 3: Inspected the API endpoints and request headers used in the integration

Step 4: Found that the request header {x-ctx-type: PROJECT} was missing in the API endpoint (https://{domain}/rest/api/v3/module-record/draft/shared-draft)

Step 5: Verified that the web app works correctly when the request headers contain the property x-ctx-type: PROJECT

Based on the investigation, it has been concluded that the missing request header {x-ctx-type: PROJECT} in the Nexus integration is causing the incorrect project record creation in the custom module (Village Information). 

This issue affects multiple projects, and its resolution is essential to maintain the integrity and accuracy of project records. 

To resolve the bug, the following solution is proposed:

Step 1: In the Nexus integration, we need to add the request header {x-ctx-type: PROJECT} to the API endpoint (https://{domain}/rest/api/v3/module-record/draft/shared-draft).

Step 2: This endpoint is responsible for sending the processed response from the Nexus integration to the backend service of the web application.

Step 3: By implementing this solution, the correct project record creation process for the custom module (Village Information) will be ensured, as the system will consider the appropriate project sequence number based on the request header.

Step 4:This solution has already been tested and proven effective within the web application, where the bug does not occur when the request headers contain the property x-ctx-type: PROJECT