Find Answers

Filter Search Results
All Products:
Source:
 
Ask a Question
Example: "Database could not be verified"  
Tips | Start Over | Solutions | Alerts | Patches | Defects  
Pages [Next]
  Results
CMS-XML Form Action does not display message.
A Form Action set to display a message when an change is made to a Multi Relational field does not display the message. Seems to work for all other field types.
CMS-XML Form Action Support for System relational fields
Form Action Support for System relational fields
CMS-XML Rest Grids do not work with Sub-Relational fields in 10.1.2 (Example: PDF Widget)
1. Have two Process apps (A and B), A is referenced to B and has a Single-Relational and Sub-Relational field. 2. Have a form (Submit form ) on A process app with RestGrid that uses Sub-Relational field as a parameter 1. Try to submit an A item.
CMS-XML SetMultiListValues does not fire change event for single or multi select and relational fields
Workaround: Use form actions Manually call FireChangeEvent on the independent field(s).
CMS-XML Subrelational field value does not display value when updating from a relational field value that initially had no value in the subrelational field
Sub-relational field value does not display value when updating from a relational field value that initially had no value in the sub-relational field ... Select a relational value where one of its sub-relational fields has a null or empty string value . ... Open the form again (via update) and select a different relational value . The sub-relational field that was empty before is now empty regardless of what you select for the Relational field
CMS-XML Using a Multi Relational field pointing to another Primary Table isn't taking permissions into account.
... Using a Multi Relational field pointing to another ... ... have a multi relational field that points a ... ... fill out my form and click the ... populate the multi relational field it shows me ... ... change the mult relational field in Composer to ... you open a form with this field ... ... 0&Template=newbody&RecordId=45&TemporaryRecordId=0&FolderId=0&ProblemId=0&CopyTableId=0&CopyRecordId=0& Action =&PostTransitionId=0&&SolutionId=14&transid=285 Thread Number: 12
CMS-XML Sub-relational fields do not populate value until after post transition
Sub-relational fields do not populate value until after post transition
CMS-XML Notifications do not evaluate sub-relational field values
Notifications do not evaluate sub-relational field values
CMS-XML Notification emails show asterisks for sub-relational field values
For example, there are two workflows (Workflow A and Workflow B) that use the same primary table and there is a relational field used in Workflow B to point to items in Workflow A. There is a sub-relational field based on that relational field that points to a selection field that is used in Workflow A. This selection field is used only in Workflow A, but the notification is running against Workflow B where the selection field is in the Not Used field section.
CMS-XML Impossible to set/select value for Relational Field in a Rule
Existing rules will work correctly (those created before 10.1), but no changes can be made to such rules and no new checks for Relational Fields can be created. There is currently no workaround for this.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with Items, Part 2 (demonstration)
This Dimensions CM demonstration shows you how to copy item revisions to a work area using the Get and Update commands, deliver a modified file from a work area to a stream using the Deliver command, and action an item revision

Additional Assistance

  • Submit a Case Online
  • FAQs