Find Answers

Filter Search Results
All Operating Systems:
All Products:

All Solution Types:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML TT661 The Web service import function is not expanding elements with a reference attribute.
TT661 The Web service import function is not expanding elements with a reference attribute.
CMS-XML Getting "cannot create node for non-element context node: [#document: null][org.jbpm.bpel.sublang.xpath.XPathEvaluator]" running orchestration.
Getting "cannot create node for non- element context node: [#document: null][org.jbpm.bpel.sublang.xpath.XPathEvaluator]" running orchestration.
CMS-XML Dim cm 14.2: jenkins job fails with "FATAL: Unable to run changelog callout (IOException: Exception calculating changes (IOException: Unable to run calcRepositoryDiffs (IllegalArgumentException: The nested element needs a valid project to work on)))"
Dim cm 14.2: jenkins job fails with "FATAL: Unable to run changelog callout (IOException: Exception calculating changes (IOException: Unable to run calcRepositoryDiffs (IllegalArgumentException: The nested element needs a valid project to work on)))"
CMS-XML Order in which HideSection and ShowSection Javascript functions are called is important
HideSection() and ShowSection() can be used to hide certain form elements like Tabs from a custom form. However, upon hiding an element this element is being moved into the foreground for a moment. This means that if you ShowSection a tab first, then HideSection another tab afterwards, what's left on screen are the fields from the hidden tab.
CMS-XML Failure for Count function
WriteErrorToErrorTable.CreateAuxItemsResponse.return[1].item.id.tableIdItemId The following error occurs - cannot create element for step with numeric predicate beyond the next position: [(DefaultNameStep): mwsdl:Item][org.jbpm.bpel.sublang.xpath.XPathEvaluator]
CMS-XML Structured working data cannot be used as parameters in orchestration functions
Because that working data TTCase is generated as: <variable name="TTCase" element ="ns8:TTCase" /> No messageType attribute.
CMS-XML ZMF: Call to 'base' approvePackage web services gives error "java.io.IOException: Non nillable element 'approverEntity' is null"
The challenge here is that these web services cannot be used asis. They must be implemented within a programming language to manage session state. You must write an application (e.g. using Java) to perform a logical unit of work (LUW), understanding that you are responsible for managing session state for the LUW. Customers using the base ZMF web services must code an application to perform the ZMF function of interest (e.g. logon to ZMF, run the package approve web service, receive the response
CMS-XML Value of "Complex Type" Element is Lost
XPATH function . Using the STRING
CMS-XML KM-Dim9: Documentation on user roles, $roles, allowed role functions - Explained role functions to client
It allows the user to move a change document from any state in its lifecycle to any other state regardless of any normal or off-normal paths. Also, the CHANGE-MANAGER can edit Detailed Problem Descriptions, Action Descriptions and in general update other elements of a change document regardless of its state or pending role. This generally given to the individual responsible for managing the change management portion of your project such as configuration management personnel.
CMS-XML Refreshes on a referenced app open in another instance of composer will stop working if design element was checked out
Refreshing with nothing checked-out in the referenced application is fine and doesn't seem to break anything. Only if you refresh the referenced app between a check-out and a check-in (doesn't matter if it's before or after you make the change) will it result in breaking the refresh function going forward.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs