Skip to main content

Perceptive POS Plexus Internal Test Scripts - Perceptive

  1. Last updated
  2. Save as PDF

Where is this document located?

N:\ProjectManagement\Share\Plexus\03 Solution Review\Avatar\Perceptive

First Test

Purpose: This test is to verify that all client document types are coming across correctly. If all documents get stuck in the error queue, it is likely a sever level issue and case will need to be submitted. If only a few documents are getting stuck, this is likely a configuration error.

When to run: This test should be ran through anytime a change is made to the configuration of the baskets and/or document types. Most likely, right before Solution Review and before Final Review and Validation. This test should also be ran when testing the LIVE system.

Second, Third, and Fourth Test

Purpose: There is a common issue where larger documents will get sent to myAvatar multiple times from ImageNow. These tests are to determine whether your system is experiencing this issue. If you do see this happen, submit a case.

When to run: Since this is more of a server level/script level test, it does not need to be ran through each time a change is made to the configuration. It should be ran once in each environment used (i.e. SBOX, UAT, and LIVE).

Fifth and Sixth Test

Purpose: These tests are to go through the known issues surrounding the date fields and forbidden characters. It is hard to know how a new update will affect these items, so we test it for each client. When these items fail, they do not require configuration changes or a case to be submitted. Instead they should be used when training end users and showing the system administrator how to maintain the error queue. The script notes which steps are likely to fail. If another step fails, please add a comment below.

When to run: Since this is more of a server level/script level test, it does not need to be ran through each time a change is made to the configuration. It should be ran once in each environment used (i.e. SBOX, UAT, and LIVE).

Seventh Test

Purpose: This test is to verify that all staff document types are coming across correctly. If all documents get stuck in the error queue, it is likely a sever level issue and case will need to be submitted. If only a few documents are getting stuck, this is likely a configuration error.

When to run: This test should be ran through anytime a change is made to the configuration of the baskets and/or document types. This test only needs to be ran if the client is going to scan/import staff documents into myAvatar . Most likely, right before Solution Review and before Final Review and Validation. This test should also be ran when testing the LIVE system.