Best preventive measure to avoid performance related issues in health check.

Aquaman is just for testing code quality in design , not in runtime.

I would suggest to create test cases for all objects in your appian application (even for integrations), and just after deploy the package, execute a post deployment process generating a report with the results.

Aquaman is just for testing code quality in design , not in runtime.

I would suggest to create test cases for all objects in your appian application (even for integrations), and just after deploy the package, execute a post deployment process generating a report with the results.

Hi  , I have checked the post deployment process, there are two concerns:

1. it is not preventive measure, it will execute after deployment in PROD.

2. it run the test cases, but how it will tell me the performance of rules it executed, it just tell me pass or fail about that test case.

Hi again.

• As you said, this is not preventive, unless you use the smart servvice Database load Generation in a non productive env, with the estimated amount of data you will have in production.  For concurrency you can use JMeter or appian Locust.
• When you execute test process, it will return an id. This is the id of the test executed. and with the function a!testRunResultForId you will recover the information about each one of the rule test executed, including the execution time, ellapsedTime.....

Hi  

I have used Configure a Post-Deployment Process - Appian 22.4 to create post deployment process,

1. it is throwing this error: 

2. When I manually passed the package uuid, it ran successfully but did not return any id. What is missing?

The id  of the test executed is returned in the task StartRuleTest as output.