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 Restrict by Role on certain transitions not acting as expected or certain transitions seem to be available or unavailable to certain users unexpectedly.
Check and make sure there aren't any restrictions that have been placed on the Group or the Item Type in this screen. If there are any adjust these restrictions accordingly and see if you get the desired result.
CMS-XML XML Import restricts names to 32 characters.
This was fixed for the Transition Name, but remains for other field names, which is reported as defect DEF81718. Before it's fixed, customers can change the following from "NameType" to "LongNameType" in the "workflow.xsd" file in the "bin" directory.
CMS-XML Dim12: SBM2DM Connector: Error: Could not start transition from state Development to state QA (-1) Transition '' is not valid for transitioning item number 2511 (item 34) in table 1006. [(:TSPrimaryItemStartTransition: Error starting transition Start transition failed.
The above error is occurring because there is a Restrict by Rule on the transition within SBM. If the rule is removed, the synchronization works.
CMS-XML SBM: Submit and other transitions randomly fail with error: The transition "Submit" was not completed. Error attempting to add item to database.
Violation of PRIMARY KEY constraint 'TABLE-NAME'. Cannot insert duplicate key in object 'dbo.TABLE'. The duplicate key value is (99999).
CMS-XML KM-Dim7: SQL-0304(22034) ORA-00001: unique constraint (PRODUCT>.PENDING_ACTIONS_K1) violated
Remove duplicate lifecycle entries for the same from/to transition
CMS-XML Dim10: 1019 - DBIO: Oracle Error occurred SQL-0304 (22034) ORA-00001: Unique constraint (pcms.pending_actions_k1) violated.
One cause of this is incorrect data somewhere in the role assignments, object type definitions or lifecycle definitions. For example once in a while a control plan will indicate a transition from the same lifecycle state to the same other lifecycle state with one transition defined as NORMAL and a second defined as off-normal. In some instances, the problem can also be seen with the lifecycle of the Item Type or Request Type within Admin Console.
CMS-XML Software Error: #748 PRO: Restrict by Promotion Information
Software Error: #748 PRO: Restrict by Promotion Information
CMS-XML Problem: Admin makes a change to privileges Restricts a User in the Access Control Database
Problem: Admin makes a change to privileges Restricts a User in the Access Control Database
CMS-XML Problem: VMINET 6.x: Can't restrict report by Date/Time, only Date
Problem: VMINET 6.x: Can't restrict report by Date/Time, only Date
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...
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs