Recent changes to feature-requests

Build the Send Transmitter client for the SST Gateway

Shawn Kasulka — Fri, 05 Feb 2010 16:46:35 -0000

Create a standalone Java application to get SST Transmitters and send to to the SST Gateway Server.

Gateway Services Client GUI client for SST

Shawn Kasulka — Thu, 04 Feb 2010 18:24:29 -0000

Build the Gateway Services Client GUI for SST.
Part of the uber Gateway project had a GUI client, that has not made its way to be refactored into it a standalone project. It looks like it uses the following sub projects:
xmlbeans_maven_pom
base_client
base_client_gui
mef_base
base_utils
sstp_base
sql_base_vt
sstp_server

I would want to have the new project specialized for SST (get rid of the Code1, GatewayAV and MeF functions). Also need to update to SST Schema 2010V01.

Support Version 2010V01 Schema

Shawn Kasulka — Wed, 03 Feb 2010 18:25:09 -0000

Update the web services on the Gateway to match the version 2010V01 due to be deployed in May 2010. Highlights are:
* A restructured the whole SST schema to mimic MeF schema.
* Allow the enumeration for ‘not registered for sales tax in your state and does not expect to have sales into your state’ in the RegNewSchema.
* Changes to SERSchema changes for ExemptionsDeductions Breakouts.

The new SST2010V01 schema set can be found on the www.statemef.com website.

This will be part of the 5.0 version.

SSTP Client Database Connection Test

Thomas Cort — Fri, 31 Oct 2008 12:30:26 -0000

The client should test all database connections before performing any web service calls.

SST2009V01 Changes

Thomas Cort — Thu, 25 Sep 2008 19:20:32 -0000

A new streamlined sales tax schema has been published. Target implementation date is: January 1, 2009. We don't have to edit the XSLTs because we aren't accepting any returns with the new fields and none of the existing XPaths have changed.

Changes are:

Schema version is 2009V01. We just need to drop in the new schema files for this.

SSTPID is now a choice between SSTPID and StateID. A Vermont specific validation rule should be added to produce an error when a StateID is used since we don't accept them. Review the general non-state specific rules to see if any of them are impacted.

StateTaxDueFoodDrug was added. A Vermont specific validation rule should be added to produce an error when this element is used and the value is not $0. In the general rules, we need include this in the sum we compare against the total.

Configurable SQL*Plus Command

Thomas Cort — Fri, 29 Aug 2008 12:37:12 -0000

The path to SQL*Plus is hard coded into the client application. Currently it points to /usr/oracle/9i/bin/sqlplus; in the future that will change. Change the client so that the location of SQL*Plus is configurable. Once the configuration option is added, the file to edit is...

gateway-client/src/main/java/net/sf/gateway/client/base/sql/SQLClientBase.java

Test Deck Generator

Thomas Cort — Mon, 18 Aug 2008 16:43:35 -0000

It isn't a good idea to use real tax payer information in development or testing environments. There are several reasons for this: (1) If the test data accidentally gets run into the production system, we don't want real tax payers getting erroneous bills/debits/letters. (2) Developers don't need real tax payer information to test their programs. Only those who truly need tax payer information should access it.

We already have a transmission generator to randomly generate transmissions that are valid according to the schema and business rules, but that isn't so useful for testing. The randomly generated tax payers don't exist within the system, so a RegCOU or any type of return or payer will just go to a work list with an unknown tax payer error.

We should develop a means of creating a set of transmissions that logically flow together that can be effectively used to test the system. For example, a user should be able to create a series of transmissions that will create an account for a factitious tax payer (RegNEW), change that tax payer's address (RegCOU), file a return for that tax payer (SEROnly) and make a payment for that tax payer (PaymentOnly).

Add method to remove auto-maintained Transmitters

Matt Gagne — Wed, 25 Jun 2008 12:09:52 -0000

As an addition to the Transmitter Add/Update service we should add the ability for users added through that service to be auto managed. A new column in the users table would keep track of weather or not users were auto-managed. Based on this column, every time a new list was send in, if a user had the auto-managed flag and didn't appear on the list, they would be removed from the system. This would allow the service to "mirror" a list of Gateway transmitters from another source.

Transmitter Add/Update Service

Matt Gagne — Mon, 16 Jun 2008 18:14:12 -0000

It would be useful to create an interface that provides the ability to add/register transmitters in bulk. By creating a web service, applications could communicate with the Gateway to add in users as "Transmitters" from external sources.

This service will be fairly simple and require only a message such as:

<SendTransmitters>
<Transmitter>
<TransmitterID>aaaaaaaaa</TransmitterID>
<TransmitterPass>aaaaaaaaa</TransmitterPass>
</Transmitter>
<Transmitter>
<TransmitterID>bbbbbbbbb</TransmitterID>
<TransmitterPass>bbbbbbbbb</TransmitterPass>
</Transmitter>
</SendTransmitters>

After receiving this message, the Gateway will check for the existence of each TransmitterID, add the transmitter with the given password if they do not exist, or update the password.

The resulting response would simply echo back the TransmitterIDs and what action was taken for each.

Centralized data viewer

Matt Gagne — Thu, 05 Jun 2008 12:14:05 -0000

The log and document viewers should be combined into one page, along with a message viewer for user message counts. Adding ordering/sorting options would also be nice. Update appropriate help items and localization as well.