Posts tagged "setvalue"

LiveCycle ES: values in a LC7 SetValue expression are being lost after a process upgrade

Issue

 After upgrading a process from 7.x to 8.2 in workbench, the value expressions that existed in the 7.x SetValue activity no longer exist and appear as blank assignments in the 8.2 SetValue activity.

Example:

7.x SetValue Settings:

/process_data/myXMLVar = '<node>value</node>'

/process_data/myStringVar2 = 'test string'

/process_data/myXMLVar3 = '<node>value</node>'

8.2 SetValue Settings (post upgrade):

/process_data/myXMLVar = ''

/process_data/myStringVar2 = 'test string'

/process_data/myXMLVar3 = '<node>value</node>'

The upgrade appears to be removing XML based strings (unless escaped).

Reason

 This is a bug in LC 8.2.1.2 and is caused by the loss of XML data encoding:

- encoded XML attribute values are read from the input process action template and decoded during read by Xerces

- decoded values are rewritten as XML elements (not attribute values) and never re-encoded.

- the subsequent symptom is that the unencoded XML data is (rightly) interpreted by an XML parser, but should have been interpreted as text data.

Solution

 This issue will be fixed in Workbench ES2.  There is a patch available for LC ES 8.2.1.2, so contact enterprise support if you require this patch.

reference: (181109986/2403113)

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)

LiveCycle ES: Namespace problems in SetValue and Script services

Issue

When working with namespaces in the SetValue and Script objects in LC7, you may receive an error saying the “path” is unreachable, or similar errors pointing to problems in the expressions, after migrating to LC ES.

Reason

These errors can occur in LC ES when using namespaces such as in the following example:

LiveCycle ES now validates XPath expressions more strictly than it did in LiveCycle 7.  LC ES requires you to define the namespaces in the process, whereas Lc7 did not have this requirement.

Solution

Adding the namespace to the process properties will fix the issue.  You only need to add these namespaces once for each process, and all the Script and SetValue activities in that process will be able to reference those namespaces.

To add the namespaces:

Open the process properties and go to the Advanced > Registered Prefixes for Namespaces used in XPaths and enter the prefix (i.e. soap), and the namespace (i.e. “http://schemas.xmlsoap.org/soap/envelope/“).

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)