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 Responsive forms are broken on deploy; preview is correct
Responsive forms are broken on deploy; preview is correct
CMS-XML Responsive forms become corrupted when opened in Composer after an import
Responsive forms become corrupted when opened in Composer after an import
CMS-XML Title not found, when update auxiliary item with responsive form
Title not found, when update auxiliary item with responsive form
CMS-XML Plus sign to expand Message Address Details in Notes section does not work on Responsive Form
Plus sign to expand Message Address Details in Notes section does not work on Responsive Form
CMS-XML Using Multi Group fields with responsive forms results in not being able to read long group names.
Using Multi Group fields with responsive forms results in not being able to read long group names.
CMS-XML SBM: Responsive form with Rich Text fields containing large images may cause some data to be hidden
SBM: Responsive form with Rich Text fields containing large images may cause some data to be hidden
CMS-XML Problem: INT APPROVED: #1430 DEVELOPER 2000 ORACLE FORMS 4.5: CONVERSION FAILED WORK FILE MAY BE READ-ONLY OR UNSUPPORTED TYPE
It seems that the ORACLE FORMS interface doesn't like revisions created by Version Manager. If a user attempts to check out a revision that was created by Version Manager, he gets the above message.
CMS-XML Considerations when converting from Custom Forms to Online Forms.
OLD CUSTOM Forms and NEW ONLINE Forms use the same basic format for the package master records. Between the SHIPPED VERSIONS, only the 100 Report Distribution Information ONLINE FORM records have the same package master record keys as the OLD CUSTOM FORM records, but it is possible to make the NEW ONLINE FORM package master record look like the OLD CUSTOM FORM records, by altering field lengths and types, etc. , so that no conversion would be required.
CMS-XML SBM remembers SmartCard login at login form
SBM is setup to enable login form with a smart card login. Provide the client certificate when logging in, however, ensure that the client certificate does not transform to a valid user. The login form will indicate "invalid username/password".
CMS-XML Form elements with a "(Default)" color scheme turn transparent after upgrade to SBM 11
If you have elements on a custom form that used the "(Default)" color scheme in a pre-11 version of SBM (which is the default selection as indicated by the name), that color will actually get converted to transparent upon upgrading to version 11.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs