Is it possible to prevent an check-out(read change) on an dataset (PDF) if it's not set any status on it but the item revision has one?
Reason for this is that I have an external converter to generate a PDF and the workflow initiates this conversions through a subprocess in the workflow.
When the subprocess is started it continues with a set status task but at that moment the PDF isn't present. Therefor the original dataset get a status and when the PDF is added it's without status so I can therefore make check-out and modify the PDF.
Would like to block this to avoid any mistakes even if it's an PDF which users normally don't touch.
Any suggestion is appreciated.
Production: NX184.108.40.206 MP04 + TC10.1.7.1
Testing: NX220.127.116.11 MP07 + TC18.104.22.168
I'll give it a try,
what I would like to find is a handler that could be used in a workflow that reads the actual status from item revision and attach it to the PDF dataset.
This situation occurs when we have already released the item revision and creating the PDF after the release.