Release notes for Finance Automation releases 9.2.8.0 through to 9.2.8.12

Before: NullPointerException occurred when trigger logging is in debug mode and a call to a SAP function module is made.
After: The error has been fixed.

The ALV Download and Upload will only use the current Language instead of retrieving all languages.

To install FCA, now the following order is required:

1. fca_modules (contains fca infrastructure and all UIs except BSC,Studio,Catalog)
2. fca_content (On-Premise: contains non-SAP content)
3. fca_sap_content (On-Premise: contains SAP content)

The following Templates have been renamed:

Robotics_Process_Template => FCA_Process_Template

Robotics_SubProcess_Template => FCA_SubProcess_Template

Robotics_SAP_Process_Template => FCA_SAP_Process_Template

Robotics_SAP_SubProcess_Template => FCA_SAP_SubProcess_Template

Robotics_FCc_Process_Template => FCA_FCc_Process_Template

Robotics_FCc_SubProcess_Template => FCA_FCc_SubProcess_Template

FCA_FPA_TaskDefinition_Event_Template => FCA_FPA_Process_Event_Template

FCA_FCc_TaskDefinition_Event_Template => FCA_FCc_Process_Event_Template

It is now possible to export the status of the BSC dashboard into Excel.

Support for group of accounts has been added. All accounts with the same group name are certified at once.

Before: Attachment expiration calculation did not take period end date into account.

After: Attachment expiration calculation takes period end date into account.

Before: Submitting multiple accounts for the same group at the same time may result in some processes failing when setting up attachments and comments.

After: Submitting multiple accounts for the same group at the same time does not result in failures when setting up attachments and comments.

Before: FCA_SAP_BSC_Get_Attachments could fail when running for the same group at the same time when setting up attachments.

After: FCA_SAP_BSC_Get_Attachments doesn't fail when running for the same group at the same time when setting up attachments.

Before: Dashboard currency formats were determined based on the first account in the list.

After: Dashboard currency formats are determined for every account.

Before: Parsing of data was done using system encoding. This could lead to data corruption on systems not configured with UTF-8 as system encoding.

After: Parsing of data is always done using UTF-8 regardless of system encoding.

Before: Downloading a header attachment using the BSC UI would save the file
with the Cronacle document object name.
After: Downloading the file will now save the file with the expected name.

Before: NumberFormatException may occur, when exporting dashboard data.

After: Exporting dashboard data works fine.

Aging in BSC:

• Comparison date to calculate age of line item, can be configured for each range in parameter BS_CB_DEFINITION ('date' or 'posting_date' for example, default value in template is 'posting_date');
• First range in parameter BS_CB_DEFINITION will be used for column 'Aging' in line item list in BSC UI and for Excel Export;
• Breakup Table will use all ranges/configuration, defined in Parameter BS_CB_DEFINITION;
• Reference date to calculate age of line item is close_date from Account.json

Before: When using RuleCheckHasAttachment a NullPointerException could occur.

After: RuleCheckHasAttachment rule is working fine.

Export Job 'FCA_BalanceSheet_Certification_Export' to provide BSC Job Files is available.

Result:

• Excel file with line item list (similar to clicking on Export Button in BSC UI)
• One jobfile for each header attachment, if available
• Html file containing all header comments, if available

Content and Layout of Html Jobfile for Header comments can be configured via documents: FCA_Base_BALANCESHEET_EXPORT_HTML_MAIN and FCA_Base_BALANCESHEET_EXPORT_HTML_TABLE_COLUMNS
Associated Application Customizing entries are available.

Input Parameters with example values:

Catalog name                                 Redwood_BSC
Catalog path                                  INT/1000
Current posting period                  2021/008
Catalog account                            89000
Group Name

Important: Optional parameter 'Group Name' needs to be filled, when account is assigned to a group !

Before: Group Accounts were not sorted in Dashboard.

After: Group Accounts are sorted by account number in ascending order.

Before: Resetting the status of a line item that had an associate action item required the user to press the reset status button twice.

After: The status is correctly reset in the UI after pressing the reset status button.

Before: FCA_SAP_BSC_Upload_Header_Attachments was broken.

After: FCA_SAP_BSC_Upload_Header_Attachments jobs works well.

Before: Parameter MX_DelegateTo was visible in BSC UI.

After: Parameter MX_DelegateTo is hidden.

Before: Setting deadline is not mandatory when marking line item as reviewed.

After: Via Parameter 'MANDATORY_DEADLINE' it is configurable if setting deadline should be mandatory when marking line item as reviewed, default is not mandatory.

Before: When exporting line items into Excel ClassCastException could occur in case of amounts with zero decimal places.

After: It is possible to export line items with amounts with zero decimal places.

Before: FCA_FPA_BalanceSheet_Certification_Review_Notification process was executing a long running database query in the pre-running stage

After: The query was optimized and has now a significant better performance

Before: Processing of notification messages for Reviewer could take a long time
After: Performance of processing of notification messages for Reviewer has been improved.

Performance improvement when retrieving groupped accounts by clicking on BSC link in Inbox/E-Mail or after a certification of a group of accounts has been delegated to another user.

Before: Returning to the dashboard from a certification always refreshed the entire dashboard.

After: Only accounts which were changed during the certification process are refreshed now.

Before: When dashboard is loading data, period selection was active.

After: When dashboard is loading data, period selection is disabled.

Before: Filter by reviewed status was a freetext filter, when filtering for 'Correct' line items, also the 'Corrected' line items have been displayed in line item table.

After: Filter by reviewed status has been changed from freetext filter to checkbox filter, when filtering for 'Correct' line items, only the 'Correct' line items will be displayed in line item table.

Introduced UserMessage_NotifyMethod, a new optional parameter for user message process definitions. If this parameter is set then the NotifyMethod attribute that is specified in the user message definition is overridden. When creating new user message process definition or duplicating an existing definition, then the parameter is also added to this new definition, but it is flagged as hidden. The parameter was also added to all process definitions that are shipped by Redwood. The values that can be passed to this parameter correspond to the possible values that can be specified as NotifyMethod in the user message definition: None, IndividualEmails, OneEmail.

Before: Some processes (like KGI4) create updates which are handled asynchronous. The rule SCMA_WaitOnAsyncUpdate checks if these are complete. It can happen that control records are written containing 0 updates. The Rule would wait forever.

After: The Rule  now checks also for 0 entries (total = completed)

Before: The Insert-menu was enabled when no document was loaded, although all menu-items have no meaning in this situation.

After: The Insert-menu is now disabled when no document is loaded.

PDFBox has been updated to 2.20.24 to resolve CVE-2021-31811. This only affects the data extractor.

Before: Column descriptions could only be added when editing a column.

Add: Column descriptions can be set when adding a column.

Before: It was only possible to delete files from the file expression rule user interface.

After: It is possible to add input files via the file expression rule user interface.

Before: It was not possible to add a description to a rule.

After: A new description field has been added to the rule dialog, the contents of which will be displayed as the rule title in the rule panel.

Before: When displaying the context menu for a merge rule the option from resetting the rule was displaying incorrect text.

After: The context menu will now display the correct text for resetting the rule.

Before: When editing the example value of a DateTimeZone parameter the field was always blank.

After: When editing the example value of a DateTimeZone parameter the field displays the chosen value.

Before: Pressing the clear button on an edit column rule would not reset the description field.

After: Pressing the clear button now correctly resets the description to its initial state.

Before: Rules with REL expressions that referenced date parameters failed during execution.

After: Rules with REL expressions that referenced date parameters are executed successfully.

Before: Error messages generated in the Manage Rule Sets dialog were displayed in the main window behind the dialog.
After: Error messages generated in the Manage Rule Sets dialog are displayed in the Manage Rule Sets dialog.

Before: The Unhide option for hidden columns was inert forcing the user to use the context menu to unhide hidden columns.

After: The Unhide option for hidden columns correctly unhides columns.

Before: Lookup merges of RTX sources would only find matches for every other match when specifying key columns.

After: Lookup merges of RTX sources correctly find every possible match when specifying key columns.

Before: The input files were deleted when aborting the process of closing the Transformer whiles being in a state where you have unsaved changes.

After: The input files don't get deleted anymore and a custom dialog gets presented when trying to close the Transformer whiles having unsaved changes present. 

Before: It was possible to switch rule sets when in quick edit mode.

After: Switching rule sets is disabled in quick edit mode.

Before: The Total rule type would always generate a Grand Total for each group

After: The Total rule type can now optionally generate the Grand Total (defaults to true) along with also optionally calculating the cumulative total (default to false).

Before: Updating the target column type would not clear the source column field when adding a new column.

After: When a new column type is selected the source column value is now cleared. 

Before: Short cuts for saving and reverting a transformer opened from the job definition were missing.

After: Saving and reverting a transformer opened from a job definition via short cut keys is now possible.

Before: It was not possible to generate CSV files from a transformer process.

After: CSV is now a supported output format at both the rule set level and in the export rule.

Before: It was not possible to synchronize scrolling between two data sets.

After: There is a toggle that allows enabling synchronisation scrolling between two data sets.

Before: If an input job file could not be found the resulting message was not clear as to why the error has occurred.

After: A meaningful message is displayed when an input job file cannot be found.

Before: After reordering rulesets to restore the correct flow a spurious error message was displayed in Data Transformer.

After: The error is no longer displayed when the rulesets flow is restored.

Before: Filter rules that specified files to write matched and unmatched rows to would result in an exception when running the transformer but be successfully displayed in the user interface.

After: Filter rules that specify files to write matched and unmatched rows to successfully complete and generate the relevant files when run and when viewed in the user interface.

Before: In certain circumstances where input into a Data Transformer job share the same column structure the input can be mis-ordered when running the job.  This does not manifest in the user interface.

After: Where input into a Data Transformer job share the same column structure the input for RTX matching those structures will be treated as per the order in which they are provided.

Before: It is not possible to auto-merge two columns that have the same name, except for differences in case sensitivity.

After: It is possible to auto-merge two columns that have the same name, except for differences in the case sensitivity.

Before:  A valid expression that uses the "current" node would always fail during auto column mapping

After: A  valid expression that uses the "current" node will successfully auto-merge columns.

Before: The Group Match Rule algorithm would allow any size group to be matched against each other. When trying to match against larger groups, this was very memory intensive and resulted in jobs going into error due to an OutOfMemoryException. In the worst case, when running this on the server, this could cause system instability.

After: The Group Match Rule algorithm now limits how big a group will be used to match, and how many combinations within the group we allow. This reduces memory usage significantly and improves performance, resulting in job completion.

Before: Uploading a new RTX file that contains matching column names but different column types to the existing RTX on the transformer which consists of one or many Load Rule(s) causes the transformer to error.

After: An upgrade step has been introduced to remove the Load Rule(s) (NoOperation/ManualRtxInput Rule) from the older transformer job to prevent the auto-merge operation from triggering when uploading a new RTX file.

Before: String to Number Column conversion failed

After: String to Number Column conversion works as expected

Before: Data transformer uses version 1.6 of apache commons-text which has a CVE identified in CVE-2022-42889.

After: Data transformer uses version 1.10.0 of apache commons-text which where this CVE is resolved.

NOTE: The CVE is in a method that is not used from the Redwood code base. Nonetheless, this library has been updated out of an abundance of caution.

Before: Document Editor could only be installed as part of either FCA or Robotics.

After: Document Editor can now be installed using the document-editor.car file.

Before: When trying to convert from RTX to Excel, while using an empty sheet as a template, the process would fail with a nullpointer exception.

After: If an empty sheet is used from a template file, the process will now work accordingly and not result in an error.

Before: When using FCA_SAP_Utils_Excel_Set_Cell_Value and FCA_Utils_Excel_Action the error "java.lang.IllegalArgumentException directory cannot be null" was reported, because the Excel document was closed before data has been written to it.

After: The Excel document is only closed after all data is written to it and this error is not reported any more.

Before: Submitting of user message definitions (Redwood_Base|FCA_FPA|FCA_FCc)WorkFlow* and notification definitions (Redwood_Base|FCA_FPA|FCA_FCc)_Notification fails when using email addresses that don't match with email addresses of existing users.
After: Notification definitions listed above can be submitted to email addresses that don't match with email addresses of users and user message definitions can be submitted if at minimum one user with matching email address can be found and email is sent to additional email addresses even when they don't match with email addresses of existing users. The error message containing java.lang.NullPointerException: Cannot invoke "com.redwood.scheduler.api.model.Subject.getName()" because "subject" is null is not reported in this case any more.

Before: Documents could only be added one at a time.

After: The dialog for adding documents has been expanded to allow the user to upload multiple documents. 

Before: New files could only be added to existing documents by pressing the "Upload a new file" button.

After: The document content area now includes a drop zone for files.

Before: Editing the document properties, documentation and security grants was only possible from the edit menu.

After: The document context menu has been expanded to include these items.

Before: Text-based documents were available for preview in the extension point, but could not be edited.

After: Added support for Ace-Editor so that text-based documents can now be edited.

Before: RTX files were displayed in raw XML format.

After: RTX files are now displayed in the RTXTable component.

It is now possible to disable delegation of a message in the Inbox by adding a parameter with the name Inbox_SuppressDelegation and value Y to the user message.

Before: Account action item notes would not automatically be added to the open account in the UI.

After: The account notes are now automatically refreshed when an action button is selected and a comment provided.

Before: The process list status was saved to a job file and updated continuously causing high IO throughput.

After: The process list status is now saved to the database and continuous updating does not cause high high IO throughput anymore.

Before: Completion of Action Item did not work, when the account was grouped.

After: Completion of Action Item now works working when account is grouped.

Before: When using FCA_Utils_File_Transfer, IN_TO_DOCUMENT documents had to be specified by their entire path.

After: When using FCA_Utils_File_Transfer, IN_TO_DOCUMENT can be just a filename with extension, if an IN_TO_DOCUMENT is specified, this path will be used. When entering multiple documents, they will be paired in order of appearance.

Before: Values of notification job parameters containing 'balance' in parameter name were displayed in the BSC UI based on the configured number format.

After: Only values of notification job parameters with names starting with 'balance' are displayed in the BSC UÍ based on the configured number format, all others are displayed as non formatted String.

Before: Home could only be installed as part of either FCA or Robotics.

After: Home can now be installed using the home.car file.

Before: Notes and attachments could not be updated when pressing the "Refresh All" button.

After: Notes and attachments can now be updated when pressing the "Refresh All" button.

Before: For loading tables, a specific table via a unique id or a set of tables via business keys could be used.

After: JobFiles can now be loaded as a table and saved as a new JobFile.

Before: Parallel execution of jobs could lead to persist errors in GenericLoop.

After: Parallel execution of jobs won't lead to persist errors in GenericLoop anymore.

Before: Table Editor, Home, Runner and Wopi Viewer, could only be installed as part of either FCA or Robotics.

After: Table Editor, Home, Runner and Wopi Viewer, can now be installed using their respective car file.

Before: The JobDefinition Robotics_Convert_RTX_toExcel made use of the Apache POI library which caused issues with memory usage.

After: Added a new implementation based on streaming and the fastexcel library which benefits from a significantly smaller memory footprint. The Apache POI library implementation is still accessible via parameter 'Use Fastexcel' = 'no'.

Before: The add and edit dialogs launched from the rule list and tool bar for Min, Max and Total types would display the wrong title - "Add Transformation"

After: The add and edit dialogs launched from the rule list and tool bar for Min, Max and Total types display the correct title - e.g.: "Add Min"

Upgrades the version of Apache Commons-Compress used by Financial Automation from 1.20 to 1.21 to overcome CVE-2021-35515 which potentially allowed a denial of service attack using a specially crafted .7z archive.

NOTE: This library is only used indirectly by POI, so this is unlikely to be exploitable, however, this library could potentially be used from scripting for other purposes, and so has been updated to improve system security.

Azure authentication for SharePoint and Power BI now uses the Microsoft Authentication Library (MSAL) instead of the Azure Active Directory Authentication Library (ADAL).

Username and password authentication for SharePoint through Azure is using the "MyFiles.Write" scope by default. The master account authenticator for Power BI has its scope set as "AllSites.FullControl".

Upgrades accessors-smart and json-smart, addressing CVE-2021-27568 which could cause crashes or sensitive information leaks when used with old versions of json-smart, which was used in the Sharepoint connector

Before: For RestartContinueAbort-UserMessages the return code was set to 1 for "Continue" and to 0 for "Restart"

After: The return code is set to 0 for "Continue" and to 1 for "Restart"

Before: When selecting a recent transformer from the menu bar the user was not being prompted to lose the unsaved changes.

After: When selecting a recent transformer from the menu bar, and the user has unsaved changes, they are now prompted before the transformer is changed.

Before: Wopi Viewer could only be installed as part of either FCA or Robotics.

After: Wopi Viewer can now be installed using the wopi-viewer.car file.

Before: Transformer could leave some temporary files after the user interface is closed down.

After: Transformer cleans up all temporary files when the user interface is gracefully closed.  When not shut down gracefully temporary files will be removed after an hour when the transformer UI is next launched and interacted with.

Before: Generic Loop did not run any child jobs when using High Parallel Volume mode and the block size was lower than the number of repetitions.

After: Generic Loop now runs child jobs when using High Parallel Volume mode and the block size is lower than the number of repetitions.

Before: If Generic Loop is set to wait after a block in High Parallel Volume mode it also waited after completion of the last child job.

After: If Generic Loop is now set to wait after a block in High Parallel Volume mode it does not wait after completion of the last child job anymore.

Before: The parameter Close Date (TASKLIST_END_DATE) was not added automatically by the Orchestrator to process lists that didn't contain tasks created from the template FCA_SAP_Process_Template - tasks created from the FCA_Process_Template were insufficient. And if the parameter was added to the Process List manually it was not properly evaluated and ignored when calculating timing for task scheduling, so the day offset parameters in the Orchestrator were wrongly added to the day of the process list submit.

After: Also process lists that contain only tasks that had been created from the FCA_Process_Template now automatically get the parameter Close Date (TASKLIST_END_DATE) and this parameter is properly evaluated as reference date to calculate negative and positive offsets in Orchestrator.

Before: When submitting FCA WorkFlow user message definitions with the parameter MX_To set to a delimited list of users, they would not get recognized as internally. The list was not expanded before the user mapping was performed.

After: Submitting FCA WorkFlow user message definitions with the parameter MX_To set to a comma-delimited list of users, will now result in all users being recognized and set as a participant and running the user message process as intended.

Before: If certification has been rejected by approver, then its status on 'Approver' tab in Dashboard is displayed as 'Rejected', but in excel file its status is shown as 'Error'.

After: If certification has been rejected by approver, then its status is displayed as 'Rejected' in both, dashboard and excel file.

Before: When using FCA_FPA_WorkFlow_Confirm, FCA_FPA_WorkFlow_AcceptReject or FCA_FPA_WorkFlow_RestartContinueAbort with the MX_To parameter set to an email address, this email address will not be resolved to a username. This causes the workflow to fail because the participant is set to a plain email address instead of a username.

After: Added an additional query, which will resolve the given email address to it's corresponding username and subsequently setting the username as the participant.

Before: Generic Loop was displaying the complete number of child jobs in the description right from the start when set to High Volume Parallel mode.

After: Generic Loop now displays the number of actually submitted child jobs in the description when set to High Volume Parallel mode.

Before: The version of POI was updated to address potential CVE when using this library. The new version of POI has an additional dependency on SparseBitSet, however this was not included in the libraries that were shipped, leading to issues when using this part of the POI API. This would then lead to failures with a stack trace that included:

Caused by: java.lang.NoClassDefFoundError: com.zaxxer.sparsebits.SparseBitSet
	at org.apache.poi.ss.format.CellNumberFormatter.formatValue(CellNumberFormatter.java:482)
	at org.apache.poi.ss.format.CellFormatter.format(CellFormatter.java:93) 

After: Adds SparseBitSet to all libraries which include Apache POI-ooxml, as it is required to use the POI streaming API.

Before: It was not possible to use client/secret authentication for SharePoint app-only registrations.

After: it is now also possible to use SharePoint app-only registration clients.

Before: When submitting FCA_SAP_Convert_Spool_to_RTX with no input spool file, data types are ignored and per default set to String.

After: FCA_SAP_Convert_Spool_to_RTX will now set all column types accordingly, when there is no input spool file.

Before: Running a process list that included a nested process list resulted in an error.
After: Running a process list that includes a nested process list now completes successfully.

Before: Home screen was not shown after installation of Robotics/FCA

After: Registry entry to setup Home screen is created when initialization process the Home module is executed and Home screen is shown again

Before: The version of Jackson shipped used within the product has a HIGH ranked CVE reported against it: CVE-2020-36518.

After: The Jackson libraries have been updated to a version not affected by this CVE.

NOTE: The product is not affected by this CVE, as the component in the library that caused the CVE to be raised is not used in the product. However, this has been updated out of an abundance of caution.

Before: A false warning was displayed in Orchestrator when the Deadline Day Offset for the task was zero and the Start Day Offset negative.
After: No warning is displayed anymore in Orchestrator when the Deadline Day Offset for the task is zero and the Start Day Offset negative.

Before: Aging was not correct when Date info was missing in Parameter BS_CB_Definition: all line items have been assigned to the ‘oldest’ aging interval

After: Aging is correct when Date info is missing in Parameter BS_CB_Definition: line items are assigned to the correct aging interval

Before: Installation of Orchestrator by on-premise customers with case sensitive database like MS SQL Server with corresponding settings failed with error message "JCS-102459: Failed to apply DDL for Custom Entity: {RW_O_ExternalizedParameters ..."

After: Fixed installation error and now Orchestrator and subsequent modules can be installed successfully.

Before: OnChange trigger did incorrectly replace slashes in file paths.
After: OnChange trigger does not replace slashes in file paths.

Before: Workbench did not recognize column configuration changes in CUS_FCA_Workbench_BoardConfiguration after they were loaded for the first time.
After: Workbench now always recognizes column configuration changes in CUS_FCA_Workbench_BoardConfiguration.

Before: The wrong rule can be highlighted as a cause of error even though a previous rule was the cause.

After: The correct rule is highlighted as the cause of an error when one occurs.

Before: The list of roles that gets access to the Control Center button was hardcoded.

After: Administrators will always have the Control Center, other roles can be configured through the Configuration option AdditionalControlCenterAccessRoles (default: ["scheduler-it-user"] for backwards compatibility)

Before: Deleting files from the user message didn't remove the reference from OUT_UPLOADED_FILE .

After: Deleting files from the user message now also updates the references in OUT_UPLOADED_FILE .

Before: For UserMessages in status Killed or Unknown a red X was shown. The time filter in the Inbox filtered on the ReplyTime of the UserMessages. Since these were never replied they were not filtered out.

After: For UserMessages in status Killed or Unknown a black X is shown. The time filter now filters on the RunEnd of the related UserMessage-Job and thus filters out UserMessages in any final status. For UserMessages for which the job is in status Completed or Error, the icon shown also depends on the return code of the job (see below).

Before: When clicking on the 'Refresh All' button in the delegation history dialog, the history items were not updated.

After: The 'Refresh All' button in the delegation history dialog is fixed, so that the history items are updated.

Before: Filter states were lost after closing the Inbox.

After: Filter states can be saved to and subsequently loaded from filter profiles.

Before: Only the participants specified on the user message definition were displayed, while those added through the UserMessage_Participants parameter were omitted.

After: All user message participants are displayed.

Before: A user message could be delegated only to any business-users regardless of the settings.

After: In business mode the list of users a user message can be delegated to depends on the value of the MX_DelegateTo parameter. In admin mode a user message can be delegated to any business-users.

Before: When two tasks had a property with the same name but different types multi-edit would allow editing the field, however due to the ambiguity the input could not be processed correctly.

After: Properties with ambiguous types are disabled during multi-edit.

Before: Even though all job definitions could be included in a task only those that were stored in the default/application partition were executed successfully.

After: Job definitions from any partition can be included in a task.

Before: Sometimes Add/Remove Parameters dialog didn't have the right checkbox selection.

After: Add/Remove Parameters dialog checkbox selection reflects the state of selected parameters.

Before: Changing a parameter value had no effect on depending parameters.

After: Changing a parameter value re-evaluates other parameter values and highlights those that are now invalid.

Before: "Clear" removed the value of the Unknown parameter.

After: "Clear" removes the Unknown parameter.

Before: Job ID and scheduled start time could not be viewed in the Instances tab.

After: Job ID and scheduled start time columns have been added to the Instances tab.

Before: Approver and Supervisor fields could only store one value.

After: Approver and Supervisor fields allow multiple values.

Before: "New process list" dialog could not be closed via the Cancel button.

After: "New process list" dialog can be closed via the Cancel button.

Before: After collapsing several groups, expanding a group could expand more than one  group.

After: Only the selected collapsed group is expanded.

Before: Undefined offset/time was assumed to equal 0/23:59:00 .

After: Undefined offset/time is handled in relation to the close start.

Before: Dragging and dropping node cells no longer connected them.

After: The functionality has been restored.

Before: Errors during template creation crashed Orchestrator UI.

After: Errors during template creation are handled gracefully.

Before: Users could see all process lists on the overview page.

After: By default users can only see process lists they created or have explicit grants for. Administrators can see all process lists.

Before: Autosuggest was not offered for built-in parameters during multi-edit.

After: Autosuggest is now presented for built-in parameters during multi-edit.

Before: Killing a process list job only killed the process list itself. The elements of the process list were not killed.

After: Killing a process list kills the it and all elements of the process list.

Before: Changing a parameter value may result in other parameters getting erroneously marked as incorrect.

After: Parameters will be marked as incorrect only when that's the case.

Before: Nested process list did not inherit parameter values set on the parent process list.

After: Nested process list inherit parameter values set on the parent process list.

Before: Milestones from nested templates were not inherited by the parent process list.

After: Milestones from nested process list are inherited by the parent process list.

Before: Job parameters were marked as mandatory on the group and process list level even though providing values there is not necessary.

After: Job parameters are no longer marked as mandatory on the group and process list level.

Before: Search results used to include the process list node even if the searched parameter was not externalised.

After: Search results only include the process list node if the searched parameter has been externalised.

Before: Process lists with Time parameters failed during execution.

After: Time parameters are processed correctly.

Before: Name/description toggle was only available on the overview page. By default the toggle was set to display the node name.

After: Name/description toggle is now also available on the editor page. By default the toggle is set to display the node description (if available). 

Before: Parameters set on the process list level in Orchestrator were not propagated to the submitted jobs.

After: Parameters set on the process list level are now propagated to the submitted jobs.

Before: A milestone could be assigned to a number of tasks and groups.

After: A milestone can be assigned to only one task at a time. 

Note: Any existing process lists need to be adjusted manually where a milestone is assigned to more than one task.

Before: On scheduling of a task from Orchestrator only the fields Value (type String) and ValueNumber (type Number) were written for JobDatums FCA_Task_StartTime and FCA_Task_Deadline.

Fields ValueDateTimeZone and ValueTimeZone were left empty (null).

After: On scheduling of a task from Orchestrator fields Value, ValueNumber and ValueDateTimeZone of type DateTimeZone are written (the latter also sets field ValueTimeZone) for JobDatums FCA_Task_StartTime and FCA_Task_Deadline.

Before:

• Pressing ctrl+f on Windows didn't open the search pane
• Pressing Esc to close the no search results dialog had no effect
• Pressing Esc to close the search pane didn't refocus on the template pane

After:

• Pressing ctrl+f on Windows opens the search pane
• Pressing Esc closes the no search results dialog
• Pressing Esc to close the search pane refocuses on the template pane

Before: Task lists with status "Error" could not be monitored in Workbench.

After: All task lists except those that failed during initialization can be monitored in Workbench.

Before: Privileges were not applied if a user inherited them from a role.

After: Privileges apply whether they are specified for a user or one of their roles.

Before: Deleting a process list without deleting associated processes failed (reporting an exception).
After: When deleting a process list without deleting associated processes, this process list now is instead hidden, so the action no longer fails.

Before: Gannt chart was always visible.

After: Gannt chart is hidden by default. Visibility can be toggled via a button in the process list editor.

Before: Occasionally when Orchestrator submitted TaskLists an error NoRowsUpdatedException could occur.

After: The error does not occur in these situations any more.

Before: Runner could only be installed as part of either FCA or Robotics.

After: Runner can now be installed using the runner.car file.

Before: Users could see all available process definitions.

After: By default users can only see process definitions they created or have explicit grants for. Administrators can see all process definitions.

Before: The left hand application panel by default showed application and process definition names instead of descriptions. There is a toggle to show descriptions (if available) instead. The setting of this toggle was not persisted over sessions.

After: The setting of this toggle is now persisted per user and the default is now showing descriptions (if available) instead of names.

Before: Cannot retrieve SAP joblog in pipe delimited format via the Spool Host when FL_SPOOL is set.

After: SAP joblog can now be retrieved in pipe delimited format via the Spool Host.

Before: Running jobs that make use of the RTXWriter that contained RTX without column descriptions on a platform agent would result in a NullPointerException and the job consequently failing.

After: Running jobs that make use of the RTXWriter that contains RTX without column descriptions on a platform agent proceed to completion successfully.

Note, the DataTransfomer extension point uses RTXWriter, and needs to be upgraded to get this fix.

Before: The Table Editor user interface would display a maximum of 5000 rows.

After: The Table Editor user interface can now display a maximum of 100000 rows.

Before: When using the immutable flag with the externalConstraintTable url parameter, the text pop-up was not shown for the read-only values.

After: The text pop-up is always shown, regardless of read-only status.

Before: Copying from an external source that was not Excel would truncate the last letter.

After: Pasting works reliably for local copy, external (excel) and external (non-excel).

Before: Making changes on multiple rows would only save the last row's change.

After: All changes made are saved.

Before: Continuous loading of large tables would cause the browser to crash.

After: Continuous loading of tables will not cause the browser to crash.

Upgrades the version of the fasterxml Jackson products used in all products to 2.13.2, to overcome CVE-2020-36518 which could potentially allow a denial of service by uploading specially crafted JSON documents.

Before: The order of the time filter was: "Always", "1 Hour", "1 Day", "1 Week", "1 Month", "Never".

After: The order of the time filter is changed to: "Never", "1 Hour", "1 Day", "1 Week", "1 Month", "Always". In addition the flickering of the table when the time filter was changed was fixed.

Before: Notes could not be deleted in Workbench.

After: Notes can be deleted in Workbench.

Before: The items in Workbench were loaded oldest first.

After: The items in Workbench are loaded newest first.

Before: There was a maintenance job running in the background which updated the Workbench cache, potentially causing performance issues.

After: The maintenance job has been removed and the cache is replaced with direct select queries to the database.

Before: Sometimes enumeration filters displayed filtered out values when used in combination with inline filters.

After: Only relevant options are displayed in the enumeration filters when used in combination with inline filters.

Before: Unsaved filters were removed after refreshing the Workbench.

After: Unsaved filters are retained after refreshing the Workbench.

Before: Task details were only updated after restarting Workbench.

After: Task details are updated during autorefresh or after selecting Refresh from the task context menu.

Before: Workbench had a performance issue when showing many tasks > 1000 on customer cloud environments
After: Improved Workbench performance when showing large number of tasks

Before: The Process Description in Workbench sometimes showed the description of the process list instead of the process. Also the Owner Key was always "Other".
After: Now the Process Description in Workbench always shows the description of the process. Also the Owner Key now shows the correct values.

before: Skipped and ignored tasks were shown in workbench when filtering for non final tasks.

after: Skipped and ignored tasks are not shown in workbench when filtering for non final tasks.

Before: Workbench failed to load when the database is SQL Server and the system has a large number of tasks.

After: The executed query for loading the tasks has been optimised to support SQL Server binding limits.

Before: Line items marked as Corrected without a deadline would remain in this status indefinitely until the status is changed either through a rule or manually.

After: It is possible to configure the process such that line items marked as Corrected without a deadline would be automatically set to status Unanalyzed in the next period. The default behavior is still not to reset automatically.

Users now have the option to select clearing date to be used as posting date in SAP, which allows users to clear selected line items on defined posting date.

In BSC Line Items table, checked line items are now highlighted with light grey color.

Before: After performing an action (eg restart, request review, etc.) certification or action pages and returning back to the dashboard, all accounts and actions were automatically reloaded.

After:  It is now possible to disable auto-reloading of accounts and actions after returning to the dashboard via parameter 'DISABLE_DASHBOARD_RELOAD'. Auto-reload will be disabled for the specified actions.

To get this feature also for existing definitions, manual action is needed: The parameter 'DISABLE_DASHBOARD_RELOAD' needs to be created at the chain level and mapped to the notification definitions within the chain.

Possible values, comma separated: never,all,restart,restartGroup,requestReview,requestReviewGroup,completeReview,completeReviewGroup, acceptReview,acceptReviewGroup,rejectReviewGroup,rejectReview,resetStatus,createActionItem

default value: never

Before: .xlsb format was not supported in BSC

After: .xlsb format is supported in BSC

FCA_SAP_Generic_Loop has a new out parameter of type table called LOOP_SUMMARY. This table contains job description, status and return code of all jobs performed in the loop.

Before: Users could delete, edit, submit and monitor process lists if they were in administration mode.

After: Users can delete, edit, submit and monitor process lists only if they have explicit grants on the object. 

Before: Users could delete and edit process lists if they had sufficient platform privileges.

After: Users can delete and edit process lists only if they have explicit grants on the object. In administration mode platform privileges still apply.

New SAP transports have been generated.

The below functionality is now available again:

• Reports
  • /JCS/HR_PA03
• Transactions
  • CKMLCP
  • FDTA (admin information update)
• Functionality
  • Upload ALV Layouts
  • Uploading TVARV(C) changes to SAP
  • Locking/Unlocking of Batch Input maps

Before: SAP Transports are available for BSC and FCA Infrastructure. 

After: Add Ons available for BSC and FCA Infrastructure.

For further info see 'Redwood.Robotics.SAP.Setup.Guide.pdf'

Before: It was not possible not customize default order of columns in on the BSC dashboard and on the certification page.

After: It is now possible to customize the default order of columns on the BSC dashboard and on the certification page via table CUS_FCA_BSC_Configuration_ColumnDefinition. Users can change column orders via existing Column Chooser.

Before: Number of accounts in dashboard was limited to 5000.

After: Number of accounts limit in dashboard has been increased to 50000.

Before: Restart, request for review, accept and reject of grouped accounts could be slow when many accounts in the group.

After: Restart, request for review, accept and reject of grouped accounts are simplified without usage of SQL query and therefore faster.

The performance of BSC dashbaord has been improved.

Before: The drop-down list with accounts belonging to a group are not sorted in BSC UI.
After: The drop-down list with accounts belonging to a group are sorted in BSC UI.

The maximum number of accounts has been increased to 150000 per period.

The required installs have been reduced:

1. Robotics.car contains
   1. FCA Infrastructure
   2. Data Extractor
   3. Data Transformer
   4. Inbox
   5. Orchestrator
   6. Workbench
   7. Runner
   8. Home
   9. Wopi Viewer
   10. Document Editor
   11. Table Editor
   12. RTX extraction from SAP spool
2. FCA.car contains
   1. FCA content (including Triggers)
   2. FPA content
   3. FCc content
   4. SAP content

Replacements  have been renamed:

• For FCc implementation
  • ${F to ${FF
  • ${V to ${FV (only if FCc defaults are required)
• For FPA implementation
  • ${V to ${PV (only if FPA defaults are required)

The following process definitions are renamed:

• Robotics_Convert_Excel_toRTX => Redwood_Convert_Excel_toRTX
• Robotics_Convert_MergeRecord_toRTX => Redwood_Convert_MergeRecord_toRTX
• Robotics_Convert_RTX_toExcel => Redwood_Convert_RTX_toExcel
• Robotics_Convert_RTX_toMergeRecord => Redwood_Convert_RTX_toMergeRecord
• Robotics_RTX_Concatenate => Redwood_RTX_Concatenate

The new ApplicationCustomizing Table parameter Base_RTX_PostRunning, if set to X will create the RTX result parameters in PostRunning.

Before: fca_content.car and fca_sap_content.car are not installed during upgrade on cloud docker image

After: fca_content.car and fca_sap_content.car are installed during upgrade

Before: It was not possible to insert a reorder rule part way through a rule set nor was it possible to delete it.

After: Reorder rules can be inserted within an existing rule set and can also be edited.

Before: Burst file names could get long with no possibility to shorten them

After: Burst file names can be optionally shortened by basing their names on a numerical index.

Before: Previously entered values for format would be retained when switching between Date/DateTime/DateTimeZone and Number types when changing the type of column during column edit rules.

After: The format is cleared when switching to the Number type from other types.

Before: It was not possible to verify the expected output of a transformer against reference data to determine if there have been material changes to the transformer.

After: Control verification state can be generated and saved for each rule set.  As changes to the transformer are made new verification state can be generated and compared against the control state.  Discrepancies are reported in the user interface.  A verification policy can be set on each rule set to determine if the comparison of the control state be made against a newly generated state when the job runs.  The policy allows for no verification, logging of verification failures only or logging of verification failures and additionally failing the job if any are encountered.

Before: Rules that were added/edited/deleted couldn't be restored without pressing the "revert" button.
After: All changes to rules are now tracked and the user can undo/redo them using either the menu items or short keys.

Before: Rule sets could be reordered by dragging and dropping them in the Rule sets management dialog.  Rule sets would swap position which was confusing for end users.

After: Rule sets can still be reordered by dragging and dropping them in the Rule sets management dialog.  Rule sets when dropped are inserted at the new location.  Other rule sets are moved down the processing list with their order maintained.

Before: Users would have to launch the manage rule sets dialog by clicking on the menu bar.

After: A context menu option has been added to the rule set tab to launch the manage rule set dialog with the rule set selected.

Before: Input files were ordered based on an algorithm that compares them with the example data used when the transformer robot was created. Should files arrive out of order the best effort is made to correct this based on the metadata for the input.

After: A system-wide configuration has been introduced to allow the user to enable/disable input file ordering. This configuration is set to true by default and can be overridden by adding/updating a registry entry under the following path "/configuration/jcs/datatransformer/inputsourceordering”. The only valid values are true or false. By default, all transformers will adhere to this configuration unless overridden on the transformer level.
Overriding the configuration on the transformer level can be achieved via the “Manage Input Files” dialog where a new select component has been introduced with the following options:

• Default - The system-wide configuration should be respected.
• On - Override the system-wide configuration and turn the Input File Ordering on.
• Off - Override the system-wide configuration and turn the Input File Ordering off.

Note, When upgrading from a previous version, or prior to importing, the environment-wide configuration can be created and set as desired to ensure consistent behavior.

Before: When viewing excel files the Document Editor displayed the "Document cannot be previewed" message.

After: The Document Editor now displays the Excel Viewer component when rendering Excel files.

Before: Reloading the table was only possible by pressing F5 which also reloads the extension point.

After: Pressing the Refresh button will retrieve the latest server data on the table. Any unsaved progress will be lost.

Before : MailReactor and Robotics libraries contained jsoup.jar version 1.14.2 which is vulnerable to CVE-2022-36033.

After : jsoup has been updated to version 1.15.3 which resolves that vulnerability.

Note: The product doesn't use jsoup in a way that would be vulnerable, however it has been upgraded out of caution.

Before: All tabs and menus were visible to privileged users.

After: Retention tab and the context menu on the Instance tab is hidden by default. Setting parameter 'Mode' to 'admin' will make these items visible.

Before: Only Process Definitions of type RedwoodScript provided support for local REL expressions e.g. for the default expressions of parameters.

After: All Process Definition types support local REL expressions now. The additional optional field RELRelatedLibrary was introduced in the Process Definition entities for this purpose. If this library is specified then it is used to lookup the available REL entry points that can be used without specifying Partition and Library prefix directly in the REL expression. For backward compatibility reasons the old behaviour of RedwoodScript definitions is still supported, i.e. if the RELRelatedLibrary is not specified the REL entry points of the Library are retrieved that is assigned to the Script object as it was done before the change.

Before: Table Editor could only be installed as part of either FCA or Robotics.

After: Table Editor can now be installed using the table-editor.car file.

With this change, dashboard columns are fully configurable, by adding any parameter of BSC review and approver notification job into table CUS_FCA_BSC_Configuration_ColumnDefinition:

• value of column 'Name' needs to be the parameter name in the associated notification job
• row key needs to start with 'Dashboard '

Important: balancesheet-certification.car needs to be installed twice to get the needed changes in table CUS_FCA_BSC_Configuration_ColumnDefinition.

Before: Tasks could only be delegated/assigned to business users.

After: Tasks can be delegated/assigned to all active users.

Before: The definitions Redwood_Convert_Excel_toRTX and Redwood_Convert_RTX_toExcel made use of the Apache POI library which caused issues with memory usage.

After: Added a new implementation based on streaming and the FastExcel library which benefits from a significantly smaller memory footprint as default for both definitions Redwood_Convert_Excel_toRTX and Redwood_Convert_RTX_toExcel.

NOTE: The default excel processor has changed to FastExcel. This library is generally faster, and uses less memory, however is not as fully featured as Apache POI. To use the old Apache POI library implementation, select it by setting parameter 'Use FastExcel or POI' (IN_PROCESSING_ENGINE) to the value 'POI'.

Before: The default SAP job name was defined in Application Customizing table with the key "SAP_Default_JobName" .

After: The default SAP job name is now always 'RW_<jobid>' .

The SLA functionality has been removed.

NOTE When upgrading from a older version it is required that all running and planned occurrences of FCA_SLA_Maintenance and FCA_SLA_Monitor are killed or cancelled before the upgrade starts.

The key for SAP_Default_JobName has been removed from the application customizing. This is no longer customizable. The default SAP job name is now always 'RW_<jobid>' .

Extra SAP security has been implemented to ensure that the functions can not be misused.

Each AddOn has his own extra authorization check:

• RW4MA  ->  /RW4MA/RFC 
• FCA4NW -> /JCS/NW
• FCA4ERP -> /JCS/ERP
• FCA4BSC -> /JCS/BSC

Appropriate security needs to be provided to the RFC user.