When the fields (subject and description) are NOT mapped the issue is created (xml tags are recognised) without field values and if they are mapped XML tags are not recognised They have not seen this behaviour when the email is sent from GMAIL or Outlook
The following error may be seen in the Common Log when trying to execute an orchestration: "cannot create node for non- element context node: [#document: null][org.jbpm.bpel.sublang.xpath.XPathEvaluator]" This can be caused by the namespace of a working data variable being different than the namespace for other working data variables.
The auth section gets ignored if it's mapped to the auth input element . If you have SSO turned on then it will use the SSO credentials and not be overwritten by the auth section.
The workaround for this is to import users with the "Import users as copy of" set to a template user that has an access type that has available licenses and make sure the "When user already exists" setting set to "Replace mapped attributes".
Array records, default values, and mappings are removed from a working data element and its child elements when another working data element at the same level as the containing working data element is deleted. This only happens when the two working data elements have the same name or start with the same letters.
The documented limit for the number of members that can be specified in an XML -driven selective promote is 800. When specifying larger numbers of members for promote, but staying below the 800 limit, the service execution becomes unpredictable. In a series of tests on a single package the following results were encountered:
