IPTD-305
Saving License and Requirement Documents in one secure pdf file.
Description
Need a way to combine NJEMS LetterBuilder Permit Document and Requirements Report into single PDF
Project Justification
One radioactive materials license document automatically saved as a secure pdf in NJEMS which includes the information from the Rad Word Doc and the Requirements Report.
We believe it could have benefits for all DEP programs. We are unsure if other programs need secure documents. Surely, they should be secure if PII is included in any document. Our license documents do not contain PII, however they must be secure as stated above.
We believe it could have benefits for all DEP programs. We are unsure if other programs need secure documents. Surely, they should be secure if PII is included in any document. Our license documents do not contain PII, however they must be secure as stated above.
Activity
Show:
Permit PDF combination was completed, and CGI created a mechanism to exclude PPI Types from uploading attachments to HighView. This is complete. Note that it does not yet work in Pega, as CGI is still investigating a way to do this, since they cannot use the local machine to export Word to pdf, or print to folder and upload, as is done in legacy
DOIT is working with BER and CGI o determine the rules in NJEMS on what to exclude and what not to exclude, as well as combining the permit report PDF for BER. See attached email
A meeting was held on 2/1/2023, where the following was discussed/put into motion:
The ability exists to combine NJEMS LetterBuilder documents and NJEMS reports (e.g. the Requirements Report) into a single PDF and place that PDF under the NJEMS activity. This PDF could then viewed, printed, and/or be e-mailed out of NJEMS using the NJEMS email functionality. This only requires reference table data to be configured for this specific PDF to be created.
Mike McCormack and Glenn Savary will work with the Rad folks and Dave Bowman to set up this reference data in Dev to test prior to moving it to production
2. Although items in the attachment list can be flagged not for public consumption, they still get migrated into HighView, as well as do Central File PDFs. Due to the sensitivity of the Rad documents/attachments, we need to be able to exclude these items from being automatically ingested into HighView before we can put the new Rad Permit PDF into production or have the Rad folks start using the Attachment List.
Michele Zola will discuss with CGI the level of effort and possible timeframe to modify the existing NJEMS-HighView interface to exclude the ingestion of any document/attachment from any of the 6 PI Types for Rad Mat into HighView
3. Jim B. will update the DOIT IT Project Tracking System to add these notes to the item for this project (IPTD 305) and the Rad folks can subscribe to this item to track its progress