AdityaJ

"lock" object editing is counter intuitive

Hello Lennelei, Thank you for your request, I am able to reproduce this issue in my environment. This issue is reported as a bug in our Change Management System. Please find the JIRA issue link for your reference: * JOC-1165: "Lock" object editing is not able to deploy the changes once value is given to Max. non-exclusive Tasks. Please follow the JIRA Issue JOC-1165 for release date and updates. Thanks and best regards Aditya Jain

How to clean up dead process from JOC console or JobScheduler database

Hello David, Thank you for your request. As per your request here is the process of clean up of database can be resolved by following below article: Database Cleanup Scripts When you are using file order sink then you don't need to add ad hoc order, it will start running once a file is found in file source folder. So if you don't want your job chain to start running then just don't put files in source folder. For more details you can follow below article: How to configure File Order Sink - job chain...