Is there a way to overwrite the previously created file instead of creating a new one, whenever the PDF transformation is executed? I am trying to hold on to the original file id, which in my use case is shared with certain sub-processes spawned from the parent process, when the sub-processes are initiated by the parent.
Any flexibility to overwrite the content of a file in the RMP file world with updated content from a second file would suffice.
Also, I have noticed that the created files through PDF transformation have restricted access. We have public users as well, so is there a way to alter the accessibility of a file resource once it is created?
Thanks!
This is my use case: We have an awards nomination process (parent process). After the nominator has completed filling up the nomination and submitted the form, the references (provided in the nomination) receive notification requests (child processes) to log into the system and provide endorsements for the nominee. On the reference form, there is a link to view the Nomination details in PDF mode.
The catch: Parent process (nomination process) stays open for 2 years and the nominator can return to it at any time and adjust the nomination data. Hence, there is a need to refresh the Nomination PDF every time there is an update, so that when the Reference tries to view the Nomination details on the PDF, he sees the latest data.
Please let me know your thoughts. I designed the flow to create the nomination PDF, from the nomination process level data when the nominator submits the form. When spawning the reference requests, I intend to pass the PDF file id to the reference processes (child).
Thanks!
id_collection.
listCallback
(pattern,options,callbackSuccess,callbackFailure)
Thank you for helping here and for providing your suggestions!