Why test mode is required
The main dynamic values in the recorded script for installable
cloud apps are “sessionid” and “transactionid”. Both values are
dynamic and can only stay valid for a short time, therefore, it is
necessary to capture them and save them into variables in the
script.
Specially, about “sessionid”: Because all the requests and
responses between the client application and PowerServer are tracked
by “sessionid”, “sessionid” is encrypted in every request/response
for security reasons in the production environment, which makes it
difficult to correlate the value in the script. To work around the
problem, the PowerServer Web APIs has two modes:
-
“0”- normal mode
-
“1”- test mode
Under the test mode, the “sessionid” included in the requests
and responses is in plain text. The security is compromised but it
shall be sufficient for the test environment.