The following check steps have been created or changed in this release:
| Check Step | Phase | Type | Description |
|---|---|---|---|
| IDoc configuration retrieval | Recording | Post Data Transfer | In versions 2.21 of Testimony, both inbound and outbound IDoc’s can be captured during the recording and compared in the playback. In order to faciltate this comparison, the remote IDoc definitions must be retrieved from the source and target systems. After capturing IDoc’s in the recording, this post data transfer step will retrieve the IDoc related configuration that supports in the IDoc comparison. |
| IDoc configuration retrieval | Playback | Preparation | Since the configuration of IDoc’s may have been changed in the target system as a part of the tested changes, this step will retrieve the IDoc configuration from the target system prior to the playback starting. This data is then used to support the IDoc validation of the IDoc’s . |
| Generate Playback Summary | Playback | Post Processing | Once a playback has completed successfully, the playback summary will now be automatically generated. |
| Retrieve Batch Job Spools | Playback | Post Processing | Once a playback has completed successfully, the batch job spools will all be automatically retrieved from the playback system so that the investigation of batch job failures is supported by the analysis of the recording versus playback batch job spool output. |
| Bot Configuration Check | Playback | Check Step | The check on the bot configuration has been significantly enhanced. Additional checks are now done on the following – (1) Correct theme is set, (2) SAP GUI History is turned off, (3) Bot executable has been authorised for the new visual theme, (4) Bot screen resolution is sufficient. |
Post your comment on this topic.