Release 2.13 Notes

Changes made in this release of the software are detailed below.

Issue#	Application Module	Primary Function	Detail
Reported Issues
CAB-1	Clinic	Cycle Adjust	Issue: For a Pregnant Woman with bi-monthly or tri-monthly issuance frequency, users receive the following standard error message when attempting to Show Max Benefits on the Benefits (Issue Benefits) screen: "Benefits will not be issued for the participants in this household. REASON: No household members are currently eligible for benefits". When OK is selected, no benefits are suggested by the application. Resolution: The current build displays no standard error messages when selecting Show Max Benefits. A bug was encountered where CertEffectiveDate was being used instead of CertStartDate. This has been resolved. The last set of benefits is not suggested through the Benefits (Issue Benefits) screen because of the rule "If the participation month is the same as the month of the certification end, then the benefit should be allowed via add set". This is the same behavior as in earlier versions.
CAB-3	Clinic	Cycle Adjust	Issue: Issuance check boxes on the Benefits (Issue Benefits) screen are refreshed after editing the first set of benefits. Resolution: The SyncCheckTreeNodesToDate function has been modified to not run when an update is caused by the Edit First Set button.
CAB-4	Clinic	Cycle Adjust	Issue: When issuance frequency is set to bi-monthly and a system determined LDTU is used, users are able to issue an infant benefits with a FDTU of 2/28/2011 and an LDTU of 4/11/2011. The infant was set to receive the first set of benefits in a household with a previously established issuance cycle. Resolution: The issue involving a 42 day benefit period was caused by the bug where CertEffectiveDate was being used instead of CertStartDate. This has been resolved.
CAB-5	Clinic	Cycle Adjust	Issue: In the new Select LDTU calendar control on the Benefits (Issue Benefits) screen, selecting an LDTU through the calendar control sets the LDTU for the benefit appropriately, but if the user types in an LDTU and uses the Tab or Enter key, the benefit will not change and will print using the base LDTU. Resolution: Due to the date range limitations, users are not allowed to type dates in this control. Instead, users must select dates from the calendar control. The code has been updated to enforce this limitation.
CAB-6	Clinic	Cycle Adjust	Issue: When users check the Show Max Benefits check box on the Benefits (Issue Benefits) screen, FDTUs and LDTUs are changed. When the check box is unchecked, the dates do not revert back to the original settings. While this check box is only temporary, users would like to ensure that there are no underlying problems with FDTU/LDTU. Resolution: Code has been added to force a reset of issuance dates when Show Max Benefits is toggled.
CAB-8	Clinic	Cycle Adjust	Issue: The system dropped a set of benefits for an infant on tri-monthly issuance. The system determined LDTU included benefits for 3/3/2011-4/2/2011. The user set the LDTU to 3/31/11 and the system dropped the benefits for March. The mother's benefits included 3/3/2011-3/31/2011. Resolution: The range of dates for manual cycle adjustment in this issue was invalid since the LastSetLDTU was not taken into account. This issue was also caused by the bug where CertEffectiveDate was being used instead of CertStartDate. This has been resolved. Additionally, the reason the FBF infant's benefits started on 4/1/2011 after a manual cycle adjustment to 3/31/2011 was because the infant's first benefit ExpectedFDTU=Today. This was before the infant's 6 month birthday or the effective date of the infant's 6 month prescription. The code has been modified to set the first ExpectedFDTU for a FBF Infant = 6 month birthday. Users will need to select Show Max Benefits to explore the possible dates for this situation. This could lead to the proration of the first set of benefits. With the rule that the FirstFDTU for a FBF infant should be the FirstFDTU of the household that is on or after the infant's 6 month birthday, the benefits issued to the infant are now correct.
CAB-9	Clinic	Cycle Adjust	Issue: An FBF infant less than 6 months old and on bi-monthly issuance frequency can be issued future benefits. However, during the issuance process, the system keeps presenting messages that the infant cannot receive benefits. The message is only true for the first set of benefits, but not for the second. Resolution: The code has been modified so that the message is not displayed when there is a valid benefit in the future. With the rule that the FirstFDTU for a FBF infant should be the FirstFDTU of the household that is on or after the infant's 6 month birthday, the benefits issued to the infant are now correct.
CAB-11	Clinic	Cycle Adjust	Issue: Users receive the following standard error message on the Benefits (Issue Benefits) screen: "Conversion from type 'DBNull' to type 'Date' is not valid". Resolution: This issue related to the way in which Delete and Enter were handled. For System Determined dates, users are no longer able to select or delete dates in the Select LDTU calendar control.
CAB-13	Clinic	Cycle Adjust	Issue: For a child participant, the system determined LDTU (3/31/2011) drops the third set. When the user sets the LDTU to 3/30/2011, the third set appears. Resolution: Additional logic has been added to evaluate the last benefit of a certification where the FDTU and LDTU <= CertEndDate and the certification is ending due to categorical ineligibility. Those benefits that occur entirely during the certification will be allowed.
CAB-14	Clinic	Cycle Adjust	Issue: When an FBF participant is late picking up her last month of benefits, the infant also did not receive the last month of benefits. Resolution: A method for adjusting the PrintedFDTU of FBF infants when the household is late for pickup and the infant is receiving the first benefit of the certification has been added to the code.
DFDD-20	Clinic	BMI	Issue: The BMI Growth Grids display recumbent measurements. This growth grid should only be graphing children 2 or older who are measured standing. Resolution: The system no longer plots recumbent weight or displays the text "Recumbent" next to plot points for children 24 months and older while measured recumbent. The Growth Grids topic in the DFDD has been modified to indicate that the BMI Growth Grids graph only children 2 or older who are measured standing.
DFDD-32	Clinic	Participant List menu	Issue: The Participant List menu refers to the View Household EBT Account screen. This screen does not exist and this sentence should be removed from the DFDD. Resolution: The DFDD has been corrected as requested.
DFDD-62	Clinic	Generate No Show Report	Issue: The DFDD for the Generate No Show Report includes details on options to view the report on screen or save it as a PDF. These options do not appear on the screen. Resolution: The DFDD has been corrected. References to the Report Destination radio button group have been removed, as have references to options to View, Print, or Save the report as a PDF.
DFDD-63	Appendix	Risk Factors	Issue: The fix introduced for SUG-1299 requires that the Assignment Method drop-down list box on the Risk Factor screen in Reference Utility be disabled and pre-populated with the specified assignment method for those risk factors identified as "System Assigned" or "CPA Assigned" only. This change in functionality needs to be addressed and updated in the DFDD. Resolution: The Risk Factor topic in Reference Utility has been updated to document the changes to the Assignment Method drop-down list box. The Risk Factors Matrix has been upgraded to HTML (formerly PDF) for ease of use and for future maintainability. The existing CPA Assign/System Assign columns in the Risk Factors Matrix have been replaced with a new Assignment column, indicating whether a risk factor is System Assigned Only, CPA Assigned Only, or Both System and CPA Assigned. Previously, several SYS_ASSIGN_RF_XXX business rules were used to control whether a particular risk factor was assigned by the system or user. Now, all state business rules regarding risk factor assignment have been removed from the application. Corresponding references to these business rules have been removed from the DFDD. All risk factor assignment methods and restrictions are now controlled only by settings in the RiskFactorReference table of the database.
DFDD-64	Clinic	Child Health Information	Issue: The DFDD for the Date Food Package III Verified calendar control on the Child Health Information screen does not reflect current system functionality. It should be updated. Resolution: This issue cannot be found in the current version of the DFDD. It was corrected in a previous version. The Date Food Package III Verified calendar control now states that it defaults to today's date and only today's date will be accepted.
DFDD-66	System Administration	Program	Issue: The fix for SUG-501 introduced several validations and checks when there is a change to a program's visibility. This additional functionality needs to be updated in the DFDD. Resolution: The Program topic in the DFDD has been updated as requested.
SUG-171	Clinic	Cycle Adjust	Issue: When issuing checks for a household that has different cycle dates, the system will only print the participant with the latest cycle date, and will not show the participant with the current cycle date. Resolution: The issuance process has been redesigned. Pro-rated checks are printed if the cycle date is less than the cycle date for other household members.
SUG-208	Clinic	Participant Folder	Issue: Users are unable to start or finish a certification for an infant who has turned one year old. A standard error message is displayed stating "Date of Birth is invalid for an infant". An unhandled exception standard error message is then displayed after clicking OK on the above message. Resolution: The unhandled exception standard error message has been corrected. This was related to an EOD issue. Now, when EOD runs, it changes the infant's status to that of a child and creates a pseudo certification. As designed, infant risk factors will be dropped by EOD and no risk factors will be carried forward to the new child status.
SUG-223	Clinic	Default Printers	Issue: Documents are printing on Tray 1 when they should be printing on Tray 2, even after the users change their printer settings. Resolution: Many changes have been made to the code that handles printing pointed to specific trays, as specified in the Default Printers settings. Checks, reports, and documents can now all be printed successfully to each of three destinations on the Default Printers settings.
SUG-316	Clinic	Cycle Adjust	Issue: Users cannot issue checks to a participant who has just been certified. This following recurring issues have been identified: Participants will not display in the issuance list when the issuance frequency is monthly; however, they are displayed in the issuance list when their issuance frequency is changed to bi-monthly or tri-monthly. Participants will not display in the issuance list, but issuances become available by moving participants to their own household. Some participants will not be displayed in the issuance list when other household members are displayed. By issuing benefits to one of the other household members and then immediately clicking the Issue Benefits to Selected Members button again, the missing participant is displayed in the issuance list. Resolution: Several code changes have been made to fix certain aspects of this issue. If the infant is FBF and nearly 6 months old, the issuance will now be present. Previously, the code was comparing Participation Dates between the previous issuances and the possible future issuances. If they matched, the system would incorrectly remove the future issuance. While this test is valid, the date it was using was wrong. With late pickups, added 7th sets, or previous household cycle adjustments, the ParticipationDate could be calculated as occurring twice for the same month. The PrintedFDTUs are now compared to remove possible duplicate issuances from the possible set. The remaining aspects of this issue have been fixed with the cycle adjust changes. The issuance process has been redesigned and has corrected all of the possible issues listed above.
SUG-341 / SUG-425	Clinic	Generate Official Notification	Issue: The Official Notification Document (Output) is not printing the correct information. It indicates that participants will be terminated and states "NOT CERTIFIED". The termination dates do not match the certification end dates. In other instances, recertification due notices are printed when the participant will instead be categorically ineligible. When generating pending termination notices while working with an onsite group, the official notification is generated when participants will be terminated within 15 days of today's date. This is not useful when working with a class. For the official notification to be useful, the certification end date must print on the official notification. Resolution: The following changes were made to resolve these issues: The entire view used to get Pending Termination records has been rewritten. The sorting and return of the most impending Termination record has been improved. Recertification due 36 days after the previous certification expired has been changed to the current certification due date. The EOD selection of non-participating members (due to failure to pick up food instruments for 2 consecutive months) has been improved. Member records with a null CategoricalIneligibilityDate will use the CertDueDate field instead of determining what upcoming pending terminations should be applied. Termination notices are no longer generated exclusively within 15 days of termination. Instead, the TERMNOTICEWARNINGPERIOD business rule is used to determine the lead time for notices. For participants with an upcoming termination event (delayed blood work, categorical ineligibility, failure to pick-up, or recertification due), the system now calculates and displays the correct termination reason code and termination date on the Official Notification Document (Output). Participants toggled on-site will receive an Official Notification Document (Output) when the Generate Official Notification check box is checked and the participant has an event (delayed blood work, categorical ineligibility, recertification due, or non-participation) that will occur within the number of days set in the value of the PENDINGTERMPERIOD business rule.
SUG-491 / SUG-608	Clinic	Cycle Adjust	Issue: When a user changed the cycle adjustment on the Benefits (Issue Benefits) screen to designate the second household member as the base participant, the benefit period changed for both members of the household. In a household where the infant was the base participant, the system skipped the prorated set of benefits for the mother and child. The benefits are missing because of cycle adjust errors. Resolution: The issuance process has been redesigned. Now, benefit times are correct when adjusted to various possible LDTUs. The new issuance process now allows users to cycle adjust to various LDTU dates (the system will allow cycle adjustment to a selected date given that it falls within a certain date range determined by: Target Dates >= LatestFutureCurrentLDTU of the household members and <= EarliestFutureLDTU of household members. If the LatestFutureLDTU = EarliestFutureLDTU, then LatestFutureLDTU = Today + 1 Month. Finally, LatestFutureLDTU and EarliestFutureLDTU must be <= Today + 1 Month and >= Today.)
SUG-501	System Administration	Program	Issue: When editing a State Level Program to be an Agency Level Program in the Program screen, the system uses the StateProgramID as the AgencyProgramID instead of creating a new AgencyProgramID. Resolution: The system now generates a new AgencyProgramID and deletes the StateProgramID if visibility is changed from State to Agency. Several validations and checks have been added for when visibility is changed.
SUG-614	Clinic	Certification Guided Script	Issue: The CLN_NutritionEducationIsRequired business rule does not work as expected. When the business rule is set to "Y" and the user simply opens the Nutrition Education Contact screen and then closes it, the system interprets that as a valid nutrition education contact record. When the business rule is set to "N", the system does not allow users to skip the Nutrition Education Contact screen. Resolution: Code has been added to make sure that an EducationContact record has been created and saved in order to complete a certification and issue benefits when the CLN_NutritionEducationIsRequired business rule is set to "Y".
SUG-624	Clinic	Risk Factors	Issue: Risk Factor 135 is not being correctly auto-assigned for a 4 year old child. Resolution: Risk Factor 135 is defined as follows: 1. 0-14 days, do not assign 2. 14-29 days, only system-assign if weight is less than birth weight 3. 1 mo.-6 mo., find the last measurement at least 30 days prior and compare the growth based on the grams per day 4. >6 mo., find the last measurement at least 90 days prior and compare the growth based on the grams per day For numbers 2 and 3 above, use the birth weight if no other measurement is available. This Risk Factor auto-assignment is working as designed. Risk Factor 135 is properly auto-assigning for infants and children when the average weight gain per day is less than the amounts listed in the USDA information and Risk Factors Matrix. Each age group was tested at the minimum acceptable weight gain to ensure Risk Factor 135 was not assigned, and then an ounce was subtracted to ensure that Risk Factor 135 was auto-assigned. The following age groups were tested: Infant 1-2 months, Infant 2-3 months, Infant 3-4 months, Infant 4-5 months, Infant 5-6 months, Infant 6-12 months, Child 1-2 years, Child 2-3 years, and Child 3-5 years.
SUG-626 / SUG-1213	Reference Utility	Reference Dictionary	Issue: The Active flag in the Reference Dictionary is not working properly. Items are still displayed in the application after being deactivated. When the "Converted from Old System" option is deactivated in the Reference Dictionary, the option is not removed from selection in the Clinic Applicant Prescreening process. Resolution: The drop-down list boxes on the Demographic Information screens that are populated from the Reference Dictionary now respect the setting in the Active flag. This includes the following categories: DISABILITY, DOCMNTLANG, EDULEVEL, GENDER, HOUSEHOLDSMOKE, HOWHEARD, IDPRFCHILD, IDPRFWOMAN, INSTYPE, LANGUAGE, MARITALSTS, REASONNOTPRESENT, REGISTERTOVOTE, RESIDPROOF, TVVIDEOAMOUNT, and TYPEMEDHOME. It includes the following drop-down list boxes on the Demographics sub-tab: Gender, ID Proof, Residency Proof, and Reason Not Present. It includes the following drop-down list boxes on the AdditionalInfo1 sub-tab: How Heard about WIC, Disability, Insurance Type, Type of Medical Home, Household Smoking, and TV/Video Viewing. It includes the following drop-down list boxes on the AdditionalInfo2 sub-tab: Correspondence Preference, Language1, Language2, Marital Status, Education Level, and Register to Vote. Note: The remaining categories with "Converted from Old System" as an option in the drop-down list box will be addressed in a future release.
SUG-729	Clinic	Income Calculator	Issue: Changes to the Pending Proof of Income check box on the Income Calculator screen are only applied to the current participant. Such changes should be applied to all members of the participant's household since income contacts are now handled at the household level. Resolution: PendingProof has been copied to all members of the household instead of just the current member when saving income contacts.
SUG-788	Reference Utility	Reference Dictionary	Issue: The Reference Dictionary for ResidencyProof and TermReasons is inconsistent with the business rules and EOD. Several records have been terminated in the CertContact table with a reason of "D" or "F". In Missouri, the reason "D" is set up as a key value in the business rule for Residency Proof. The TermReason "D" is not listed in the Reference Dictionary. The TermReason "F" should be deactivated. The ResidencyProof codes of "D" and "F" are not listed in the Reference Dictionary. Records with these TermReasons show a pending proof in the Residency drop-down list box in Demographic Information. They also indicate a termination date but no termination reason in Demographic Information. Resolution: Reference Dictionary termination reasons "D - No Proof of Residency Provided" and "F - Does not meet residency requirements" are now clearly defined as separate termination reasons even though the descriptions are very similar. The Reference Dictionary has been updated to use "D" as the EOD termination reason for failure to show proof of residency in the required timeframe. Termination reason "F" is used as the manual termination reason by the user when the member does not meet residency requirements. Since termination reason "D" is reserved for EOD, it will no longer be available for selection in the drop-down list box for manual termination (it is marked as system-defined and hidden). Reason "F" is available in the drop-down list box for users to select when the participant does not meet residency requirements. The certification records that were terminated with reason "D" by any user other than EOD will be modified to reflect the new standard reason of "F". A SQL will be provided to the states as a separate script to run immediately after the installation of Release 2.13. The Reference Dictionary changes will be included in the software release database scripts.
SUG-846 / SUG-1346	Direct Distribution	Food Package List Search	Issue: When issuing the benefits shopping list for Direct Distribution, users receive the following standard error message from the Food Package List Search screen: "There are more than 7 items on the participant's food prescription indicating print on the same specific check. Please contact the Help Desk to reduce the number of items to 7 or less." This is a check-specific standard error message and not related to Direct Distribution. For Direct Distribution sites, benefit issuance is being printed in check format. Users must add and replace benefits to print in the correct format for vouchers. Resolution: Code has been added to suppress the above standard error message in the Direct Distribution application. Vouchers now print in the correct format. A fix for SUG-1115 in Release 2.12 caused Direct Distribution sites to be flagged as issuing checks in some situations. This has now been addressed. If a set of benefits was replaced in the Clinic application, the new benefits were not available for redemption in Direct Distribution. This has also been fixed and the new benefits are available in Direct Distribution.
SUG-869	State Office	PC20XX File (Output)	Issue: The Number in Economic Unit field (Field 12) in the PC20XX File (Output) should be reported for all participants; however, 1,388 records do not have a value. Resolution: For each instance in which the Family Income information was missing from the PC20XX File (Output), the information was missing from the participant's most recent certification period as of reference month April 2010. For each instance in which this data was present, the information was pulled from the participant's most recent income contact recorded between the date the participant's certification started and the date the participant's certification ended. This functionality reflects the most recent changes to the report. The value in this field is entered by the user in the Income Calculator screen and stored in the IncomeContact table (in the HouseholdSize field). For participants who have had information recorded at some point in the past, but not during the certification being reported, a SQL script has been provided to determine why this data is missing as needed.
SUG-954	State Office	PC20XX File (Output)	Issue: The participant's height and weight is not being reported in the PC20XX File (Output) when the measurement date is not between the current certification start date and end date (Fields 16a(i), 16a(ii), 17a(i), and 17a(ii)). Resolution: The height and weight (from the AnthropContact table) will now be the last measurement taken during the participant's most recent certification. The PC20XX File (Output) will not use any measurements from any certification prior to the most recent one as they may not be relevant. The participants included in the PC20XX File (Output) must have been certified for participation in the WIC program over a period that ended in, started in, or extended through the month of April 2010. For participants who have had information recorded at some point in the past, but not during the certification being reported, a SQL script has been provided to determine why this data is missing as needed.
SUG-987	State Office	PC20XX File (Output)	Issue: The Baby's Length at Birth in Inches field (Field 30a(i)) in the PC20XX File (Output) displays numeric values for a specific record. This field should instead contain alphabetic values. Resolution: The PC20XX File (Output) includes the data that exists in the database for each person certified for participation in the WIC program over a period that ended in, started in, or extended through the month of April 2010. If there are unreasonable values for any data in the PC20XX File (Output), it is because unreasonable values were entered for the participant. The single case noted in this issue in which a person certified for participation had incorrect values reported in this field can be explained by the fact that a child participant was incorrectly certified as a breastfeeding postpartum woman. For information about children included in the PC20XX File (Output) that are missing Birth Length information or that have Birth Length information that might be considered unreasonable, a SQL script has been provided.
SUG-1011	Clinic	Cycle Adjust	Issue: Cycle adjusting caused a lapse in benefits for one family member and four months issuance to another. Resolution: The issuance process has been redesigned. There are now no missing benefits or extra sets of benefits. The cycle adjustment has been verified with different WIC categories, Age categories, and CPA follow-up frequencies. The cycle can now be adjusted to different LDTUs.
SUG-1028	Direct Distribution	Direct Distribution Redemption	Issue: The amount left to be redeemed on the Direct Distribution Redemption screen does not match the amount displayed on the Food List Receipt. Resolution: This issue concerned a CVB item with a price of $0.44. In this instance, several items were redeemed, creating a decimal amount in the redeemed and remaining balance columns. The Food List data grid in the Direct Distribution Redemption screen rounds the totals, but the Food List Receipt was not rounding values. This caused the amounts displayed to appear different. Now, the receipt has been modified to use the rounded amount to be consistent with the Food List for CVB items. Non-CVB items are not rounded as their decimal values can be relevant. Additionally, values in the Redeemed Food Items list are not rounded so that visibility for the user performing the checkout is retained. Finally, the DB connection handling within the Direct Distribution application has been improved.
SUG-1072	Clinic	Risk Factors	Issue: Risk Factor 153 (Large for Gestational Age) was not auto-assigned when entering birth weight greater than 9lbs, 0 oz. This occurs in age category 4 (6 months to 1 year). Resolution: The RiskFactorReference table for RiskFactorID = 153 and AgeCategoryID = 1 had an ExpirationDate of 01/01/2001 (it had expired). A SQL script has been used to fix the problem.
SUG-1089	Clinic	Certification Guided Script	Issue: After users have successfully completed a certification in the Certification Guided Script and attempt to issue benefits, they receive a SQL DateTime overflow standard error message and cannot issue checks. Resolution: The DateTime Overflow standard error messages were caused by SPIRIT attempting to display dates which had not been entered or calculated yet because the Health Information step had not been completed. The Health Information step check box in the Certification Guided Script indicates only that the user has entered the Health Information step, not that it has been completed. During certification review, SPIRIT now checks for completed Health Information values instead of the Health Information check box to determine whether the step has been completed.
SUG-1129	Clinic	Cycle Adjust	Issue: Users receive the following standard error message and are unable to print benefits for a participant: "Benefits will not be issued for the participants in this household. REASON: Failed to determine the Base Participant". Resolution: This standard error message was due to a cycle adjustment issue. With the cycle adjustment changes in this release, this standard error message has been removed as it no longer applies.
SUG-1130	Clinic	Participant List	Issue: The Show Details view of the Participant List does not display properly for the second participant in the list after a search has been completed. The details shown for the second participant are the same as those shown for the first participant. Resolution: The current and previous row tracking has been modified so that the correct Show Details information is displayed for each participant in the list.
SUG-1141	Clinic	Produce VOC Document	Issue: Users receive the following standard error message from the Produce VOC Document screen when attempting to print a VOC document for a participant who already has a VOC document printed and who would still be in a valid certification, but who has been terminated and reinstated: "Termination date must be a date equal to or greater than the current date and less than or equal to the ending date of the current certification period." Resolution: The following changes have been made to the code to fix this issue: The Produce VOC Document menu option has been disabled immediately after terminating the participant. It will be enabled once the participant is reinstated in the system. The Terminate Participant check box in the Produce VOC Document screen has been enabled at any time the screen is active. This allows users to produce VOC documents as many times as needed (so long as it does not exceed the count in the VOC_ALLOWED business rule).
SUG-1144	State Office	Reports	Issue: The MT8PNS1003.txt report file for the CDC has several errors: Participant records from Clinic 88 are included in the file; about 21 duplicate records are in the file; the Heights measurements do not correspond to the dates given in the records when compared to the database, which results in near duplicate records with the same data and different heights; records for with one infant display the "Number of Infants" column as 2 or 3 and twins display as 3. Resolution: The following changes have been made: The report now finds the last CertContact record that was active during the reporting period. Previously, not finding this record lead to the inclusion of multiple records for a single StateWICID. Also, the instructions for fields 18 and 19 were misinterpreted. Previously, it was thought that a "2" should be used for records that were neither Pregnancy nor Postpartum. Instead, these records should hold a space in these fields. Likewise, in field 56, it was thought that "9" meant Unknown, but instead a space should have been used. Finally, a change was made to use the new IncomeContactAdjunctiveItem table when looking at IncomeContact data (Income, TANF, Food Stamps, etc.). The file has been validated and now reports the correct data.
SUG-1145	Clinic	Risk Factors	Issue: Risk Factor 121 (Short Stature) is being incorrectly assigned by the system to a participant who is above the 98th percentile for height. A pseudo certification was created when Household Smoking was changed from Yes to No. Although the existing certification did not have Risk Factor 121 assigned and no new Height/Weight/Blood information was entered, Risk Factor 121 was assigned to the pseudo certification and could not be removed. Resolution: This issue was resolved with SUG-1203. N/A is displayed in the percentage field when the boundaries of the height and/or weight calculations are reached. The secondary issue noted was unable to be recreated after version 2.10. Risk Factors and pseudo certifications were updated correctly and no additional Risk Factors were assigned by the system when the value in the Household Smoking field was changed.
SUG-1157	State Office	Reports	Issue: The Monthly Termination Detail Report OPR018 (Output) and Monthly Termination Summary Report OPR017 (Output) both contain spelling errors. The word Unknown is misspelled as "Unkown". Additionally, the termination reason, "Unknown", is not listed in the Reference Dictionary. Resolution: The spelling issue has been corrected. A Reference Dictionary entry has been incorporated into the scripts for places that have CertContact records with a TermReason of "V".
SUG-1158	Clinic	Risk Factors	Issue: In the dbo.CertContact, the CERTASSIGNEDPRIORITY changes to NULL when a CPA-assigned risk factor is added and the system does not prompt to save prior to exiting the Participant Folder. Resolution: The code was retrieving the certification's priority from the risk factors. This created a problem when risk factors were added manually, as the code did not populate the priority of the new risk factor. Since a blank space is less than any valid value (and the smaller the number, the higher the priority), the priority was always set to a blank space which was saved as a NULL value. Now, the code has been modified to retrieve the RiskFactorReference record in order to get all of the proper priority values. The CertContact.CertAssignedPriority now records the correct priority for CPA-assigned risk factors. Clicking the OK button on the Assign Certification Risk Factors screen saves the values to the database. Users will not be prompted to save the data upon leaving the screen.
SUG-1161	Clinic	Risk Factors	Issue: Expired Risk Factors 801 and 802 are system assigned when breastfeeding is N/A. Resolution: Code has been added to make sure that the household level risk factors (801, 802, and 904) can be assigned to each member of the family but only if the risk factor is not expired and it is able to be assigned by the system.
SUG-1163	State Office	PC20XX File (Output)	Issue: Over 10,000 records had 0 or missing income in the Family Income field (Field 13a) of the PC20XX File (Output). Resolution: Due to the fact that the IncomeContact.CertStartDate is only populated when the record is created during CGS, the PC20XX File (Output) previously only reported income entered during certification, and not necessarily the latest one. The uspGetUSDAData script has been changed to look for the last income contact entered during the certification being reported. The PC20XX File (Output) now includes data from the database for each person certified for participation in the WIC program over a period that ended in, started in, or extended through the month of April 2010. For cases in which family income was not included in the PC20XX File (Output), income information was not recorded during the most recent income contact of the most recent certification period (as of the reference month of April 2010). In all cases, the failure to record a family's income occurred when the family was adjunctively eligible. For information about why family income information is missing from the PC20XX File (Output) for those participants who have income contact information that was recorded during the certification being reported, a SQL script has been provided to determine why this data is missing as needed.
SUG-1164	Clinic	Income Line Item	Issue: The Income Line Item screen in the Certification Guided Script does not accept six-digit numbers. The same screen used during pre-screening does not have the same limitation. Resolution: The precision of the IncomeItem Amount column has been increased from 99,999.99 to 999,999.99. The width of the Total Amount fields on the Income Calculator and Income Line Item screens has been increased to display wider calculations resulting from these six-digit numbers.
SUG-1166	Clinic	Certification Guided Script	Issue: Users receive a standard error message when attempting to certify a participant. The participant was initially set up as an infant. During certification, the date of birth was changed so that the participant would be a breastfeeding woman. The certification could not be continued unless the status was changed back to that of an infant. Resolution: The CCWG has decided that the WIC Status during Certification Guided Script can be changed only after removing the incomplete certification. The Remove Incomplete Certification menu option on the Participant Activities menu has been enabled. Previously, this menu option was enabled only for the day on which the certification was started. Functionality to change the WIC Status has been added. After a user attempts to change the WIC Status in Certification Guided Script, a standard confirmation message is displayed. When the user selects "Yes" on the standard confirmation message, Certification Guided Script will close and reset the participant to the desired WIC Status, allowing Certification Guided Script to be continued.
SUG-1170	Clinic	View Appointments for Date	Issue: The View Appointments for Date screen is not working correctly. Months are being skipped when users advance the month either by using the arrow button or dragging the slide bar. Resolution: The code has been reworked to correct the problem where months are skipped when using arrows for navigation. All months are now present and display correctly.
SUG-1173	Clinic	Issue Benefits	Issue: Users receive the following standard error message when they click on the Issue Benefits toolbar button in the Participant Folder: "The conversion of a varchar data type to a datetime data type resulted in an out-of-range value". Resolution: This was caused by an old certification record with a null end date (CertContact records with null values in the CertEndDate column). The view has been modified to exclude such records since they are invalid, thus resolving the issue.
SUG-1195	Clinic	Participant List	Issue: The Certification Effective Date on the Participant List changes after opening the Participant Folder and returning to the Participant List. Resolution: The Certification Effective Date in the Participant List was not being refreshed properly for pseudo certifications. The maximum pseudo certification date was being displayed instead of the minimum Certification Effective Date. The code has been modified to display the minimum Certification Effective Date if the current certification is a pseudo certification.
SUG-1200	Clinic	Issue Benefits	Issue: The PRINTREASON in the FOODINSTRUMENTPRINT table is not being populated correctly when reprinting benefits. Additionally, Replace Set of Benefits is not accounted for in the REPRINTRSN. The DESCRIPTION for Identify Lost/Stolen Benefits should include Lost, "Reprint Lost/Stolen Benefit". Finally, all DESCRIPTIONs for REPRINTRSN in Reference Dictionary should use "Benefit" and not "Check". Resolution: The code has been corrected as requested above for verbiage on all database entries. Code has been added to insert records in the FOODINSTRUMENTPRINT table when reprinting benefits during Identify Benefits to Reprint for Custody Change, Identify Benefits to Void, and Identify Lost/Stolen Benefits.
SUG-1203	Clinic	Risk Factors	Issue: Risk Factor 121 is not being correctly auto-assigned. When the participant's height measurement plots above the max height on the growth grid, the system cannot calculate a percentile and indicates that it is "N/A"; however, the code then treats "N/A" as a low value that cannot be calculated instead of as a high value that cannot be calculated. Since the system interprets "N/A" as a low value, Risk Factor 121 is incorrectly assigned (Short Stature or At Risk of Short Stature). Resolution: In this issue, the numbers entered were out of bounds causing the function to fail and return a -1 instead of the correct percentile. Since that value was below the Risk Factor threshold, Risk Factor 121 was assigned. Now, the code has been changed to check if the percent is at or above 0%. Additionally, the code for GetParticipantSummaryInfo() was corrected as it uses the same function as the code in this issue.
SUG-1215	Clinic	View Appointments for Date	Issue: A day that has not been designated as a holiday appears as a holiday in the View Appointments for Date screen; however, appointments can be scheduled for that day. Resolution: The ColorCodeCalendar() code has been reworked to correct holiday and business day color coding. The Daysoflook method was replaced with the GetDayLook method to retrieve the correct dates from the calendar control.
SUG-1222	System Administration	Programs	Issue: Users are unable to delete a record from the Programs screen. Resolution: This was related to a performance issue. The code has been modified to improve performance while loading programs.
SUG-1226	Clinic	Formula Replacement	Issue: When a participant has purchased all available formula for the month and then returned some of the formula, users are unable to replace formula using the Formula Replacement screen. The returned cans of formula are entered on a previous issuance month rather than the current month. Resolution: The code has been modified to include only the current food instruments in the data grid. Note: New functionality will be implemented to accommodate situations where two formula food items are on a food prescription. Currently, the application is designed to replace a formula in a prescription with only one formula item. Note: The Value of formula returned is displayed only when making the replacement for the first time. Once the replacement is made and the user tries to replace the formula again for the same benefit period, the formula returned will not display any value but 0. The system does not show the history of formula returned.
SUG-1229	Clinic	Participant Folder	Issue: Users are unable to create a two-way link between a mother and an infant in the Participant Folder. Resolution: Previously, the code used the POSTPARTUM ID as the key to determine if a link existed between the mother and infant. This assumed that the largest POSTPARTUM ID for a mother's State WIC ID would be for the latest pregnancy; however, that is not always the case for converted data. The code used to retrieve POSTPARTUM records has been modified to get the POSTPARTUM ID from the mother's latest certification record, if one exists. If a certification record does not exist, it indicates that the data is being entered for a new participant.
SUG-1238	Scheduled Job Administration	Reports	Issue: The Missouri PEDS report file for the CDC has errors. Resolution: There was some ambiguity about what the guidelines meant by "Supplementary Field for Children < 24 Months of Age". To resolve this issue, either the first of the reporting month or the date that breastfeeding was verified is used (from the PedNSS_Users_Guide_Fields.pdf). Additionally, there was an issue with whether there was data to report. It was found that in most cases, the data was simply not present in the system. The file has been validated and now reports the correct data.
SUG-1239	Clinic	Add/Replace Set of Benefits	Issue: When using the Add/Replace Set of Benefits screen to add a set of benefits, the system does not record the benefits as mailed if the Mailing Benefits check box is selected. Resolution: Previously, the Add/Replace Set of Benefits screen was only coded to update the mailed value when replacing a set of benefits. Now, the code has been corrected to update the MAILING field when Mailing Benefits is checked in all locations where benefits are issued and/or replaced.
SUG-1240	State Office	Initial and Closeout Participation by Clinic, Agency and Grantee FDI013 (Output)	Issue: The Grantee Number does not display correctly on the Initial and Closeout Participation by Clinic, Agency and Grantee FDI013 (Output) report. Resolution: The report previously displayed the Grantee IDs numerically as they appeared in the database (i.e. A1 was displayed as "1"); however, the state asked that IDs be displayed as "001". Now, this report (and all future Minnesota reports) will display Grantee IDs as 3 digits padded with zeroes. Also, the state of Minnesota requested that Grantees have specific IDs. Since the names and IDs are specific only to Minnesota, a SQL script has been provided that will need to be run on any Minnesota database prior to testing.
SUG-1251	Clinic, Central Administrative Site	Help screens	Issue: When users select either the F1 key or the Help on Screen menu option, the incorrect Help screens display for Certification History and Benefits History from the Clinic and Central Administrative Site applications. Resolution: The Help screen display has been corrected for Certification History, Benefits History, Postpartum Information, Pregnancy Information, Default Printers, Breastfeeding Item Issuance History, Breastfeeding Peer Counselor Contacts, and Unlock Locked Household. These and the following additional Help screen displays were verified: Nutrition Education Contact, Immunizations, Appointments, Nutrition Assessment, Risk Factors, Food Prescriptions, Demographics, AdditionalInfo1, AdditionalInfo2, Referrals and Other Programs, Height/Weight, and Blood. Screens not specifically listed above are outside the scope of this issue and therefore not tested. Any problems found with other Help screen displays will be addressed in a separate issue.
SUG-1252	Clinic	Goal Setting Contact	Issue: The drop-down list boxes in the Goal Setting Contact screen do not display the full text available. The text is truncated. Resolution: The drop-down list boxes have been resized to display the existing data without concatenation.
SUG-1264	Management Console	User Profile	Issue: Users receive an "Index out of Range" standard error message when editing the User Profile, changing the location, and clicking OK without selecting a role. Resolution: Now, when no roles are visible in the Roles data grid, the Edit and Delete buttons are disabled. They are enabled when roles are visible in the data grid. If a role is not selected when the user clicks OK, the following message is displayed: "Please select an item in the data grid".
SUG-1271	Clinic	Work with On-site Group	Issue: There is a slight discrepancy between the way in which the Work with On-site Group screen functions and the way in which it is documented in the DFDD. The DFDD states that upon unchecking the Issue Benefits check box, the Mailing Benefits check box is unchecked and disabled; however, in the system, when the Mailing Benefits check box is disabled, the field is not unchecked. Resolution: The screen now behaves as follows: The Mailing Benefits check box is enabled when the Issue Benefits check box is selected. It is unchecked and disabled when the Issue Benefits check box is unchecked. When the Mailing Benefits check box is selected, the Generate Address Label(s) First check box is enabled. The Generate Address Label(s) First check box is disabled when both the Mailing Benefits and Generate Official Notification check boxes are not selected. When the Generate Official Notification check box is selected, the Notice Type section is enabled. The Notice Type section is disabled when Generate Official Notification is not selected. The remaining controls in the Address Label(s) section are controlled only by the Generate Address Label(s) First check box.
SUG-1272	Clinic	EBT Household Change Guided Script	Issue: Beginning a new household change prior to finishing all steps in the EBT Household Change Guided Script for a previous household change locks the records for all members in the household. Resolution: A new household change record is created when determining a new household. When that step is repeated before completing the household change, a new record is created with a higher sequence number. This buries the old record and locks the household records. To resolve this issue, the Determine New Household step will be disabled after it has been completed. This will prevent the new record from being created while the original is still incomplete. If a user attempts to revisit this link, the Remove Current Benefits link, or the Add Benefits to New Household link after they have been completed, the system will display a standard warning message with the following text: "You have already completed this step". The Remove Cards link remains active whenever the EBT Household Change Guided Script is open, as long as the first two steps have been completed. This is by design.
SUG-1273	Clinic	Child Health Information	Issue: The Date Breastfeeding Began calendar control is enabled and Required on the Child Health Information screen in a linked infant record. This calendar control should be disabled when the Breastfeeding Now check box is checked. Resolution: The fix for this issue enables the Date Breastfeeding Began calendar control and makes it required when the Breastfeeding Now check box is checked and the calendar control is empty. Once the dates are entered, the data is saved even upon unchecking the check box. The calendar control is not cleared, but is still enabled so that updates to the field can be made.
SUG-1274	Clinic	EBT Household Change Guided Script	Issue: When attempting to perform a household change on a mother who was never issued a card, users are unable to proceed past the Remove Cards option in the EBT Household Change Guided Script. The following standard confirmation message is displayed: "Invalid/Missing Primary Cardholder Date of Birth". Resolution: This was caused by null values being returned by the account inquiry when the EBT Processor account did not exist. Code has been added to check if an account exists. If none exists, the household change is allowed to proceed.
SUG-1278	State Office	PC20XX File (Output)	Issue: There are three problems with the PC20XX File (Output): (1) There are 37 participants with no data in the NutritionRisk field (Field 14 a-j). (2) There are 10 infants and 30 children missing height and weight data. (3) Staff estimates of all WIC participants who receive TANF, SNAP, and Medicaid services are roughly 20% TANF, 60% SNAP, and 90% Medicaid. Resolution: (1) For most cases in which nutrition risk codes were not included in the PC20XX File (Output), the certification being reported had been modified by a batch process (most likely EOD) or had been created as a pseudo certification. In all cases, nutrition risk factors were not available in the database for the most recent certification as of April 2010. (2) The height and weight data used for the PC20XX File (Output) now includes data from certifications that ended in, started in, or extended through April 2010. Data collected before the certification, after the certification, or after April is not included. For cases in which height and weight data were not included in the PC20XX File (Output), the data was not available for the most recent certification as of April 2010. (3) The income contact data used for the PC20XX File (Output) now includes Adjunctive Eligibility data collected during the certification being reported but before the end of April 2010. The data is now collected from both the IncomeContact table and the IncomeContactAdjunctiveItem table. The V_IncomeContact view is used to combine the two sources of Adjunctive Eligibility data into one.
SUG-1279	State Office	Initial and Closeout Participation by Clinic, Agency and Grantee FDI013 (Output)	Issue: The November initial counts in the Initial and Closeout Participation by Clinic, Agency and Grantee FDI013 (Output) report did not match the September Closeout amounts. The report did not include all of the "no food package" counts for converted agencies. Resolution: The problem stemmed from the way in which participants who did not receive checks were counted. This specifically concerned women who were partially breastfeeding more than the max and fully-breastfed infants. If these participants received checks after the initial EOM process and before another EOM process was run, they were not included in the count of participants who did not receive checks. Now, the report simply counts the participants who should not have received checks as of the first EOM run as well as the participants who received checks for the month as of the first EOM. This corrects the Initial and Closeout totals.
SUG-1284	Vendor	Approve New MAR Prices	Issue: Category 19 (CVB) appears in the list on the Approve New MAR Prices screen. This is incorrect. Resolution: A change has been made to the code to exclude Category 19 items from the MAR calculation. This will prevent Category 19 items from being displayed in the MAR table and/or being displayed in the Approve New MAR Prices or Override MAR Prices screens. Additionally, a database script has been included to remove any existing Category 19 items from the table.
SUG-1285	System Administration	Organizations	Issue: When editing organization information in the Edit Organization screen, only the name of the organization appears. The other saved information (address, etc.) is not displayed on the screen. Resolution: This was an issue with the code not displaying the complete organization information on the screen. The code has been modified to show the complete organization details. The system is now storing and retrieving the organization records properly.
SUG-1293	Clinic	Demographics	Issue: Two-word last names are not being populated correctly in the Authorized Representative Name field of child records when copied from a family member's record. Resolution: The code has been modified to copy Authorized Representative, Proxy 1, and Proxy 2 names directly from the selected household member instead of attempting to parse the names from the line item display in the Copy Demographics from Another Household Member screen.
SUG-1299	Reference Utility	Risk Factors	Issue: In Reference Utility, all Risk Factors that should be setup as System Assigned or CPA Assigned Only should be locked down so that they cannot be changed to any other assignment method. Resolution: The risk factors in question are now setup such that they can only be System Assigned or CPA Assigned. These settings are hard coded and cannot be changed by the states or ITOs. In Edit mode, the Assignment Method drop-down list box on the Risk Factor screen in Reference Utility is disabled and pre-populated with the specified assignment method for those risk factors identified as "System Assigned" or "CPA Assigned". In add mode, the Assignment Method drop-down list box is disabled and pre-populated with "CPA Assigned". This fix includes adding a new column to the RiskFactorReference table called "AssignmentRestriction". If populated, this field will indicate the only valid value for the AssignmentMethod field (C = CPA Assigned, S = System Assigned, or a space for both). When this field is populated with a C or S, the Risk Factor screen will be populated with the appropriate value regardless of what value is in the AssignmentMethod field, and the drop-down list box will be disabled. If the value in AssignmentMethod is different from the value in AssignmentRestriction, it will only be saved when the user clicks on the OK button to save the record.
SUG-1308	Clinic	Reports	Issue: State and Clinic totals need to be added to the Minnesota Summary Statistics Report - Breastfeeding. Resolution: Clinic/State sections have been added for all sub-reports. The Breastfed Ever sub-report has been removed. Clinic, Agency, and State totals are calculated based on the Breastfeeding criteria description for both Ever Breastfed = "Y"/"N".
SUG-1326	Reference Utility	UPC	Issue: The Rebate Item check box in the UPC screen is not retaining its selection after being uploaded to the EBT Processor. It was set to "Yes" prior to upload. After being uploaded, the check box reverted to "No". Resolution: The code has been changed to use EbtAuthorizedUPC.RebateItem to populate the rebate flag correctly. After this fix, the user will see the correct flag for the RebateItem field in the APL file.
SUG-1333	Clinic	Child Health Information	Issue: The Birth Information group box controls are disabled on the Child Health Information screen. Resolution: The code has been modified to enable birth information controls for a participant in the Participant Folder.
SUG-1336	Reference Utility	Risk Factor	Issue: The Assignment Method is displayed in the Risk Factors screen, but the drop-down list box is blank when attempting to edit a record using the Risk Factor screen. Resolution: This problem was addressed when the AssignmentRestriction column was added to the RiskFactorReference table for SUG-1299. Now, this field is disabled if the Assignment Method is "S" (System Assigned) or "C" (CPA Assigned). It is enabled when the Assignment Method is "B" (Both). When it is enabled, it displays the value stored in the database but can be changed by the user as needed.
SUG-1427	Clinic	Certification Guided Script	Issue: Users cannot certify an infant with a date of birth of 12/30/2010. They receive a standard error message stating that the date of birth is invalid for an infant. Resolution: This problem occurred when trying to calculate the age of a participant born on January 30th or 31st when the current date was March 1st or 2nd. The GetAge() function would have trouble with the month of February and display the standard error message. The change has been in place since March 1st, resolving this issue. Additional code has been added so that this type of standard error message will not occur again. Note: Since this issue is isolated to specific dates in a calendar year, the resolution cannot be fully tested as the original timeframe has lapsed; however, the same scenarios found in this issue have been recreated with current dates without any problems.
SUG-1431	Reference Utility	County/City by ZIP Code	Issue: A standard error message is displayed when users attempt to add a new ZIP/City/County relationship on the County/City by ZIP Code screen. When users attempt to delete an entry, the deleted entry reappears when the screen is refreshed. When users attempt to edit an entry, edits are not retained and the old data reappears when the screen is refreshed. Resolution: A code issue related to the 2.13 changes for validating the ZIP code when in Demographics screens has been addressed. This fix will allow the Add, Edit, and Delete buttons to work as intended.
SUG-1450	Clinic	Cycle Adjust	Issue: Users cannot issue benefits for the current date with a FDTU of 3/27 when the LDTU of the last set was 3/10. Resolution: The issuance process has been redesigned. If the late pickup is for the cycle-adjusted participant, the FDTU is calculated correctly.
Recertification
SUG-1422	Central Administrative Site	CAS-001	The Enrollees by County/Municipality Report CAS001 (Output) has been through a recertification process to correct format, data, DFDD content, and add minor clarifications as necessary.
SUG-1423	Clinic	CLN-005	The Special Formula Prescription Expiration Date Report CAS006/CLN005/OPR025 (Output) has been through a recertification process to correct format, data, DFDD content, and add minor clarifications as necessary.
SUG-1424	Central Administrative Site	CAS-006	The Special Formula Prescription Expiration Date Report CAS006/CLN005/OPR025 (Output) has been through a recertification process to correct format, data, DFDD content, and add minor clarifications as necessary.
SUG-1425	State Office	OPR-025	The Special Formula Prescription Expiration Date Report CAS006/CLN005/OPR025 (Output) has been through a recertification process to correct format, data, DFDD content, and add minor clarifications as necessary.
SUG-1445	Clinic	CLN-006	The Benefit Pickup Report CLN006 (Output), Benefit Pickup Letter (Output), and Benefit Pickup Letter Address Labels (Output) have been through a recertification process to correct format, data, DFDD content, and add minor clarifications as necessary.
SUG-1457	Financial Management	FIN-001	The Supplier Rebate Report FIN001 (Output) has been through a recertification process to correct format, data, DFDD content, and add minor clarifications as necessary.
SUG-1458	Financial Management	FIN-008	The Obligation Value for O/S FIs Issued Report FIN008 (Output) has been through a recertification process to correct format, data, DFDD content, and add minor clarifications as necessary. Note: This report depends on data generated by the Benefit Issuance process. SUG-1200 identifies an issue where the PRINTREASON is not being correctly identified in the FOODINSTRUMENTPRINT table. All benefits were being identified as original issuance. SUG-1200 has been fixed in Release 2.13. From the date that 2.13 is in use, the system will correctly identify benefits as being original issuance or as being reprinted. Thus, there will not be historical data available for this report in production environments.

Release 2.13 Notes

CAB-1

CAB-3

CAB-4

CAB-5

CAB-6

CAB-8

CAB-9

CAB-11

CAB-13

CAB-14

DFDD-20

DFDD-32

DFDD-62

DFDD-63

DFDD-64

DFDD-66

SUG-171

SUG-208

SUG-223

SUG-316

SUG-341 / SUG-425

SUG-491 / SUG-608

SUG-501

SUG-614

SUG-624

SUG-626 / SUG-1213

SUG-729

SUG-788

SUG-846 / SUG-1346

SUG-869

SUG-954

SUG-987

SUG-1011

SUG-1028

SUG-1072

SUG-1089

SUG-1129

SUG-1130

SUG-1141

SUG-1144

SUG-1145

SUG-1157

SUG-1158

SUG-1161

SUG-1163

SUG-1164

SUG-1166

SUG-1170

SUG-1173

SUG-1195

SUG-1200

SUG-1203

SUG-1215

SUG-1222

SUG-1226

SUG-1229

SUG-1238

SUG-1239

SUG-1240

SUG-1251

SUG-1252

SUG-1264

SUG-1271

SUG-1272

SUG-1273

SUG-1274

SUG-1278

SUG-1279

SUG-1284

SUG-1285

SUG-1293

SUG-1299

SUG-1308

SUG-1326

SUG-1333

SUG-1336

SUG-1427

SUG-1431

SUG-1450