Release notes for Finance Automation releases 9.2.9.0 through to 9.2.9.1

The job definitions FCA_FCc_Utils_ActionRules and FCA_FPA_Utils_ActionRules now execute the same code as FCA_SAP_Utils_ActionRules.

With this new Execution Action for SAP transactions it is possible to use Call Transaction using a user which is not the RFC or Credential user.

Before: Group Accounts were not sorted in Dashboard.

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

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: Parameter MX_DelegateTo was visible in BSC UI.

After: Parameter MX_DelegateTo is hidden.

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

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

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

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: 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: FCA_SAP_BSC_Upload_Header_Attachments was broken.

After: FCA_SAP_BSC_Upload_Header_Attachments jobs works well.

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.

Before: FCA_BDC_QIDs_Execute did not return the values of the output parameters from the child jobs.

After: FCA_BDC_QIDs_Execute does now return the values of the output parameters from the child jobs.

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: All parameters created in Transformer were optional and didn't have any constraint data set.

After:  It is possible to mark a parameter as mandatory or set the constraints through the Parameters dialog.

Before: When certain rules failed in Data Transformer they would incorrectly report the area they failed in.
After: Rules now show correctly what rule failed when a validation error occurs.

Before: Replace functionality is not always available in the "Manage Data Files" Dialog.

After: Replace functionality is always available in the "Manage Data Files" Dialog.

Before: When a "Load Data" rule is deleted the example inputs become invalidated.

After: The initial "Load Data" rule can not be deleted or disabled once created.

Before: The RuleDataSets.name is displayed in the header of transformer when it launches

After: The Job definition name is displayed in the header of transformer when it launches.

Before: Double clicking on the buttons in the top right of a rule dialog would cause the rule dialog to expand to full screen

After: Double clicking on the buttons in the top right of a rule dialog only activates that button's functionality.

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: 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: When displaying two RTX tables in transformer it is possible to select multiple columns from both tables which are invalid when used in a rule

After: When displaying two RTX tables it is only possible to select columns from one table.

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 impossible to merge two input sources that share column names but with different cases.

After: A toggle feature has been added to the UI and when it is switched on two input sources that share column names with different cases can now be merged. 

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: String to Number Column conversion failed

After: String to Number Column conversion works as expected

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: 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: Processing inflated Excel files with FCA_SAP_Utils_Excel_Get_Cell_Value caused the System to crash, because of high heap memory size.
After: Added POI_Zip_Ratio, POI_Zip_Entry_Size and POI_Zip_Text_Size to FCA_ApplicationCustomizing which allows to set the poi values of MinInflateRatio, MaxEntrySize and MaxTextSize for Job Definitions working with POI. The default values have been adjusted to avoid further system crashes.

• POI_Zip_Ratio = 0.01
• POI_Zip_Entry_Size = 50MB
• POI_Zip_Text_Size = 50MB

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: When working with a template excel file, a new cell style was created for every cell. For large files this caused an exception, since the maximum amount of cell styles is limited to 64000.
After: Cell styles will now be cached. Before setting a new cell style, this cache will be checked if the cell style already exists and if so it will be used instead of creating a new one.

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: When Generic Loop was ran in mode "Sequential" (default) and the blocking size was set to greater than 1 it behaved like it was ran in mode "Parallel by Order" ("O") and used blocks to submit child jobs.

After: When Generic Loop now is running in mode "Sequential" (default) and the blocking size is set to greater than 1 it ignores the set blocking size and submits every child job one by one.

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: 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: CPU utilization reaches 100% of a CPU core when a process list is submitted in the Orchestrator in Delayed submit mode (App customizing "Orchestrator_DelayedSubmit" = "true")

After: CPU utilization increase cannot be measured, the thread that is monitoring delayed submitting of processes from the process list is almost idle

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: The process definition Convert_Excel_toRTX used the first row, or if IN_HEADER_ROW was set to 'yes' the second row, to determine the column types which will be set for the RTX columns of the output file.

After: Added the new parameter SET_COLUMN_TYPES to the process definition Convert_Excel_toRTX. This allows three different approaches on how the column types will be determined. The default detect_types_from_values will first read the whole sheet to determine the compatible type for each column, this will result in a slightly slower execution then the other options. string_for_all_columns will set the type of all columns to string. Also, users will now be able to set each column type individually. Use any of 'string', 'number', 'date', 'datetime' or 'datetimezone' as an array corresponding to the expected types for the output RTX columns.

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: There was no indication that another user was editing the same process list.

After: A warning is displayed if another user is editing the same process list.

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: 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: 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: 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: The context menu only provided a insert and Delete option. This was also the only way to delete a row.

After: The context menu also has Save and Refresh options. This menu is also made more accessible by a column button.

Before: UI actions like loading a table, filtering and copy-paste would take a long time, and without an indication.

After: Various UI actions have had speed improvements, and loading overlays whenever the user is waiting for the action to be completed, this is usually on large data.

Before: The cell pop-up would display an "edit" title.

After: The cell pop-up displays a "show" in its title.

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: 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: 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: Orchestrator did ignore periodicities set in the task list and its tasks.

After: Orchestrator now respects periodicities set in the task list and its tasks.

Before: Orchestrator did not recognize skipped tasks and therefore never completed process lists including such.
After: Orchestrator now recognizes skipped tasks and completes process lists including such.

Before: Killing process lists from the Instances tab in the Orchestrator was slow and unresponsive and often errors occurred while trying to kill the processes.
After: Killing process lists from the Instances tab in the Orchestrator is now fast and responsive and errors should not occur anymore while trying to kill the processes.

Before: To see new entries in the instances table the whole view had to be refreshed.
After: After submit the new entry will directly appear in the instances table. Also a "Refresh Instances" button has been added to be able to refresh only the instances table.

Before: It was not possible to use the JobDefinitions Redwood_Convert_Excel_toRTX and Redwood_Convert_RTX_toExcel on the platform agent.
After: Two new JobDefinitions Redwood_PA_Convert_Excel_toRTX and Redwood_PA_Convert_RTX_toExcel have been introduced for use on the platform agent. These also include a parameter to choose between FastExcel (default) and POI as processing engine.

Before: Downloading an attachment in Inbox or Workbench opened a new window.

After: Attachment are downloaded using the same window Inbox or Workbench is opened in.

Before: When Inbox was ordered by status new messages were added to the end of the group.

After: New messages now appear at the top of the list. 

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: Files were uploaded to different jobs depending on the value of parameter IN_UPLOAD_TARGET.

After: Files are always uploaded to the user message job.  IN_UPLOAD_TARGET now affects which job will have its OUT_UPLOADED_FILE parameter updated.

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: Process list name was limited to 30 characters.

After: Process list name can be up to 80 characters.

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: Queue could no be selected at submit time. Queues from across all partitions could be used.

After: Queue can be selected at submit time. Only queues from the same partition as Orchestrator can be used.

Before: Killing a process list job in Process Monitor only killed the top job.

After: Killing a process list job in Process Monitor kills all jobs in the hierarchy.

Before: Some node created through copy-and-paste failed at runtime.

After: Copy-and-pasted nodes now execute successfully.

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: The Gantt chart for any process list was hidden by default. It could be shown by clicking the "Toggle Gantt Chart" button. However this setting was not persisted. After closing a the process list or reloading the Orchestrator, the Gantt chart would be hidden again. This was implemented this way due to pre-existing possible performance problems with the Gantt chart.

After: The shown status of the Gantt chart is now configurable. The new config option GanttChartVisibility in the config group Orchestrator makes this possible. Options are:

• ALWAYS_SHOWN: Gantt charts are shown for all process lists, they can not be toggled.
• ALWAYS_HIDDEN: Gantt charts are hidden for all process lists, they can not be toggled.
• SHOWN_BY_DEFAULT (Default): Gantt charts are shown for all process lists by default but can be toggled. The toggled status is persisted per process list, per user.
• HIDDEN_BY_DEFAULT: Gantt charts are hidden for all process lists by default but can be toggled. The toggled status is persisted per process list, per user.

The toggled shown status per process list per user is persisted as the ganttChartShownStatusPerUniqueId user setting.

This is possible due to performance improvements for the Gantt chart.

Before:

• If a process list or regular process definition had been submitted and was later renamed, new process lists with the original name could not be created. It would falsely be reported that a process list / process definition with that name already exists.
• A new process list could also not be created if a process list or regular process definition by the same name existed in a different partition. It would also falsely be reported that a process list / process definition with that name already exists in the selected partition.

After:

• Process lists can now be created with the original name of a renamed process list / process definition.
• Process lists can now be created with the same name as an existing process list / process definition in another partition.

Before: Submitting a process list with nested templates in Orchestrator resulted in an error.

After: Now submitting a process list with nested templates in Orchestrator will complete correctly.

Before: In the header bar of the expanded process list dialog in the Orchestrator, the same buttons as in the header in the main window where shown. They mostly didnt make sense in the expanded process list dialog context.
After: In the header bar of the expanded process list dialog we now only show the "show/hide gantt chart" button, which does function properly.

No impact since the local view functionality has not yet been release.

After: improved the performance of the Gantt chart

Before: Parameter SAP Client was missing in the Business Entity.
After: Parameter SAP Client is now stored in the Business Entity.

No impact since localview functionality has not yet been released

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

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

No impact since the issue on which this was broken ( ROSO-10022 Merged ) has not been released.

Before: Aside from the regular platform privileges provided by the api, what the user could see and do while not in "admin mode" was based on explicitly granted security ranks.

After: This dependence on explicitly granted ranks has been changed to a dependence on the privileges these explicitly granted ranks provide. This allows for more flexibility now and in the future.

Now, while in "admin mode" what the user can see and do is (still) fully determined by platform privileges. When not in "admin mode", in addition, the user can not see lists and execute actions on lists if they do not have an explicit privilege to do so. An explicit privilege is a privilege on the list granted to the user or one of their roles. The owner of the list is considered to have all explicit privileges.

This change and improvements that come with it also have some direct impact:

• If the user has submit or viewJob privileges, there now is an option to open the process list in readonly mode.
• If privileges make a certain action (button, context menu item) unavailable, we will now just not render the associated button/context menu item. Before we would sometimes render it as disabled instead.
• Submit privileges are now needed to see the resubmit and restart context menu items on the jobs in the instances table. EditJobs privilege is now needed for the kill context menu item.

Before: It was not possible to mark a process list as a global close template.

After: Process lists can be marked as global close templates.

Before: The entity parameters BUKRS, KOKRS and SAP System where not propagated to the local tasks.
After: Now the entity parameters BUKRS, KOKRS and SAP System are propagated to the local tasks.

The priority of a task in Orchestrator can now be automatically increased on submit when the requested start time or the deadline is missed or when the task is marked as Critical Task. The default priority and the amount of increase in priority can be customized through the according settings in the table FCA_ApplicationCustomizing:

• Orchestrator_Default_Task_Priority (Default: 50)
• Priority_Increase_Start_Time_Missed (Default: 10)
• Priority_Increase_Deadline_Missed (Default: 20)
• Priority_Increase_Critical_Task (Default: 20)

Before: When one process list could not be parsed (due to marformed source json), no process lists would be shown in the Orchestrator.
After: When one process list can not be parsed, only that process list will not be shown in the Orchestrator.

Before: Orchestrator UI save behaviour differs from other extension points.

After: Orchestrator now more closely aligns with other extension points by only allowing the save button to be pressed when changes have been made.

After: the performance of the Orchestrator Gantt chart when dealing with large list has heavily been improved.

After: The underlying window can not be interacted with anymore as longs as the expanded process list dialog is open in the Orchestrator.

 Before: In the Runner, when a parameter was set to a value that did not match a constraint on the parameter and the user tries to run, an error message stating "Failed to persist [..]" was displayed. The actual constraint validation error was buried in the stacktrace.
After: The error message now displays the constraint validation error directly.

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: 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: 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: Messages tab was not refreshed when a task was refreshed.

After: Messages tab is now refreshed when a task is refreshed.

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: Sometimes the number of total tasks didn't match the number of tasks in the table.

After: Irrelevant tasks are ignored when counting the total task number.

Before: Popup filters after the first one could only have one value.

After: All popup filters can have multiple values.

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.

New Rule RuleColumnCompareAmountColumns has been added. It allows checking if the difference between two number values is within a given threshold.

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

Before: It was not possible to remove rows from top or bottom of the RTX file.

After: A new rule has been added that allows removing rows from top or bottom of the RTX file.

Before: Only text inputs were available to enter vales for all column types.

After: An appropriate picker is available based on the column type.

Before: Collapsing/Expanding all folders and nested template had to be done manually.

After: All folders and nested templates can be collapsed/expanded with a button click.

After: the option to add (and customize) entities to a ProcessList is added to the Orchestrator. The list of selectable entities is populated from the OrgStructure table. The added entities are stored on the ProcessList json source, they are not yet used.

Before: Dependencies could only be created through drag-and-drop.

After: Now it is also possible to add dependencies via a dialog accessible through the Predecessor/Successor panels.

Before: It was not possible to assign periodicity to tasks or groups.

After: Periodicity can be assigned to task or groups. The table where periodicities are stored is referenced in table FCA_ApplicationCustomizing through a key Orchestrator_Periodicity.

The new boolean property "Critical Task" was added to the Orchestrator template. It can be set under the Timing category to mark a task as critical and raise its priority when submitted.

After: For every (local) entity on a global process list, a local process list is created and shown in the Orchestrator overview. When editing such a local process list, all the nodes in the global list are shown. All the nodes that are not already skipped and have execution set to local can be set to be skipped for the local list specifically. Other properties and the list of nodes can not be edited.

before: Workbench showed all processes that were visible to the user depending on that users roles.
after: Workbench shows only the processes that a user created or has explicit privileges granted for. The old behaviour can be recreated by adding "Mode=admin" as an attribute in the workbench row of Home_Modules table.

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.

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

New:

The $FP replacement is extended with Quarter handling.

The Libraries Redwood_Robotics, Redwood_FPA and Redwood_FCc have been merged into the new Library Redwood_FCA.

The old Libraries have been renamed to ensure that the upgrade continues.

All Definition that use the renamed libraries should be checked and their references changed to the new Library. This includes the REL usage.

Before: Data files were added through the Data Files menu.

After: Data files are now added through the Manage Files dialog.

Before: Only static values could be used a replacement value in replace transformations.

After: Dynamic values can be used as replacement values in replace transformations.

Before: No visual indication is seen on RuldataSet tabs that a set is temporary

After: A clear visual  indication is now presented on RuldataSet tabs that a set is temporary

Before: It was impossible to retain specific columns.

After: A Retain Column rule has been added to allow users retain specified columns,

Before: When input files were removed the rule execution failed with a generic error.

After: When an input file is removed a warning is displayed advising which rules are using the file. When rules are executed a clear error is displayed that indicates which input file is missing.

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: Usage of the large Apache poi-ooxml-full library.

After: Replaced by the substantially smaller Apache poi-ooxml-lite library.

Before: Files uploaded through Inbox created simple job files.

After: Uploading files through Inbox creates file attachments so that their history can be audited.

Before: The template parameters TASK_TIMEZONE and TASK_CALENDAR where not passed down to the jobs.
After: The template parameters TASK_TIMEZONE and TASK_CALENDAR are now passed down to the jobs when the corresponding job definition parameters exist. In addition the new parameter TASK_DEADLINE_MISSED is set to "missed" when the deadline is missed and the corresponding job definition parameter exists.

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

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

Duplicates of chain FCA_BalanceSheet_Certification_ActionItem needs to be adjusted after BSC Upgrade regarding following Parameter Mappings:
<ChainName>.UserMessage_Participants to FCA_BalanceSheet_Certification_ActionItem_Notification.UserMessage_Participants and FCA_BalanceSheet_Certification_ActionItem_Processed_Notification.UserMessage_Participants