This information applies only to users that are linked
to the Permit Plan/Accela permitting system. In previous
versions the RASWIN program checked to see what set of SQL
statements to execute in two steps. First, there is a query
to validate the permit # and payer name. Second, there is a
query to retrieve the open permit items based on the Permit
Plan receipt number and date (one or both), or based on a
'Case Number' (permit number) depending on the specifics of
your implementation.
The SQL statements for both steps is stored in the SQL
STATEMENTS table. The first query was typically called
ACCELA_PRODMODE_1, or
TIMEMARK_CASE_NAME_QUERY.
At some sites this sql looked something like this:
SELECT NAME FROM APD_PEO WHERE
NUMBER_KEY = '@A_RCPT_NUM@' or
SELECT
CSM_NAME_LAST AS PAYER_NAME FROM CASEMAIN WHERE CSM_CASENO =
'@CASENO@'
At some sites the payer name is stored in another field
entirely.
SELECT FEE_SUM.NOTATION AS
NOTATION FROM FEE_SUM WHERE FEE_SUM.RECEIPT_NO =
'@A_RCPT_NUM@'
A run time the RASWIN program substitutes the user
entered values (such as the receipt number or case number
into the query and tries to find the matching entry,
which it displays on the entry screen for the user to
confirm.
To lessen the chance for program updates changing the
entries that have been customized specifically for your
site, the
SQL STATMENTS table key values for these queries
have been made customer specific. Within the RASWIN
MISCPARMS table there is a setting called SHORT_USER_NAME. This is a QSI
controlled value with identifies your site to the program
so that customer specific logic cab be processed in such
a way that it applies only to your site and is ignored by
other locations.
The current version of RASWIN, and carrying forward from
this release will therefore look for ACCELA_GET_NAME_[short-user-name] keys
instead of the older ACCELA_PRODMODE_1 keys.
So, for example, if your old settings were:
Command Name Sequence Command Text
----------------- -------- ----------------------------------------------------
ACCELA_PRODMODE_11SELECT FEE_SUM.NOTATION AS PAYER_NAME FROM FEE_SUM
ACCELA_PRODMODE_12WHERE FEE_SUM.RECEIPT_NO = `@A_RCPT_NUM@`
and your SHORT-USER-NAME
setting is GOTHAM the new
'Command Name' the program will look for will be:
Command Name Sequence Command Text
---------------------- -------- ----------------------------------------------------
ACCELA_GET_NAME_GOTHAM1SELECT FEE_SUM.NOTATION AS PAYER_NAME FROM FEE_SUM
ACCELA_GET_NAME_GOTHAM2WHERE FEE_SUM.RECEIPT_NO = `@A_RCPT_NUM@`
Followed by a second query to get the permit data itself.
Again, the specific SQL executed varied by client site
depending on the details of your Permit Plan/Accela setup
and version. The new name for the second query (to get
the details) is now going to be
ACCELA_GET_DETAILS_[short-user-name]
e.g., as in our GOTHAM example
ACCELA_GET_DETAILS_GOTHAM
Command Name Sequence Command Text
------------------------ -------- ----------------------------
ACCELA_GET_DETAILS_GOTHAM1 whatever sql is required
ACCELA_GET_DETAILS_GOTHAM2 etc
ACCELA_GET_DETAILS_GOTHAM3 etc
