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 $CHANGES() E-mail Template Tag Returns Incorrect Values for Backlog Priority Field
$ CHANGES () E-mail Template Tag Returns Incorrect Values for Backlog Priority Field
CMS-XML Values changed in a driving field via form action fail to restrict dependents
Values changed in a driving field via form action fail to restrict dependents
CMS-XML Deleted user value in form prevents transition even when field is not changed
Description: Deleted user value in form prevents transition even when field is not changed. The case for this issue is as follows: A form with 5 fields
CMS-XML Unable to change default values for selection field via Web Administrator.
To override the default value , either go to Mashup Administrator and override it at the project level or go to Mashup Composer, change the default value and redeploy.
CMS-XML When changing the field in a form action the "Value" doesn't stay selected.
When you use the "a field [operator] a value" action and set it up correctly it works fine but if you then change the field it points to the "Value" part isn't held onto even though it looks like it does in the overview window. If you click on the " Value " part after changing the field name even though the overview shows the value the value selection field will be blank.
CMS-XML Dim12: Evemt does not list attribute as changed if new value matches value from previous revision on check-in
If attributes for an item type are defined as: Stored per revision, default as specified and the default for the attribute is null
CMS-XML Changing value of Single Select or Single Relational field gives error "Currently processing previous request, please wait until the request completes."
This problem does not happen during the submit transition. Also, it only happens when the first dependent field is changed from "(None)" to something else.
CMS-XML Changing value of Single Relational field throws error "Currently processing previous request..." Custom Form
Since the upgrade to SBM 10.1.3. in certain circumstances single relational fields can show the following error:
CMS-XML Changing value of Single Select or Single Relational field in a transition other than submit gives an error
Changing value of Single Select or Single Relational field in a transition other than submit gives an error
CMS-XML Listing Report: Previously selected values for relational field filter is not remembered when edit report
Steps to Repro: a) Create a report that filters on a relational field (for example, Project contains "project A, project B"). b) Save and run the report.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Viewing work area and repository changes (demonstration)
This Dimensions CM demonstration shows you how to use the Windows Explorer integration to view the changes made to a work area and a repository.

Additional Assistance

  • Submit a Case Online
  • FAQs