Post

3 followers Follow
0
Avatar

Sharing a dictionary between projects

I am working in a multi team member environment, where all of us are doing separate projects within the same Line of Business inside the organization. I would like to set up a dictionary for the Line of Business that each of us can access from within our individual projects. I can't seem to get it to work, and I don't see anything in the knowledgebase relating to 2013. My goal is to have one definition for any term that is used across the LOB, then each of us will have our own supplemental dictionaries for our own applications.

Kchase

Official comment

Avatar

Hey Kevin. Regrettably, this sort of file sharing doesn't quite work in the tool today. There's no way I'm aware of to have a single dictionary file that gets "accessed" from different projects - no sort of central file that can be updated by multiple projects, that is. You can certainly start with a single dictionary that you then import into each of your individual projects, but it's not a "live" update that will subsequently edit the original dictionary file. Check this out to learn more:
https://casecomplete.zendesk.com/entries/21933278-Re-using-Items-between-Projects
And if there's anything else we can help with, let us know - here, or by emailingsupport@serlio.com .
Jason

Jason Payne

Please sign in to leave a comment.

3 comments

0
Avatar

For anyone who may come across this question, Jason was able to help me work something out. Essentially, I have set up one "project" in Case Complete, with folders under it for each of the different business areas that the entire team services. That way, each person can check out their "Folder" within the project, and we all share a dictionary that is at the same level. There isn't a way to systemically limit who can access the Global dictionary, but we'll handle that via policies. Its really fairly elegant, you just have to make sure your reports select just your project, and the global dictionary. I did this by adding a parameter to the report we use to generate the full BRD, and we key in the project name we want. Then, we don't get other people's use cases, etc. in our BRD. But, by "hard coding" the template to also include the global dictionary in the "Glossary" section of my BRD, I got everything I needed. The folder structure looks like this (using the tutorial as an example, and imagine each of the sub folders are a separate department within the business, with their own application to handle their unique business processes); Loan Processing: ------ Global Dictionary ------ Loan Accounting ------ Customer Service ------ Delinquency Processing

Kchase 0 votes
0
Avatar

Creat a package called Glossary (or dictionary or whatever). Add it to your son repository. Then add all your glossary terms to that one package. Nothing else goes in that package. Then open that package ever time you open any other package. If someone needs to add a term, they have to check it out of son, add the term, and check it back in. Other team members will then get notified that their glossary package is out of date. Since a lot of terms get created at once, it might be a good idea to hold a brainstorming session at the beginning of the project to generate an initial list.

Mary D'Arrigo 0 votes