Hide Forgot
Description of problem: The design time governance UI uses the term 'Design Time' in several areas, including the label in the top level tab (shared with S-RAMP and Runtime Governance) and elsewhere. 'Design Time' as a UI label isn't meaningful for new users or those not familiar with SOA concepts. Something more descriptive, associated to functional capabilities would help new users understand the intended use of the tool, e.g. 'Release Workflow' or 'Lifecycle Workflow'.
Happy to do this if someone would like to make a decision regarding what the specific text should read.
My suggestion is "Project Workflow" I think. Still trying to get the UI up and running again so I can take another look at the contents of this tab to see if there are any conflicts or problems with this name. Not sure if "project" is a term we should not be using for some reason - but it feels like anything a developer is trying to track through from concept to production would be a 'project' in a sense!
I think Project Workflow could be fine in the short term but it's too narrow for what we have planned in future releases. In the future we'll have various UI screens that manage different aspects of what we consider Design Time Governance. For *this* release the only UI (other than the very generic Task Inbox) in that tab is the Deployment Lifecycle Management UI. Deployment Lifecycle Management is one application of design time governance, but we certainly plan on having more. Not all of them will be related to projects or even workflows. :) It's a pain, I know, and I don't have any great ideas. I agree that the current labeling is bad. I also think that any of the proposed changes would be better! I'm just trying to add context so someone more creative might be able to come up with something perfect.
Someone does need to make a decision about any labels we might change as part of this BZ.