I'm assuming that the approvers' name are collected from the workflow actions along the way. Since the names are not picked and using an Image Picker at the BP is not an option, you need to get the image for the signature from other source. It could be from another BP or even from User Administration form (added with an image picker to store the signature). Not sure if custom print reports can fulfill this requirement, but pretty sure that it can be achieved when using a custom report, where you could query multiple BPs to combine the respective BP with another BP that holds the signature.
Using the custom print, you can also control the permission on who gets access to print the approval form; when using custom print - if I'm not mistaken - all users who have access to the record can print the form.
Yes, I had done exactly this, the way Edwin describes it. I had built a Custom Print (with External Data Model) that sees who the WF approver was, and then retrieves their signature image from a separate BP.
Note: This was before we had the eSignature integrations with Docusign and Adobe Sign... so those may be alternate solutions.
thanks a lot Jeff
After modifying the external data model and everything, do we still have to add a dummy picture to the rtf file and add the path as alt text to be able to print the signature picture?
I did modify the external data model and all, but when i print the custom print it gives me the picture name instead!
i retrieved the signature from user attribute instead of separate BP
Could you please advice.
Thanks a lot Edwin
this is my variable definition
and this is the link path
and I added the picture DE value to the workflow steps query in BI.
Did I miss anything!?
btw we use Unifier cloud, is that going to make a difference?
Yes, that's the correct way to do it... by adding a dummy image and putting the code you had above in.
Troubleshooting the images not appearing is difficult - I suggest you log an SR so support can investigate with you. From your variable definition above, you appear to be on the right path, so it's really hard to say what the issue is.
One note is that you may want to use the server_token method instead of the older method you're using: