Page 1 of 1
error on sig pad save.
Posted: Mon Jun 26, 2017 1:07 pm
by mwalter
I'm getting the error "Operation Prevented by Exit Program" when trying to save the contents of a Signature Pad widget. Anyone else come across this? Anyone know which exit point may be being invoked?
Re: error on sig pad save.
Posted: Mon Jun 26, 2017 1:17 pm
by Scott Klement
Are you attempting to upload the signature pad as an image? (vs. saving the source in a variable, as is normal?)
If so, it would be the file upload exit program (PUIUPLEXIT).
http://www.profoundlogic.com/docs/display/PUI/Security
If not, then please explain further.
Re: error on sig pad save.
Posted: Mon Jun 26, 2017 1:37 pm
by mwalter
Yes, using the pui.uploadSignature API.
Re: error on sig pad save.
Posted: Mon Jun 26, 2017 2:15 pm
by mwalter
Noticed something odd. Not sure if it applies.
The source for PUIUPLEXIT accounts for image/jpeg file types.
However, when I load that program into the debugger, it does not. The source in the debugger looks completely different.
I started a service job over my http job, and put the program into debug. It didn't stop, that's why I wasn't sure if it was applicable. However, I'm not sure which job would handle the API call (pui.uploadSignature).
I'm also not sure if the source for the exit program is up to date, or the actual exit program is up to date.
Re: error on sig pad save.
Posted: Mon Jun 26, 2017 2:41 pm
by mwalter
Ok, So I bit the bullet. Saved the current program object and compiled the source in PROFOUNDUI/QRPGLESRC,PUIUPLEXIT and the save of my signature
worked. I don't think we're doing any other types of uploads other than CSV exports.
Re: error on sig pad save.
Posted: Mon Jun 26, 2017 2:51 pm
by Scott Klement
By default, there is no compiled exit program included with the product. We do provide an EXAMPLE source member that demonstrates allowing jpeg's and also text files < 10mb. But, this is just an example....
The idea is that you copy this source into your own library (the source file that's included with the product is replaced each time you upgrade, so don't put your code there) and modify it to suit your needs. Then compile it into the product library. (The compiled program is not replaced during upgrades -- only the source code.)
From your description, it sounds like someone created an exit program in the past that did not allow your images. When you looked at the source code, you looked at our example source that gets replaced each time you upgrade, and so you saw something different from what the exit program was compiled with.