Why does changing some substitution variables values not change the amx.bpm.app status to 'Out of Sync'?

Why does changing some substitution variables values not change the amx.bpm.app status to 'Out of Sync'?

book

Article ID: KB0087464

calendar_today

Updated On:

Products Versions
TIBCO ActiveMatrix Service Grid -
Not Applicable -

Description

Resolution:
Description
=========
For example, if you change the substitution variables ec.maxMsgThreads and ec.coreMsgThreads and refresh the application view, you see that the amx.bpm.app status remains 'In Sync'. Now change the substitution variable ‘pe.engineThreadCount’ and the amx.bpm.app status will change to 'Out of Sync'.

Resolution
=========
The reason for this is that the platform only marks an application as 'Out of Sync' if the substitution variable is directly referenced by the amx.bpm.app itself. In the case of the two "ec."  substitution variables, they are referenced by resource templates and not the amx.bpm.app, which is why the amx.bpm.app status does not change to 'Out of Sync. As these two "ec.*" substitution variables are referenced by a thread pool resource template, once changed the resource instance "amx.bpm.ec.threadpool" status changes to 'Out of Sync'. 
Conversely, the "pe."  substitution variable is referenced by the amx.bpm.app and therefore the status does change to 'Out of Sync'.

Issue/Introduction

Why does changing some substitution variables values not change the amx.bpm.app status to 'Out of Sync'?