You are viewing limited content. For full access, please sign in.

Discussion

Discussion

Forms 10.4.2 - Unreadable error when trying to use Email Activity

posted on February 4, 2020

We are getting this error trying to use the Email Activity in Forms 10.4.2. I can not interpret it though, normally email errors show the error received from the email server.

An unexpected error has occurred. [LFF502-UnexpectedError] Details: URL: Error: UnexpectedError Date: 2/4/2020 4:40:48 PM (Pacific Standard Time) HTTP Status Code: 500 Business Process ID: 7 Instance ID: 3214 Business Process Name: Athletics Check Request Stack Trace: Caught exception: Laserfiche.Forms.CommonUtils.Exceptions.LFFormsException Message: An unexpected error has occurred. [LFF502-UnexpectedError] Inner exception: System.Xml.XPath.XPathException Message: Expression must evaluate to a node-set. at MS.Internal.Xml.XPath.XPathParser.ParseNodeTest(AstNode qyInput, AxisType axisType, XPathNodeType nodeType) at MS.Internal.Xml.XPath.XPathParser.ParseStep(AstNode qyInput) at MS.Internal.Xml.XPath.XPathParser.ParseRelativeLocationPath(AstNode qyInput) at MS.Internal.Xml.XPath.XPathParser.ParsePathExpr(AstNode qyInput) at MS.Internal.Xml.XPath.XPathParser.ParseUnionExpr(AstNode qyInput) at MS.Internal.Xml.XPath.XPathParser.ParseMultiplicativeExpr(AstNode qyInput) at MS.Internal.Xml.XPath.XPathParser.ParseAdditiveExpr(AstNode qyInput) at MS.Internal.Xml.XPath.XPathParser.ParseRelationalExpr(AstNode qyInput) at MS.Internal.Xml.XPath.XPathParser.ParseEqualityExpr(AstNode qyInput) at MS.Internal.Xml.XPath.XPathParser.ParseAndExpr(AstNode qyInput) at MS.Internal.Xml.XPath.XPathParser.ParseOrExpr(AstNode qyInput) at MS.Internal.Xml.XPath.XPathParser.ParseExpresion(AstNode qyInput) at MS.Internal.Xml.XPath.XPathParser.ParseXPathExpresion(String xpathExpresion) at System.Xml.XPath.XPathExpression.Compile(String xpath, IXmlNamespaceResolver nsResolver) at System.Xml.XPath.XPathNavigator.Select(String xpath) at System.Xml.XmlNode.SelectNodes(String xpath) at Laserfiche.Forms.Routing.AttributeToken.ParseTokens(Boolean Encode, XmlDocument xmldoc, String inString, cf_users user, Boolean keepIfNoMatch, String TimeZone, Int32 pos, ConvertToLocalDateFormat ConvertToLocalDateFormat, Boolean translateTokens, Boolean escapeEncode, ICollection`1 fields, Boolean replaceNewlines, ParseTokenOptions tokenOption, Boolean retainCurrentUserToken, Boolean removeGroupSeparators, Int32 currentRow, Boolean useGregianCal, Int32 attempts) at Laserfiche.Forms.Routing.AttributeToken.ParseTokensEncoded(XmlDocument xmldoc, String inString, cf_users user, Boolean keepIfNoMatch, String TimeZone, Int32 pos, ConvertToLocalDateFormat ConvertToLocalDateFormat, Boolean translateTokens, Boolean escapeEncode, ICollection`1 fields, Boolean replaceNewlines, ParseTokenOptions tokenOption, Boolean retainCurrentUserToken, Boolean removeGroupSeparators, Int32 currentRow, Boolean useGregianCal) at Laserfiche.Forms.Routing.EmailService.Execute(Int32 instanceId, IRoutingContext routingContext, RoutingInstanceStatus OriginalStatus) at Laserfiche.Forms.Routing.ServiceTask.Execute(Int32 instanceId, IRoutingContext routingContext)

0 0
replied on June 24, 2020

With Forms 10.4.4, you will no longer see such unreadable error, instead the invalid variable will be parsed as empty. 

0 0
replied on February 4, 2020

Are you using variables in the email body? It may be caused by invalid variable token is used in the email body. For example if there is something like "<a href="https://maps.google.com/?q={/dataset/Single_Line"><u><font color="#0066cc">{/dataset/Single_Line</font></u></a>}" in the email body, there will be error "Expression must evaluate to a node-set". Can you switch to the "Html" tab of the body for the email service task and copy the content and share with us?

0 0
replied on February 5, 2020

It looks clean from what I can tell, here is the full HTML

The Athletic Check Request detailed below that you submitted has been approved and processed. Please contact Cari Fivecoat if you have further questions.<div><br></div><div><span style="font-size: 14px;">Event Name: </span><span style="font-size: 14px;">{/dataset/Event}</span></div><div><span style="font-size: 14px;">Team:&nbsp;{/dataset/Team_1}</span></div><div><span style="font-size: 14px;">Amount: </span>{/dataset/Amount}<span style="font-size: 14px;"></span></div><div><p></p><div><span style="font-size: 14px;">Comment from approver :</span><br></div><div><span style="font-size: 14px;"><br></span></div><div><span style="font-size: 14px;">{/dataset/_</span><span style="font-size: 14px;">Comment</span><span style="font-size: 14px;">}</span><br></div></div>

 

0 0
replied on February 5, 2020

The variable token of comment is broken.

2 0
replied on February 5, 2020

Oh I see, they tried to put a span inside of the token syntax. The way they constructed the email it looks like they never even went into the HTML editor to do anything custom, not sure what happened. I will let them know.

0 0
replied on February 10, 2020

The user should edit the content with the HTML editor as you won't be able to add content as "<span style="font-size: 14px;">" using the Visual editor.

0 0
You are not allowed to follow up in this post.

Sign in to reply to this post.