E-Filing-Case PDF V1 (Vf)

[Susmitabe]

Is your feature request related to a problem? Please describe.

Scope: PUCAR Case PDF Format -with Feedback.pdf PUCAR_ Sample Case Bundle.pdf

Describe the solution you'd like Complaint Pdf , All documents appended

Tasks - @anirudh-0

• [x] #2276
• [x] Store Case Complaint PDF pre-sign, post-sign and Case Bundle PDF separately.
• [ ] endpoints for case PDFs
  • [x] #2275
  • [ ] endpoint for multi-sign of case complaint PDF - @shambhavigoel1002
  • [ ] endpoint for generating case bundle PDF, to be called anytime during filing - does not save to filestore
  • [ ] endpoint for generating case bundle PDF, to be called by cronjob post filing - saves to filestore
• [ ] notes and undertakings - @Taherabharmal this section needs info on where to show note and content/language of the note/undertaking
  • [ ] note to upload only complaint section
  • [ ] undertaking in signing page about case details ( language yet to be received )
• [ ] cover pages for all applications and documents and case bundle (for applications, on initial upload or on generation TBD, currently going with on generation) @TusharKatiyar2002
• [ ] ensure application document has uploaded docs merged into the application PDF post signing

Additional context

• Multi sign we need confirmation
• CMP/1/2024 instead of CMP No. 1 of 2024 in all places applicable
• leave signature text as is in template, if possible leave some whitespace above, like 4 lines

[atulgupta2024]

Tasks

1. Create CRON job to run at midnight and invoke /casemanager/case/v1/bulk/_buildcasebundle API. SYSTEM ROLE.
2. Create Master data as per design sheet master for bundle structure master for events to listen to
3. Implement Bulk and Single Case bundle APIs including Entity to store details with regards start/stop/count, error details (retry logic). log in case of error
4. Implement Event listeners 2 listeners, both with case management service listener 1 - listening to this event from CRON job. only 1 specific event it will listen to listener 2 - listening to all sorts of events in the system for updating the bundle index (edited)
5. Create Template PDFs for cover page and title page
6. write additional event emitters for things that don't already have a supporting event
7. Update case NIA schema as per changes that have happened to the complaint section of case filing. @anirudh-0 seems to have already done this
8. @anirudh-0 @manimaarans there is a common-masters.DocumentType which has the different types of documents that are being uploaded as part of the complaint. Is the ID mentioned here used to store the types of documents uploaded with the case complaint? IF not, then we need to do the following

• update case create/update API calls to use case_nia.json schema to store the complaint data. Without this will not be able to identify different types of documents submitted along with the case.

@suresh12 @Ramu-kandimalla @subhashini-egov FYI