FAQ - Troubleshooting

In this article you will find Participation Frequently asked Questions and/or Troubleshooting

Limitations

Limitations:

  • When using the email push method, some of the files could potentially be big, and the receiving email inbox may not be able to deal with these large files.  Limitation of your e-mail server, but e-mail is not typically recommended for large files.
  • Using the email method there is no way to combine emails due to the file size limitations.
  • Maximum files size allowed when using SSL will be less than non SSL due to the overhead of encryption and security.
  • If using AccuAccount to AccuAccount transfer method the document structure must be the same.  Based on the document code.
  • No way to combine FTP emails due to the functionality being shared with the email transfer method.
  • If you have a case sensitive FTP software, changes in folder names in the document structure or FTP folder structure can cause issues.

 

Configuration Testing

There are many different scenarios that need to be tested, to assure that all aspects of Participation loans work as designed.

Administrative Tools
Here are test cases that must be tested for in the administrative tools

  1.  Can you add and edit a participating non-affiliate and affiliate bank
  2.  Ensure you can verify an affiliate URL
  3.  Can you add and edit a participating bank contact
  4.  Can you delete an unused participating bank contact and participating bank

Loan Maintenance
Here are test cases that must be tested for loan maintenance

  1.  Can you make a loan a participation loan
  2.  Can you add a participating bank to the loan
  3.  Can you edit the participating bank

Console Application
When all the data has been set up, we will need to test the two document push methods which are executed via the console application Participation Loans Process.  These two methods need to be broken out into testable scenarios.

Import Service
Here are test cases that must be tested for the Import Service

  1. Document history should exist on originator for each document that was pushed
  2. Document history should exist on affiliate for each document that was received
  3. Document history should exist on originator if a document has a document status of 1 but the physical document is missing
  4. If all documents are set to be pushed at once, all the documents should be pushed, regardless of the "Last Push Date"
  5. If all documents are set to be pushed at once, once the push is complete, the check should be removed from the loan record for push all documents.
  6. If the customer mapping for the affiliate is incorrect on the originator, a log should be created informing the user and all documents should be pushed to the affiliates upload directory
  7. If the loan mapping for the affiliate is incorrect on the originator, a log event should be created informing the user and all documents should be pushed to the affiliates upload directory.
  8. If the collateral mapping for the affiliate is configured incorrectly on the originator, a log event should be created informing the user and all documents should be pushed to the affiliates upload directory.
  9. If there are more than one loan on the affiliate bank with the same number, a log event should be created, and all documents should be pushed to the affiliates upload directory.
  10. If a matching document tab is not found on the affiliate bank, the default document tab should be used. However, if a default is not set, the document should be pushed to the upload directory and placed within the intended directory structure. A log event will be created informing the user. 
  11. Loan record should reflect a new "Last Push Date" after a push has been conducted.
  12. Documents added to AccuAccount via AccuScan, AccuCapture, Upload, Merge, RemoteScan, RestoreDocument must be pushed by the console application.
  13. If a customer, loan, document sub type, or participating bank contact are blocked, then no documents should be pushed for these particular scenarios.

Email Push
Here are test cases that must be tested for the Email Push

  1. A log entry should be produced if the SMTP server data is incorrect and the email fails to send.
  2. Documents should be received via email to the address that was configured in the primary email address on the bank contact
  3. Document history should exist on originator for each document that was pushed
    Loan record should reflect a new "Last Push Date" after a push has been conducted.
  4. If a customer, loan, document sub type, or participating bank contact are blocked, then no documents should be pushed for these particular scenarios. 

Participation Loan Service Workflow

How it works

This will describe how participation loans console application works through visualizing it internal structure  using a simple flow diagram.

2018-01-10_1508.png

  1. Nightly Participations Console Application is Executed
    • a. Settings are loaded
      b. Document lists are generated based on selected criteria
  2. View scan history
    • a. View scan history records are compared with the list of returned documents to ensure that documents selected have been altered since the last push date.
  3. The Participations Service is called
    • a. This injects the list of returned documents
      b. Determines the push method based on the contact information
  4. Email Push Method
    • a. Email code generated and documents are attached to the email
      b. Email is sent to primary email of the contact
      c. Appropriate view scan history records are created
  5. Service Push Method
    • a. Generates a service call to affiliate bank
      b. Includes all the necessary documents and all mapping information
      c. Calls the service, passing the information
  6. Affiliate Web Service
    • a. Service call is received by the affiliate bank
      b. Customers, accounts, collaterals, and groups & tabs, are looked up based on the mappings
      c. Service attempts to import the documents, failed documents are moved to upload directory
      d. Error are handled and logged by the service
      e. Appropriate view scan history records are created
      f. If “Push Participation Docs?” was checked, this will be unchecked upon completion
      g. A new “lastPushDate” will be added to the loan record
Was this article helpful?
0 out of 0 found this helpful
Have more questions? Submit a request

Comments

0 comments

Please sign in to leave a comment.