JAMS

Scheduling of sequences.

Using email trigger jobs.

Notification emails.

None I can think of.

Automate workflows across languages

folder watches

UI could be improved

History search function could be more user-friendly

Integrates with PowerShell

Can be called remotely

Has stored credentials

When setting up new jobs, what each option does is quite confusing as it can take a while to luck across it working sometimes.

The online documentation for Jams needs to be considerably improved. I want to look up a field and know what it does, what input is expected, and what things to be careful of when submitting it.

There needs to be much more done to provide in-application support documentation. The biggest problem my team has with it is frustration that they don't have the time to mess with why a job isn't running and they logically can't tell why.

I job should never run and not show something in the monitor. If submit is clicked, the Monitor should say something helpful why it did or didn't run.

The WorkFlow Modules in Jams has helped tremendously with the Sequential processing of the files

Multiple Execution options from Powervshell to SQL stored procedures to SSIS packages makes it easy for legacy code executions

The Alert Notifications to page someone when a job failed is extremely useful

We could definitely use some better import Export features coming from other tools especially Automate since both are owned now by the same company

While submitting setups if you want to submit and select/Unselect only a few jobs a Select/Unselect all feature could be helpful

Technical Support Response

Partner with

GUI

Patching

Enhancements timing

Training depth

Failover not graceful

The granular security model allows us complete control when defining access levels to the JAMS functions and features, as well as the individual folders and jobs we define within JAMS.

There are many built-in features when it comes to defining job schedules. For instance, you can schedule a job to run at a specific time, on certain days of the week or month, based on the completion of another job, or on an interval, etc.

The ability to define multiple notifications or alerts based on the success, failure, or exit code level of a job is very convenient.

It would be very helpful if the application had the ability to display help text based on where the cursor is hovering on the screen. There are many times when a brief explanation of an on-screen prompt would be very handy. For example, when you attempt to Cancel a job from the Monitor, you are presented with the checkbox that says "Reprocess completion?" It would be very nice if you could hover over the prompt and see a pop-up help screen that explains what happens if you check this checkbox. The same applies to all the checkbox options presented when you attempt to "Release" a job from the Monitor.

easy to configure

job scheduling is great whiteout issue.

history shows the information about the job very well

global search

Automation of scripts allowing for different use cases including interval and daily runs

Simple implementation of source code to automate which is unlike many other solutions

Has solutions for many use cases allowing for a wide range of solutions for company issues

Documentation both in documenting the capabilities of JAMS and documenting how to interact with JAMS via powershell cmdlets.

Has functionality to have agents in other domains but there is no way to either do pre processing of input files before running source code on agent or transfer the input file or output file to and from the main client

Some Error messages are truncated thus not allowing for full debugging

The text editor is plain and not drawn out meaning that development usually happens in vscode or another ide

Documentation tab of a job is unusable. It would be nice if we could either upload files that document the job or link to a website that documents the job

More detailed failures when JAMS module cmdlets fail

Watching for files

Running Power shell scripts

JOB notifications of failures to teams

Being able to interface / run other programs as either dos window, Power shell window, Python window through configurable execution methods

Purging JAMS history by Parameters, like dates and # of copies to keep of a job

Being able to configure a hot backup to take over in the event a Primary JAMS Server goes down, the backup automatically kicks in after 3 minutes. - High Availability mode

Being able to set up variables that can be used in JOBs / Sequences to hold login information (encrypted), date ranges or other Job Parameter values. And be able to programmatically updated by Power shell scripts to track progress between runs of the same job: count of orders processed, API Skip values when retrieving orders, when the API call only returns X amount per call and you need to get all available orders with multiple calls

JOB logs can be put anywhere on network for other users to access - IT allowing of course. With the high availability option, this is Great, since you don't have to check each of the JAMS Servers for a log when a fail over occures

GUI Color selections - we use colors to determine environment - DEV, TEST, PROD. Some of the color combinations are difficult to read.

With the upgrade from 6 to 7, We lost the ability to view all jobs, or all Sequences (workflows) across the system, now we have to go subfolder to subfolder when looking for a job.

Manages daily jobs across multiple machines, viewable on a single pane of glass.

Seamlessly deal with our "end of day", while adjusting for holidays and early close days (typically before holidays).

Securely manages FTP credentials for connecting to trusted partners.

Prior to JAMS I organized various batch job runs with a user friendly naming process (job, machine, date, etc). I had to jump through hoops to get JAMS to replicate by having a post-completion job rename and copy the log.

Natively support JAMS commands in Powershell7.

Failsafe guard to prevent runaway jobs that submit other JAMS jobs that were improperly coded. i.e. A throttle setting for new JOBS. I once had production go down when hundreds of jobs used up our daily license allocation in under a minute.

I have similar (but different) Execution Methods that would benefit from a shared template. Current setup is awkward to change.

I'd love my job Definitions to be natively linked to github for version control.

Run powershell scripts

Execute SQL Agent Jobs

Excellent all-around scheduling tool

I think the user interface could be a bit more intuitive.

When something goes wrong it sometimes just provides a generic error message

Job Scheduling

File movement/management

Encryption/Decryption with PowerShell Modules

Sequence viewing for wide parallel job triggers.

Vendor fit - ability to deliver in a timely manner and ongoing support.

Compatibility - fits in with our modernisation vision and integrates with Windows Server 2019.

Non-functional requirements - user friendly interface, using job history is easier and uses less code.

Cancellation of jobs – there's no easy way of cancelling one job while other jobs are running.

Stop and restarting services – this causes disruptions to workflows.

Event based scheduler

Multiple Integration capabilities

Several types of jobs, Linux, Windows and other command line

Nothing in specific

JAMS manages our daily multi tasks reporting databases refresh

JAMS automates various source data import and export

JAMS makes SQL Server log shipping log copy and restore working together with reporting databases refresh.

JAMS is a very powerful and useful tool

Schedules pretty much any type of job SQL, Powershell, Other applications, and Workflows.

Encryption/decryption.

Monitoring of job statuses.

Alerts when things go wrong.

Automated retries.

Document the REM statement a little better; it took me quite a bit of digging to figure it out and would be better if one could use standard comment characters like in other languages (although with Powershell scripts, the Powershell one works ok.

It's important to comment on the code in the source tab especially when changes happen, and you want to keep track of historical changes.

Definition of Date parameters (i.e. - Today, TodayDate, Workdays, Day) that gives great flexibility in scheduling

Copying/cloning of specific existing processes that makes implementation of new processes easy

Easily accessible logging to review/fix issues when they occur (in Dev and Prod)

When searching for Definitions, it would help if you had a right-mouse click option to 'select last component accessed' ...One has to type a job name, setup name over and over if switching between the job and setup tabs

For Development (vs Production) Parameters setup (i.e. - for Jobs) allow updates on the 1st screen. One has to double-click or click the Properties button to update the particular parameter, but could save significant time if updates were allowed at the parameter list level...

In History, instead of 90 days, retain last 30 occurrences, of course depending on the type of scheduling (if applicable - daily, weekly, monthly). List of last occurrences is more valuable than runs in the last 90 days

Automates jobs that run 24/7.

Allows us to have a dashboard to monitor jobs.

Notifies us via alerts of failed jobs.

JAMS performs poorly for jobs that run for a very long time.

Would like greater usability to create JAMS jobs.

v6 has reduced capacity for # of jams jobs allowed.

Scheduling jobs in different timezones

Scheduling repeated recurring jobs

Able to set the resource count to 0 when doing patching etc

Also has a thick client and web api tool

Needs AWS support for cloud initiatives

Needs better swagger documentation from whats already present

In-app monitoring of job scheduling and completion

Providing tools to adapt schedules based on changing conditions

Robust options to rerun and otherwise manage failures

Requires use and knowledge of PowerShell to get the most out of it

While scheduling options are far superior to other tools, we have still had circumstances where schedules we wanted to set up were not available in a single job

Organizing jobs is a pain once they've been created - difficult to move jobs to different folders, and cloning existing jobs can cause new runs to be submitted

The Web App is woefully inferior to the desktop app

Scheduled Tasks

Trigger or Conditional based execution

Workload Automation

Scalability

Some of the Example jobs are harder to convert to Use - for example a workflow

The documentation - Although the Support Team are super, they are fast and accurate with questions on live chat or email, but I don't feel it would be appropriate to ask questions on setting up a job from scratch.

Runs a complex series of jobs in the correct order using dependencies.

Transfers files on and off-premises at scheduled times.

Alerts on-call staff of critical successes and failures, enabling restart.

An underlying Job Definition Language would be nice for source control and automation.

Running jobs/application in multiple languages, Python, Powershell etc..

Smooth UI to create and manage jobs

Flexible options for scheduling jobs and setting triggers

Inclusion of a better coding interface such as Visual Studio Code to improve the script development process and more easily debug jobs.

Improvement of the Authentication layer; to better integrate with Active-Directory/Azure-AD across the Desktop and Web-Interface to simplify access to managed groups.

Easy to Navigate

Change jobs on the fly

Look ahead at what's scheduled

The web interface is a bit clunky

It would be nice to have all connections in one central location. SQL agents and connections are located in different tabs.

By default it would be nice to have a day view of all jobs scheduled.

the scheduling with the ability to add holidays to the work calendar. so jobs wont execute.

support for a wide range of execution methods, python, powershell, cmd batch, oracle, informatica integrations makes it particularly easier for users to build their jobs/sequences

always looking for GMSA support if applicable

if there were more report functionality?

if agents could "round robin" through the scheduler if you're licensed for X, only X can be active but have the scheduler "auto manage" the activation/ deactivation of agents so that only X agents are running at any given time.