The following check steps have been created or changed in this release:
|Check Outbound RFC destinations||Recording||Preparation||If outbound RFC functinality has been enbaled and RFC destinations have been “re-pointed”, this preparation step will check that those RFC destinations are valid.|
|Reset recording RFC destinations||Recording||Post Processing||During setup of outbound RFC, the RFC destinations that outbound calls to will be captured are “re-pointed”. This post processing step automatically restores those RFC destinations to their original state.|
|Retrieve inbound RFC signatures||Recording||Post Processing||After the recording is complete, the signatures of the unique list of inbound RFC’s is retrieved. This supports us in the result analysis phase where the investigate screen is used. It retrieves the RFC signature stored in this step rather than retrieving the RFC signature dynamically from the source system(s).|
|Check outbound RFC analysis has run||Playback||Preparation||Before a playback is started, the test scripts that contain outbound RFC calls are analyzed to ensure that the stub generation has been executed and the stubs are in place for the outbound RFC calls.|
|Reset playback RFC destinations||Playback||Post Processing||Once the playback is complete, those RFC destinations that were re-pointed on the target system for service virtualization purposes are restored to their previous state.|
Thanks for your feedback.