2.36.00 Release Notes

Enhancements

Enhancement#

Primary Function

Enhancement Detail

ENH-609

Duplicate Participant Service

End of Day Process

Within the SPIRIT WIC system, the End of Day Command Line Batch Processing that occurs when the BatchProcessor.dll is run from the Command Prompt was expanded to include Duplicate Participant Service processing.

R1: Ensure that the new EOD correctly processes and updates the appropriate records for the following:

• Identify Potential Duplicate Participants

To accommodate the R1 requirement for this enhancement, the following new stored procedures were added and distributed with this release of the software:

• GetDuplicateParticipantConfiguration

• GetNonDuplicateParticipants

• RemoveDuplicateParticipant

• GetMemberPhoneticNullValues

Four new values were added to the MEMBER table.

For more information, see the database changes for this enhancement.

R2: The release notes should contain the name of any stored procedures used by EOD after these changes have been applied.

To accommodate the R2 requirement for this enhancement, the following stored procedures were added and distributed with this release of the software:

• GetDuplicateParticipantConfiguration

• GetNonDuplicateParticipants

• RemoveDuplicateParticipant

• GetMemberPhoneticNullValues

For more information, see the database changes for this enhancement.

R3: The legacy EOD process shall discontinue the process of identifying potential duplicate participants

To accommodate the R3 requirement for this enhancement, changes to End of Day Processing for ENH-609 removed Duplicate Participant Service processing from the End of Day Process in the Scheduled Job Administration application module. With the 2.36.00 release of the SPIRIT WIC system, Duplicate Participant Service processing now occurs only during End of Day Command Line Batch Processing.

R4: The new EOD will accept any modifications to criteria in the DuplicateParticipantConfiguration table.

To accommodate the R4 requirement for this enhancement, the following new GetDuplicateParticipantConfiguration stored procedure was added and distributed with this release of the software to return criteria from the DUPLICATEPARTICIPANTCONFIGURATION table for determining potential duplicate participants.

For more information, see the database changes for this enhancement.

R5: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition.

To accommodate the R5 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database.

R6: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOD.

To accommodate the R6 requirement for this enhancement, the prerequisite processes continue to run as intended.

This process will only run in End of Day if at least one record exists in the DuplicateParticipantConfiguration table with the Include in Compare column equal to "Y".

ENH-611

Appointment Reminder E-mail (Output)

End of Day Process

Within the SPIRIT WIC system, the End of Day Command Line Batch Processing that occurs when the BatchProcessor.dll is run from the Command Prompt was expanded to include Appointment Reminder E-mail (Output) processing.

R1: The release notes should include a reminder that states will want to clear participant emails from records, in their test environment, so that real participants are not sent test emails.

To accommodate the R1 requirement for this enhancement, states should clear participant e-mails from records in their test environment, so that real participants are not sent test e-mails.

R2: Ensure that the new EOD processes correctly sends appointment reminder emails for the appropriate records.

To accommodate the R2 requirement for this enhancement, the following new stored procedures were added and distributed with this release of the software:

• GetAppointmentReminders

• GetReferenceDictionary

Four new values were added to the EBTCONNECTIONINFO table.

The Appointment Reminder Service adds a new record with the “WICEOD” value for PROCESSNAME and the "WICEOD" value for SYSTEMNAME to the COMMREQUEST table if one does not exist.

For more information, see the database changes for this enhancement.

R3: Ensure that the new EOD logs the appointment reminder email details appropriately in the EOD process log if business rule APT_REMINDERLOGDETAILSENABLED is set to Y.

To accommodate the R3 requirement for this enhancement, the following new GetStateBusinessRuleParametersstored procedure was added and distributed with this release of the software.

Failed appointment reminder e-mails are always logged in the SCHEDULEDJOBLOG table of the SPIRIT database. If the value of the APT_REMINDERLOGDETAILSENABLED business rule equals "Y", the Appointment Reminder Service also logs all successful appointment reminder e-mails.

For more information, see the database changes for this enhancement.

R4: Ensure a note is entered in the participant folder if an appointment reminder email is sent.

To accommodate the R4 requirement for this enhancement, the following new stored procedure was added and distributed with this release of the software:

• GetNextHealthNoteId

The Appointment Reminder Service creates a participant Health Note for each successful e-mail.

For more information, see the database changes for this enhancement.

R5: The release notes should contain the name of any stored procedures used by EOD after these changes have been applied.

To accommodate the R5 requirement for this enhancement, the following stored procedures were added or modified and distributed with this release of the software:

• GetStateBusinessRuleParameters

• GetAppointmentReminders

• GetReferenceDictionary

• GetNextHealthNoteId

For more information, see the database changes for this enhancement.

R6: The legacy EOD process shall discontinue sending appointment reminder emails.

To accommodate the R6 requirement for this enhancement, changes to End of Day Processing for ENH-611 removed Appointment Reminder E-mail (Output) processing from the End of Day Process in the Scheduled Job Administration application module. With the 2.36.00 release of the SPIRIT WIC system, Appointment Reminder E-mail (Output) processing now occurs only during End of Day Command Line Batch Processing.

R7: The legacy EOD process shall discontinue logging details of appointment reminder emails.

To accommodate the R7 requirement for this enhancement, changes to End of Day Processing for ENH-611 removed Appointment Reminder E-mail (Output) processing from the End of Day Process in the Scheduled Job Administration application module.

R8: All new processes will log information to the scheduled job log in a manner consistent with the original versions; however, the order may be different since the job order may change during transition.

To accommodate the R8 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database.

R9: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOD.

To accommodate the R9 requirement for this enhancement, the prerequisite processes continue to run as intended.

ENH-617

Process Pending Vendor Disqualifications

End of Day Process

Within the SPIRIT WIC system, the End of Day Command Line Batch Processing that occurs when the BatchProcessor.dll is run from the Command Prompt was expanded to include Pending Vendor Disqualifications Service processing.

R1: Ensure that the new EOD processes Vendor Disqualifications correctly and updates the appropriate records when business rule EOD_PROCESSPENDINGDISQUALIFICATION is set to Y.

To accommodate the R1 requirement for this enhancement, the new UpdatePendingVendorDisqualifications stored procedure was added and distributed with this release of the software.

When the EOD_PROCESSPENDINGDISQUALIFICATION business rule and the EOD_RUNVENDORPROCESSES business rule equal "Y", the Pending Vendor Disqualifications Service updates the appropriate vendor records.

For more information, see the database changes for this enhancement.

The legacy End of Day process contained the following errors, which CDP believes were resolved with the changes made to End of Day Command Line Batch Processing for ENH-617:

• Vendor stamps were not terminated.

• Records were not inserted into the STATUSHISTORY table.

• The SEQNUMBERS table was not updated with the Max STATUSHISTORYID value for the STATUSHISTORY KEYCODE record.

R2: Vendor disqualifications should not process in new EOD when business rule EOD_PROCESSPENDINGDISQUALIFICATION is set to N.

To accommodate the R2 requirement for this enhancement, the new UpdatePendingVendorDisqualifications stored procedure was added and distributed with this release of the software.

If value of the EOD_PROCESSPENDINGDISQUALIFICATION business rule equals "N", the Pending Vendor Disqualifications Service does not update the appropriate vendor records.

For more information, see the database changes for this enhancement.

R3: The release notes should contain the name of any stored procedures used by EOD after these changes have been applied.

To accommodate the R3 requirement for this enhancement, the new UpdatePendingVendorDisqualifications stored procedure was added and distributed with this release of the software.

R4: The legacy EOD process shall discontinue processing vendor disqualifications.

To accommodate the R4 requirement for this enhancement, changes to End of Day Processing for ENH-617 removed Process Pending Disqualification processing from the End of Day Process in the Scheduled Job Administration application module. With the 2.36.00 release of the SPIRIT WIC system, Pending Vendor Disqualifications Service processing now occurs only during End of Day Command Line Batch Processing.

R5: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition.

To accommodate the R5 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database.

R6: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOD.

To accommodate the R6 requirement for this enhancement, the prerequisite processes continue to run as intended:

ENH-618

Process Sanction Points

End of Day Process

Within the SPIRIT WIC system, the End of Day Command Line Batch Processing that occurs when the BatchProcessor.dll is run from the Command Prompt was expanded to include Sanction Points Service processing.

R1: Ensure that the new EOD processes expired vendor sanction points correctly and updates the appropriate records when business rule EOD_PROCESSSANCTIONPOINTS is set to "Y".

To accommodate the R1 requirement for this enhancement, the new ProcessSanctionPoints stored procedure was added and distributed with this release of the software.

When the values of both the EOD_PROCESSSANCTIONPOINTS and EOD_RUNVENDORPROCESSES business rules equal "Y", the Sanction Points Service updates the appropriate vendor records.

For more information, see the database changes for this enhancement.

R2: The new EOD process should not remove expired vendor sanction points if business rule EOD_PROCESSSANCTIONPOINTS is set to “N”.

To accommodate the R2 requirement for this enhancement, the new ProcessSanctionPoints stored procedure was added and distributed with this release of the software.

If value of either the EOD_PROCESSSANCTIONPOINTS business rule or the EOD_RUNVENDORPROCESSES business rule equals "N", the service terminates.

For more information, see the database changes for this enhancement.

R3: The release notes should contain the name of any stored procedures used by EOD after these changes have been applied.

To accommodate the R3 requirement for this enhancement, the new ProcessSanctionPoints stored procedure was added and distributed with this release of the software.

For more information, see the database changes for this enhancement.

R4: The legacy EOD process shall discontinue processing expired vendor sanction points.

To accommodate the R4 requirement for this enhancement, changes to End of Day Processing for ENH-618 removed Process Sanction Points processing from the End of Day Process in the Scheduled Job Administration application module. With the 2.36.00 release of the SPIRIT WIC system, Sanction Points Service processing now occurs only during End of Day Command Line Batch Processing.

R5: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition.

To accommodate the R5 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database:

R6: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOD.

To accommodate the R6 requirement for this enhancement, the prerequisite processes continue to run as intended:

ENH-642

Expired Benefits File

End of Day Process

Within the SPIRIT WIC system, the End of Day Command Line Batch Processing that occurs when the BatchProcessor.dll is run from the Command Prompt was expanded to include Expired Benefits File processing.

R1: Ensure that the new EOD imports the Expired Benefit File and updates the appropriate records by adding the FoodInstrumentItemDetail Rows with a transaction code of 5.

To accommodate the R1 requirement for this enhancement, the new GetFoodInstrumentId stored procedure was added and distributed with this release of the software.

For more information, see the database changes for this enhancement.

The legacy End of Day process contained the following error, which CDP believes was resolved with the changes made to End of Day Command Line Batch Processing for ENH-642:

• Only the last record was inserted into the FOODINSTRUMENTITEMDETAIL table.

R2: Ensure the new EOD receives the file in the FileReceivePath and writes to the file archive path with the date/time attached.

To accommodate the R2 requirement for this enhancement, two new values were added to the EBTCONNECTIONINFO table.

For more information, see the database changes for this enhancement.

R3: The name of the Expired Benefit File is the value specified in the VALUE column of the ExpiredBenefitsFileName row within the EBTCONNECTIONINFO table of the SPIRIT database.

To accommodate the R3 requirement for this enhancement, the existing file naming process continues to run as intended.

R4: The new EOD shall archive files that have already been processed.

To accommodate the R4 requirement for this enhancement, the new RemovePreviousExpiredBenefits stored procedure was added and distributed with this release of the software.

For more information, see the database changes for this enhancement.

R5: The release notes should contain the name of any stored procedures used by EOD after these changes have been applied.

To accommodate the R5 requirement for this enhancement, the following stored procedures were added and distributed with this release of the software:

• RemovePreviousExpiredBenefits

• GetFoodInstrumentId

For more information, see the database changes for this enhancement.

R6: The legacy EOD process shall discontinue the import of the Expired Benefit File.

To accommodate the R6 requirement for this enhancement, changes to End of Day Processing for ENH-642 removed Expired Benefits File processing from the End of Day Process in the Scheduled Job Administration application module. With the 2.36.00 release of the SPIRIT WIC system, Expired Benefits File processing now occurs only during End of Day Command Line Batch Processing.

R7: All new processes will log information to the scheduled job log in a manner consistent with the original versions, however the order may be different since the job order may change during transition.

To accommodate the R7 requirement for this enhancement, information is logged consistently in the SCHEDULEDJOBLOG table of the SPIRIT database.

R8: Exceptions shall be logged to the appropriate table.

To accommodate the R8 requirement for this enhancement, information is logged consistently in the EXCEPTIONLOG table of the SPIRIT database.

R9: The same work shall be done whether the process runs at 11PM or 1AM.

To accommodate the R9 requirement for this enhancement, End of Day Command Line Batch Processing will function correctly at any time of the day.

R10: Any prerequisite processes for either of these processes shall continue to run ahead of these processes in either legacy or the new EOD.

To accommodate the R10 requirement for this enhancement, the prerequisite processes continue to run as intended:

R11: CDP shall document within the release notes what order States/ITOs needs to run existing and new EOD/EOM.

To accommodate the R11 requirement for this enhancement, Expired Benefits File processing is included in the End of Day Command Line Batch Processing as part of the new .NET core EOD solution.

Reported Issues

Issue#

Primary Function

Issue Detail

Issue Resolution

CDP-61

EBT Transaction History Detail

WEM removed the first digit "1" from the PLU number, which caused a "UPC Not Found" description to incorrectly display in the UPC Description column within the Transaction Details data grid on the EBT Transaction History Detail screen.

The SPIRIT WIC system was modified to add the first digit "1" to restore the complete PLU number to populate the correct value(s) in the UPC Description column of the Transaction Details data grid on the following screens:

• EBT Transaction History (Central Administrative Site)

• EBT Transaction History (Clinic)

• EBT Transaction History (State Office)

CDP-389

EBTCARDSIGNATURE table

EBT cards were assigned to a household with no corresponding record in the EBTCARDSIGNATURE table.

The SPIRIT WIC system was modified as follows:

• The "X" button in the upper right corner of the Capture Signature for Card screen behaves the same as the Close button if a signature was not captured. Clicking the "X" button adds a "Signature Cancelled by User" row with a blank ESIGNATURE value to the Card History data grid on the EBT Card History screen for the household.

• The EBT Household Demographics screen correctly displays the Capture Signature for Card screen after the standard error message.

CDP-396

End of Day Process

When a split transaction was voided, incorrect PAIDAMOUNTs displayed in various locations throughout the SPIRIT WIC system.

The InsertFIItemRedeemedAggregated stored procedure in the SPIRIT WIC system was modified to remove the original purchase from the FOODINSTRUMENTITEMREDEEMED_AGGREGATED table for split transactions during End of Day Processing and to display the correct PAIDAMOUNTs in the following locations throughout the SPIRIT WIC system:

• EBT Data screen (System Administration)

• EBT Redemption Data screen (Vendor)

• UPC/PLU Redemption File (BatchProcessor.dll)

• EBT Household Reconciliation Report (Output) (State Office)

• WIC Reported Participation (per FNS-798) Report CLD022 (Output) (State Office)

• Benefit Redemptions FIN023 (Output) (Financial Management)

• Supplier Rebate Report FIN001 (Output) (Financial Management)

• FNS-798 Statement Spreadsheet (Output) (Financial Management)

For more information, see the database changes for this reported issue.

CDP-398

End of Day Process

The Redemption Processing within the BatchProcessor timed out during End of Day Command Line Batch Processing.

The SPIRIT WIC system was modified to add a configurable CommandTimeout setting in the appsettings.json file within the BatchProcessing_Core.zip file to resolve this issue.

DFDD Updates

Issue#

DFDD Location

DFDD Resolution

ENH-609

Scheduled Job Administration

(jobadmn.chm)

Changes to the Scheduled Job Administration DFDD for ENH-609 are documented below.

A new Duplicate Participant Service Processing within the BatchProcessor topic was added to document the Duplicate Participant Service processing that occurs when the BatchProcessor.dll is run.

The Identify Potential Duplicate Participants topic was renamed as Duplicate Participant Service and updated as follows:

• The introduction at the top of the topic was expanded to include a hypertext link to the new Duplicate Participant Service Processing within the BatchProcessor topic.

• Reference to End of Day in introduction was replaced with End of Day Command Line Batch Processing.

• Replaced the content with a summary of the SPIRIT .NET Processing steps from the Duplicate Participant Service Processing within the BatchProcessor topic.

• A See Also section was added at the bottom of the topic to include a hypertext link to the new Duplicate Participant Service Processing within the BatchProcessor topic.

Within the DFDD's Table of Contents (TOC) (Scheduled Job Administration -> Scheduled Job Administration-> End of Day Processing -> End of Day Command Line Batch Processing-> BatchProcessor.dll Process Flow), a new page was added for the new Duplicate Participant Service Processing within the BatchProcessor topic, and a new page was added for the existing, but renamed Duplicate Participant Service topic.

The dotnet BatchProcessor.dll -EOD [CN] Processes section at the bottom of the Run End of Day Command Line Batch Processing topic was updated to include a hypertext link to the new Duplicate Participant Service Processing within the BatchProcessor topic.

The BatchProcessor Processing topic was updated to include a new step for Duplicate Participant Service Processing within the BatchProcessor.

System Administration

(sysadmn.chm)

State Office

(stateofc.chm)

Reference Utility

(refutil.chm)

Changes to the System Administration, State Office, and Reference Utility DFDDs for ENH-609 are documented below.

The View Duplicate Participant Criteria (System Administration), View Duplicate Participant Criteria (State Office), Configure Duplicate Participant Criteria (Reference Utility) topics were updated as follows:

• In the Type of Compare column section, a note was added, "Only the values Exact and Double Metaphone are used to identify potential duplicate participants. If the value is set to Soundex, then Double Metaphone will be used."

ENH-611

Scheduled Job Administration

(jobadmn.chm)

Changes to the Scheduled Job Administration DFDD for ENH-611 are documented below.

A new Appointment Reminder Service Processing within the BatchProcessor topic was added to document the Appointment Reminder E-mail (Output) processing that occurs when the BatchProcessor.dll is run.

The Appointment Reminder E-mail (Output) topic was updated as follows:

• The introduction at the top of the topic was expanded to include a hypertext link to the new Appointment Reminder Service Processing within the BatchProcessor topic.

• References to End of Day Processing were replaced with End of Day Command Line Batch Processing.

• The Data Elements section was updated to reflect changed Origin of Data Element values as follows:

• ClinicName (Letter Format) The value will be taken from SERVICESITE. SERVICESITENAME.

• ClinicAddressLine1 (Letter Format) The value will be taken from SERVICESITE. ADDRESS.

• ClinicCity (Letter Format) The value will be taken from SERVICESITE. CITY.

• ClinicST (Letter Format) This value is taken from SERVICESITE. STATECD.

• ClinicZIPCode (Letter Format) The value will be taken from the SERVICESITE. ZIPCODE.

• ClinicTelephone The value will be taken from the SERVICESITE. TELEPHONE.

• A See Also section was added at the bottom of the topic to include a hypertext link to the new Appointment Reminder Service Processing within the BatchProcessor topic.

Within the DFDD's Table of Contents (TOC) (Scheduled Job Administration -> Scheduled Job Administration-> End of Day Processing -> End of Day Command Line Batch Processing-> BatchProcessor.dll Process Flow), a new page was added for the new Appointment Reminder Service Processing within the BatchProcessor topic, and a new page was added for the existing Appointment Reminder E-mail (Output) topic.

In the tutorial within the BatchProcessing_Core.zip Installation and Configuration topic, the Update the EBTCONNECTIONINFO table step was updated to include EBTCONNECTIONINFO table requirements for the Appointment Reminder E-mail (Output).

The Run End of Day Command Line Batch Processing topic was updated as follows:

• The Update the EBTCONNECTIONINFO table step was updated to include EBTCONNECTIONINFO table requirements for the Appointment Reminder E-mail (Output).

• The dotnet BatchProcessor.dll -EOD [CN] Processes section at the bottom of the topic was updated to include a hypertext link to the new Appointment Reminder Service Processing within the BatchProcessor topic.

The BatchProcessor Processing topic was updated to include a new step for Appointment Reminder Service Processing within the BatchProcessor.

Appendix

(busrule.chm)

Changes to the Appendix DFDD for ENH-611 are documented below.

The Enable System Generated Appointment Reminder E-mails topic was updated as follows:

• The DFDD References at the bottom of the topic was updated to include a hypertext link to the new Appointment Reminder Service Processing within the BatchProcessor topic.

The Log System Generated Appointment Reminder E-mails topic was updated as follows:

• References to End of Day Processing were replaced with End of Day Command Line Batch Processing.

• The introduction was modified to indicate that failed e-mails are always logged, but the state can define whether the system logs or does not log the successful appointment reminder e-mail details.

• The "N" value result in the Values Allowed table was modified to Log appointment reminder e-mail details in the SCHEDULEDJOBLOG table for failed e-mails only.

• A DFDD References section was added with a hypertext link to the new Appointment Reminder Service Processing within the BatchProcessor topic.

ENH-617

Process Pending Vendor Disqualifications

End of Day Process

(jobadmn.chm)

Changes to the Scheduled Job Administration DFDD for ENH-617 are documented below.

A new Pending Vendor Disqualifications Service within the BatchProcessor topic was added to document the Pending Vendor Disqualifications Service processing that occurs when the BatchProcessor.dll is run.

The Process Pending Disqualification topic was renamed as Pending Vendor Disqualifications Service and updated as follows:

• The introduction at the top of the topic was expanded to include a hypertext link to the new Pending Vendor Disqualifications Service within the BatchProcessor topic and to require that both the EOD_PROCESSPENDINGDISQUALIFICATION business rule and the EOD_RUNVENDORPROCESSES business rule equal "Y" in the STATEBUSINESSRULES table.

• References to End of Day Processing were replaced with End of Day Command Line Batch Processing.

• The action of retrieving the Max Termination Date was updated to reflect that the service updates the DEACTBANKEFFECTIVEDATE value in the VENDORSTAMP table.

• The action of setting the Vendor Status to Disqualified was combined with calculating the REINSTATEDATE.

• A See Also section was added at the bottom of the topic to include a hypertext link to the new Pending Vendor Disqualifications Service within the BatchProcessor topic.

Within the DFDD's Table of Contents (TOC) (Scheduled Job Administration -> Scheduled Job Administration-> End of Day Processing -> End of Day Command Line Batch Processing-> BatchProcessor.dll Process Flow), a new page was added for the new Pending Vendor Disqualifications Service within the BatchProcessor topic, and a new page was added for the existing Pending Vendor Disqualifications Service topic.

The Run End of Day Command Line Batch Processing topic was updated as follows:

• The dotnet BatchProcessor.dll -EOD [CN] Processes section at the bottom of the topic was updated to include a hypertext link to the new Pending Vendor Disqualifications Service within the BatchProcessor topic.

The BatchProcessor Processing topic was updated to include a new step for Pending Vendor Disqualifications Service within the BatchProcessor.

Appendix

(busrule.chm)

Changes to the Appendix DFDD for ENH-617 are documented below.

The End of Day Pending Vendor Disqualification topic was updated as follows:

• References to End of Day Process and End of Day were replaced with End of Day Command Line Batch Processing.

• References to Pending Vendor Disqualification function were replaced with Pending Vendor Disqualifications Service.

• A statement was added that this rule is tied to the EOD_RUNVENDORPROCESSES business rule.

• A DFDD References section was added with hypertext links to the existing Pending Vendor Disqualifications Service topic and the new Pending Vendor Disqualifications Service within the BatchProcessor topic.

• In theSee Also section, a hypertext link was added to the EOD_RUNVENDORPROCESSES business rule.

The Run Vendor Processing topic was updated as follows:

• References to End of Day Process and End of Day were replaced with End of Day Command Line Batch Processing.

• A DFDD References section was added with hypertext links to the existing Pending Vendor Disqualifications Service topic and the new Pending Vendor Disqualifications Service within the BatchProcessor topic.

• In the See Also section, a hypertext link was added to the EOD_PROCESSPENDINGDISQUALIFICATION business rule.

ENH-618

Scheduled Job Administration

(jobadmn.chm)

Changes to the Scheduled Job Administration DFDD for ENH-618 are documented below.

A new Sanction Points Service Processing within the BatchProcessor topic was added to document the Sanction Points Service processing that occurs when the BatchProcessor.dll is run.

The Process Sanction Points topic was renamed as Sanction Points Service and updated as follows:

• The introduction at the top of the topic was expanded to include a hypertext link to the new Sanction Points Service Processing within the BatchProcessor topic.

• The introduction at the top of the topic was expanded to include all criteria for removal, including that both the EOD_PROCESSSANCTIONPOINTS business rule and the EOD_RUNVENDORPROCESSES business rule equal "Y" in the STATEBUSINESSRULES table.

• Criteria for removal were deleted from the Roll-Off Points section.

• A See Also section was added at the bottom of the topic to include a hypertext link to the new Sanction Points Service Processing within the BatchProcessor topic.

Within the DFDD's Table of Contents (TOC) (Scheduled Job Administration -> Scheduled Job Administration-> End of Day Processing -> End of Day Command Line Batch Processing-> BatchProcessor.dll Process Flow), a new page was added for the new Sanction Points Service Processing within the BatchProcessor topic, and a new page was added for the existing Sanction Points Service topic.

The Run End of Day Command Line Batch Processing topic was updated as follows:

• The dotnet BatchProcessor.dll -EOD [CN] Processes section at the bottom of the topic was updated to include a hypertext link to the new Sanction Points Service Processing within the BatchProcessor topic.

The BatchProcessor Processing topic was updated to include a new step for Sanction Points Service Processing within the BatchProcessor.

Appendix

(busrule.chm)

Changes to the Appendix DFDD for ENH-618 are documented below.

The End of Day Sanction Points Process topic was updated as follows:

• References to End of Day Process and End of Day were replaced with End of Day Command Line Batch Processing.

• References to Pending Vendor Disqualification function were replaced with Pending Vendor Disqualifications Service.

• A statement was added that this rule is tied to the EOD_RUNVENDORPROCESSES business rule.

• A DFDD References section was added with hypertext links to the existing Sanction Points Service topic and the new Sanction Points Service Processing within the BatchProcessor topic.

• A See Also section was added with a hypertext link to the EOD_RUNVENDORPROCESSES business rule.

The Run Vendor Processing topic was updated to add a DFDD References section with hypertext links to the existing Sanction Points Service topic and the new Sanction Points Service Processing within the BatchProcessor topic.

ENH-642

Scheduled Job Administration

(jobadmn.chm)

Changes to the Scheduled Job Administration DFDD for ENH-642 are documented below.

A new Expired Benefits File Processing within the BatchProcessor topic was added to document the Expired Benefits File processing that occurs when the BatchProcessor.dll is run.

The Expired Benefits File topic was updated as follows:

• The introduction at the top of the topic was expanded to include a hypertext link to the new Expired Benefits File Processing within the BatchProcessor topic.

• The Detail Record section was updated to reflect File Mapping to SPIRIT Database (Table. Column) values.

Within the DFDD's Table of Contents (TOC) (Scheduled Job Administration -> Scheduled Job Administration-> End of Day Processing -> End of Day Command Line Batch Processing-> BatchProcessor.dll Process Flow), a new page was added for the new Expired Benefits File Processing within the BatchProcessor topic.

In the tutorial within the BatchProcessing_Core.zip Installation and Configuration topic, the Update the EBTCONNECTIONINFO table step was updated to include EBTCONNECTIONINFO table requirements for the Expired Benefits File Processing within the BatchProcessor.

The Run End of Day Command Line Batch Processing topic was updated as follows:

• The Update the EBTCONNECTIONINFO table step was updated to include EBTCONNECTIONINFO table requirements for the Expired Benefits File.

• The dotnet BatchProcessor.dll -EOD [CN] Processes section at the bottom of the topic was updated to include a hypertext link to the new Expired Benefits File Processing within the BatchProcessor topic.

The BatchProcessor Processing topic was updated to include a new step for Expired Benefits File Processing within the BatchProcessor.

DFDD

(wicdfdd.chm)

For this release, the title bar of the Detailed Functional Design Document (DFDD) was updated to reflect build version "2.36.00". Additionally, the footer was also updated to reflect software version "2.36.00".