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 Deployment hangs on process app with a dozen subworkflows
If you try to deploy the process app that has quite a few workflows defined (e.g. 12), AE will never finish the deployment.
CMS-XML Creating table in global mashup should stop you from using a system table name. Incoming table already exists
Trying to deploy the Global Mashup in composer you may see an error like the following.
CMS-XML Validating a process app hangs after upgrade
Validating a process app hangs after upgrade
CMS-XML Mashup Snapshot Promotion fails with some Relational Field Reports
The report will reference primary table records, by UUID, however, primary table records are never included with mashup snapshots. So this will always fail on Promotion.
CMS-XML Patch Context Process app with INCLUDE statement to global fail validation. 09R4.01
A process app in a patch context. This process app references the global app. Scripts in the process app that include scripts from the global can't validate because the scripts from the global are not written to the validation directory.
CMS-XML Process App validation passes even when "Validate AppScript" fails in Composer
The expected result is that if "Validate AppScript" fails , the Process App validation should also fail , and the Process App should not deploy successfully.
CMS-XML Deploy stops working for a Process App - no errors - just never ends
If the deploy just seems to hang after this statement then do other Process Apps deploy ok? Does an earlier version of the Process App deploy ok?
CMS-XML Unable to import process app from .msd with error "Error Failed to import webservice from ...
Expected result: User is able to import process app
CMS-XML Web Administrator does not respond after user exits business mashup web interface
If you have accessed the Web Administrator through the Business Mashup web interface closing the interface cause the Web administrator to stop responding. This is due to the Single Sign On cookie being invalidated once user exits from main interface while Web Admin window is still open.
CMS-XML Composer reports 'Load attempt failed' for report without any columns
Steps to reproduce: 1) Create new process app with application 2) Add new listing report to the process app
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs