Re-using Items Across Projects

Have you ever wondered how to import a package, or share common elements across projects? How about making a project template that you can use as a starting point down the line? Or, maybe you just want to be able to re-use a certain set of actors or dictionary terms in multiple projects.

Nearly all CaseComplete elements - dictionaries, actors, use cases and more - are owned either directly or indirectly by packages. What's a package? You can think of them like folders within your Windows directory structure; they serve to organize your project. In addition, you can save each package in a separate file - which is the default setting - to allow each package to be checked out and worked on independently in a shared project/team environment. Packages can own multiple elements - such as terms and actors - similar to how files are kept within your Windows folders (and subfolders).

With the improved package import feature in CaseComplete¹, you can now store information - such as a common set of actors, or a default project format - in one or more template projects, and more easily import that information into other projects.

Start off by creating your source project.

• This will be your source for future imports, and needs to be kept in its own location.
• It can be either a local-only or a shared project.
• The project must contain at least one package below the top level, since you won't be able to import the top level project file into other projects.
• Ensure your sub-packages are saved in separate files. As mentioned above, this is the default setting when creating new packages.

Build it!

• Create your template packages - actor sets, dictionary terms, requirements, etc. - in one or more sub-level packages of your source project. Name them in a manner that will remind you of their contents for the import step below.
• You can have a single package per project, or you can make a single project your global source for all of your desired imports by creating multiple sub-packages with different content.
• Once you've got your template packages set up just the way you'd like them, make sure you know where the project is stored (note the working folder - not the repository - if your project is shared) and close it out.

Import it!

• Create/open up your destination project, then choose Connect / (Import) Package^2,3 from the ribbon bar.
• Browse to your source project location noted above and choose the appropriate template package you'd like to import.
• If you're working with a shared destination project, you'll be prompted to check out the destination package, if you don't have the lock already.
• Choose an owner in your destination project, and you're done!
• Repeat as necessary to include all the desired template packages in your new project.

If you need to make changes to your destination project, go ahead! Just remember that any changes made after the import won't be reflected in your source project. The imported template packages are, after all, copies of the originals. Similarly, if you make any changes in your original template packages you'd like to be reflected in any other projects, those packages will need to be re-imported, overwriting any changes that have already been made in your destination project(s).

As always, if you have any questions, comments or would like additional help, email our support staff at [e-mail].

---

¹This process applies to CaseComplete 2012 R2 and later.

²You can also use this method to import legacy dictionary/glossary files (.ucg) created with previous versions of the software into your newer projects.

³Versions prior to CC2014 use File / Import-Export / Package File