When you create a new item in your project (e.g. a use case), it gets added to the end of the list in the owning package. You may change the order of items in the project browser by selecting an item (excluding definitions) and clicking the green up and down arrow buttons located immediately above the project browser tree. Alternatively, you can use the keyboard shortcut, Ctrl+Arrow key.
If you would like the ID numbers of the items to match the order shown in the project browser, select Tools / Renumber. On the renumber IDs dialog, select the package(s) you'd like to change the formatting in, set your prefix and starting IDs for each of those packages, then select only those item kinds you'd like to change and click Perform Renumbering.
In the example below, all use cases in the Loan Origination package will be renumbered with a "TLA-" prefix, and will begin at the number 15:
I am working on a large(ish) project with 12 users, some of the users complain that when they reopen folders the packages have been re-ordered?
Has anyone else seen this behaviour?
If so is there a way to stop it happenning?
Thanks
... I mean that when the re-open a higher level package the packages within it are re-ordered in a different order than they were positioned with the green arrow
Keith, where are they seeing the packages ordered differently? In the project browser itself or in a report or something else?
In the project browser. They sub packages actually have a date in the name like 'Nov 15 2010' and are initially ordered in date order, so it's pretty easy to see that they get re-ordered. It almost (and I mean almost) looks like they are ordered by the first number in the name, except for one or two execptions. Not sure if that is a clue or a red herring.
Wow, that's odd. the storage order is saved, so that shouldn't be happening. I'm not able to reproduce what you've described based on the information that you shared. Any other clues that might help? What version of CaseComplete are you using? Are packages being added to the project before you're seeing this happen?
Any other clues you can share would be great!
R