up to date description 

previous description:
As a user I would like to associate workflow templates with software components

1. When users apply templates to execute a workflow, we will provide an option to redirect them to a form if a higher level of customization or dependencies is required as these features are not currently supported by Backstage's software template functionality (Ford's request)
2. In the long term, we aim to explore a solution for incorporating this high level of customization within the scaffolder plugin itself. This could involve collaborating with the Backstage team to enhance the plugin or creating an additional plugin to support these extra configurations
3. When users select a template from the creation page, we will give them the option to choose an existing Catalog entity in the first step of the wizard. If they don't select one, a new component will be created. It's important that users can only choose entities they have permission to access
4. The creation of the catalog entity should occur in the background, with the repository including a catalog-info.yaml file, and the entity should appear live in the catalog
5. Each catalog entity will display previously executed workflows under the Workflows tab. We also aim to include potential workflows that users can apply to the specific catalog entity
6. It appears there is an option to edit a catalog entity created via a template. Currently hidden for RHDH users, we plan to enable this functionality (targeted for version 1.7, scheduled for release in September). When users click "edit" on a catalog entity they will be directed to a pre-filled wizard they can edit