Pros & Cons for storing Enumerations in Process Config or Database
When it is stored in Process Spec, Project admin is the only person to modify the enum. When it is stored in Db, we can grant edit rights to specific roles & remove the dependance of Project Admin.
Is there any other advantage in storing Enum in Db ? We maintain the template in one project and share it with 14 other projects. Other 14 projects use the process config of "template" project. Process Sharing. Pointers welcome. |
Accepted answer
Ralph Schoon (63.3k●3●36●46)
| answered Apr 15 '15, 6:34 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
My 2 cents:
In database
Pro: More fine grained permission to modify the literals e.g. by users that don't have permission to sabe the process template
Con: Does not work with process sharing
In Process XML
Pro: works with process sharing
Con: need permission to edit values
Chidambaram L selected this answer as the correct answer
|
Your answer
Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.