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 Tabs/sections do not hide on mobile interface when form action is unchecked in composer
Tabs/sections do not hide on mobile interface when form action is unchecked in composer
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 HTML 5 Warning Message overwrites field warnings after SBM 11 upgrade
When the forms are generated, HTML5 is used for compactness and efficiency, but when the form is then displayed in the browser that is connected to an SBM system where the Web Admin interface has HTML5 disabled, that causes the message above to appear. ... Disable the HTML5 features in Composer and re-deploy or ideally enable HTML5 in the Web Admin.
CMS-XML HTML 5 Warning Message overwrites field warnings after SBM 11 upgrade
When the forms are generated, HTML5 is used for compactness and efficiency, but when the form is then displayed in the browser that is connected to an SBM system where the Web Admin interface has HTML5 disabled, that causes the message above to appear. ... Disable the HTML5 features in Composer and re-deploy or ideally enable HTML5 in the Web Admin.l
PDF Scaling for the Enterprise
The SBM client component is SBM Composer . SBM Composer is a modern smart-client application built using the Microsoft .NET platform. It provides an extremely rich interface with features such as ribbon bars, drag and drop, zoom and unlimited undo/redo. SBM Composer is the design environment from which you can find, customize, and create process apps. SBM Composer uses
CMS-XML Help not available in System Administrator and Composer with 64 bit installation
(2) unzip the "studio.zip" file in ...Serena\SBM\ Composer \help" folder.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs