Pega Robotics v22 Questions
I have a few questions/suggestions for Robotics (mostly v22 related):
1) In Robotics v19, when using the playback tool, there was the ability to navigate forward and backward through the log file. In v22, there is no step backward. While you can choose an exact point from the step list, it doesn't indicate the current step. You'd have to know exactly which step to go back to. This can be difficult in larger log files. Is there any way to step backward that we're not seeing?
2) This is more of a general studio question rather than v22. Many years ago I created a simple standalone exe to parse larger log files and only extract lines under the Playback category into a new text file. This helped step through log files much faster in playback. In v22, with the log changes, it still works, but requires some manual changes to get the log files to work in playback. Is there any plan to incorporate something like this in the playback tool? Having it automatically create a temp playback file would help expedite troubleshooting.
I have a few questions/suggestions for Robotics (mostly v22 related):
1) In Robotics v19, when using the playback tool, there was the ability to navigate forward and backward through the log file. In v22, there is no step backward. While you can choose an exact point from the step list, it doesn't indicate the current step. You'd have to know exactly which step to go back to. This can be difficult in larger log files. Is there any way to step backward that we're not seeing?
2) This is more of a general studio question rather than v22. Many years ago I created a simple standalone exe to parse larger log files and only extract lines under the Playback category into a new text file. This helped step through log files much faster in playback. In v22, with the log changes, it still works, but requires some manual changes to get the log files to work in playback. Is there any plan to incorporate something like this in the playback tool? Having it automatically create a temp playback file would help expedite troubleshooting.
3) If a utility/component project was created in v19, we could import this project into another solution and utilize those automations. In v22, we have assets, but they currently do not currently support global containers. This limits their functionality. If we were to build a utility project to use in other projects, and it utilized any globals, is there a way to merge this global container with another project or import this project into another to use this? It seems if we create 2 projects that utilize the global container, there is no easy way to merge these projects due to the single-global container. (We could possibly modify the XML directly, but we'd need to update all automation references to the global objects to the new global container ID.)
Thanks!