Make Jobs API deal with JobNames instead of IDs
When you want to use Jobs API to trigger a job you have to give the JobID.
When you define the job (integration profile) the ID is invisible. The definition of one integration profile leads to the creation of several jobs with several IDs.
To define an API trigger you have to search the ID of the wanted job manually by calling "GET /almaws/v1/conf/jobs" from here
To make it all worse the ID of all jobs inside an intergration profile changes when you save a profile after changing a part of it. As one profile contains several jobs you can be sure this really hurts as you don't notice it.
One day later you see that half of your jobs are not running smoothly anymore because they use the API to trigger IDs that are not existing anymore (because they were changed, although you cannot remember to have changed that particular Job - of course not, because you didn't).
The jobs already have canonical names (combination of integration profile name and job class). They don't change whenever you change the profile.
I would suggest to use the names of the jobs for triggering rather than their volatile ID.
Florian Steinborn
shared this idea
Hello All,
This idea has been closed as part of a cleanup process for ideas older than two years with fewer than 20 votes.
This cleanup process is necessary to streamline our idea management process and ensure that the most relevant and impactful ideas receive the attention they deserve. If you still feel strongly about this idea, you may submit it via the NERS process.
We value your feedback and encourage you to continue submitting and voting for ideas that you believe will enhance Alma.
Alma Product Team