• A correction to the SQLStoredProc Execution Method to save changes to the job source.  Previously, changes were not saved unless the authentication type was changed.
• A correction when adding new job definitions through the Job Definition wizard to allow clicking "Edit...".
• An enhancement to trigger definitions to wait for the triggered job to complete before resetting for trigger variable events, job events, and setup events.
• Added support for drop down lists for agent nodes in job\setup submit options.
• Added drop down for username in file events of trigger definitions.
• An enhancement to SQLCommand, SQLStoresProc, and SSISDirect execution methods to display results result of SQL queries to the job log.
• Added support for the Symitar add-on including Workflow Activities for Symitar.
• A correction to avoid "ExecuteNonQuery requires an open..." error message when submitting a setup that contains jobs that have reports.
• An enhancement to add a scrollbar to About--> Server status.

• Added support for PSExecutionPolicyPreference parameter.
• Added support for ErrorActionPreference parameter.
• A correction for deleting an agent.  The JAMSScheduler service no longer need to be restarted to fully deleted the Agent listing. 
• Added support for SQL execution methods to now support :connect, :setvar, :out, :ON ERROR and $(VAR) substitution.
• A correction to SQL execution methods to use V2.0 of the .NET Framework.  
• A correction for jobs that have multiple threads writing to the log file and was being run via a JAMS Agent, a synchronization issue could cause the connection to fail and it would continue failing when we reconnected.
• A correction for complex setups that include jobs that have file dependencies that could result in a deadlock.

Regarding the "PSExecutionPolicyPreference" and "ErrorActionPreference" parameters, these were added to all of the PowerShell execution methods but, only on a new install.  We don't change existing installations.

The PSExecutionPolicyPreference sets the execution policy for the job, this will eliminate the issue of having to do a Set-ExecutionPolicy before PowerShell jobs will work.  The ErrorActionPreference is set to "Stop" so that PowerShell jobs fail if they hit an error.