Hi Everyone,
Background: We setup SPARX as an organization wide/shared repository in one database instance. All projects has a separate package as their workspace. We also have govern/trusted content on a separate package, so all projects can reuse and account in their project development.
The Element Status raised passionate discussions on our group. Some sees it as a life cycle status versus other proposing to use it to whether is trusted/verified, or work in progress.
So we need to:
* classify all elements and connectors whether trusted or WIP, or was trusted but no longer in use.
* We also know that projects will reuse these elements and might propose new connectors as a result of adding relationships to current state, or propose a relationship for a future, but yet still consider non-trusted because it is not yet governed, so we need to differentiate between what has been trusted, and its life cycle. also other projects might propose similar relationships between same elements, and we need to identify who is proposing what? and make sure projects can only see their own architecture elements and relationships (we doing this by using model views).
We looked at the Tagged Values for this, and it was strait forward, but it is time consuming and in some cases you need scripts to do bulk remove, but edits, and bulk adds (very error prone and labour intensive). The reason we looked at the Tagged Value as a solution is because connectors don't have a status attribute.
Any suggestion on how deal with such case? or are we completely off on this?
Another Question about the Element Status.
The "Proposed" Status is always the default one, and if I removed all the statuses from the project settings, and set new statuses, there is no way I can set a default status. so if "Proposed" is not part of the list, the default is always blank.
Is there is a ways to setup a default status that is not a "Proposed"?
Thank you for your help.
