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 In Composer, single selection field shows too many options and causes confusion
In Composer , single selection field shows too many options and causes confusion
CMS-XML Composer crashes when using compare feature if a step in an orchestration contains a string greater than 128 characters in a mapping or option
If a reference to a part of a web service envelope is greater than 128 characters in a calculate step option or a mapping in an orchestration workflow, running a compare on the process app with cause Composer to crash.
CMS-XML Delete the last selection value in Composer causes Composer to crash
Delete the last selection value in Composer causes Composer to crash
CMS-XML Composer crashes when removing a selection on a condition on a form action
Composer crashes when removing a selection on a condition on a form action
CMS-XML Security token is sent even though Use SSO Authentication check box is not selected in Composer
Security token is sent even though Use SSO Authentication check box is not selected in Composer
CMS-XML In Composer, select the items referenced by typing first letter when adding an action
In Composer , select the items referenced by typing first letter when adding an action
CMS-XML Composer crashes when adding a value to single selection fields
When creating a new single selection field in composer that utilizes the 64 character name limit, composer crashes with the following error message - The name 'Insert Name of Single Selection field using more than 58 characters Value' is invalid because it exceeds 64 characters in length. The 64 character limit is not a true 64 character limit - It's really a 58 character limit since " Value" is added to the name when adding a value for the single selection field
CMS-XML List box size setting is overriden for multi-select fields after each deploy from Composer
However, when deselecting the override in Composer , deploying the changes, and setting the override again (for any reason) the list box size reverts back to a single box. The result is that any time a field is overridden, the list box value reverts back to 5. While you are allowed to override this in Application Administrator, the feature does not work in SBM Composer.
CMS-XML Composer exception occurs when selecting dependencies in special case
2. Setup sel2 as a dependent field of sel1, click on "Edit Restriction Value" and it will bring you to workflow dependencies tab, under "Restrict dependent field:", click on the available "sel2" field (attached screenshot). Composer crashes with exception as attached.
CMS-XML SBM Composer Service Mappings for web services provide wrong selection values for binary fields
SBM Composer Service Mappings for web services provide two selection values for binary fields and these are True and False. These values do not comply with SOAP standards which require true|false|0|1. This is why the web service response defaults always to the Boolean value 'false' regardless of what is intended in the SBM Composer .
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs