How to store filters persistently that would not disappear after cleanup of cookies

The filters in the JobScheduler JOC GUI are stored in cookies due to the implementation in Javascript.

• Since release 1.3.7.x you can set the filters by editing the configuration file custom.js.
  • This file is stored in the ./config/operations_gui directory.
• For releases < 1.3.9 you will find the custom.js in the ./config/html directory.
• For further information about custom.js  see How to configure JOC - an overview.

Filters are added like this:

 _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

• Example 1:
  The filter projectA contains all objects that are stored in the Hot Folder subdirectory projectA:
   

 _project_filter['projectA']        = '^/projectA/';

• Example 2:
  The filter ftpJobs includes all jobs that have a suffix _ftp in the job names:
   

 _job_filter['ftpJobs']             = '_ftp$';

• Example 3:
  The filter someJobChains contains the job chains myFirstProject/myFirstJobChain and mySecondProject/mySecondJobChain:
   

 _job_chain_filter['someJobChains'] = '^/(myFirstProject/myFirstJobChain|mySecondProject/mySecondJobChain)$';
 //or
 _job_chain_filter['someJobChains'] = '^/my(First|Second)Project/my(First|Second)JobChain$';

• Example 4:
  The filter hideTest1AndTest2 contains all objects that are not stored in the Hot Folder subdirectories dev/test1 and dev/test2:
   

 _project_filter['hideTest1AndTest2'] = '^/(?!dev/test1/|dev/test2/)';