OOTB PLC Workflow not autoattaching dependencies

Leigh

We are experiencing problems with OOTB PLC Workflow in TS 7.2 production environment.

Problems exist for existing .pages when we do the following steps:
1) Amend template (eg. to add new component) and submit to staging
2) For same template, select Get Latest Components with update option (NOT overwrite) all existing .pages
3) Submit template to staging
4) Edit existing .page using DCR XML component for content amendments
5) Save and regenerate .page
6) Send .page file to LiveSite Runtime via OOTB PLC workflow
7) View changes in LiveSite Runtime url - CHANGES ARE NOT DISPLAYED
8) Check workflow email - no dependent files are included in workflow task

Then we created a new .page using the same DCR xml, published and deployed new .page. This time, the workflow task included all dependent files and we were able to see our changes in LiveSite Runtime.

We have come to the conclusion that whenever we make changes to .template or layout .xml file, we cannot update any existing .pages.

Is there any way we can enforce existing .pages to include any dependent files in PLC workflow tasks via autoattachment whenever we make changes to layout xml or template files?

Any advice will be most appreciated.

Thanks,
Leigh