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 SQL Server: Incorrect SQL unique constraint violation occurs during SLS import when data contains characters that are not in the default SQLServer collator
drop index SLS_CATEGORY_UI_1 on SLS_CATEGORY; alter table SLS_CATEGORY alter column lower_name nvarchar(256) collate Latin1_General_100_BIN not null; create unique index SLS_CATEGORY_UI_1 on SLS_CATEGORY(lower_name);
CMS-XML Dim CM 2009 R2: Visibility of items / requests in global catalogue owned by products where users do not have a role is not restricted
Dim CM 2009 R2: Visibility of items / requests in global catalogue owned by products where users do not have a role is not restricted
CMS-XML Restrict by Item Type does not work for mass update
What are the steps to reproduce the problem? Create two items: one of the restricted type and one of another type. Search to find both items and check them Click "update all checked"
CMS-XML Dim: Web client gives error in info bar when previewing a change request: This content might not be displayed properly. The file was restricted because the content doesn't match its security information. Click here for options...
Dim: Web client gives error in info bar when previewing a change request: This content might not be displayed properly. The file was restricted because the content doesn't match its security information. Click here for options...
CMS-XML IE11 - actions toolbar does not restrict options based on Composer configuration
To Reproduce: Take a Process App and select a state or transition form and deselect some of the toolbar actions. Deploy and then submit an item . If you look at the form that you turned off some of the actions in IE11 then all are still shown.
CMS-XML KM-Dim9: Restricting Access to Products and/or Items, CDs, Objects
Users will not be able to see any objects owned by products on which they do not have a role. Even in the Global Workset they will not be able to see any such objects for which they do not have a role on the owning product. This includes Catalog and relationship displays.
CMS-XML SBM: How does "Restrict by Role" work with the "Transition All Items" privilege?
After this step, privileges are viewed as a whole collection. The system does not consider if the privileges came from the user directly, a group, or a role. The user will either have a privilege or not have a privilege.
CMS-XML Process app does not list incident type values for restricting a transition by type
An incidents process app upgraded to SBM that uses the Incident Type system field does not list the incident type values when trying to restrict a transition by type. Also, when clicking the "Edit item types" link at the bottom of the Restrict By Type tab on a transition, you are taken to the primary table, but the Incident Type field is not selected. This is caused by Composer not recognizing the Incident Type field (database field name of "INCIDENTTYPE") as being the field that is storing item types.
CMS-XML Properties not visible if the item is not checked out
The Restrict By Role properties of a transition are not shown correctly, if you do not have the item checked out.
CMS-XML Dim10: Find Item Dialog dropdown for Product does not produce results in Find Now tab except for current project
The Find Item dialog is limited by the current project and therefore the Product dropdown only affects the Find Item dialog under the following circumstances:
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Product Demos

Dimensions CM: Working with items, part 1 (demonstration)
This Dimensions CM demonstration shows you how to perform impact analysis to determine which files are affected by specific changes

Additional Assistance

  • Submit a Case Online
  • FAQs