Release notes for RunMyJobs releases 2024.1.0.0 through to 2024.1.0.2

Before: When PeopleSoft jobs are deleted that are monitored by RMJ, RMJ ignored the removed message. When the Job is killed within RMJ the killed job is not removed from monitoring.

After: This has been fixed.

Before: If you allow just one spooled file as output retreived from AS400 you must specify the correct spooled file number.

After: You can now use *ONLY or *LAST for the spooled file number to retrieve a specific spooled file.

*ONLY will find the first entry in the list of spooled files.
*LAST will find the last entry in the spooled files.

Before: It could be that an error message was shown that we didn’t fill in mandatory parameters when LOV’s should find the display values in huge EBS chains.

After: This has been fixed.

Before:
It was not possible to limit the download of PeopleSoft spool files, bases on the size of of the file.
After:
It is now possible to set a maximum file size for the spool files. If the actual file size exceeds the maximum size, as set
by Process Server Parameter ‘JobSpoolMaxSize’, the file will not be retrieved. Specifying this file size limitation is only
possible if the extra functionality package ‘RAI_RUNREMOTE’ is activated in PeopleSoft.

Before: An error message (e.g.

ERROR 2023-10-19 23:52:24,752 GMT [Redwood Job Thread Pool: T<>JDBCService worker 0] com.redwood.scheduler.jdbc.service.impl.JDBCJob - Error disabling dbms_output for Process <process Id>: SQLException (CODE=17041, STATE=99999): Missing IN or OUT parameter at index:: 2)

was thrown for every finish of an Oracle JDBC job.

After; This has been fixed.

Before: There was no support for fetch clauses in high-level SQL.

After: High-level SQL supports fetch clauses now. E.g. The statement - “Select * from Job fetch first 100 rows only” - will return the first 100 rows.

Before: The export process is throwing exceptions while exporting non-exportable objects.

After: The export process should be handled non-exportable object.

Before: A Process definition for HTTP POST that specified a Content-Type of application/json resulted in a charset=UTF-8 being added by default. This charset was also added by default for non-text Content types including image/jpeg, application/octet-stream, multipart/form-data and application/x-www-form-urlencoded for example.

After: A Process definition for HTTP POST that specifies a Content-Type of application/json will not have charset=UTF-8 added by default. It is only added by default for text and xml content types such as “text/plain” and “text/xml”.

Though if the charset is explicitly included in the [Headers] section, it will be used. for example:

[Headers]
Content-Type=application/x-www-form-urlencoded;charset=UTF-8

Before: In 9.2.9.2/9.2.10.0 an issue was introduced where IntelliSearch queries would generate an incorrect query when combing results. For example the search string jd:aa jd:bb would only return results where the job definition had both aa and bb in the name, instead of aa or bb.

After: IntelliSearch queries now correctly combine results. For example the search string jd:aa jd:bb returns results where the job definition has either of aa or bb in the name.

Before: When refreshing local cache related to libraries, there is a short period of time where its configuration is not available.

After: Improved the library configuration reload process to avoid situations where configuration is not available.

Before: Mail Connector did not support client credentials flow with client secret for MS Graph.

After: Mail Connector now supports client credentials flow with client secret for MS Graph. To use a client secret add a new entry to Connection Settings of a Mail Connector using MS Graph:

• Property Name: redwood.connection.oauth.use_client_secret
• Property Value: true

The field Password in the Mail Connector will then serve as input for the client secret instead of the user’s password.

Before: Redwood application upgrade fails from version 2023.2.0.0 to 2023.3.0.0 if SqlServer database is a case sensitive.

After: This should be resolved.

Before: In 2024.1.0.0, users without edit privilege for an object, would see a popup with an HTTP 500 error when attempting to edit that object.

After: Users see the edit page with a warning on top that they cannot edit that page.

Before: RMJ was running on Tomcat 9.0.82, which is vulnerable to CVE-2023-46589.

After: RMJ is now hosted on Tomcat 9.0.83, which is the latest release and without known vulnerabilities.

NOTE: The configuration of RunMyJobs limits the impact of these vulnerabilities, making the believed risk of exploitation low, however the version is being upgraded out of precaution.

Before: File events were only being detected by polling the affected directories periodically by the Platform Agent
After: As performance improvement, Platform Agent on Linux now also makes use of the OS’s inotify functionality, when available.
(See documentation for additional information about how to enable/disable, and the restrictions for the file event definitions to be able to make use of inotify).

Before:
A failure in the execution of child job by the job-processor could also log a ‘Bad file descriptor’ error in stderr.log. This error was a result of the failing job (execle() system call) and not a cause.
However, the failure prevented the cause of the failure (the ‘OS error’) from being logged or sent as an operator message.

After:
In the unusual event of a failing execle() call by the job-processor, we now successfully log the associated OS error.

Before: Existing SAP variant values were removed if they were not explicitly filled during SAP job submission

After: Existing SAP variant values are preserved if they are not filled during SAP job submission.

Before: Potential NPE when running SAP_ImportApplicationServers

After: Avoid NPE when running SAP_ImportApplicationServers

Before: SAP process server getting shutdown by error messaged “Invalid arguments supplied for SNC-API call”

After: SAP process server will not be shutdown by error messaged “Invalid arguments supplied for SNC-API call”

Before: SAP_Info job will be in error if the description field of release has not been set in SAP

After: Check if the field has been set properly

Before: When an parameter has a LOV that retrieves data from EBS all rows are passed from EBS to RMJ. This could have issues with performance and memory.

After: Default we will retrieve 256 rows from the EBS database. That number of rows is cached in RMJ. If you want different values that are outside the cache we will retrieve another data set from EBS.

Before: This functionality is not present before.

After: The object tag SYSTEM_DONT_EXPORT_RECURSIVE was added. When this tag is applied, it instructs the system to exclude that object and its children from the export.

Before: The insufficient privilege exceptions were not showing user info in the error message.

After: The insufficient privilege exceptions will now display the username in the error message, providing information about the missing privilege on a specific object and for whom it is lacking.

Before: The support for import/export of Custom Object was not present before.

After: We have added support for import/export of Custom Objects (Backend). This functionality will primarily be useful for users of extension points, as it will allow for promotion of objects defined in them.

Before: The support servlet used GET queries to process the queries that were entered by the user. This could trigger some WAPs to reject the call as it detected a SQL query in the Referer header, after the internal redirect.

After: The support servlet uses POST, and so the query no longer turns up in the Referer header.

Before change:

Catalog version is managed only manually by the user, no automatic upgrades happen.

After change:

When the Catalog is already installed and a newer version of the Catalog is available with the forceUpdate flag set, then the this newer version is installed by the System_Upgrade job.

Affected projects:

• ui-library/style-library
• ui-library/ui-library

Fixed an issue that caused an error message to display when you clicked Preview new user interface.