253 lines
7.7 KiB
Plaintext
253 lines
7.7 KiB
Plaintext
JIRA Story - RAG Knowledge Base
|
||
|
||
Accounting IA-2691: Remove Nightly Cancel Process for Manual Cancels from MP Nightly
|
||
|
||
Chunk 1: Overview
|
||
|
||
Metadata:
|
||
storyId=IA-2691, type=overview, domain=manualCancel, workflow=nightlyProcessing
|
||
|
||
Content:
|
||
Purpose:
|
||
Extracts the manual cancel process from the MP nightly job to enable independent execution, ensuring manual cancels continue to function after MP is decommissioned.
|
||
|
||
Business Goal:
|
||
Maintain continuity of cancel notices while decoupling from the MP nightly schedule, allowing operational flexibility and independent scheduling.
|
||
|
||
Core Behavior:
|
||
|
||
Remove manual cancel logic from MP nightly job
|
||
Execute cancel process independently as a standalone job
|
||
Generate cancel notices that exactly match requested manual cancels
|
||
Replicate MP weekend and holiday behavior (as per C390)
|
||
|
||
Outcome:
|
||
Manual cancel requests continue to be processed reliably, producing accurate cancel notices even if MP nightly job is no longer active.
|
||
|
||
Chunk 2: Preconditions and Dependencies
|
||
|
||
Metadata:
|
||
storyId=IA-2691, type=preconditions, dependencies=MPNightly,C461,IINSE461,C390
|
||
|
||
Content:
|
||
Required Preconditions:
|
||
|
||
MP nightly job currently includes the manual cancel process
|
||
C461 program and IINSE461 logic are accessible for reuse
|
||
Weekend and holiday behavior must be mimicked (C390)
|
||
|
||
Dependencies:
|
||
|
||
Access to MP nightly job logic for verification
|
||
Spool files for validation of cancel notices
|
||
Potential creation of a new scheduled job for independent execution
|
||
|
||
Implicit Rule (Made Explicit):
|
||
|
||
Manual cancels must continue to execute correctly regardless of MP nightly status
|
||
Any changes to logic must maintain consistency with prior cancel notice behavior
|
||
Chunk 3: Functional Requirement - Manual Cancel Process
|
||
|
||
Metadata:
|
||
storyId=IA-2691, type=functional, documentType=ManualCancel
|
||
|
||
Content:
|
||
Required Fields (Normalized):
|
||
|
||
CancelRequestId
|
||
PolicyNumber
|
||
CancelNoticeDate
|
||
CancelReason
|
||
|
||
Purpose:
|
||
Represents manual cancel requests that must trigger cancel notices.
|
||
|
||
Implicit Rules (Made Explicit):
|
||
|
||
Each manual cancel request generates exactly one cancel notice
|
||
CancelNoticeDate represents the date notice is generated
|
||
CancelReason must be preserved for downstream reporting and decisioning
|
||
Weekend/holiday cancel logic (C390) must be applied consistently
|
||
Chunk 4: Workflow and Processing Flow
|
||
|
||
Metadata:
|
||
storyId=IA-2691, type=workflow, orchestration=manualCancel
|
||
|
||
Content:
|
||
Processing Flow:
|
||
|
||
Receive manual cancel requests
|
||
Execute cancel logic via standalone job (extracted from MP nightly)
|
||
Call C461, which invokes IINSE461
|
||
Generate cancel notices for each request
|
||
Output spool file for validation
|
||
Verify cancel notices match requested cancels
|
||
|
||
Key Rule:
|
||
Standalone cancel process must replicate MP nightly behavior, including weekends and holidays, without requiring MP job execution.
|
||
|
||
Chunk 5: Non-Functional Requirements
|
||
|
||
Metadata:
|
||
storyId=IA-2691, type=nonFunctional, category=processReliability
|
||
|
||
Content:
|
||
System Requirements:
|
||
|
||
Standalone job must reliably produce accurate cancel notices
|
||
Execution should be schedulable independently of MP nightly job
|
||
Process must not degrade existing system performance
|
||
|
||
Performance Consideration:
|
||
|
||
Must complete within acceptable operational window
|
||
Spool file validation must be efficient and precise
|
||
Chunk 6: External System Responsibilities
|
||
|
||
Metadata:
|
||
storyId=IA-2691, type=externalSystems, systems=MPNightly,C461,IINSE461
|
||
|
||
Content:
|
||
MPNightly Responsibilities:
|
||
|
||
Previously provided manual cancel execution logic
|
||
|
||
C461 Responsibilities:
|
||
|
||
Execute cancel process logic
|
||
Call IINSE461 for core cancel functionality
|
||
|
||
IINSE461 Responsibilities:
|
||
|
||
Generate cancel notices for each manual cancel request
|
||
|
||
Implicit Rule (Made Explicit):
|
||
|
||
Spool files act as primary validation mechanism for cancel notices
|
||
Standalone job leverages existing logic but becomes the primary executor of manual cancels
|
||
Chunk 7: Business Rules
|
||
|
||
Metadata:
|
||
storyId=IA-2691, type=businessRules, domain=manualCancelProcessing
|
||
|
||
Content:
|
||
Core Rules:
|
||
|
||
Each manual cancel request triggers one cancel notice
|
||
CancelNoticeDate must reflect actual notice generation date
|
||
Weekend and holiday rules (C390) must be applied to standalone execution
|
||
Standalone job must fully replicate MP nightly cancel behavior
|
||
|
||
Edge Cases:
|
||
|
||
MP nightly job is offline → manual cancels must still execute correctly
|
||
Multiple cancel requests for same policy → each request generates a separate notice
|
||
Discrepancy in cancel notice count → requires spool file validation
|
||
Chunk 8: Data Quality Assumptions and Risks
|
||
|
||
Metadata:
|
||
storyId=IA-2691, type=dataQuality, riskLevel=low
|
||
|
||
Content:
|
||
Assumptions:
|
||
|
||
Cancel requests are accurate and complete
|
||
C461/IINSE461 logic correctly reflects MP nightly behavior
|
||
Spool files reliably record all cancel notices
|
||
|
||
Risks:
|
||
|
||
Discrepancies between standalone job output and prior MP behavior
|
||
Missing or incorrect cancel requests may result in missing notices
|
||
|
||
Mitigation:
|
||
|
||
Validate output against MP nightly logic before full deployment
|
||
Use spool files to verify notice counts
|
||
Test weekend/holiday scenarios explicitly
|
||
Chunk 9: Search Queries Supported
|
||
|
||
Metadata:
|
||
storyId=IA-2691, type=queryPatterns, purpose=RAGRetrieval
|
||
|
||
Content:
|
||
This knowledge base supports queries such as:
|
||
|
||
"How is manual cancel process extracted from MP nightly?"
|
||
"Which programs handle manual cancel notices?"
|
||
"How are cancel notices validated?"
|
||
"How is C390 weekend/holiday behavior applied?"
|
||
"What fields are required for manual cancel requests?"
|
||
"How do standalone cancel jobs differ from MP nightly execution?"
|
||
"How are discrepancies in cancel notice counts handled?"
|
||
|
||
|
||
Chunk 10: Before vs After Architecture
|
||
|
||
Metadata:
|
||
storyId=IA-2691, type=architecture, domain=manualCancel, view=beforeAfter
|
||
|
||
Content:
|
||
|
||
Before:
|
||
|
||
Manual cancel logic was embedded in MP nightly job.
|
||
Execution depended on MP nightly schedule.
|
||
Weekend/holiday behavior (C390) applied implicitly within MP logic.
|
||
Cancel notices generated as part of broader MP nightly spool output.
|
||
|
||
After:
|
||
|
||
Manual cancel process extracted into a standalone job.
|
||
Independent scheduling possible outside MP nightly window.
|
||
C461/IINSE461 handle cancel execution logic directly.
|
||
Weekend/holiday behavior (C390) explicitly applied.
|
||
Spool file output used solely for manual cancel validation.
|
||
|
||
Impact:
|
||
|
||
Decouples manual cancel responsibility from MP nightly job.
|
||
Reduces dependency risk if MP nightly fails or is decommissioned.
|
||
Provides clear operational boundaries for monitoring and reruns.
|
||
|
||
Chunk 11: Operational Runbook Implications
|
||
|
||
Metadata:
|
||
storyId=IA-2691, type=operations, domain=manualCancel, category=runbook
|
||
|
||
Content:
|
||
|
||
Rerun Procedure:
|
||
|
||
Identify pending manual cancel requests.
|
||
Execute standalone manual cancel job.
|
||
Verify spool file output matches requested cancel count.
|
||
If discrepancies exist, rerun job after investigation.
|
||
|
||
Monitoring:
|
||
|
||
Track job execution status via scheduler logs.
|
||
Validate cancel notice count against request queue.
|
||
Compare output against historical MP nightly behavior for consistency.
|
||
|
||
Alerts:
|
||
|
||
Alert if job fails to complete or crashes.
|
||
Alert if cancel notice count ≠ cancel request count.
|
||
Alert for spool file generation issues.
|
||
Alert for failed weekend/holiday behavior logic (C390).
|
||
|
||
Key Operational Considerations:
|
||
|
||
Job can be scheduled independently of MP nightly batch window.
|
||
Spool files are primary source for verification; store and retain per SLA.
|
||
Include rollback or compensating actions if notices are incorrectly generated.
|
||
Document all manual reruns in operational logs for auditing purposes.
|
||
|
||
These two chunks complement the earlier 9 chunks perfectly: the architecture chunk visualizes the decoupling and the runbook chunk gives concrete operational guidance for execution, monitoring, and alerting.
|
||
|
||
If you want, I can
|
||
also generate a compact visual diagram for “Before vs After Architecture” to include in the KB—it’s highly useful for onboarding and RAG retrieval.
|
||
|
||
|