Does anyone else have any advice or practical tips for automating these processes? Maybe someone lacks programming skills. It is worth using the web development service https://admiral-studios.com/web-development-services This will help to adjust and optimize the website and bring it to a new level of use.

This would be helpful for local authorities as well. I would be able to schedule a regular job to modify subject heading fields so that the already available jobs for linking and changing subject headings would work for local authorities as well.

This would be very helpful. We have work orders we'd like to place on particular items that need additional processing before being loaned to another patron and adding work order automatically would help us accidentally triggering holds.

This would help us as well. We need to regularly run a bib norm process to add a local field to IZ records in order for them to display in Primo VE with the correct resource type. We don't have bandwidth or enough staff expertise for scripting something using the API, or to do the same every time we need to regularly run a manual-only job/process.

I enthusiastically support this proposed functionality. I've created logical sets for various record groups to keep our publishing management tags up to date. We publish bibliographic holdings to OCLC weekly, and we have to manually run the Synchronize Bib records with external catalog job on all sets with members. This is just one local example.

We have been fighting with this as well. I support this and would love to see added functionality so staff can automate routine processes, normally handled by jobs.
There are some daily tasks or specific functions that you handle by running a job, that would be better automated to reduce human error in setting up the job each time and addition of task to someones task list (remembering to do it and how it is set up each and every time). An example of this is to use a set of records, update the set each day, the use a job to change a flag. Each and every time it is needed you have to manually update the set, the select the right job and set, then select which aspect you wish to change. This is would better automated.
Canned reports and the ability to create report templates to preform specific functions that mimic the choices given through the "jobs" process when the ability to choose when and how often would be amazing.

Ability to schedule the "Withdraw physical items task job" to occur once a month or whatever the frequency we choose.

Supported. There are several use cases at our site for this as well, to automate regular jobs currently done on a manual basis. It really should be possible to do this natively within the Alma application (like other customers, we do not have ready access to local programming/development resources to go the API route).

Implementing this idea would help us out a lot. I much prefer native Alma solutions over the APIs, if they are available. The APIs are helpful in certain circumstances but from a systems management perspective, this seems like something better managed within the application itself.

Agreed! While there are alternatives using the API, including the ability to schedule jobs to run on sets allows Alma administrators (who may not have time/support for programming around APIs) to set up automated jobs, which would reduce the failure points and allow them to effectively monitor those jobs.

Very important for us too at Hebrew University of Jerusalem

A very needed ability.
We also need such a development for the media conversion job, so that we can run it at night.