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 KM-Dim9: How to check out a file at revision 1 and check same file in as revision 1.1? How to change revision numbering to branched workset? Workset > Set Flags > Flags tab > select Branch as the workset type flag > select Forced Revision Generation
KM-Dim9: How to check out a file at revision 1 and check same file in as revision 1.1? How to change revision numbering to branched workset? Workset > Set Flags > Flags tab > select Branch as the workset type flag > select Forced Revision Generation
CMS-XML KM-Dim9: Add item: specified revision is ignored and 1.0 set
Unset the item type option "Use standard level numbering scheme for revisioning " in the Admin Console.
CMS-XML Dim10: How can we not allow the users to change the Revision Number within Dimensions?
This can be done by setting the workset flag or project flag of Revision Generation to forced. This also aplies to named branches.
CMS-XML Software Error: #724 Specifying revision number on initial check-in doesn't work
want to start at 0.1 for example) and you check in the workfile, it will have revision set to 1.0 (default). Workaround: Do an Actions | Create archive, then do the Actions | Check In and specify the revision number.
CMS-XML Dim9: General Client Issues: "Don't force new revision number on check-in" option does not work
Setting the option "Don't force new revision number on check-in" via the Administration Console was being ignored in the desktop client and web client.
CMS-XML Problem: Check-out and check-in default to incorrect archive revision numbers.
Check to see if users have "Default Version " set to any value ( ie.: 2.0 or some version greater than the baseline)
CMS-XML KM-Dim9: Reported Defect DEF91504: Revision numbering is no longer working automatic - using Dim 9.1.3.2
1. Define the item number scheme as being standard (switch on item option 11 in the admin console) 2. Create new workset and set it to be of type branch and select a single named branch for the workset 3. Edit an existing item - note the dialog,
CMS-XML KM-Dim9: Revision numbering in Dimensions
management rules are switched on for this item type and the minimum state where change doc is required is set to the initial state, then these latter settings will force you to
CMS-XML KM-Dim10: Reported Defect DEF106827: 'Don't force new revision number on check in' ignored for first revision
The item type UDOC has 'Don't force new revision number on check in' Enabled (Green check box on #5). In the desktop client, make sure project Flags has ' Revision Generation' set to 'Optional'. Edit/update or checkout revision 1 of a UDOC type item, the New revision window automatically populates with revision 2. This is an issue only on the 1st revision . Performing the same operation on revision 2 shows rev number remaining the same as expected.
CMS-XML KM-Dim9: How to Setup and Control revision numbering (or should I be using 'branch' or 'trunk' revision numbering)?
If a workset has the 'trunk' flag set , then item revisions are based upon the previous revision . If the first revision of an item within the workset is revision 1, then subsequent revisions will be automatically named 2, 3, 4, etc. If the first revision of an item within the workset is revision 2.5, then subsequent revisions will be automatically named 2.6, 2.7, 2.8, etc.
Pages [Next]

Welcome kb sso

My Recent Searches

Search Feedback

Are we answering your questions?

Additional Assistance

  • Submit a Case Online
  • FAQs