Posted: 18 May 2017 11:47 EDT Last activity: 16 Oct 2018 12:03 EDT
pdfConnector Close() Doesn't Completely Close File
In Pega Robotics 8.0.1037.0 if IsOpen is called immediately following a call to Close(), it will return True. Not until the FileName is set to null will IsOpen return a False. Whether this is by design is not addressed in the online Help documentation. It also appears that setting the FileName is the equivalent of an Open although this really isn't described in the online Help documentation either. The textbox for the code below returns the following:
Is NOT Open
***Updated by Moderator: Marissa to update SR Details***
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Incidentally, the first example opens the passed filename, and the second will always show that the file is already Open [which is what would be expected]. Pega Robotics must decide that it does a pull when the target property is in the execution path and a push when it isn't.
SR-B52968 has been opened. It's not a question of goals. I had to mess with my automation for quite a while to figure out that the Close was not sufficient. I am sure others will encounter the same issue. It would be better if the Close actually completely closed the PDF.
I also find it a little odd that there is not Open, and that specifying the filename opens the PDF.