PDF EForm Help
-
PDF EForm Help
-
I am using my self-study VM as a lab to prototype POC for merging/concatenating PDFs.
-
With such I am attempting to upload PDF with the EForm Accelerator and then Map the Pdf fields to properties on the clipboard.
-
I can create both rules for PDF which include Rule-File-eForm and Rule-Map-eForm rule.
-
I then create an activity to call the ‘GenerateEForm’ activity.
-
For the parameters, I have entered the MapPurpose and TargetEFormPage.
-
I run the activity from the ‘Actions’ menu on my calling activity.
-
I get the error Unable to find the specified Rule-Map-eForm rule ‘Code-Pega-eForm.ManualTest’
-
I have tried this many ways for a few days now.
-
No matter what I do I get the same error.
-
Any ideas
-
(See Attachment)
***Edited by Moderator Marissa to branch from this thread and to add attachment***
**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.
Accepted Solution
Pegasystems Inc.
US
Hi,
Looking over your screenshots in the "Help screenshots_1.docx" document from your original post, it looks like you are calling GenerateEForm with the "pdf1" as both your step page and your TargetEFormPage. As the "pdf1" page is used as the TargetEFormPage, I suspect that this page is of the class Code-Pega-eForm. When "pdf1" is used as the step page as well, that means your step page context is also Code-Pega-eForm and the system will look for your Rule-Map-eForm rule in that class. As you're Rule-Map-eForm rule is in SAE-Myapplic-Work-Practice, the system won't find it.
I believe you should be able to avoid this error by creating a page of the class SAE-Myapplic-Work-Practice , and use that newly created page as your step page when you call GenerateEForm. You'll still want to use your "pdf1" page as the TargetEFormPage, but swapping to a step page with the same class as your Map eForm rule will likely avoid the error.
Hope this helps!
-Kurt
Accepted Solution
Pegasystems Inc.
US
Hi,
Looking over your screenshots in the "Help screenshots_1.docx" document from your original post, it looks like you are calling GenerateEForm with the "pdf1" as both your step page and your TargetEFormPage. As the "pdf1" page is used as the TargetEFormPage, I suspect that this page is of the class Code-Pega-eForm. When "pdf1" is used as the step page as well, that means your step page context is also Code-Pega-eForm and the system will look for your Rule-Map-eForm rule in that class. As you're Rule-Map-eForm rule is in SAE-Myapplic-Work-Practice, the system won't find it.
I believe you should be able to avoid this error by creating a page of the class SAE-Myapplic-Work-Practice , and use that newly created page as your step page when you call GenerateEForm. You'll still want to use your "pdf1" page as the TargetEFormPage, but swapping to a step page with the same class as your Map eForm rule will likely avoid the error.
Hope this helps!
-Kurt
Veteran Careers First
US
WOW!
It worked!!
Thanks for such a clear explanation.
I will now continue with the activity, adding additional PDFs, then use the concatenateEForms rule to merge the PDFs into a single PDF.
And then call AttachEForm rule to attach the 'merged into single' PDF to the work object.
Verizon Data Services
IN
Hi ,
Do you have a sample pdf which I can upload in eform . I am having some issues with the pdf which I am uploading.
Pegasystems Inc.
US
Hello Henry,
You don't show your pages and classes tab on the activity. Do you define the page pdf1 in your class SAE-Amapplic-Work-Practice? It's possible that the page context is throwing things off. I haven't had a moment to dig into your trace, so I could be way off, but that might be a quick place to look. The error is pretty clear that it's looking in the class Code-Pega-eForm. Another thing you could try might be to create your Map eForm rule in that class to see if it gets picked up.
Thanks,
Mike