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 Query at Runtime Embedded Reports display error when clicking Show Full Interface
- create a listing report in SBM UI which uses a Query At runtime field and give it a reference name - open the process app in Composer - and add this listing report to a state form as an embedded report (the QAR parameter should get selected automatically) - deploy the process app
CMS-XML WorkCenter form styling incorrect and does not match preview in Composer for aligning fields
The form styling shown in Composer differs from that in WorkCenter and may be misaligned incorrectly. Classic interface is fine.
CMS-XML Preview form of classic in Composer is not representative of the default upgrade to10.1.4.x whereby HTML5 is turned on
With the upgrade to 10.1.4.x the Form Preview in Composer of classic is not representative of the default interface after upgrade. After upgrade the default is that HTML5 is switched on in the classic interface . The Work Center view is a better representation of the HTML5 classic.
CMS-XML "Unable to create EndPoint" message when attempting deploy of imported ProcessApp
If you import a ProcessApp to a system where it has never existed and there are some missing settings in Endpoint definitions, you may get the message above and the ProcessApp will not deploy from Composer or even from the AR interface .
CMS-XML After upgrade to 10.1.3.1 and deploy, forms are very short (about 1 inch tall)
This problem only happens when using a shell interface and only after deploying from Composer 10.1.3.1. Example Steps: 1) Install SBM 10.1.1.2 and Release Control (which uses a shell interface).
CMS-XML RSS widget no longer works due to unavailable external service
The RSS widget that used to be in the SBM Composer form palette used an external service that is no longer available. Therefore, any custom forms you built with this widget will no longer work.
CMS-XML Printable view not available after 10.1.1.1 upgrade
The workaround is to force Composer to re-generate the Process App. You can't just re-deploy.
CMS-XML Printable view not available after 10.1.1.1 upgrade
The only workaround is to force Composer to re-generate the ProcessApp. Re-deploy is not enough - you must make Composer regenerate and re-publish. For example, check-out the forms tree and check in again, with no changes. It is not necessary to create a new "Print form", though that can be done at the same time and will then cause the forms to be generated correctly.
CMS-XML Users cannot select subprojects in searches in the WorkSpace interface
Users cannot select subprojects in searches in the WorkSpace interface
CMS-XML Common log entries are entered without namespace value
Common log entries are entered without namespace value
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs