PLC WF Dependencies

Andy Knipp

OK really strange. Got a overall project with several sites (on several branches) deploy to the same docroot. Share templates and components.

We have noticed some site specific files (.js etc) are being deleted.

When I submit branch1/site1/pagea.page, for some reason it thinks some asset from branch2 js/branch2.js is a dependency. So it deploys that file as well (even though it does not exist on branch 1), and it deletes the object from the prod server, royally **** off everyone who cares about branch2.

Thing is, these objects are not shared, they are branch specific. So branch1 should not even know about branch2.js.

My choices are: turn off deletes for files, keep copies of all js on each branch (and then hope people remember to update all), or see if I can fix it.

So I need to get an idea how does the PLC decide a dependency exists ? If I parse the EA and XML of the page is that sufficient ?

TIA

Andy