You are viewing limited content. For full access, please sign in.

Question

Question

ISO things to test in a parallel test for AP Invoice Solution

asked on July 5, 2022

Hello, 

We are conducting a parallel test where a user is manually entering invoices into one system and Workflow is writing new records via API to a test environment (Skyward Q). This is rather unusual since the business side isn't sure of what to test and monitor. They are not providing the developers much guidance in this area. There are a few things we have identified but am curious if there are any other important items that we should be testing. Here is what we have so far:

  • Encumbrances occur on all POs
  • All reports show the newly written records and are accurate
  • General data accuracy - what is sent is received per record
  • Processing the new invoices for payment works correctly

 

I know many of you have already gone down this road, so I'm looking for any 'gotchas' that you came across. 

Thank you very much!

 

0 0

Replies

replied on July 5, 2022

Web API? How are things supposed to fail? Is WF expected to get an error? Do you know what the limits on the size of the data being pushed through are?

I would turn on termination notification for this workflow so you know immediately if something goes wrong.

If it's a web API that they are hosting, you can also monitor the web server for 500 errors to know when things start failing.

 

1 0
replied on July 5, 2022 Show version history

great suggestions, thank you!

We are using the HTTP Web Request activity in Workflow. 
I have a condition where if the activity does not succeed it halts the WF. We are pushing extremely small amounts of data through. Approx 10 fields per activity. 

I like the idea of monitoring for 500 errors.

0 0
replied on July 5, 2022

Do you put any limits on those fields on the data entry side?

What's the plan for handling downtime on the API side? What error will be returned to WF?

0 0
replied on July 5, 2022 Show version history

Yes, Forms restricts what is going in, so we do have that set up. If the WF terminates then the Form will suspend, so if anything bad happens on the API side we can retry it.  Usually all maintenance for that system happens outside of business hours. They are really good about communicating outages as well. 

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.