Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
CMS-XML Email XML submit from Outlook Express does not work correctly.
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
CMS-XML Orchestration failing when working data variable mapped to
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.
CMS-XML Mapping auth section to working data complex type doesn't use userid password
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.
CMS-XML Import users from spreadsheet not working to update users if no available licenses
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".
CMS-XML Values Removed from Working Data Elements when a Working Data Element with a Similar Name is Deleted
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.
CMS-XML Dim 14 - Eclipse annotations do not work for xml files.
Dim 14 - Eclipse annotations do not work for xml files.
CMS-XML Selective promotion XML service not working correctly
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:
CMS-XML XML Scratch does not work with IMS FMT members containing special characters
Trying to delete an IMS FMT member using the XML below as an example: <?xml version="1.0"?> <service name="CMPONENT">
CMS-XML Advanced XML Reports - filtering doesn't work for multi-relational field
There is a problem when d efining reports on Advanced XML views, where filtering is not available for multi-relational fields. The problem is twofold:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs