We are beginning our catalog planning & design and I would appreciate your input on a few questions:
- Is anyone publishing additional information concerning a Service within a Request Offering form? Information such as the following: features and benefits of the service, additional information on pricing/fees associated with the service, links to reference documents, etc? Or has someone expanded the default Service definition to include additional content beyond name, description, value proposition, and price description?
- If you have expanded the Service definition, what suggestions do you have to make this information visible to your users (something beyond the out-of-the-box Service list view)?
- Has anyone built a more content-rich service catalog outside of Heat (intranet, SharePoint), and linking directly to the Request Offerings within Heat?