I though about using event callout interface to build a custom DLL trigger for this verification purpose. However my colleague has checked and a file size arrives into events only after the file or new revision has been already added under source control.
Another possible solution can be doing such post-commit checks using PulseUno Chain or Jenkins job (integrated with Dimensions CM). There file size can be analyzed and chain/job failed notifying via email or MS Teams a committer, other necessary people that there were delivered potentially unexpected file(s).
Can you describe in more details - where does the requirement about file size come from? Is that to prevent temporary files being mistakenly delivered or anything else?
-- Thanks, Alex
-- Alex Shevchenko Sr Development Manager Although I work for OpenText, I am speaking for myself and not for OpenText. If you found this post useful, give it a “Like” or click on "Verify Answer" under the "More" button.
Support
Documentation
Learning Services
Partner Programs