The SPIRIT
web applications (Vendor Online Application
and Vendor Online Price Survey)
now use a spiritweb user account with limited rights to execute any query
against the database. The updated SQL is in the SPIRITweb
Account SQL (2.15.05) topic.
Issue# |
Application Module |
Primary Function |
Detail |
Reported Issues |
DFDD-43 |
Clinic |
Print Preview |
Issue: The image of the screen
on the Print Preview
topic shows lines of text that do not display for all states.
Resolution: The
DFDD has been updated with a new screen
image. Additionally, a note has been added stating that not all
elements listed in the topic display for each state. |
DFDD-61 |
Clinic |
Individual Nutrition Education Contact |
Issue: The DFDD states that the Type
drop-down list box
on the Individual Nutrition Education Contact
screen is
populated with the NETYPE category
in the Reference Dictionary.
However, no NETYPE category
exists.
Resolution: The
DFDD has not been modified. The NETYPE category
in the Reference Dictionary
and the Reference Dictionary
Category does exist. Because the NETYPE category
is system-defined, it does not display on the Reference Dictionary
screen of
the Reference Utility
application. |
DFDD-91 |
Clinic |
Income Calculator |
Issue: The DFDD incorrectly documents the
Pending Proof of Income
check box on
the Income Calculator
screen. According
to the DFDD, when the Pending Proof of Income
check box is
checked,
it updates all other household members with the pending proof
information.
Resolution: The
DFDD has been updated to specify that when the Pending Proof of Income
check box is
checked
during a Certification Guided Script,
the pending proof value is not copied to the other household members.
When the Pending Proof of Income
check box is
checked
or unchecked
from within the Participant Folder,
it updates the proof of income for all household members. |
DFDD-93 |
Appendix |
Risk Factors |
Issue: The DFDD does not clearly define
the BMI range for Risk
Factor 133. The values are displayed with the operator "<="
when it should display with ">=".
Resolution: The
DFDD has been updated to use the correct operator to display the
BMI range. |
DFDD-99 |
Appendix |
Permissions Matrix |
Issue: The DFDD does not document all of
the features and feature groups for permissions on the Permissions Matrix.
Resolution: The
Permissions Matrix
has been updated to include all available features and feature
groups. Currently, the Permissions Matrix
is a work in progress, and not all feature groups and features
may be fully documented at this time. |
DFDD-101 |
Vendor |
Communications |
Issue: The DFDD does not document the Comments
column on the
Communications screen.
Resolution: The
DFDD has been updated to correctly document the Comments column on the Communications screen. This information
was updated during the Vendor
review. |
DFDD-104 |
Vendor |
Food Pricing |
Issue: The DFDD incorrectly documents the
screen elements
on the Food Pricing screen.
Resolution: The
DFDD has been updated to correctly document the screen elements on the Food Pricing screen. This information
was updated during the Vendor
review. |
DFDD-105 |
Appendix |
INCOMEVIEWFREQ |
Issue: The INCOMEVIEWFREQ
business rule needs
to specify that, according to FNS guidance, it must be set to
1.
Resolution: The
DFDD has been updated to include the FNS information. |
DFDD-111 |
Vendor |
Vendor List |
Issue: The DFDD does not include the Administration menu
under Interface Initialization
on the Vendor List topic.
Resolution: The
DFDD has been updated to include the Administration menu
under Interface Initialization.
This information was updated during the Vendor
review. |
DFDD-112 |
Vendor Online Application |
Peer Group Assignment |
Issue: The DFDD incorrectly documents the
screen elements
on the Peer Group Assignment
screen.
Resolution: The
DFDD has been updated to correctly document the screen elements on the Peer Group Assignment
screen. This
information was updated during the Vendor
review. |
DFDD-114 |
Vendor Online Application |
Business Information |
Issue: The DFDD incorrectly documents the
Business Information
screen for
a Partnership.
Resolution: The
DFDD has been updated to correctly document the Business Information
screen. The
Business Information
screen is
the same for all types of ownership structure. This information
was updated during the Vendor
review. |
DFDD-119 |
Clinic |
Benefits (Issue Benefits) |
Issue: On the Benefits (Issue Benefits)
screen topic,
the following information does not reflect how the system currently
functions:
"When a previous certification was not
terminated, and the recertification is occurring before the remaining
LDTUs, the system will attempt to keep the established issuance
cycle. Otherwise, if the CertEffective date > LastLDTU then
the next FDTU=LastCheckLDTU+1 day. This is the only time the next
FDTU is not calculated from the previous PrintedFDTUs."
Resolution: The
system is functioning as designed, and the DFDD has been updated
to clarify the information. The following information has been
added:
"When a previous certification is still
effective, and the recertification is occurring before the remaining
LDTUs, the system attempts to keep the established issuance cycle
only when the LDTU is in the future."
"When a previous certification is still
effective, and the recertification is occurring after the LDTU
of the last set of benefits issued, the system calculates the
FDTU = LDTU + 1 day. If the result is less than the system date,
the FDTU is set to the system date. If it is greater than the
system date, the system uses the calculated FDTU." |
DFDD-123 |
Clinic |
Confirm Benefits to Mark as Lost/Stolen and Reprint |
Issue: The DFDD incorrectly states that
the Identify Lost/Stolen Benefits
screen displays
when the OK
button is clicked on the
Confirm Benefits to Mark as Lost/Stolen and Reprint
screen.
Resolution: The
DFDD has been updated to document that the previous screen displayed within
the Participant Folder
displays when the OK
button is clicked. |
DFDD-124 |
Clinic |
Benefit Management menu |
Issue: The DFDD does not provide all of
the information about when the Mark Benefits as Lost/Stolen
menu option
is enabled on the Benefit Management menu.
Resolution: The
DFDD has been updated for the Mark Benefits as Lost/Stolen
menu option
and the Void Benefits
menu option
to clarify the menu options
are enabled when the participant is in a valid certification period
or the participant has a previous certification that currently
has benefits with a LDTU greater than the current system date. |
DFDD-125 |
Clinic |
Void Benefits Issued at Another Clinic |
Issue: The DFDD incorrectly defines the
Benefit Number
and Confirm Benefit
masked edit boxes
as the Check Number and Confirm
Check Number masked edit boxes
on the Void Benefits Issued at Another Clinic
screen.
Resolution: The
DFDD has been updated to refer to the controls correctly as the
Benefit Number and Confirm Benefit
masked edit boxes. |
DFDD-126 |
Appendix |
DAYSALLOWRESIDENCYCOPY |
Issue: The DFDD incorrectly states that
the DAYSALLOWRESIDENCYCOPY
business rule is
called the DAYSALLOWRESIDENCYPROOF business rule.
Additionally, the DFDD is incorrect on the value range for the
DAYSALLOWRESIDENCYCOPY
business rule and
the DAYSALLOWINCOMECOPY
business rule, documenting
the range as 1-99.
Resolution: There
is no reference in the DFDD to the DAYSALLOWRESIDENCYPROOF business rule, so no change was
made. The DAYSALLOWRESIDENCYCOPY
business rule and
the DAYSALLOWINCOMECOPY
business rule have
been modified in the DFDD to correctly document the range as 0-99. |
DFDD-129 |
Vendor |
Cost Containment Certification Spreadsheet (Output) |
Issue: The DFDD incorrectly states that
the third worksheet on the Cost Containment Certification Spreadsheet (Output)
is blank.
Resolution: The
DFDD has been updated to specify the spreadsheet has data populated
on the third worksheet. |
DFDD-130 |
Clinic |
Edit Food Item |
Issue: When the Quantity of Item
spin control
value on the Edit Food Item screen contains an invalid
amount, no standard error message
is displayed. Instead, the system converts the value to the maximum
value when the OK
button is clicked.
Resolution: The
DFDD has been updated to specify that when the Quantity of Item
spin control
value is greater than the maximum value of the Food Item, the
system resets the spin control
value to the maximum food item value. No standard error message
is displayed to alert the user. |
SUG-1633 |
Clinic |
Benefits (Issue Benefits) |
Issue: When the Issue Benefits
toolbar button
is clicked
within the Participant Folder
and inactive food items exist for the food prescription, the system
displays a standard error message
with the text "Benefits will not be issued for participant
{participant} REASON: Food Prescription contains inactive Food
Item(s)". However, the Benefits (Issue Benefits)
screen displays
when the standard error message
is dismissed and the benefits can be issued with the inactive
food items.
Resolution: The
issue was caused by a validation function that is part of the
benefit issuance process. The function was not returning an error
code when an inactive prescription food item was found. The code
has been modified to return the error code. |
SUG-1937 |
Clinic |
Benefits (Issue Benefits) |
Issue: For a participant certified on 1/31/12
with a LDTU of 2/29/12, the system is suggesting a quarter package
for February with a PFDTU and LDTU of 2/29/12 on the Benefits (Issue Benefits)
screen.
Resolution: When
determining benefits, the calculated LDTU is compared to the FDTU
to ensure the calculated LDTU is never less than FDTU. The system
was comparing this value using the greater than or equal to operator
(>=). The code has been modified to use the greater than operator
(>). |
SUG-1954 |
Reference Utility |
Food Item Wizard (1 of 3) |
Issue: When a new Contract Formula food
item is created on the Food Item Wizard (1 of 3)
screen, and
the food item expires, it can still be issued to a participant
without any notification to the user that it is expired.
Resolution: The
code has been modified to correctly recognize the Food Item Effective
date and Expiration date. Additionally, when one set of benefits
contains an inactive or expired food item(s), the system prevents
the issuance of all benefit sets. |
TOF-1 |
Clinic |
Certification History |
Issue: The "created:" date for
Income Contact on the Certification History
screen does
not stay consistent with the date entered initially for the participant.
Resolution: The
income contact record is created when an income contact is edited.
As a result, the income contact created information changes whenever
the income contact is edited. The code has been modified to stop
the record from being recreated and instead to update the record
when an income contact is modified. |
TOF-2 |
Clinic |
Food Prescription |
Issue: The Maximum
value label of
the Milk Products
group box on
the Food Prescription
screen for
a fully breastfeeding woman displays 30 quarts when the maximum
value should be 27 quarts.
Resolution: The
code has been modified to alter the stored procedure for uspGetBaseCatLimitInfo
to allow for category VII and VII+ to have 2 pounds of overlap. |
TOF-3 |
Clinic |
Capture Electronic Signature (for Receipt of Food Instrument Benefits) |
Issue: When the signature pad is prompted
to capture a signature from the Capture Electronic Signature (for Receipt of Food Instrument Benefits)
screen, if
the OK
button is clicked when
no signature has been entered on the signature pad, the screen displayed by the
signature pad software on the computer becomes blank. If the signature
pad is signed and the OK
button is clicked, the
signature pad locks up.
Additionally, the system does not display
the standard error message
with the text, "Form must be signed to proceed further."
Resolution: The
code has been modified to clear the signature pad screen to prevent it from
becoming locked.
Additionally, when no signature has been
entered, the code has been modified to display a standard error message
with the text, "Signature is required to proceed." |
TOF-5 |
Clinic |
Benefits (Issue Benefits) |
Issue: When a Pregnant with Multiples participant
is certified, the system is not issuing the Pregnant with Multiples
food package on the Benefits (Issue Benefits)
screen. Instead,
the system is reducing the quantities for the food package to
that for a Pregnant with Single participant. The Default Food
Package, Base Food Category Limits, and Food Item Limits are all
correct.
Resolution: When
the breastfeeding calculation was fixed, the calculation for multiples
for a pregnant woman was modified incorrectly. The code has been
changed to correctly calculate the Pregnant with Multiples food
package. |
TOF-7 |
Clinic |
Food Item Distribution |
Issue: When food items are set to rounding-alternate,
the system evenly distributes the higher amount on the Food Item Distribution
screen.
Resolution: The
code to select
the month index based on the benefit date was faulty. If a benefit
date was exactly one (1) month after the time frame calculation
start date, it returned an index that was one (1) less than the
correct value. This resulted in the quantity on the first two
(2) benefits being the actual quantity that should have been on
the first benefit. The third benefit had the quantity that should
have been on the second benefit. The code has been modified so
the correct quantities are on the correct benefits. |
TOF-8 |
Clinic |
Certification Guided Script |
Issue: When the EBT Household Demographics
link
is clicked
on the Certification Guided Script
screen, and
the system is unable to communicate with the EBT Processor,
the system displays a standard error message
with XML code.
Resolution: The
code has been modified to add a new standard error message
with that text, "Temporarily unable to communicate with JP
Morgan. Please try again later." |
TOF-10 |
Clinic |
Applicant is Certified |
Issue: When the Applicant is Certified
screen displays
for a second time after the Schedule Appointment
check box is
unchecked,
if the OK
button is clicked the system
creates a one day certification.
Resolution: The
code has been modified to disable the OK
button after it
is clicked. |
TOF-12 |
Clinic |
Food Item Distribution |
Issue: When food items are set to rounding-front
load, the system does not correctly distribute the food items
on the Food Item Distribution
screen.
Resolution: The
code to select
the month index based on the benefit date was faulty. If a benefit
date was exactly one (1) month after the time frame calculation
start date, it returned an index that was one (1) less than the
correct value. This resulted in the quantity on the first two
(2) benefits being the actual quantity that should have been on
the first benefit. The third benefit had the quantity that should
have been on the second benefit. The code has been modified so
the correct quantities are on the correct benefits. |
TOF-22 |
Clinic |
Special Prescription Item |
Issue: When the OK
button is clicked on the
Special Prescription Item
screen and
the infant is over 6 months old and has Food Package III, the
system is no longer displaying the standard confirmation message
with the text, "Infant is over 6 months receiving Food Package
III. Do you want the system to automatically remove the solid
food items from the food prescription so the formula quantity
may be increased to the 4-5 month old limit?"
Resolution: The
code has been updated to display the standard confirmation message
to conform with previous functionality. |
TOF-24 |
Clinic |
Work with On-site Group |
Issue: When only some members of a household
are checked
on the Work with On-site Group
screen and
the user makes modifications to those household members, the system
issues benefits for all household members, not just those who
were checked.
Additionally, the system generates the Official Notification Document (Output)
for all household members, not just those who were checked.
Resolution: The
code has been modified so that when a check box
is checked
for one household member, the check boxes
are checked
for all the remaining household members. Additionally, the Actions
group box has
been renamed the Actions for Household group box. |
TOF-25 |
Reference Utility |
Default Food Package/Default Food Package Item |
Issue: When the Preview
button is clicked on the
Default Food Package/Default Food Package Item
screen, an
object reference error displays followed by an unhandled exception.
Resolution: This
issue is caused by code that is trying to build a fake date of
birth for an infant on a preview where there is no participant.
There is non-preview related code in the fake date of birth that
does not distinguish when it is being called for a preview or
for a non-preview scenario. The code has been modified to ensure
the non-preview code is only called for non-preview scenarios. |
TOF-26 |
Clinic |
Work with On-site Group |
Issue: When benefits are issued for household
members not checked
on the Work with On-site Group
screen, the
Work with On-site Group
screen is
cleared even though benefits were not issued to all household
members.
Resolution: The
code has been modified so the system verifies that benefits have
been issued on the current system date for the participant before
clearing the participant from the Work with On-site Group
screen. |
TOF-29 |
Clinic |
Risk Factors |
Issue: When a certification is not completed
because the participant was over income, the Risk Factors screen displays the certification
as an incomplete certification.
Resolution: The
ineligible certification node
on the Risk Factors screen has been moved to
the Certification History
screen. The
code has been updated to have the previous certification end date
be the day the pending certification is deemed ineligible for
over income. |
TOF-30 |
Clinic |
Error Messages |
Issue: The Food Item ID is displaying in
front of the food item description in standard error messages.
Resolution: The
code has been modified to correctly display the Food Item ID after
the food item description in standard error messages. |
TOF-31 |
Clinic |
End of Day |
Issue: The WIC category for an infant is
never changed to child during the End of Day
Processing.
Resolution: The
code has been modified to change the WIC category from infant
to child during the End of Day
Processing. |
TOF-33 |
Clinic |
Food Prescription (Issue Benefits) |
Issue: When food prescriptions are edited
on the Food Prescription
screen when
called from the Food Prescription (Issue Benefits)
screen, the
changes are not saved.
For some food prescriptions, when the Change Food Prescription
button is clicked, the
wrong month's food prescription displays.
When the user switches from the Food Prescription
tab to the Benefits
tab, all the check boxes for benefits are
unchecked
for the benefits to be issues.
Resolution: The
Food Prescription
screen, because
of the way it was implemented, is using the current prescription
as the input instead of the selected
prescription in tvFoodPrescription. Additionally, it is not setting
the prescription changed flag.
The behavior of the check boxes
was unchanged as this is the existing design. The tvchecks tree
is regenerated because the benefit is not the same benefit after
it has been edited. |
TOF-36 |
Clinic |
Food Prescription |
Issue: On the Food Prescription
screen, the
equivalent value of a food item (for example, "22 quarts
of milk product" is displayed at the end of the food item
description) is no longer displaying.
Resolution: The
code has been modified to display the quarts value. |
TOF-38 |
Clinic |
Certification Guided Script |
Issue: When a fully breastfeeding infant
is certified on the Certification Guided Script
screen and
the infant is under six (6) months of age, the system does not
suggest the 6-month default food package.
Resolution: The
code that added additional food packages had a validation that
ran to verify the infant was allowed to have formula. This causes
a problem for any infant that might not be allowed formula, but
later might be allowed a default prescription. The code has been
modified to remove the validation. |
TOF-39 |
Clinic |
Benefits (Issue Benefits) |
Issue: When a fully breastfeeding infant
is certified on the Certification Guided Script
screen, no
future food prescriptions are suggested and the Food Prescription
link
is not checked.
On the Benefits (Issue Benefits)
screen, the
system displays a standard information message
with the text, "Benefits will not be issued for participant
{WIC ID} {Last Name}, {First Name} REASON: Participant needs a
Food Prescription that is effective for the current certification."
The standard information message
should inform the user that the participant is fully breastfed
and cannot receive benefits until they are 6 months old.
Resolution: The
code has been modified to display a standard information message
with the text, "Benefits will not be issued for participant
{WIC ID} {Last Name}, {First Name} REASON: Participant is Fully
Breastfed and cannot receive benefits until they are 6 months
old." |
TOF-41 |
Clinic |
Work with Another Household Member |
Issue: When the Work with Another Household Member
screen is
displayed from the Certification Guided Script
screen and
the user chooses a new family member, the previous member's Certification Guided Script
remains open. If the user attempts to switch back to the other
member using the Work with Another Household Member
screen, a
standard error message
displays with the text, "Another copy of folder for this
Participant is already opened. Please use the existing folder."
Resolution: When
working with a pregnant, breastfeeding, or non-breastfeeding participant,
the Work with Another Household Member
screen does
not close the currently opened Participant Folder.
The code has been modified to close the current Participant Folder. |
TOF-43 |
Clinic |
Exit
menu option |
Issue: The Exit
menu option
on the File menu of the Participant Folder
is only closing the Participant Folder
and not the whole application as documented in the DFDD.
Resolution: The
code has been modified so the Exit
menu option
closes the application.
Additionally, the Exit
button has been
removed from the Certification Guided Script
screen. The
Exit
menu option
has been removed from the File menu on the Certification Guided Script
screen. |
TOF-45 |
State Office |
Unduplicated Reported Participation - BF Amt and Ethnicity/Race (Calendar Year) Report CLD035 (Output) |
Issue: The Unduplicated Reported Participation - BF Amt and Ethnicity/Race (Calendar Year) Report CLD035 (Output)
contains the following issues:
The End of Month Processing
should not generate this report due to its size. The report
should only be available on-demand on the Generate Unduplicated Reported Participation - BF Amt and Ethnicity/Race (Calendar Year) Report
screen.
The Multi-Race
breakdown should be included on the report when generated
on-demand.
The Clinic(s)
list box
should be disabled when the Agency,
Grantee,
or State
radio button
is selected.
When generating
the report with the Save to Excel
radio button
selected,
it does not specify the file type.
The Excel
version output has the label CLN032 instead of the correct
report number, CLD035.
There is a
colon (:) followed by the phrase "Not Hispanic or Latino"
after each of the races in the "Ethnicity: Not Hispanic
or Latino" section.
The Unduplicated Reported Participation - BF Amt and Ethnicity/Race (Calendar Year) Report CLD035 (Output)
contains the following formatting issues:
The report
heading should wrap and fill two lines.
When the report
is generated at the Clinic level, it should list the Agency
ID and Agency Name above the Clinic ID and Clinic Name.
The first
header on each page of the report that describes the participants
who are included should be formatted in all capital letters
and be bold.
The ethnicity
headers, totals for the ethnicity sections, and the Unknown
Race/Ethnicity Totals should be bold.
At the end of each section, the
word "Total" should be added. The text should be
formatted in all capital letters and be bold.
When the header is "Women"
or "Infants", the headers and total lines should
include the word "All" (e.g., "All Women"
and "All Infants").
On the last page, the total should
include the descriptor of what the total is dependent on and
how it was run.
Resolution: The
following changes were made to the code:
The report
has been removed from the End of Month Processing.
The report
heading now wraps to two lines.
The Grantee
ID and Name, when applicable, and the Agency ID and Name have
been added above the Clinic ID and Name.
The requested
formatting changes for all capital letters and bold or simply
applying bold to the text have been implemented.
A Multiple
Race Details section has been added for all report types.
"Children"
and "Women" headers now read "All Children"
and "All Women".
The Clinic(s)
list box
was being disabled, but it was not changing colors. This has
been corrected to disable the control.
When saving
to Excel format, it now has two extensions: XLS or All.
The report
name in the Excel file has been changed from CLN032 to CLD035.
The font for
the Race/Ethnicity has been changed from 9-pt to 10-pt to
improve readability.
The last line
for each report and the last line for individual clinics now have
how the report was run.
|
TOF-46 |
Clinic |
Summary Statistics Report CLN031 (Output) |
Issue: The divisor description was changed
on the Agency Summary but not on the individual clinics for the
Summary Statistics Report CLN031 (Output).
The new description is confusing as it lists the children in years
but the column
lists them in months.
Resolution: The
divisor description has been changed to the following:
63(<12 mo) + 21(12 to <18 mo) + 19(18
to <24 mo) + 23(30 to <36 mo) + 46(36 to <48 mo) + 51(48
to <60 mo)
The divisor description has been changed
on all levels (Clinic/Agency/State) to display values for seven
(7) groupings. The DIV column
has not been modified; it continues to indicate all columns (1-7). |
TOF-47 |
State Office |
Weight Status of Women and Children Greater than 2 Years (BMI) Report OPR032 (Output) |
Issue: The Weight Status of Women and Children Greater than 2 Years (BMI) Report OPR032 (Output)
should only include children who are twenty-four (24) months or
older at the time of the measurement, and those who were measured
standing.
The Weight Status of Women and Children Greater than 2 Years (BMI) Report OPR032 (Output)
contains the following formatting issues:
The report
heading should be mixed case and include the grantee and agency
in the title.
Some letters
are being cut off from the bottom of a line of text.
There is a
hyphen following a greater than sign.
The headers
are not always centered for columns.
The grantee
number is not provided before the "Grantee Total".
The agency
name is being printed on the last page which should read "State
Total".
The use of
capitalized words and mixed case words is inconsistent.
Resolution: The
report has been updated to document that it only reports children
greater than two (2) years of age who were measured standing.
The following changes were made to the code:
The title
was changed to mixed case.
The rows where
letters were being cut off have been expanded.
The text in
the legends was made mixed case.
The header
on the last page has been changed to read "Grantee Total".
The row headers
were changed to mixed case.
|
TOF-48 |
Reference Utility |
Food Item Wizard (1 of 3) |
Issue: When the Distribution Rule
drop-down list box
on the Food Item Wizard (1 of 3)
screen is
changed from "Quantity on Separate Check(s)" to "Balance
on Remaining Check", the benefits correctly use the maximum
check quantity for the food item, but the formula is printed on
the benefits with other food items.
Resolution: The
code has been modified to change Rule4 separate checks to be set
to front load rather than even distribution. This also corrects
various bugs with the checks when the Max Check Qty is not a multiple
of the largest purchase size. |
TOF-49 |
Clinic |
Select Risk Factors |
Issue: Risk
Factor 335 is displaying multiple times on the Select Risk Factors
screen.
Resolution: Risk
Factor 335 was added to the RiskFactorReference table more than once to
account for multiple births for one pregnancy. The code has been
modified to filter the list based on the breastfeeding amount
field. Risk
Factor 335 now displays only one time. |
TOF-64 |
Clinic |
Print Preview |
Issue: The Close
button on the
Print Preview
screen does
not function with the keyboard shortcut of the Escape (ESC) key.
Resolution: The
DFDD has been updated to remove the keyboard shortcut of the Escape
(ESC) key. The Close
button does have
a mnemonic of "C", which has been documented. |
TOF-65 |
Clinic |
Confirm Benefits to Mark as Lost/Stolen and Reprint |
Issue: The DFDD incorrectly documents when
the Mailing Benefits
and Generate Address Label
check boxes are
enabled on the Confirm Benefits to Mark as Lost/Stolen and Reprint
screen.
Resolution: The
DFDD has been updated to correctly document when the controls
are enabled or disabled. |
VDP-164 |
Vendor Online Price Survey |
Create New Price List |
Issue: On the Create New Price List
screen, the
Fruit and Vegetable benefits do not display in the data grid.
Resolution: The
code has been modified to remove the filter within the database
procedure that was preventing base food category "L"
(Cash Benefit) from displaying. |
VRP-1 |
Vendor Online Application |
Owner Information (Sole Proprietorship),
Owner Information (Partnership),
Owner Information (Corporation),
Store Information |
Issue: There are some inconsistencies on
screens that
do not follow current standards.
On the Owner Information (Sole Proprietorship)
screen, Owner Information (Partnership)
screen, and
Owner Information (Corporation)
screen, in
the Address Information
group box, pressing
TAB while focus is placed in the State
drop-down list box
does not send focus to the ZIP Code masked edit box.
On the Owner Information (Sole Proprietorship)
screen and
Owner Information (Partnership)
screen, the
WIC Stores Owned
and Non-WIC Stores Owned
masked edit boxes
do not contain a comma for the numeric value.
On the Store Information
screen, the
Account Number
text box was
not limiting the maximum characters based on the BANKACCOUNTNUMLENGTH
business rule.
On the Store Information
screen, the
State Sales Tax Number
text box tooltip
text should read "up to 15 digits" and not "must
be 15 digits".
On the Store Information
screen, the
Cashiers and Cash Registers
masked edit boxes
do not contain a comma for the numeric value.
Resolution: On
the Owner Information (Sole Proprietorship)
screen, Owner Information (Partnership)
screen, and
Owner Information (Corporation)
screen, pressing
TAB while focus is in the State
drop-down list box
now moves focus to the ZIP Code masked edit box.
The WIC Stores Owned
and Non-WIC Stores Owned
masked edit boxes
now display a comma based on the mask: "#,###".
On the Store Information
screen, the
Account Number
text box is now
correctly limiting the length of the value based on the BANKACCOUNTNUMLENGTH
business rule. The
tooptip has been modified to update based on the value of the
BANKACCOUNTNUMLENGTH
business rule.
On the Store Information
screen, the
State Sales Tax Number
text box tooltip
has been updated to read "up to 15 digits".
On the Store Information
screen, the
Cashiers
and Cash Registers
masked edit boxes
now display a comma based on the mask: "##,###". |
VRP-2 |
Vendor |
Manage Food Price Multipliers |
Issue: When a selection
is made in the Primary Food Distribution Item column
on the Manage Food Price Multipliers
screen, after
selecting
the Multiplier column
blank rows are added to the Food Price Multipliers
data grid.
Resolution: The
code has been modified to correct the filtering of the drop-down list boxes by moving
the code from the CellEnter event to the CellBeginEdit event.
Rows without a BaseFoodCategoryID (blank rows) now correctly filter.
The Delete
button now correctly
deletes the row selected
by the user.
The blank rows being added to the Food Price Multipliers
data grid were
the result of binding to a DataTable object. The object does not
correctly dispatch the state change messages which results in
the blank row being added. The code has been modified to change
the Manage Food Price Multipliers
screen so
that no binding is used to prevent any possibility of an underlying
bound object creating blank rows. |
VRP-3 |
Vendor |
Vendor List |
Issue: When resizing any of the columns in the data grid on the Vendor List screen, the records are
resorted based on the column
being resized or based on the column
next to the column
being resized.
Resolution: The
Vendor List
data grid has
been modified to differentiate between a column
resize event and a sort event. The columns
will no longer sort when resized. |
VRP-4 |
Vendor Online Price Survey |
Price List Details |
Issue: When a price is entered for a parent
item on the Price List Details
screen, the
child item is correctly calculated. However, if the price for
the parent item is cleared and a rejection reason is selected, the
child item's price is not cleared.
Resolution: The
system is working as designed. If a user rejects the parent item,
when the vendor resubmits the price, the system fixes the price
for the child item that belongs to the multiplier. |
VRP-6 |
Vendor Online Application |
Business Information |
Issue: When multiple tabs
are added to the Contact Information
group box on
the Business Information
screen, the
Primary Contact tab
is no longer visible. When this occurs, the user cannot see that
required information is missing from the tab
after the Save
or Next
button is clicked.
Resolution: The
code has been modified to add MultiRow capabilities to the tab controls. All tabs in the Contact Information
group box are
visible at all times. |
VRP-7 |
Vendor |
Events and Follow-up Activities |
Issue: When a selection
is not made in a required drop-down list box,
the system displays a standard error message
with the text, "A selection is required in the {control topic}."
The correct standard error message
is "A selection is required for the {control label}."
Resolution: The
code has been modified to display the correct standard error message. |
VRP-8 |
Vendor and Vendor Online Application |
Vendor Folder |
Issue: The required fields of the Vendor Online Application
do not match the required fields in the Vendor Folder.
Resolution: The
code has been modified to add values to the VendorOnlineApplicationParameters
table to
tie definitions to the three tabs
of the Demographics
screen. The
required fields are configurable from the database. |
VRP-9 |
Vendor Online Application |
Owner Information (Sole Proprietorship)
and Owner Information (Partnership) |
Issue: When entering the address information
on the Owner Information (Sole Proprietorship)
screen or
the Owner Information (Partnership)
screen, the
Mailing Address tab
does not display if the Physical Address information is entered.
Clicking
the Save
or Next
button clears
the data that was entered.
Resolution: The
code has been modified to set the selected
index using a safer method for the State
drop-down list box.
Setting an individual list item's
Selected attribute to "true" can confuse the control.
In uwtAddress_TabClick, the system now makes sure that both physical
and mailing addresses have been looked up and are identical before
syncing the address field values between Physical and Mailing. |
VRP-11 |
Reference Utility |
Violation Types |
Issue: When a new violation type is added
on the Violation Types
screen, it
is not saved when the OK
button is clicked.
Resolution: The
maximum number of characters for the Violation column was not limited. Entering
more characters than could be saved in the database caused the
issue. The code has been modified to limit the maximum number
of characters for the Violation column
to 135 characters. |
VRP-12 |
Vendor |
High Risk Analysis |
Issue: When the highlight color is set for
the high risk vendors on the High Risk Analysis
screen, the
cells for high risk vendors do not have the color applied. If
a dark color is chosen, the cells become completely white with
no visible text.
Resolution: The
WIC.Windows.Common.EditableDataGridView data grid
was designed to enforce style consistency across all applications,
and as a result, it does not allow cells to have custom background
colors. The base class behavior was modified to allow custom background
colors.
Additionally, the system not checking the
check boxes was
caused by the system not returning the correct DialogResult code.
The code to return the correct value has been added. |
VRP-13 |
Vendor |
High Risk Analysis |
Issue: When attempting to sort the columns on the High Risk Analysis
screen by
double-clicking
the column header,
the system displays the Edit High Risk Criterion
screen or
a standard error message
with the text, "You must select a high risk criterion to
edit."
Resolution: The
code has been modified to enable sorting of the data grid. |
VRP-14 |
Vendor |
Notes |
Issue: When a note is deleted under special
circumstances, a standard error message
displays with the text, "Index was out of Range. Must be
non-negative and less than the size of the collection." This
standard error message
displays multiple times when a new note is added on the Notes screen
within the Vendor Folder where
an old note currently exists that has a blank Staff ID and the
note that has a blank Staff ID is deleted.
This standard error message
also displays multiple times when two notes currently exist on
the Notes screen
within the Vendor Folder and
one has a blank Staff ID, and the note that has a blank Staff
ID is deleted.
Resolution: The
code has been modified to remove the selected
VendorNote from the collection and then refresh the data grid after the delete
occurs. |
VRP-15 |
Clinic |
Growth Grids |
Issue: On the various Growth Grids screens, when a row is resized
and the user double-clicks
the line between the rows, an unhandled exception displays.
Resolution: The
code has been modified to remove the Percentage Gained column since it does not exist
in the growth grid. |
VRP-16 |
Clinic |
Schedule Appointments for Household |
Issue: When opening the Schedule Appointments for Household
screen from
the Immunizations screen, the Schedule Appointments for Household
screen displays
behind the Participant Folder.
Resolution: The
code has been modified so the Schedule Appointments for Household
screen opens
and displays correctly in front of the Participant Folder. |
VRP-17 |
Reference Utility |
Default Food Package/Default Food Package Item |
Issue: When attempting to print from the
Default Food Package/Default Food Package Item
screen after
clicking
the Preview
button, only the
last page prints.
Resolution: The
Default Food Package/Default Food Package Item
screen uses
a variable to keep track of how many checks have to be printed.
The system loops through all the checks, placing them on one or
more pages until there are no more checks to print. The issue
was caused by the variable not being re-initialized back to zero
(0) after each complete process had run. The code has been modified
to always re-initialize the variable to zero (0) after each successful
run of the process so that each subsequent printing attempt starts
from the first check and loops through them until all are printed.
Additionally, another issue was fixed to
prevent a blank page from printing when the maximum number of
checks is printed on the last page. |
VRP-18 |
Vendor Online Price Survey |
New Price List |
Issue: The text on the New Price List screen cannot be read because
the background color matches the text color.
Resolution: The
code has been modified to handle the compatibility level for Internet
Explorer. |
VRP-19 |
Vendor Online Application |
Business Information |
Issue: When the maximum number of characters
is entered in the Trade Name (DBA)
text box on the
Business Information
screen, an
error occurs if all of those characters are numeric.
Resolution: The
IsNull() method in the OnlineApplicationManager was formatting
the Trade Name value as a number because the characters were all
numeric. The code has been modified so the IsNull assumes that
the value being formatted is text. An optional argument has been
added to IsNull to force a value to be formatted numerically if
the specified value is numeric and the argument is passed a True. |
VRP-22 |
Vendor Online Price Survey |
Price Survey |
Issue: When the maximum price ($999.99)
is entered for a record on the Price Survey screen and the Submit
button is clicked, a standard error message
displays with the text, "404 - File or directory not found."
Resolution: The
code has been modified to have an error handling routine to log
the error in the ExceptionLog table
and report the reference number as part of the standard error message.
The system now displays a standard error message
with the text, "An error has occurred on the page. Reference
Number: {number}." |
VRP-23 |
Vendor |
Price Survey |
Issue: On the Price Survey screen within the Vendor Folder, if
the columns in
the data grid
are expanded to be very wide, and the user clicks
on a different tab
and then returns to the Price Survey screen, an object reference
error is displayed followed by an unhandled exception.
Resolution: The
errors result from a column
that is partially shown (half hidden and half visible) on the
left of the data grid
after widening a previous column.
The code has been modified so the Price Survey screen rebuilds itself and
continues functioning. |
VRP-24 |
Vendor |
Documents |
Issue: When expanding the columns on the Documents screen within the Vendor Folder, the
column width
is retained until the Vendor Folder is
closed and reopened.
Resolution: The
code has been modified to correct some resizing code that did
not account for the user leaving and navigating back to the Documents
screen within
the Vendor Folder. |
VRP-26 |
Clinic |
Height/Weight, Immunizations, Nutrition Assessment,
Nutrition Education Contact,
Food Prescriptions,
and Add SOAP Note |
Issue: The default button
that receives focus on certain screens
during a Certification Guided Script
is not consistent with the default button
documented in the DFDD.
On the Height/Weight
screen,
the Growth Grids
button has
focus when the screen
is launched, but the DFDD states that the Add
button is
the default button
for the screen.
On the Immunizations
screen,
no button
has focus.
On the Nutrition Assessment
screen,
no button
has focus.
On the Nutrition Education Contact
screen,
no button
has focus.
On the Food Prescriptions
screen,
no button
has focus.
On the Add SOAP Note
screen,
the OK
button is
highlighted, but the focus is in the multi-line text box
preventing the Enter key from activating the button.
Resolution: The
code has been modified to make the following changes:
On the Height/Weight
screen,
the Add
button is
now the default button.
On the Immunizations
screen,
the Add
button is
now the default button.
Additionally, the Close
button now
has a keyboard shortcut of Escape (ESC).
On the Nutrition Assessment
screen,
the Add
button is
now the default button.
Additionally, the Close
button now
has a keyboard shortcut of Escape (ESC).
On the Nutrition Education Contact
screen,
the Add Individual Contact
button is
now the default button.
Additionally, the Close
button now
has a keyboard shortcut of Escape (ESC).
On the Food Prescriptions
screen,
the Add
button is
now the default button.
Additionally, the Close
button now
has a keyboard shortcut of Escape (ESC).
On the Add SOAP Note
screen,
the OK
button is
the default button
when focus is not in the multi-line text box.
The tab order topic
of the DFDD has been updated to specify that some controls
remove focus from the default button
when focus is placed in the control.
|
VRP-27 |
Vendor Online Price Survey |
Online Price Survey |
Issue: The title text of the Online Price Survey
screen and
all other screens
of the Vendor Online Price Survey
do not display the correct title.
Resolution: The
code has been changed to pull the title text for the primary Vendor Online Price Survey
screens from
the REPORTHEADING
business rule. |
VRP-28 |
Vendor |
Log Telephone Call
and Vendor List |
Issue: The Log Telephone Call
menu option
on the Vendor List menu is
enabled after the user has searched, cleared the search criteria,
and then searched again to display no results on the Vendor List screen. When the Log Telephone Call
menu option
is selected,
an object reference error is displayed.
Additionally, selecting
the Corporate Parent
radio button
on the Vendor List screen and searching displays
the standard error message
for a required field instead of the standard error message
with the text, "Please specify search criteria."
Resolution: The
code has been modified so the Log Telephone Call
menu option
is no longer active when no search results are found.
The code has been modified to remove the
verification of the Corporate Parent
drop-down list box
and instead treats it like all other standard search controls. |
VRP-29 |
Vendor |
Compliance Buy Benefits |
Issue: When the Package browse button is clicked
on the Compliance Buy Benefits
screen, an
unhandled exception error displays.
Resolution: The
error was caused by a lack of validation of the package records
in the Benefit Set
editable data grid
when the Package browse button
is clicked.
The code has been modified to add validation to the Package browse
button. |
VRP-30 |
Vendor |
Generate Vendor Inventory Audit Report |
Issue: When generating the Vendor Inventory Audit Report (Output)
on the Generate Vendor Inventory Audit Report
screen, the
report prints the date one day before the date of visit recorded
for the audit. If the computer's time zone is changed to CST,
the report prints the same date as the date of visit.
Resolution: The
code has been modified to remove the time component in the date. |
VRP-31 |
Vendor |
Vendor Benefits Redeemed Report VND068 (Output) |
Issue: When the Vendor Benefits Redeemed Report VND068 (Output)
is output in Excel, the column
heading Serial Number should be Benefits Number. Additionally,
the Vendor ID and Stamp Number do not display the leading zeros.
Resolution: The
code has been modified to rename the column
from "Serial Number" to "Benefits Number".
Additionally, the Vendor ID and Stamp Number now correctly display
the leading zeros. The missing leading zeros were the result of
the fields being changed to a Number cell in certain versions
of Excel. |
VRP-33 |
Appendix |
HEALTHNOTESORTORDER
and NOTESORTORDER |
Issue: The HEALTHNOTESORTORDER
and NOTESORTORDER
business rules' information
is not clear. The two business rules
essentially have the same definition in the DFDD.
Resolution: The
DFDD has been updated with clearer information for the business rules. The HEALTHNOTESORTORDER
business rule is
used for sorting the notes on the View Notes screen of the WIC Outreach Loaner Program
application. The NOTESORTORDER
business rule is
used for sorting the notes on the Manage Notes screen of the Central Administrative Site,
Clinic,
and State Office
applications. |
VRP-34 |
Vendor |
Scan Document |
Issue: On the Scan Document screen, there is no information
in the standard confirmation message
explaining what to do when the user has completed scanning individual
pages.
Resolution: The
standard confirmation message
has been modified and now displays the text, "To continue
the scanning process, place the next page of the document face
down on the scanner glass, as indicated by the reference marks,
and click OK.
To end the scanning process, click Cancel." |
VRP-35 |
Vendor |
Manage Food Instrument Types |
Issue: The Manage Food Instrument Types
screen takes
several minutes to run and uses a large amount of the computer's
memory. The memory does not immediately release after closing
the Manage Food Instrument Types
screen.
Resolution: Food
Instrument Types are large in most databases, so every time a
new combination of food items is printed, a new Food Instrument
Type is created. The system contains code that reads every Food
Item detail record for every Food Type from the database. The
system pulling in all of this data resulted in the Manage Food Instrument Types
screen using
a large amount of memory to load and run.
The code has been modified to remove the
function to retrieve all of the Food Items when the screen is launched. Instead,
only the food items for the currently displayed page are retrieved.
A new VendorService web service, GetFoodInstrumentTypeFoodItemsSet(),
has been created to retrieve the Food Items using the fifty (50)
or fewer Food Type IDs displayed on the first page of the screen.
Additionally, the Clear
button process
has been modified to always show the first page of the original
list after clearing the search results. |
VRP-36 |
Vendor |
Vendor Benefits Redeemed Report VND068 (Output) |
Issue: When the Vendor Benefits Redeemed Report VND068 (Output)
is generated for Excel, the frozen panes cannot be viewed. Moving
the horizontal scroll bar does not affect the frozen panes. The
user must manually unfreeze all panes in the worksheet to view
the frozen panes.
Resolution: The
code has been modified to remove the frozen panes from the output.
This makes the report compatible with all versions of Excel. |
VRP-37 |
Vendor |
All |
Issue: When certain follow-up activities
are added to the tree list
on the All screen
on the Event Log screen within the Vendor Folder, the
date entered on the Follow-up Activities
screen displays
in the tree list.
When the Vendor Folder is
closed and reopened, the date of the follow-up activity changes
to the date entered on the screen
for adding the follow-up activity. This occurs for the Corrective Action
and Corrective Action Plan
follow-up activities.
Resolution: For
the Corrective Action
and Corrective Action Plan
follow-up activities, the Date of Activity value was not being
preserved when creating the activity record. The code has been
modified to use the correct Date of Activity. This issue appears
to have been isolated to these two activities. |
VRP-38 |
Vendor |
Custom Letter Sent Summary |
Issue: When sending a custom letter to one
vendor on the Send Form Letters
screen, the
Recipients
value label on
the Custom Letter Sent Summary
screen shows
"Multiple Vendors" for the recipients even though only
one letter was sent to a single vendor.
Resolution: The
code has been modified so the Recipients
value label now
correctly displays the recipient of the letter based on the following
criteria:
If the letter
was sent to a single vendor, the Recipients
value label
displays "Single Vendor".
If the letter
was sent to a single corporate parent, the Recipients
value label
displays "Single Corporate Parent".
If the letter
was sent to multiple vendors, the Recipients
value label
displays "Multiple Vendors".
If the letter
was sent to multiple corporate parents, the Recipients
value label
displays "Multiple Corporate Parents".
|
VRP-39 |
Vendor |
Create New Template |
Issue: When a new custom letter template
is created on the Create New Template
screen using
all available mail merge fields, a signature, and logo, the letter
cannot be generated on the Custom Letter Sent
screen. The
system displays a standard error message
with the text, "There was no mail merge data generated for
the criteria that you selected."
Resolution: The
original design of the custom mail merge engine used Left Joins
and Outer Apply statements for non-critical data, while contact
information was Inner Joins to prevent blank contact records.
The code has been modified to change all Inner Joins and Cross
Apply statements to be Outer Joins and Outer Apply statements.
This has the potential to increase the number of records produced
depending on the mail merge fields selected
since it may result in a Cartesian join of the data. The system
continues to filter out rows where all the fields are blank. |
VRP-40 |
Vendor |
Manage Communication Templates
and Custom Letter Sent |
Issue: The ability to maintain an e-mail's subject and
body contents is missing from the Reference Utility
application. It was supposed to have been added in VND-38.
Resolution: The
Manage Communication Templates
screen has
been modified to add functionality. The code that retrieves the
communication template information has been modified to retrieve
the templates by text instead of CommunicationTemplateID only.
A new Custom E-mail
Template function has been added on the Manage Communication Templates
screen. It
allows the user to add or edit the sender's e-mail,
name, and subject for e-mails.
The Custom Letter Sent
screen has
been modified to use information from the new Custom E-mail Template function
instead of using system-wide information.
The following new standard error messages
have been added on the Custom Letter Sent
screen:
If the system
cannot retrieve the template record, the system displays a
standard error message
with the text, "The system is not configured to send
e-mail."
If the sender's
e-mail
address is blank or is not valid, the system displays a standard error message
with the text, "The system is not configured with a sender
e-mail
address."
If the subject
or body is blank, the system displays a standard error message
with the text, "The system is not configured with an
e-mail
subject."
The system still needs to be configured with
a valid SMTP server on the E-mail Settings
screen. The
From E-mail
Address text box
is unchanged for cases when the system needs to send out system
generated e-mails
in the future. |
VRP-41 |
Vendor Online Price Survey |
Create New Price List |
Issue: When two retail items share the same
ID and only one item has the Include in Average column checked
on the Create New Price List
screen, an
error displays.
Resolution: The
code has been modified to correct two occurrences of primary key
errors by changing the SQL stored procedure to properly process
items that have "IncludeInAvg" checked,
and to have subselect correctly use the column
name when accessing the FoodDistributionItem table.
The system calculates the price for the distribution item only
if the Include in Average column
is checked
for at least one retail item. If there is nothing checked, there
is no entry for the distribution item in the price survey. |
VRP-42 |
Vendor |
Manage Authorization Steps |
Issue: When there are multiple blank rows
on the Manage Authorization Steps
screen and
a row in the middle is set to Active and OK
is clicked,
validation occurs and the screen
is not processed. If the newly activated
row is deleted, an unhandled exception displays.
Resolution: The
unhandled exception was caused by a lack of validation for the
cells in the Priority column
when records were reordered by priorities. The code has been modified
to add validation to the Priority column. |
VRP-45 |
Vendor |
Manage Online Application Parameters |
Issue: The Bank Account Number, Bank Name,
and Bank Transit Number are listed as required fields on the Manage Online Application Parameters
screen. These
values cannot be deselected.
Resolution: The
code has been modified to add values to the VendorOnlineApplicationParameters
table to
tie definitions to the three sub-tabs
of the Demographics
screen. The
required fields are configurable from the database. |
VRP-46 |
Vendor Online Price Survey |
Vendor Online Price Survey |
Issue: When the browser is not maximized,
all screens
in the Vendor Online Price Survey
application do not display correctly. The group boxes
display below the menu
instead of next to it.
Resolution: The
PriceSurvey.Master markup has a "sidebar1" DIV that
holds the navigation bar on the left and another "content"
DIV to hold the contents to be displayed to the right. The "content"
DIV wraps down below the "sidebar1" DIV when the browser
is resized. A table
was added around these two DIVs so they stay side-by-side on the
same table
row when the browser is resized.
Additionally, the width of the "content"
DIV was changed to prevent horizontal scroll bars displaying when
the browser is maximized. The scroll bars still display if the
browser is sized down small enough. |
VRP-47 |
Vendor Online Price Survey |
Web
Help |
Issue: When the Site Help
menu option
is selected,
the help file displays but the Contents, Search, and Glossary
are not functioning.
Resolution: The
web help was missing the whtdata0.xml and whtoc.xml files. The
files have been added. |
VRP-53 |
System Administration |
View System Access Log |
Issue: When the All
radio button
is selected
in the Users and Date group boxes
on the View System Access Log
screen and
the Apply Filter
button is clicked, a standard error message
displays with the text, "Invalid Input Format".
Resolution: The
issue was unable to be recreated, but an OutOfMemory Exception
was encountered when the All
radio button
is selected.
This is caused by the number of records returned exceeding the
computer's available memory. A new standard error message
has be added with the text, "The "All" option is
returning {number} records exceeding the computer's available
memory. Please purge the system access log and retry or provide
additional filter criteria." |
VRP-55 |
Reference Utility |
Reference Dictionary Entry |
Issue: The DFDD is not clear in regards
to the Value
text box on the
Reference Dictionary Entry
screen. The
maximum number of characters for the Value
text box is controlled
by the Null Value that is in the table
for each Reference Dictionary
item; it is not controlled by a business rule.
Resolution: The
code and the DFDD have been modified. The Value
text box now
defaults to a maximum of ten (10) characters if the ValueLength
column from the
database is null. Additionally, it still only allows numeric characters
if the ValueType is null.
The maximum length of the Description
text box was
unchanged.
The maximum length of the Sort Order
text box was
unchanged. Additionally, invalid input that is pasted from the
clipboard is no longer accepted.
The following items have been corrected to
fix the maximum value allowed by the database when values are
not defined:
SNAPACTION:
ValueLength = 9, ValueType = "A"
VNDCOMPBUYDONEBY:
ValueLength = 9, ValueType = "N"
VNDCOMPBUYFOODDISP:
ValueLength = 9, ValueType = "N"
VNDCOMPINVESTSTATUS:
ValueLength = 1, ValueType = "A"
VNDCORRECTIVEACTION:
ValueLength = 9, ValueType = "A"
VNDDOCUMENTTYPE:
ValueLength = 9, ValueType = "A"
VNDPHONETYPE:
ValueLength = 3, ValueType = "A"
VNDREFERTOOTHERORG:
ValueLength = 1, ValueType = "A"
VNDSURVEYREJECTRSN:
ValueLength = 9, ValueType = "A"
|
VRP-58 |
Vendor |
Generate High Cost Food Instruments Report |
Issue: When the OK
button is clicked on the
Generate High Cost Food Instruments Report
screen using
the default values for all fields, a standard error message
displays and the report is not generated.
Resolution: The
parameter value was missing from the report generation. The code
has been modified to add the parameter value. |
VRP-67 |
Vendor |
Initiate Compliance Investigation |
Issue: The Initiate Compliance Investigation
screen does
not check
the high risk indicators found during the high risk analysis.
Resolution: The
WIC.Windows.Common.EditableDataGridView data grid
was designed to enforce style consistency across all applications,
and as a result, it does not allow cells to have custom background
colors. The base class behavior was modified to allow custom background
colors.
Additionally, the system not checking the
check boxes was
caused by the system not returning the correct DialogResult code.
The code to return the correct value has been added. |
VRP-68 |
Vendor |
Documents |
Issue: Some scanned and uploaded documents
cannot be viewed on the Documents screen within the Vendor Folder when
the View Document
button is clicked.
Resolution: This
issue is caused by an undocumented difference in the System.Diagnostics.Process
object behavior between Windows
XP and Windows
7. This is a parameterless process wait blocking call that would
block as expected in Windows
XP but would return immediately in Windows
7, causing the temporary preview file to be deleted before the
preview process began.
The code has been modified to add a SPIRIT folder to
the Windows
temporary user's folder. This folder stores the previewed documents
for viewing on an on-demand basis. When the user logs out of the
SPIRIT
application, all files that can be deleted in the temporary SPIRIT folder are
deleted. If the file is locked by another process or is in use,
it is not deleted.
The blocking calls in the preview function
have been removed. |
VRP-69 |
Vendor Online Price Survey |
Create New Price List |
Issue: On the Create New Price List
screen, the
Max Price column
displays the price for the record that the price is divided into.
The Max Price column
should show the price based on the unit size. When calculating
the ounces for WIC Approved Cereal, the distribution item size
should allow for an item where the price is not calculated from
ounces.
Resolution: The
code has been modified to update the stored procedure to calculate
the Max Price to be displayed. The maximum price for the distribution
item for the Peer Group is multiplied by the Size amount for the
associated Retail Item. |
VRP-72 |
Vendor |
Upload Document |
Issue: The File Name
text box on the
Upload Document
screen does
not accept a back slash (\) or double quotes ("). When these
special characters are entered, a standard error message
displays with the text, "Illegal characters in path."
Resolution: The
issue occurs when the .NET function System.IO.Path.GetDirectoryName()
raises an ArgumentException when trying to parse a path string
that is not valid. The code has been modified to remove this error
on the Upload Document
screen and
the Image or Logo screen. |
VRP-77 |
Reference Utility |
Violation Classification |
Issue: On the Violation Classification
screen, the
In Days
text box does
not allow more than two (2) characters. If the disqualification
is for one year, the value of 365 cannot be entered.
The Subsequent Period In Months
masked edit box
only accepts two (2) characters. Additionally, zero (0) cannot
be entered as a valid entry for this masked edit box.
Resolution: The
code has been modified to set the In Days
text box maximum
number of characters to three (3) characters.
The Subsequent Period In Months
masked edit box
only accepts two (2) characters, but it now accepts zero (0) as
a valid entry. |
VRP-79 |
Management Console |
User Profile |
Issue: When another SPIRIT application is
running and the Management Console
application is opened to reset a password on the User Profile screen, a standard error message
displays with the text, "The request failed with HTTP status
401: Unauthorized."
Resolution: The
issue was the result of the reset password function attempting
to update the logged on user's credentials. The code has been
modified to only update the logged on user's credentials when
the reset password function resets the user's password. In all
other instances, the password is only updated in the production
database. |
VRP-80 |
Vendor |
Create New Template |
Issue: When creating a new template with
a signature on the Create New Template
screen and
Microsoft Office Word 2010 is installed, Word 2010 fails to launch
and display the template. If no signature is included, Word 2010
opens and displays the template.
Resolution: There
is a compatibility issue with Office 2007 and Office 2010. In
Office 2007, a copy/paste operation with the Office Runtime would
not cause a file lock, which is what occurs in Office 2010. The
code has been modified to add a SPIRIT
folder to the Windows
temporary user's folder. When the user logs out of the SPIRIT application,
all files that can be deleted in the temporary SPIRIT folder are
deleted. If the file is locked by another process or is in use,
it is not deleted. |
VRP-81 |
Clinic |
Certification Guided Script |
Issue: When using the Tab key or the down
arrow key on the Certification Guided Script
screen, the
EBT Household Demographics
link
is not selected
after the Demographics
link
but instead after the Issue Benefits
link.
Resolution: The
code has been modified to correct the tab order. |
VRP-82 |
Clinic |
Certification Guided Script |
Issue: On the Certification Guided Script
screen, the
check box for
the Height, Weight and Blood
link
does not become checked
when only height and weight are entered for an infant.
Resolution: The
code has been modified to mark the Height, Weight and Blood
link
as checked
for an infant whose age is less than the INFANTBLOODWORK
business rule when
height and weight information is entered. |
VRP-83 |
Vendor |
Manage Authorization Steps
and Authorization |
Issue: When a new Authorization Step
is added on the Manage Authorization Steps
screen and
it not marked as being active, the authorization step still displays
on the Authorization screen on the Event Log screen within the Vendor Folder.
Resolution: The
code has been modified to include six new database triggers. After
the modification, the system now functions differently. When an
applicant record is being created and the P number is assigned,
the system automatically captures all the active Authorization Steps
that exist at the time the applicant was added to the system.
Any new Authorization Steps
that are created later are not assigned to the applicant or vendor
record. When an Authorization Step
is activated
or deactivated,
it does not change the Authorization Steps
for an existing applicant or vendor. The Authorization Steps
now immediately display on the Authorization screen. If there are no
active Authorization Steps
when the applicant record is created, no Authorization Steps
are assigned.
The inactive Authorization Steps
displayed on the Authorization screen because the GetVendorCertificationSteps
stored procedure did not verify if an Authorization Step
was active or inactive. The code has been modified to verify the
status of the Authorization Step. |
VRP-87 |
Vendor |
Vendor Inventory Audit Report (Output) |
Issue: The DFDD does not specify if End of Day or End of Month Processing
must be run before the Vendor Inventory Audit Report (Output)
generates.
Resolution: The
Vendor Inventory Audit Report (Output)
requires that an Inventory Audit - First Visit
event or follow-up activity and an Inventory Audit - Second Visit
follow-up activity be recorded before the report can be generated. |
VRP-89 |
Vendor |
Authorization |
Issue: Authorization Steps
that have not been completed do not display on the Authorization screen on the Event Log screen within the Vendor Folder until
the Contract Issued
follow-up activity has been added.
Additionally, the Stamp Issuance
follow-up activity does not become checked
on the Authorization screen when it is completed.
Resolution: The
code has been modified to include six new database triggers. After
the modification, the system now functions differently. When an
applicant record is being created and the P number is assigned,
the system automatically captures all the active Authorization Steps
that exist at the time the applicant was added to the system.
Any new Authorization Steps
that are created later are not assigned to the applicant or vendor
record. When an Authorization Step
is activated
or deactivated,
it does not change the Authorization Steps
for an existing applicant or vendor. The Authorization Steps
now immediately display on the Authorization screen. If there are no
active Authorization Steps
when the applicant record is created, no Authorization Steps
are assigned.
The inactive Authorization Steps
displayed on the Authorization screen because the GetVendorCertificationSteps
stored procedure did not verify if an Authorization Step
was active or inactive. The code has been modified to verify the
status of the Authorization Step. |
VRP-90 |
Vendor |
Manage Retail Items |
Issue: When a retail item has already been
used, it cannot be deleted on the Manage Retail Items
screen. However,
the user can change the associated distribution item and retail
item description.
On the Manage Retail Items
screen, there
is no functionality to deactivate
retail items.
Resolution: The
Manage Retail Items
screen has
been updated to include a new Active column
with a check box
to allow the user to activate
or deactivate
the record.
Additionally, any distribution IDs that are
currently in use by the system cannot be fully edited. The Distribution Item
drop-down list box
is disabled if the record is in use by the system.
The SQL script used to gather the active
items for a price list was updated to include only active retail
items rather than retrieving all retail items. |
VRP-91 |
Vendor |
Zone |
Issue: There is a typo in a standard error message
on the Zone screen.
The word "exist" should be "exists".
Resolution: The
code has been changed so the standard error message
displays the text, "The Zone name already exists. Please
enter a different value." |
VRP-92 |
Vendor |
Manage Authorization Steps
and Authorization |
Issue: When a new Authorization Step
is added on the Manage Authorization Steps
screen and
it is marked as being active, the Authorization Step
displays on the Authorization screen on the Event Log screen within the Vendor Folder for
all vendors. Vendors that are authorized and have completed the
Authorization Steps
now have incomplete steps because the newly added Authorization Steps
were not completed. This could cause confusion for authorized
vendors regarding why they were allowed to skip authorization
steps.
Resolution: The
code has been modified to include six new database triggers. After
the modification, the system now functions differently. When an
applicant record is being created and the P number is assigned,
the system automatically captures all the active Authorization Steps
that exist at the time the applicant was added to the system.
Any new Authorization Steps
that are created later are not assigned to the applicant or vendor
record. When an Authorization Step
is activated
or deactivated,
it does not change the Authorization Steps
for an existing applicant or vendor. The Authorization Steps
now immediately display on the Authorization screen. If there are no
active Authorization Steps
when the applicant record is created, no Authorization Steps
are assigned.
The inactive Authorization Steps
displayed on the Authorization screen because the GetVendorCertificationSteps
stored procedure did not verify if an Authorization Step
was active or inactive. The code has been modified to verify the
status of the Authorization Step. |
VRP-93 |
Vendor Online Application |
Calendar
Controls |
Issue: When focus is placed in a calendar control and the
Enter key is pressed, the control expands displaying a one-month
calendar.
Resolution: The
calendar control's
launch image button
was being treated by the browser as the default button for the screen. The code has been
modified to add a defaultButton attribute to the "form"
tag in the master page which points to a hidden button that does nothing. This
prevents the calendar controls
from responding to the Enter key. |
VRP-94 |
Vendor |
Civil Money Penalty
and Fine |
Issue: When adding a Civil Money Penalty
event on the Civil Money Penalty
screen, entering
the maximum penalty amount causes the system to display a standard error message
with the text, "The Penalty Assessed must be less than or
equal to the Maximum Penalty". Reducing the amount to a round
number (for example, $4,100) allows the screen
to be processed.
Additionally, after adding the Civil Money Penalty
event, if a Fine
follow-up activity is added, a standard error message
displays with the text, "All violations have been assessed."
Resolution: The
issue is caused by the system rounding the penny amount to the
nearest whole dollar. The code has been modified to keep the maximum
amount intact allowing pennies so that the comparison with the
Penalty Assessed amount is accurate to the penny without rounding.
The standard error message
received after adding a Civil Money Penalty
event then a Fine
follow-up activity is correct. The system is working as designed. |
VRP-96 |
Vendor |
Onsite Letter, The Integrity Profile (TIP) File (Output),
and Vendor Violation Report (Output) |
Issue: When an Onsite Warning Letter
or Disqualification Notification Letter - Final Notice
is expected to print, the Onsite Letter
prints instead.
Additionally, The Integrity Profile (TIP) File (Output)
does not contain the accumulated sanction points or the sanction
point expiration dates.
The Vendor Violation Report (Output)
contains the sanction points but does not report the accumulated
sanction points or the sanction point expiration dates.
There is no vendor event called Federal Sanction.
Resolution: The
issue of the Onsite Letter
printing could not be recreated.
The lack of the accumulated sanction points
or the sanction point expiration dates on The Integrity Profile (TIP) File (Output)
is because the change order does not provide any details about
them, and the USDA specification does not provide for such columns on the output.
A separate Federal Sanction event does not
exist. A federal sanction is added on the Sanction screen. |
VRP-97 |
Vendor |
Compliance Buy Returned |
Issue: The Edit
button on the
All
screen on
the Event Log screen within the Vendor Folder is
disabled for a Compliance Buy Returned
follow-up activity. This occurs even though a Finish Compliance Investigation
follow-up activity has not been added to the tree list.
Resolution: The
code has been modified to enable the Edit
button when a
Compliance Buy Returned
follow-up activity is selected.
When a Finish Compliance Investigation
follow-up activity has been added, the Edit
button is disabled. |
VRP-98 |
Vendor |
Finish Compliance Investigation |
Issue: When an Initiate Compliance Investigation
event is added on the All screen
on the Event Log screen within the Vendor Folder, a
Finish Compliance Investigation
follow-up activity can be added. The Close Investigation
button on the
Finish Compliance Investigation
screen is
clicked,
and there is no standard error message
alerting the user that the criteria for a Finish Compliance Investigation
follow-up activity have been met.
Resolution: The
code has been updated to add validation to the Finish Compliance Investigation
screen and
to display a standard confirmation message
with the text, "Criteria to log a Finish Compliance Investigation
have not been recorded. Do you want to continue?" |
VRP-99 |
Vendor |
Compliance Buy Meeting Letter |
Issue: The mail merge field for the number
of checks is not pulling the correct information for the number
of checks on the Compliance Buy Meeting Letter.
Resolution: This
is caused by the GetMailMergeFieldsValues method incorrectly assigning
the total number of violations to the number of checks variable.
The code has been modified so the GetMailMergeFieldsValues method
assigns the number of checks. |
VRP-100 |
Vendor |
The Integrity Profile (TIP) File (Output) |
Issue: On The Integrity Profile (TIP) File (Output),
the values for "Compliance Investigations" and "#
of Compliance Buys" are not displaying the correct values.
Resolution: The
Number of Compliance Buys column
has been updated to also count the number of Compliance Buy Returned
follow-up activities along with the benefits associated with the
Compliance Buy Returned.
Dropped Compliance Investigations cannot be counted. |
VRP-101 |
Vendor |
Send Form Letters
and Exception Details |
Issue: When sending a custom letter on the
Send Form Letters
screen, an
exception is encountered on the Exception Details
screen. The
Reference Message
value label displays
the text, "FaxDocument must have either cover page or body."
Resolution: There
is a compatibility issue with Office 2010 that is causing copies
of the generated templates to be deleted before the templates
could be converted from PDF to TIFF file format. The code has
been modified to upgrade SPIRIT
to use Office 2010 interops instead of Office 2007 interops.
The mail merge engine has been modified to
generate temporary files in the user's temporary SPIRIT folder. Occasionally,
a call to retrieve a temporary file name would return a path that
was not expected. When the user has insufficient permissions,
this caused the engine to fail unexpectedly.
The code has modified to never expect a cover
page from the user's hard drive. The cover page is included as
part of the content of the custom template file. |
VRP-102 |
Vendor Online Application |
Business Information |
Issue: When a new Authorized Agent Information
tab is added on
the Business Information
screen, there
is no way in the Vendor Online Application
to delete the tab.
Resolution: The
code has been modified to add a new Remove
button to the
Business Information
screen to
delete an Authorized Agent Information
tab. |
VRP-103 |
Vendor |
Scan Document |
Issue: On the Scan Document screen, if a scanner is
being used that has an automatic document feeder, the Scan from
Tray radio button
is disabled. If the system encounters a problem scanning from
the automatic document feeder, the system cannot recover from
the error and must be terminated.
Resolution: The
SPIRIT
application uses a standardized algorithm from AtlasSoft for the
detection of a scan tray or an automatic document feeder. If an
imaging device's drivers are not fully twain compliant, then detection
of the scan tray and/or automatic document feeder may not be possible.
It is possible for an imaging device to have only a scan tray,
only an automatic document feeder, or both a scan tray and an
automatic document feeder. When the imaging device's driver informs
the SPIRIT
application that the imaging device does not have a scan tray,
the Scan from Tray radio button
is disabled.
According to AtlasSoft, the software vendor
for the EZTwain scanning library used by the SPIRIT
application to communicate with imaging devices, low-level twain
calls sometimes dead-lock due to faulty imaging devices or bugs
in the actual device driver code. To correct this issue, EZTwain
calls will be hosted in completely separate application processes
than the SPIRIT
application. This reduces the risk of a dead-lock.
Every EZTwain call is now given a time-out
of seven (7) seconds to complete since most device driver calls
have an upper bound of approximately two (2) seconds to complete.
If the call does not return after seven (7) seconds, the device
is assumed to be dead-locked.
EZTwain calls that scan a single page are
given a larger time-out to complete. If the device does not return
any messages for sixty (60) seconds during an Acquire operation,
the devices is assumed to be dead-locked.
If a dead-lock is detected, the scan is aborted
and the system displays a standard error message
with the text, "The imaging device failed. Power it off and
back on before attempting the scan again. If the problem persists,
please contact the Help Desk." |
VRP-105 |
Vendor |
Complaint |
Issue: When adding a complaint on the Complaint
screen, a
foreign key error occurs and a complaint cannot be recorded.
Resolution: When
a complaint is created, the user ID is stored in the FollowupUserID
column of the
Complaint table.
The column allows
a maximum of twenty (20) characters, but the mapping class had
this property set to ten (10) characters. If the user ID is greater
than ten (10) characters, the mapping class code fails. The code
has been updated to allow for twenty (20) characters. |
VRP-106 |
Vendor |
Vendor Violation Report Spreadsheet (Output) |
Issue: The Vendor Violation Report Spreadsheet (Output)
has the Address column
displaying the Vendor Name column
information.
Resolution: The
code has been modified to remove a line of code that was overwriting
the column name
with the label "Address". The Vendor Violation Report Spreadsheet (Output)
now correctly displays the column
name as "Vendor Name". |
VRP-107 |
Vendor |
Generate Vendor Violation Report |
Issue: On the Generate Vendor Violation Report
screen, when
any option other than "Vendor" is selected
in the Criterion
drop-down list box
and the user selects
either the Terminated
or All
radio button,
an unhandled exception error occurs.
Resolution: The
issue was caused by the code assuming the Criterion
drop-down list box
was always set to "Vendor" when one of the three radio buttons was selected. The
code has been modified to verify that the Criterion
drop-down list box
has a value of "Vendor" before calling the process that
filters the list box
when the associated radio button
is selected.
When the Criterion
drop-down list box
contains a value other than "Vendor", selecting one
of the radio buttons
does nothing to the list box,
but it is still used when generating the report. |
VRP-108 |
Vendor |
Initiate Compliance Investigation |
Issue: The check boxes
on the Initiate Compliance Investigation
screen are
not pre-populated when the high risk analysis has been run on
the High Risk Analysis
screen through
the Vendor List screen.
Resolution: The
WIC.Windows.Common.EditableDataGridView data grid
was designed to enforce style consistency across all applications,
and as a result, it does not allow cells to have custom background
colors. The base class behavior was modified to allow custom background
colors.
Additionally, the system not checking the
check boxes was
caused by the system not returning the correct DialogResult code.
The code to return the correct value has been added. |
VRP-109 |
Vendor |
Authorization |
Issue: The Stamp Issuance
follow-up activity does not become checked
on the Authorization screen when it is completed.
Resolution: The
code has been modified to include six new database triggers. After
the modification, the system now functions differently. When an
applicant record is being created and the P number is assigned,
the system automatically captures all the active Authorization Steps
that exist at the time the applicant was added to the system.
Any new Authorization Steps
that are created later are not assigned to the applicant or vendor
record. When an Authorization Step
is activated
or deactivated,
it does not change the Authorization Steps
for an existing applicant or vendor. The Authorization Steps
now immediately display on the Authorization screen. If there are no
active Authorization Steps
when the applicant record is created, no Authorization Steps
are assigned.
The inactive Authorization Steps
displayed on the Authorization screen because the GetVendorCertificationSteps
stored procedure did not verify if an Authorization Step
was active or inactive. The code has been modified to verify the
status of the Authorization Step. |
VRP-110 |
Vendor |
Monitoring Visit |
Issue: On the Monitoring Visit
screen, the
Comments Below column's
width was not decreased as per the original change order. Additionally,
the Areas for Monitoring/Training column's
width was to increase, but it remained the same size.
Resolution: The
columns have
been properly adjusted to accommodate the width. |
VRP-111 |
Vendor |
View
Scanned Documents and Scan Document |
Issue: In Windows
7, scanned images are grainy. If best scan quality is selected on
the Scan Document screen, the image size is
too large and cannot be uploaded.
Resolution: The
code has been modified to improve image quality and size. The
images being grainy in either grayscale or truecolor were due
to the gray images using a 4-bit channel per color and truecolor
images using a 5-bit channel per color. These channels were originally
used to keep image sizes as small as possible, but the image quality
was not as clear.
The file size of the image is addressed by
using TIFF LZW and JPEG Compression based on the following:
Large Font
Scans - These are changed to Black and White, 100 DPI, LZW
Compressed.
Small Font
Scans - These are changed to Black and White, 200 DPI, LZW
Compressed.
Handwritten
Scans - These are changed to Black and White, 200 DPI, LZW
Compressed.
Grayscale
Scans - These are changed to Grayscale, 150 DPI, 80% Quality
JPEG Compressed.
Color Scans
- These are changed to Color, 150 DPI, 80% Quality JPEG Compressed.
The VND_MAX_COMPRESSED_UPLOAD_IMAGE_SIZE
business rule has
been removed. Now file uploads to the database will use the maximum
request length configured for the web server that hosts the SPIRIT web services.
This value specifies the maximum amount of data that can be submitted
during a single web service call.
If a file being scanned in too large, a standard error message
displays with the text, "The file being scanned exceeds the
web server limit of {max_upload_size} bytes. The scan was cancelled.
Please contact the Help Desk."
If a file being uploaded is too large, a
standard error message
displays with the text, "The file being uploaded exceeds
the web server limit of {max_upload_size} bytes. The scan was
cancelled. Please contact the Help Desk."
When uploading a document in the Vendor application,
zip files and Microsoft Office files that save as a compressed
zip file are uploaded without being compressed. All other files
are compressed using zip compression. |
VRP-112 |
Vendor |
High Risk Criteria |
Issue: On the High Risk Criteria
screen, if
no value is entered in the Value column,
the system does not display a standard error message.
Instead, when the screen
is processed the blank values in the Value column
are changed to zero (0).
Resolution: The
code has been modified to add validation to ensure the Value column cannot be left blank. |
VRP-113 |
Vendor |
Manage Closing Trigger for Events |
Issue: On the Manage Closing Trigger for Events
screen, pressing
the Enter key while focus is on a single cell in a non-editable
column causes
the system to display a standard error message
with the text, "DataTable already belongs to this DataSet."
When the standard error message
is dismissed, the screen
closes.
Resolution: The
code has two instances of the Enter key press processing the data
on the screen.
This resulted in the data being saved twice, which resulted in
the standard error message.
The code has been modified to remove the code calling for the
second save when the Enter key is pressed. |
VRP-114 |
Vendor |
The Integrity Profile (TIP) File (Output) |
Issue: The DFDD does not correctly reflect
the origin of data for Compliance Information or Investigations
Conducted by Table Other than the State in The Integrity Profile (TIP) File (Output).
Additionally, the DFDD documents the display as "Investigations
Conducted by Table Other than the State"; however, the report
output displays "Investigations by other Entities".
Resolution: The
DFDD has been updated to correctly reflect the origin of values
for the Compliance Investigations, Investigations by Other Entities,
Number of Compliance Buys, and Number of Inventory Audits.
The Investigations Conducted by Table Other
than the State column
has been renamed Investigations by Other Entities. |
VRP-115 |
Vendor |
Compliance Buy Returned |
Issue: On the Compliance Buy Returned
screen, the
DFDD states that the Internal drop-down list box
is populated from the Reference Dictionary
table where
category="VNDCOMPBUYDONEBY".
Resolution: The
Internal drop-down list box
is populated from the ComplianceBuyInvestigator table. The DFDD has been
updated to correctly document this. |
VRP-117 |
Vendor |
Letter Sent and Send Letter |
Issue: When adding a Letter Sent
event or follow-up activity, if the Letter Sent Outside System
check box is
checked,
the system requires the user to select
a contact recipient and address on the Send Letter screen.
Resolution: The
code has been modified so that when the user does not check the Print Address Label(s)
check box, then
no check boxes
are required in the Recipient(s)
and Address(es)
group boxes.
If the user checks
the Print Address Label(s)
check box, then
at least one check box
must be checked
in the Recipient(s)
and Address(es)
group boxes.
This prints the mailing labels for the recipient. |
VRP-118 |
Vendor |
All |
Issue: The All screen
topic of the DFDD incorrectly states that the Letter Sent
follow-up activity has a details screen
Resolution: The
Letter Sent
follow-up activity does not have a details screen.
The DFDD has been updated to correctly document this. |
VRP-120 |
Vendor |
The Integrity Profile (TIP) File (Output) |
Issue: The Risk Designation column of The Integrity Profile (TIP) File (Output)
is being populated based on determination methods used for the
old version of the High Risk Report VND009 (Output)
and the method of determining high risk vendors. If the Indicator
columns are populating
as a result of compliance investigation results, which are based
on the new version of the High Risk Report VND009 (Output),
then the Risk Designation column
should also reflect that change. The vendors that are high risk
in the analysis are not marked as high risk in the VendorHighRisk
table.
Resolution: The
High Risk Analysis
screen has
been modified to include a new Save Analysis Results button. This button
allows the user to save the current high risk analysis for use
in the TIP report.
The Generate TIP File - Step 1
screen has
been modified to include a new High Risk Method radio button group that allows
The Integrity Profile (TIP) File (Output)
to be generated based on month-end reporting or on the high risk
analysis results saved on the High Risk Analysis
screen.
Currently there is no mechanism for retrieving
or reviewing analysis results. That functionality is to be added
in a future release. |
VRP-121 |
Clinic |
Infant Information
and Child Health Information |
Issue: On the Infant Information
screen and
Child Health Information
screen, the
Breastfeeding Now
check box is
becoming unchecked.
Resolution: There
is not a way to uncheck
the Breastfeeding Now
check box and
keep the Amount of Breastfeeding set to Fully Breastfeeding or
any amount besides Not Applicable. This issue may have been caused
by an older issue on those screens
that has been fixed.
An update to the SQL script has been added
to fix existing infant and children with this data issue. The
update sets the Breastfeeding Now
check box to
be checked
if the Date Breastfeeding Began
calendar control
is populated, the Date Breastfeeding Ended
calendar control
is not populated, and the Amount of Breastfeeding is not set to
Not Applicable. |
VRP-122 |
Reference Utility |
Corporate Parent |
Issue: When adding a new corporate parent
on the Corporate Parent
screen, data
cannot be entered in the Corporate Contacts, Addresses, or Corporate
Owners group boxes.
The screen
saves all the other information entered.
Resolution: The
code has been modified so both Add
buttons and Edit
buttons are enabled
on the Corporate Parent
screen when
displayed in Add mode.
Each button now
verifies the corporate parent validation before executing the
code behind the buttons.
If the required fields are not populated, the system displays
the standard error messages.
The corporate parent can be saved if the required controls have
values, and the addresses, contacts, and owners can be added later. |
VRP-124 |
Clinic |
Infant Information |
Issue: When the calendar controls
on the Infant Information
screen are
blank and the OK
button is clicked, an orange
halo displays around the control. When the control is selected and
the one-month calendar displays, the halo remains on top of the
one-month calendar.
Resolution: The
code has been modified to use the common control. The halo no
longer displays on top of the one-month calendar when the calendar control down arrow
is clicked. |
VRP-127 |
Vendor |
The Integrity Profile (TIP) File (Output) |
Issue: The Integrity Profile (TIP) File (Output)
does not correctly report the number of inventory audits for a
vendor. For example, a vendor with two inventory audits was reported
on The Integrity Profile (TIP) File (Output)
as having one inventory audit.
Resolution: The
code has been modified to correct the database SQL that is adding
the events and follow-up activities. |
VRP-128 |
Vendor |
The Integrity Profile (TIP) File (Output) |
Issue: The Integrity Profile (TIP) File (Output)
marks the Type of Sanction S column
when a federal sanction is recorded for a vendor. According to
the DFDD, the Type of Sanction S column
indicates when a state sanction has been recorded for a vendor.
Resolution: The
code has been modified to change the way the Type of Sanction
S column is populated.
If a sanction is marked as "Federal", it is not counted
for the Type of Sanction S column.
Any other sanctions within the date range are counted. |
VRP-129 |
Vendor |
The Integrity Profile (TIP) File (Output) |
Issue: The Integrity Profile (TIP) File (Output)
does not correctly report terminated vendors. When a vendor has
a status of Disqualified and the Terminate Stamp
follow-up activity logged, The Integrity Profile (TIP) File (Output)
may report the vendor with an "E" or a "T".
Resolution: The
code has been modified to ignore Disqualification Reason codes
and Termination Reason Codes. If the Termination Reason is 4 (Contract
Expired) or 6 (Not Renewed) then the Vendor Agreement is set to
"E". Otherwise, any other Termination Reason code value
is set to "T". |
VRP-130 |
Vendor |
The Integrity Profile (TIP) File (Output) |
Issue: The Integrity Profile (TIP) File (Output)
is not populating the Reason for Sanction T, A, I, O, R, F, C,
U, and FSP columns.
Resolution: There
were no changes for this issue. It is functioning as designed. |
VRP-134 |
Clinic |
Height/Weight |
Issue: When the Unknown Ht/Wt
button is clicked on the
Height/Weight screen, a standard confirmation message
displays. When Yes
is selected,
an object reference error displays. If the Height/Weight screen is displayed again
after receiving the object reference error, the object reference
error displays immediately.
Resolution: The
object reference error was displaying due to a duplication of
the participant object copy. The code has been modified to not
copy the duplicated object. |
VRP-136 |
Vendor |
Assessment Options |
Issue: On the Assessment Options
screen, the
Number of Cash Registers Min Range
and Number of Cash Registers Max Range
masked edit boxes
and the Square Footage Min Range
and Square Footage Max Range
masked edit boxes
are not displaying a comma for values above 999.
Resolution: The
code has been modified to add the comma to values above 999. The
system now correctly displays values of one thousand or greater
as "###,###,###". |
VRP-138 |
Vendor |
Vendor List |
Issue: On the Vendor List screen, the leading zeros
for ZIP codes are not displaying for vendors.
Resolution: The
ZIP code columns
in the data grid
were not being formatted correctly. The code has been modified
to add the leading zeros. |
VRP-139 |
Clinic |
Appointments |
Issue: When the Print Appointment Notice
button is clicked on the
Appointments screen, the system displays
a standard error message
with the text, "Index was out of range. Must be non-negative
and less than the size of the collection. Parameter name: index".
Resolution: The
internal search function was modified in the past and it required
AgencyID. Other screens
of the application were correctly modified to include the additional
information in the search function. The Appointments screen was not modified
during this change. The code has been modified to correctly use
the AgencyID requirement for the search. This prevents the standard error message
from displaying. |
VRP-141 |
Reference Utility |
UPC List and data grid |
Issue: When a record is deleted on the UPC List screen, the user is not
returned to the same location in the data grid;
instead, the first record is highlighted and the user is returned
to the top of the data grid.
When a new record is added on the UPC screen,
all the required fields are entered and, when the screen is processed, an
object reference error displays.
Resolution: The
system contains code that, when a record has been deleted, the
system would perform the search again if the search values were
present in the search fields or the code would refresh the data grid and set the selected row
to the first row if no search values were present. The code has
been modified so the system selects
the row below the deleted row, if one exists, or it selects the
row above the deleted row if it is the last row in the data grid.
Additionally, the system was trying to use
the value for the Calculation Method
drop-down list box
which is only available to clinics
set up for EBT. The code has been modified to ignore the Calculation Method
drop-down list box
for non-EBT clinics. |
VRP-142 |
Appendix |
Custom Template Merge Fields |
Issue: There are mail merge fields missing
from the Custom Template Merge Fields
topic.
Resolution: The
following changes were made to the DFDD for Custom Template Merge Fields:
The <<Title>>
field has been removed.
The <<OwnerTitleOwnerSalutation>>
field has been removed.
The <<PhysicalCountyCd>>
field has been changed to <<VendorPhysicalAddressCountyCd>>.
The <<PhysicalCountyName>>
field has been changed to <<VendorPhysicalAddressCountyName>>.
The <<CorporateParentTelephone>>
field has been changed to <<CorporateParentPhone>>.
The <<StampBankDeactivatedEffectiveDate>>
field has been changed to <<StampBankDeactivationDate>>.
The following mail merge fields have been
added to the DFDD:
<<VendorFormulaWholesalerId>>
<<VendorFormulaWholesalerName>>
<<VendorGrocerySupplierId>>
<<VendorGrocerySupplierName>>
<<VendorMilkWholesalerId>>
<<VendorMilkWholesalerName>>
<<VendorPharmacyWholesalerId>>
<<VendorPharmacyWholesalerName>>
<<VendorPhysicalAddressCountyCd>>
<<VendorPhysicalAddressCountyName>>
<<VendorAuthorizedAgentTitle>>
<<VendorWicContactTitle>>
<<StampReasonDeactivatedDescription>>
|
VRP-143 |
Vendor |
Manage Authorization Steps |
Issue: When a cell has focus in the Active
column of the
Manage Authorization Steps
screen, the
check box cannot
be checked
or unchecked
by pressing the space bar on the keyboard.
Resolution: The
code to enable the space bar functionality was missing. It has
been added, and now the space bar functions correctly for the
Active column. |