Data Capture Lifecycle Viewer (Application)

[Emir]

Duh, of course, sorry for wasting your time!

[daniel.victoria]

Hi John,
I have added a new Slot in the Business Capability class. I would Like to see that in the business/core_bl_bus_cap_summary_new.xsl Report is the detail section. This report Looks a bit different than the rest of the reports? I have added the new field in the detail section right below the description(line 1039) at line 1040:
<label><xsl:value-of select="eas:i18n('Business Cap Status')"/></label>
<div class="ess-string">{{{breaklines this.business_cap_status}}}</div>
<div class="clearfix bottom-10"></div>

The label shows up but not the value. I have checked the report contains the new field and its value.

I am assuming the "this" in line this.business_cap_status is a handlebar variable of current instance, where exactly this is getting populated from the report?

Appreciate any help!
Thanks
Parveen

[jmk]

Hi,


'this" refers to the result of the "integration/api/core_api_import_business_capabilities.xsl" report. This report creates a JSON content which is imported by "business/core_bl_bus_cap_summary_new.xsl" and then used by handlebars.js ...

So; if you want to use the new slot (business_cap_status ?) : you should first modify 'integration/api/core_api_import_business_capabilities.xsl" to add its value as a field in the capability JSON records..

J.-M.

PS : there is some caching in place for the "YYYY/api/XXX.xsl' reports (in platform/tmp/reportApiCache/). You may first modify the JSON cached result before trying to modify the "business/core_bl_bus_cap_summary_new.xsl" report...

[sven.kuhnert_ger]

Hello,

I have a question about the Apploication Lifecycle Viewer (nn). What data needs to be captured so that I can filter the view by Application Capability as it works in the Essential Demo?

I have entered the following data:

3 Applications (Application1, Application2, Application3)
3 Lifecycle_Models (1 per Application) with several Lifecycle_Status_Usages
1 Application_Capability
1 Application_Service (realises Application Capability, provided by the 3 Applications entered before)
3 Application_Provider_Roles (link Application to Application_Service)

The Lifecycle are shown in the Viewr, but I can´t filter by Capability as it is possible in the Essential Demo

Thanks inadvance

[JohnM]

Can you drop this in your user folder and change the url of the view to xsl=user/...

The let me know what the counts are at the top of the screen please

core_el_lifecycle_viewer.xsl.zip

[sven.kuhnert_ger]

Hello,
Unfortunately, it didn't work. The behaviour is unchanged, filter by capability is still not possible.

Have I captured all the relevant data?

Thanks in advance

[JohnM]

Sorry Sven, this isn't a fix, we need to work out what data is being sent. There should be 2 counts at the top of the screen, capsCount and serviceCount, can you see those? it should look like this. :

Screenshot 2024-09-25 at 18.41.25.png

[sven.kuhnert_ger]

Oops, sorry, I had misunderstood that.
No, it dosn´t show any hits:

[JohnM]

Hi Sven,

That suggests that the Application Capabilities aren't mapped to Application Services. Have you capture these and related them?

[sven.kuhnert_ger]

Hello,
from my point of view I captured and related the Application_Service:

App_Service.png

[JohnM]

Sorry, this one has us confused, leave it with us.

[JohnM]

Hi Sven,

We're still puzzled by this. Can you put this view up and let me know the counts in the top left please

core_el_lifecycle_viewer_CHECK.xsl.zip

[sven.kuhnert_ger]

Hi John;

sorry for the late reply.

Here the result:

Lifecycle_Viewer_Check.png

br
Sven

[JohnM]

Sorry it took so long, we finally worked it out. The view was looking for a business mapping, despite it using App caps. Fixed version attached

core_el_lifecycle_viewer.xsl.zip

[sven.kuhnert_ger]

Thanks, it works now.
One small question: For what business mapping was the view looking for (original core_el_lifecycle_viewer.xsl)? May the original behavoir mad more sence?

THX
Sven

Lifecycle_Viewer_final.png

[JohnM]

I'm not sure why but it was using a property on application where the services are scoped to those that support business processes, it used to say which of an application's services could support a logical process you have defined. We changed the view to use a different property that returns all services for an app regardless of use.

We do this so you can say 'these applications in our organisation could support these logical processes' (useful for rationalisation analysis). The physical process maps the actual use of services by applications, a 'does use' rather than a 'could use'. The property we switched to says 'the application has all these services it can support'.

To have the 'could support', you have to map the processes to the services, which can take a while, so I think you are ok taking your current route.

Hope that all makes sense