03-11-2010

Still no links to software.  CFSCustomer needs to be tested to see exactly what fields are required and which are optional.  Using an update to date test tool to make the requests and experiment with various inputs.  The response block contains numerous error code tags.  It looks like if any of them are non-zero, then you've made a mistake on input.  Here is what we've figured out so far:

• INST_NBR - required, the field mapping says it is treated as a comment, but the tool pre-populates the value.  If you don't send it, none of the error codes are non-zero but I can't imagine that anything worked.  Get a RETURN_CODE of 72.
• RQ_BANK_ID - required, field mappings say it is required and the tool pre-populates the value.
• RQ_BRANCH_NBR - required, field mappings say it is required and the tool pre-populates the value.
• RQ_OPR_NBR - required, field mappings say it is required and the tool pre-populates the value.
• RQ_FIRST_NAME - required, if don't fill it in you get error codes and a navigation message stating that the name is missing.  If you fill it in, you get a navation message saying that the last name is required.
• RQ_LAST_NAME - required, if you fill it in you are told that the gender is missing.
• RQ_GENDER_CODE - required, it is also used as a condition for other fields to be required.  For example, using O as a gender requires that a business address be filled in.  INST-NBR MUST = TERM-BANK 
• RQ_FOREIGN_IND - required

Beth suggested using the production server but with test credentials and test banks.  That will avoid errors that don't really exist, such as the one with the gender code.