Is the Technology Roadmap a single all-encompassing roadmap?
Posted: 20 Jun 2016, 19:08
I'm fairly new to Essential, and am self-taught. Today I set out to build a Technology Roadmap. I was successful at building a simple roadmap, but less successful as I added complexity.
My desire is to have multiple technology roadmaps aligned with the teams that support them. For example, I would like to have a roadmap for Database Management, and a roadmap for Java Middleware.
When I edit the name='Technology_Roadmap' instance of the class Report_Constant and associate two Roadmap_Model class instances in the "Associated Instances" slot, the Roadmap_Model data comes out merged in the Technology Roadmap report. The <h2> heading is a concatenation of the two names appearing as 'Database ManagementJava Middleware', and the milestones and roadmap entries are merged.
What I would really like is an <h2> section for Database Management followed by a roadmap, then an <h2> section for Java Middleware followed by a roadmap.
Is there a limit of one Technology Roadmap, or am I doing something wrong?
Thank you,
Jeff
My desire is to have multiple technology roadmaps aligned with the teams that support them. For example, I would like to have a roadmap for Database Management, and a roadmap for Java Middleware.
When I edit the name='Technology_Roadmap' instance of the class Report_Constant and associate two Roadmap_Model class instances in the "Associated Instances" slot, the Roadmap_Model data comes out merged in the Technology Roadmap report. The <h2> heading is a concatenation of the two names appearing as 'Database ManagementJava Middleware', and the milestones and roadmap entries are merged.
What I would really like is an <h2> section for Database Management followed by a roadmap, then an <h2> section for Java Middleware followed by a roadmap.
Is there a limit of one Technology Roadmap, or am I doing something wrong?
Thank you,
Jeff