Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Getting error while configuring Map From field as Correspondence

SA-36326

Summary



User is getting error while configuring Map From field as Correspondence rule in Response Tab of Service-Email rule.

Error Messages



2017-03-16 00:35:52,842 [ WebContainer : 5] [ STANDARD] [ABCPQRApp:02.01.39] ( internal.services.ServiceAPI) ERROR - Email service [EmailDefault][FW-RBSAssetAppFW-Work-EmailReq][ABCXYZPQR] failed:Outbound data mapping failed:com.pega.pegarules.pub.services.ServiceException: Outbound data mapping failed
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.configureResponse(ServiceAPI.java:2844)
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.mapOutputData(ServiceAPI.java:1940)
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.processSimulation(ServiceAPI.java:2295)
at com.pega.pegarules.integration.engine.internal.services.ServiceSimulator.processServiceSimulation(ServiceSimulator.java:689)
at com.pega.pegarules.integration.engine.internal.services.ServiceSimulator.invokeServiceEmail(ServiceSimulator.java:329)
at com.pega.pegarules.integration.engine.internal.services.ServiceSimulator.execute(ServiceSimulator.java:164)
at com.pega.pegarules.integration.engine.internal.util.PRServiceUtils.executeServiceSimulation(PRServiceUtils.java:1873)
at com.pegarules.generated.activity.ra_action_execute_b3b63d75718b39f5e6441c083707ce9c.step7_circum0(ra_action_execute_b3b63d75718b39f5e6441c083707ce9c.java:705)
at com.pegarules.generated.activity.ra_action_execute_b3b63d75718b39f5e6441c083707ce9c.perform(ra_action_execute_b3b63d75718b39f5e6441c083707ce9c.java:249)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10450)
at com.pegarules.generated.activity.ra_action_runruleexecute_75eba1677022fa6d2b1fa6220f04f174.step12_circum0(ra_action_runruleexecute_75eba1677022fa6d2b1fa6220f04f174.java:1296)
at com.pegarules.generated.activity.ra_action_runruleexecute_75eba1677022fa6d2b1fa6220f04f174.perform(ra_action_runruleexecute_75eba1677022fa6d2b1fa6220f04f174.java:289)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3375)
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(ThreadRunner.java:641)
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivitiesAlt(PRThreadImpl.java:435)
at com.pega.pegarules.session.internal.engineinterface.service.HttpAPI.runActivities(HttpAPI.java:3252)
at com.pega.pegarules.session.external.engineinterface.service.EngineAPI.processRequestInner(EngineAPI.java:384)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Caused by: com.pega.pegarules.pub.PRException: Couldn't map String parameter from Correspondence: Couldn't build Correspondence: EmailResponse
From: (H0A3D3DBB7E17C573E04035F3C3687708)
at com.pega.pegarules.integration.engine.internal.ServiceHelper.getOutboundDataValue(ServiceHelper.java:2440)
at com.pega.pegarules.integration.engine.internal.ServiceHelper.mapOutboundData(ServiceHelper.java:2315)
at com.pega.pegarules.integration.engine.internal.services.ServiceAPI.configureResponse(ServiceAPI.java:2777)
... 79 more


Steps to Reproduce



1. Open Service-Email rule: Email Default.
2. In the response tab, choose the Map From field to Correspondence and place the Created Correspondence rule in Map From Key field.
3. Run the Service-Email Rule, and mention the Subject, From, To Address in the Header Values and Execute the Service.
4.In Service Simulation Results getting the below Error Message:

Email service [EmailDefault][FW-RBSAssetAppFW-Work-EmailReq][CreatepyStartCase] failed:Outbound data mapping failed


Root Cause



A defect in Pegasystems’ code or rules.
Code is not populating correspondence type at the time of selecting correspondence is causing the issue.


Resolution



Enter the correspondence type manually as below to resolve the issue:







Published May 4, 2017 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us