Distributing Job Definition Files
By default, the flat files you create and distribute will be read from the users <installation directory>\APP directory. This means that you must instruct your end users to place the job definition files in that directory, or give them a means to do so automatically.
You must also make sure that the end users have appropriate access rights for any jobs in the job definition file that you distribute. When an end user activates a batch job (for example, by clicking a button in a window), this window (and the database table on which it is based) is considered to be in the foreground. All other tables accessed by the batch job are also in the foreground. Therefore, the end users must have the appropriate rights (insert, delete, update, select) in the foreground. For more information, see the USoft Authorizer Help.
In addition, each job definition file must have the same name as the application against which it runs (with the exception of the ".job" suffix).
So, if new jobs are defined, a new job definition file must be created and distributed, that contains all the existing jobs as well as the new one(s). How you distribute these files, and what instructions you give to your end users depends on how they are going to run the jobs.