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 Binary/Trinary fields cannot be set to "Required". Form Action "make field required/optional" does not list binary fields. Deploy fails with "failed to validate and cannot be deployed" after an upgrade
Binary/trinary fields can never be blank or empty. They are always either checked or not checked (or true or false; or yes or no), but they are never blank. Setting them to required or optional does not change the funcationality of the form. They will alway have a value and will always satisfy the requirement rule. It
CMS-XML Space is removed as a selection for the binary/trinary field
For binary/trinary fields, when a space " " is entered for one of the selections so that it is a blank selection, this works and deploys without issue, however, when you open the process app from the repository, the space is removed and has to be re-entered before a deploy will complete successfully again. This is because the space is removed when the process app is re-opened from the repository, and Composer requires a value for the selection before it will deploy.
CMS-XML Binary/trinary field won't map successfully to checkbox in PDF widget
Development Manager 1.2Release Control 3.3 Requirements Manager 1.0Service Manager 3.1
CMS-XML Mass update on binary/trinary field gives a (Both) option
Development Manager 4.0Development Manager 4.0.1Release Manager 4.0Release Manager 4.0.1 Requirements Manager 4.0.1Service
CMS-XML Javascript MakeFieldRequired works incorrectly on binary field check boxes.
When you use the javascript function MakeFieldRequired to set a binary field checkbox required , the field appears as red and it is not possible to transition the item. A check box has a valid value when it checked or unchecked.
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.
CMS-XML Binary default value has 'No' selected even though undefined.
Development Manager 1.1Development Manager 1.2Release Control 3.2Release Control 3.3Release Manager 2.0 Requirements Manager 1.0Service Manager 3.0
CMS-XML Notification rule with binary field and non-single select field doesn't fire
Development Manager 1.1Development Manager 1.2Release Control 3.2Release Control 3.3Release Manager 2.0 Requirements Manager 1.0SBM 10.1Service Manager 3.0
CMS-XML Notication Rule: "Binary field is Equal to Checked" is not working as expected
Development Manager 1.1Development Manager 1.2Release Control 3.2Release Control 3.3Release Manager 2.0 Requirements Manager 1.0SBM 10.1Service Manager 3.0
CMS-XML Using form action with binary field and testing for "Not Checked" doesn't evaluate to true
Development Manager 3.5Release Manager 3.5 Requirements Manager 3.5Service Manager SOO 3.5
Pages [Next]

Welcome kb sso

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs