CDP, Inc. CDP, Inc. WIC Direct WIC Direct The EBT Solution The EBT Solution
Home 
For WIC Agencies
       System Documentation
       Release Notes
          WIC Direct System
       Screen Shot Gallery
For Retailers
       System Integration Documents 
       Retailer Cash Register (POS) System Questionnaire
       Solution Integration and Certification Status
       Release Notes
          Stand Beside POS
       Frequently Asked Questions
For Participants
       WIC Direct in Kentucky
Contact
       Contact Our Team
       Employment
  Search
Saturday, May 25, 2013 ..:: For WIC Agencies » Release Notes » WIC Direct System ::.. Register  Login
Minimize  2.2.0.7 User Stories
  • Story 469: This story added a logging capability to the ActiveX control that WDS uses to communicate with a connected PIN pad. While the ActiveX control is no longer used due to the new Core Interop code, it is important to note that the logging features were carried over from the ActiveX control to Core Interop.
  • Story 458: An ACH effective date field was added to the database to make the state’s month-end reconciliation work easier than it had in the past. Storing the effective date of the ACH allows the state’s reconciliation process to use that date in its calculations.
  • Story 657: This was a feature requested by the state. State vendor support wanted the ability to submit a “manual” purchase through the Web interface so that they may support a participant who is having PIN issues when redeeming benfits at a retail location.
  • Story 457: This story gave the user the ability to download and install the ActiveX control directly from their WDS screen. Similar to story 469, it is important to note that, while the ActiveX control is no longer part of the system, this ability was carried over into the new Core Interop code.
  • Story 659: For this story, the development team was asked enhance WIC Direct software so that transactions originating from a third-party processor, whose role is a gateway non-master of settlement, could be processed.
  • Story 775: WDS needed the ability to drive key exchanges and the work from this story enabled the system to do that.
  • Story 828: This story built off the work performed in story 659 and added a report to show reconciliation/settlement information for third-party processors in a given activity period.
  • Story 827: Various stakeholders requested that the APL be accessible to users through a central folder. This allows an institution to pick up an APL from one location and distribute that file to its connected stores so the stores will not have to pick the file up individually.
  • Story 851: Project stakeholders requested the ability to filter the retail sales and retail activity reports by contracting agency. This story added the code necessary to make that happen.
  • Story 955: This story locked down the GetInstitutionKeys web service call. That web service is used to retrieve an institution’s key exchange key. This story requested that the method be locked down so only the WIC Direct system can call it.
  • Story 962: This story directed the development team to remove the benefit reconciliation top-level menus from the WIC Direct Web interface in order to improve the navigation of the system.
  • Story 979: Previously, the creation of an FTP account for a merchant or institution involved manual intervention from the Network Operations staff. This story allows the system to create the FTP account along with all required permissions.
  • Story 1004: This story built on the work in story 827. It added a configuration flag to the merchant record that determined whether or not an APL would be written and copied to that individual merchant’s account on the FTP server. This setting helps to reduce the number of unnecessary files that are stored on the FTP server.
  • Story 456: This story covered all the work needed to allow connected PIN pads to connect to WDS via Core Interop rather than an ActiveX control. The implementation of this story addresses many requests from field staff regarding the PIN pad communication with WIC Direct screens.
  • Story 967: This story involved the creation of a programmatic process to clean files off the WDS FTP server in order to maintain the server performance and keep file lists manageable for connected clients.
  
Minimize  2.2.0.7 Issues / Enhancements
  • Issue 1307 (Story 658): Basically, the file creation process was pre-pending a number to files it was creating if it believed that file’s name was a duplicate of a pre-existing file. This was causing some FTP scripts to fail, so the duplicate naming process was re-factored to create files with easily consumable names.
  • Issue 1057 (Story 1057): An error was displayed to the user in the situation where a numeric value longer than three digits and less than seven digits was entered when adjusting benefits.
  • Issue 1126: This was an Active X issue and ActiveX control is no longer part of the system.
  • Issue 1128: This issue addressed the incorrect message text from the Out of Balance Report when no out of balance accounts exist.
  • Issue 1204: The issue occurred when the number of file creation events was greater than the file watcher was capable of keeping in memory.
  • Issue 1179: An Expungement Failed alert was received for household accounts with multiple benefit periods.
  • Issue 1222: The expunged transactions would not return any details. Instead, a message was displayed indicating no benefits issuance details were found for the particular transaction.
  • Issue 1250: This issue was investigated and addressed as a possible SQL injection problem if outside party was calling our web services. 
  • Issue 1280: An unknown error was thrown when viewing transactions or messages. 
  • Issue 1281: The issue was that no reports could be accessed,, only a blank page was displayed to the user.
  • Issue 1282: When the Files menu button was selected, there was no response.  The user was redirected to the main page.
  • Issue 1240: This issue addressed the misspelling of “Requirements” on the change password screen.
  • Issue 1288: An unknown error message was displayed when the user attempted to export an account record that had no current benefits.
  • Issue 1289: When a user attempted to generate a Prenote file with no criteria specified, an unknown error was displayed.
  • Issue 1290: This issue addressed problems associated with adding or adjusting benefits with overlapping date ranges.
  • Issue 1293: This issue addressed benefit adjustment transactions that had no details in account history and only displayed a message stating no benefit issuance details were found for the transaction.
  • Issue 1292: This issue addressed the misspelling of Redemption on the monthly redemption issuance report.
  • Issue 1285: This issue addressed an error code that was produced upon the failure of the NTE job.
  • Issue 1327: This issue addressed the retail settlement process failing on QA and generating failure alerts.
  • Issue 1454: This issue addressed the redemption by issue month report omitting voids and reversals, as well as transactions with the same amount paid being counted as one transaction.
  • Issue 1344: This issue addressed a system malfunction error that was being logged during the expungement job.
  • Issue 1365: This issue addressed the intermittent “access denied” alerts during the ARF processing on the QA server.
  • Issue 1284: This issue addressed PIN pads which would not work with specific versions of the Web application.
  • Issue 1526: This issue addressed the situation in which a cardholder is issued a replacement card that is marked active, but the PIN is still locked.  Also, the card is unable to be unlocked because the controls are locked.
  • Issue 1618: This issue addressed the lack of data in the Gateway Auto-Recon report from 02/07/2010.
  • Issue 1702 (Story 918): This issue addresses QA’s need to validate change requests through documents that describe key exchange, testing, and validation.
  • Issue 1706 (Story 915): This issue addressed two fields from the ACH History screen that had the same name.
  • Issue 1686 (Story 922): This issue addressed Out of Balance reports only reporting for one of the household accounts instead of all household accounts.
  • Issue 1131 (Story 802): This issue addressed ACH files that were dropped into the wrong FTP folder and the remainder of the files not being archived.
  • Issue 1622 (Story 822): This issue addressed Retail Sales reports showing a transaction month of November when the report was run for October.
  • Issue 1473 (Story 834): This issue addressed security on the system that caused a user to not be able to access transaction detail.
  • Issue 1831 (Story 980): This issue addressed an unknown error message that was displayed when accessing the Reconciliation/Auto Recon screens.
  • Issue 1300 (Story 414): This issue addressed the Expungment Transactions logging overlapping benefits errors.
  • Issue 1687 (Story 925): This issue addressed an unknown error being thrown when adding a cardholder to a household.
  • Issue 1724 (Story 951): This issue addressed problems with the clinic search on the transaction history screen and clinic numbers not being logged on clinic transactions.
  • Issue 1586 (Story 974): This issue addressed a key sync error that occurred during a manual purchase transaction.
  • Issue 1941: This issue addressed 5/3 key change requests that returned a 909 error code.
  • Issue 1956: This issue addressed a password malfunction in which a user could log in using any password.
  • Issue 1954: This issue addressed 5/3 key change request that returned a 919 error code.
  • Issue 1936: This issue addressed no ACH payment generated along with an application alert that indicated the failure of the get ACH for merchant function.
  • Issue 1832: This issue addressed an NTE failure that produced a 909 and divide by zero error.
  • Issue 1837: This issue addressed the 5/3 key change request that was being approved with a Bit 96 even though the institution was not master of keys.
  • Issue 1780: This issue addressed ACH files having “0.00” detail record for a voided transaction.
  • Issue 2049: This issue addressed the transaction queue for FIS becoming out of synch.
  • Issue 2100: This issue addressed voided CVB UPC item amounts not matching the original purchase amounts on the retail history transaction screen.
  • Issue 2096: This issue addressed existing CVB transaction records that did not update after upgrade.
  
Copyright ©2008 - 2010 CDP, Inc   Terms Of Use  Privacy Statement