After long investigation, I have found that it is not possible to differentiate them. The resolving is done pre-transaction-create. Also, there in the transaction object, there is no property saying that it is a "child" transaction.
There is no OOTB report anything but yes. It's possible to capture and build such a report using the event system.
All of those actions will trigger events in the backend. It would be relatively simple to write an event that captures it and writes it somewhere like a database and do the reporting tool.
Here's a good starting point: https://github.com/...
Like Chris mentioned in the comments, please provide more information so people would be able to help you. But, here are some pointers that may help you identify and solve the problem:
Are you using Curlette's ConfigurationManagerEventSystem class in your custom event handler to open the configuration XML and return the Configuration object instance? Your ...
You need to have Service Host process running on publisher also. If it is not running, then probably your event system code will not trigger.
Besides this, check the usual: configs, filepaths, check if it is loading properly, check the access.
If I understand correctly, you want to have Page Regions which are:
Separately BluePrinted (the Regions may be shared from the parent Publication, whereas the Page itself is not).
Separately Secured (a user which is allowed to edit the Page may not be allowed to edit those Regions).
If so, it sounds like you want to use Include Pages for those Regions. ...