Rebase MCP_P11 to main#324
Merged
Merged
Conversation
… fields in LTH and LT_DX.
…s in OTH and OT_DX.
…D_IND Dbdaart 15350 fix dgns cd ind
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What is this and why are we doing it?
Rebase my branch
DBDAART-15686](https://jiraent.cms.gov/browse/DBDAART-15686): Fix and unit test the defect in mcp.py
DBDAART-15932 (https://jiraent.cms.gov/browse/DBDAART-15932): MCP: Python code should check MCR header record, not PRV header record
What are the security implications from this change?
none
How did I test this?
N/A pulling in changes from main, reviewed comparison between forks
Should there be new or updated documentation for this change? (Be specific.)
Done. Updated MCP technical specs that clarifies record for fil_type ‘MCR’ is used to identify CSO (TAF MCP Technical Specifications_PI11.docx). Other ticket is fixing bug in code and does not need documentation update.
PR Checklist