Minor changes are by default collapsed in the page history.
No changes
The page does not exist yet.
Failed to load changes
Version by on
Leave Collaboration
Are you sure you want to leave the realtime collaboration and continue editing alone? The changes you save while editing alone will lead to merge conflicts with the changes auto-saved by the realtime editing session.
Running parsing functions only once in SilkPerformer scripts
When you are parsing for AR System table entries or replacing quotation marks, backslashes, or user information, repeated script runs will return the same response if you set the test environment up correctly. For example, if your goal is to only view the tickets and not create new ones, you will always have the same set of tickets to view. Therefore, you should parse the response only once to reduce SilkPerformer work. The goal is to measure Mid Tier performance, not how quickly SilkPerformer parses responses.
To verify that parsing is done only the first time through the transaction, use a Boolean check:
ifgnTxCount=1then parseRequestList(buffer); end;
Sometimes you might need to parse in every iteration, such as when searching for an instance ID or a newly created entry ID.
