The filters in the Job Scheduler OperationGUI are stored in cookies because it is only implemented by javascript.
But since release 1.3.7.x you can set the filters by editing in the configuration file custom.js.
This file is stored in the ./config/operations_gui directory.
For releases < 1.3.9 you find the custom.js in the ./config/html directory.
For further information about custom.js see here.
The filters are edit in the form
_job_filter['filter name'] = 'regular expression'; //to set a job filter _job_chain_filter['filter name'] = 'regular expression'; //to set a job chain filter _order_filter['filter name'] = 'regular expression'; //to set an order filter //or use _project_filter['filter name'] = 'regular expression'; //which is effective for jobs, job chains and orders simultaneously
- Sample1:
The filterprojectA
contains all objects which are stored in the Hot Folder subdirectoryprojectA
:
_project_filter['projectA'] = '^/projectA/';
- Sample2:
The filterftpJobs
contains all jobs which have a suffix_ftp
in its names:
_job_filter['ftpJobs'] = '_ftp$';
- Sample3:
The filtersomeJobChains
contains the job chainsmyFirstProject/myFirstJobChain
andmySecondProject/mySecondJobChain
:
_job_chain_filter['someJobChains'] = '^/(myFirstProject/myFirstJobChain|mySecondProject/mySecondJobChain)$'; //or _job_chain_filter['someJobChains'] = '^/my(First|Second)Project/my(First|Second)JobChain$';
- Sample4:
The filterhideTest1AndTest2
contains all objects which are <span style="color:red;">not</span> stored in the Hot Folder subdirectoriesdev/test1
anddev/test2
:
_project_filter['hideTest1AndTest2'] = '^/(?!dev/test1/|dev/test2/)';