Hi everyone!
Ok, so I've figured out how to load data massively, now I'm trying to model some of my architecture, for instance, here we have something we call 'Heatmap', with this we evaluate the products we use, and we divide them by 'Service' for instance we have a group called Application Development and there we have all the products for coding, and each of this product also has a 'Heatmap Status', as the status of the product in the market, like: 'Emerging', 'Preferred', 'Eliminate'...
I try to do my classes, so they were related like 'Technology_Component' and 'Technology_Capability' sort of thing, but when I try to publish the report it does nothing at all...
I've already read and learned XML and XSL, but, do you have any other examples on how to create my own classes and therefore make the XSL for the report??...
Thanks in advance!
Ana B.
Doing some reporting
-
ana.bautista
- Posts: 14
- Joined: 26 Jan 2011, 22:32
Nevermind... I guess if I don't use the architecture you are proposing there's no sense at all to ask this 
-
jonathan.carter
- Posts: 1087
- Joined: 04 Feb 2009, 15:44
We encourage everyone to add to the meta model to meet their requirements and recommend that you take an 'extends' approach rather than 'customise'. This means that you can take advantage of what's already there and add the missing parts that you need, which makes it easy to use future extensions and updates.
This same approach applies to the Views. When you've extended the existing classes, the existing Views / reports will work to show the out-of-the-box elements and you can then quickly add to the XSL to include the new extensions that you've defined.
We have already built some HeatMap views for understanding Issues and how they relate to the Business Component Model. This is a framework that can be used to create heatmaps for a variety of things and we'll be releasing this as part of the forthcoming Information and Data pack. Let me know if these might be of interest and we can explore how to use them.
OK, so that's some background. In your case, things like the Technology Product catalogue should still work, assuming that your Technology Products and Technology Product Roles are based on the Essential Meta Model definitions.
It sounds like you've add some additional classes to manage your heatmaps. Depending on how you need them to be viewed, you could add these elements to the existing core_tech_prod_def.xsl.
If you need something that presents issues across the entire Technology Product Catalogue, have a look at core_tech_product_list_by_capability.xsl which is a catalogue that colour codes each product depending on the lifecycle status of the Technology Product Role for that Product to provide that capability (there is a hidden layer [Technology Component] that is navigated to perform this query). This might provide some useful ideas about how to approach your heatmap.
I appreciate that the whole XSL approach to rendering Views may seem daunting but actually, once you've seen how it's done, extended or modified an existing View, there's actually a small number of patterns that are re-used again and again - and this is also true of the queries. For building web-based views, the XSL approach to the querying and rendering is actually very productive and powerful once you've got yourself started.
Hope this helps
Jonathan
Hope this helps.
This same approach applies to the Views. When you've extended the existing classes, the existing Views / reports will work to show the out-of-the-box elements and you can then quickly add to the XSL to include the new extensions that you've defined.
We have already built some HeatMap views for understanding Issues and how they relate to the Business Component Model. This is a framework that can be used to create heatmaps for a variety of things and we'll be releasing this as part of the forthcoming Information and Data pack. Let me know if these might be of interest and we can explore how to use them.
OK, so that's some background. In your case, things like the Technology Product catalogue should still work, assuming that your Technology Products and Technology Product Roles are based on the Essential Meta Model definitions.
It sounds like you've add some additional classes to manage your heatmaps. Depending on how you need them to be viewed, you could add these elements to the existing core_tech_prod_def.xsl.
If you need something that presents issues across the entire Technology Product Catalogue, have a look at core_tech_product_list_by_capability.xsl which is a catalogue that colour codes each product depending on the lifecycle status of the Technology Product Role for that Product to provide that capability (there is a hidden layer [Technology Component] that is navigated to perform this query). This might provide some useful ideas about how to approach your heatmap.
I appreciate that the whole XSL approach to rendering Views may seem daunting but actually, once you've seen how it's done, extended or modified an existing View, there's actually a small number of patterns that are re-used again and again - and this is also true of the queries. For building web-based views, the XSL approach to the querying and rendering is actually very productive and powerful once you've got yourself started.
Hope this helps
Jonathan
Hope this helps.
Essential Project Team
-
ana.bautista
- Posts: 14
- Joined: 26 Jan 2011, 22:32
Hi Jonathan!
Well, yes, there's one thing to add some classes, but to break all the realtionships between layers (i was doing this) is another, so, I've been capturing some Applications and checking out some of the reports that came along with the essential, and I've bumped into slots that don't even exists, like the case in core_app_def.xsl:
So, how are these slots mapped??
Thanks,
Ana B.
Well, yes, there's one thing to add some classes, but to break all the realtionships between layers (i was doing this) is another, so, I've been capturing some Applications and checking out some of the reports that came along with the essential, and I've bumped into slots that don't even exists, like the case in core_app_def.xsl:
I've looked for the slot named 'application_support_model' and there's no sign of it, so I looked below, in the template 'Support_Model' and looked for each and every slot mention and those slots don't exist!
<p class="mappingYWhite"><img src="images/support_call1.gif" alt="IT Support" width="31" height="34"/> IT Support</p>
<xsl:if test="not (count(pro:own_slot_value[pro:slot_reference='application_support_model']/pro:value) > 0)">
So, how are these slots mapped??
Thanks,
Ana B.
-
jason.powell
- Posts: 32
- Joined: 04 Feb 2009, 15:01
Hi Ana,
We are pleased to see that you are looking to re-use the existing classes and relationships. As Jonathan mentioned, extending the base meta-model will enable you to take advantage of extensions, both from the Essential Project Team as well as other members of the community.
Having said that, if there are things that you need that are not supported by the meta-model, we would love to hear about them so that we may consider them for future releases.
Regarding your core_app_def.xsl question, the code that you have quoted is actually a placeholder that we have kept in the view for a future Service Delivery capability that we have piloted. We are still in the process of finalising this meta-model extension, which means that the Support Model slots referred to in this view have not yet been included in the published release (we apologise if this is misleading).
Again, if you have any specific requirements to capture Support Model information for applications or any other area, it would be great if you could add them to the related discussion thread that we have set up here.
Thanks,
Jason
We are pleased to see that you are looking to re-use the existing classes and relationships. As Jonathan mentioned, extending the base meta-model will enable you to take advantage of extensions, both from the Essential Project Team as well as other members of the community.
Having said that, if there are things that you need that are not supported by the meta-model, we would love to hear about them so that we may consider them for future releases.
Regarding your core_app_def.xsl question, the code that you have quoted is actually a placeholder that we have kept in the view for a future Service Delivery capability that we have piloted. We are still in the process of finalising this meta-model extension, which means that the Support Model slots referred to in this view have not yet been included in the published release (we apologise if this is misleading).
Again, if you have any specific requirements to capture Support Model information for applications or any other area, it would be great if you could add them to the related discussion thread that we have set up here.
Thanks,
Jason
Essential Project Team
-
ana.bautista
- Posts: 14
- Joined: 26 Jan 2011, 22:32
Hi Jason,
Well, thanks for the reply, yes there are certain things that I've already mapped with our needs and I need to know if these things are going to be included in your next release:
http://is.gd/hkMFdP
I appreciate all your help!
Kind regards,
Ana B.
Well, thanks for the reply, yes there are certain things that I've already mapped with our needs and I need to know if these things are going to be included in your next release:
http://is.gd/hkMFdP
I appreciate all your help!
Kind regards,
Ana B.
-
jonathan.carter
- Posts: 1087
- Joined: 04 Feb 2009, 15:44
Hi Ana,
Thanks for this. We've been having a look through this spreadsheet.
There are some really good requirements in here and we'd like to bring this into ECP-6 which is where we are working on how to provide support for Service Delivery.
Many of the things you have got in your mapping will work best from the Service Delivery part of the EA Support section of the meta model. We will give you an early version of the extension pack for this to try out with your requirements, when we have factored in your mappings.
I will add a new post about this in ECP-6 as we work through this.
Thanks
Jonathan
Thanks for this. We've been having a look through this spreadsheet.
There are some really good requirements in here and we'd like to bring this into ECP-6 which is where we are working on how to provide support for Service Delivery.
Many of the things you have got in your mapping will work best from the Service Delivery part of the EA Support section of the meta model. We will give you an early version of the extension pack for this to try out with your requirements, when we have factored in your mappings.
I will add a new post about this in ECP-6 as we work through this.
Thanks
Jonathan
Essential Project Team
