Release notes for Finance Automation releases 9.2.10.0 through to 9.2.10.1

Before:
It was not noticed that the ALV Layout can only by uploaded in the logon language.

After:

The JD checks/uploads the language of the ALV Layout and notifies accordingly.

Allow Journal process to also use RUNAS functionality using action codes >USER_CHECK< and >USER_BAPI<.

The transactions FAGLB03, GD23, GD33, PCP0, MD04, MD05, MD06, V.23 now can also be started using >CALL_USER< allowing RUNAS functionality.

Before: JD is named FCA_SAP_Utils_Transport_Version
After: JD is named FCA_SAP_Utils_AddOn_Versions

Introduced: Execute FBV0 as BAPI call

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

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: There was no way to refresh data on the BSC certification page
After: It is now possible to refresh the certification page via a button or set intervals

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: Parameter values for the Review User Message job are not editable from the Certification Review UI.
After: Parameter values for the Review User Message job can be edited on the Certification Review UI if those parameters were configured as InOut on the job definition. If edited, the new values are set as the job parameter out value.

Before: If a custom Line Item was edited and the Document Number prefix removed or replaced, the Line Item would be treated as though it were a conventional ERP sourced Line Item.

After: A custom Line Item can be edited, but the Document Number prefix can no longer be removed or replaced. The Line Item is correctly identified as a custom Line Item.

Before: text in various BSC tables wasnt selectable.

After: this text now is selectable.

Before: If an “invalid line” was found when parsing a table within a spool file, parsing that table would be stopped and the line dropped.

After: If an “invalid line” was found when parsing a table within a spool file, it is tested to see whether it has TAB characters and, if so, these are removed and it is re-validated / parsed, else the line is recorded as a parse error, it is dropped from the output file and, in both cases, parsing of the spool file resumes at the next line.

Before: The Job Definition of FCA_SAP_BDC_WorkFlow sends empty Mail notifications.

After: FCA_SAP_BDC_WorkFlow will send the correct Mail notification, together with all attachments.

Before: ActionRule results do not use the parameter RULE_RESULT_HEADER for specifying the header/type of the RTX result.

After: ActionRule now uses specified Headers/Types

Before: There is no support for table input parameters.

After: Transformer now provides support to table input parameters of type Job file. Other Input parameters including Inline aren’t supported.

Before: It was not possible to unhide an individual column when many columns were hidden.

After: Individual hidden columns can be unhidden when many columns have been hidden.

Before: Changing a ruleset name would cause other rulesets with references to the updated ruleset to error.

After: Changing a ruleset name will also update all references so other rulesets won't error.

Before: The job file references in the index file for a burst job do not contain the ".rtx" extension

After: The job file references in the index file for a burst job do contain the ".rtx" extension

Before: Transformation operations that contain conditions that fail because the columns on which they rely are not of the correct type would result in the transformer failing to load in the user interface and failing at runtime.

After: Transformation operations that contain conditions that fail are correctly handled allowing the transformer to be loaded in the user interface and to process as expected when running as a job.

Before: Failed rules are automatically skipped by default.

After: Failed rules are not automatically skipped by default; the user must enable the skip feature manually

Before: Several menu items (edit, reorder and filter) were still clickable, if the user double-clicked on them, even when they were disabled.

After: The menu items will no longer function when disabled.

Before: File expression UI expert mode was set to false by default

After: File expression UI expert mode is set to true by default

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: When merging data an error message was logged that failed to indicate the column name on which the merge couldn't proceed due to a mix of column types.

After: Error messages reported when merges fails based on column types now correctly identify the column at issue.

Before:  The user is presented to Fileexpression UI v2 in the standard mode.

After:  The user is presented to Fileexpression UI v1 in the standard mode.

Before: The save operation was not working on a data set rule when it contained a merger that uses a current node.

After: The save operation works on a data set rule when it contains a merger that uses a current node.

Before: String to Number Column conversion failed

After: String to Number Column conversion works as expected

Before: It’s unclear of the effects that the date of operations “is after/before” and “is after/before” have when used.

After: The date operations “is after/before” and “is after/before” or equal to” have been renamed to “exclude rows after/before” and “exclude rows after/before or equal“ to explicitly call out their effects.

Before: Data Transformer would fail to generate total data for groups of columns where a key column had no value

After: Data Transformer correctly creates total data for groups of columns where key columns have no value

Before: Table filtering was only possible on a single column

After: Table filtering is now possible on multiple columns. The conversion from table filter to FilterRule has also been enhanced to support multiple filters.

Before: It was not possible to save a Transformer Job that contained a data source with an empty description. Upgrades to 9.2.10 will fail due to Transformers on the system that have Data Sources with no description.

After: It is possible to set empty descriptions for DataSources in DT. Upgrades to 9.2.10 no longer fail due to Transformers that have data sources with no description.

Before: Renaming rule sets could invalidate file expressions which would then require manual intervention

After: Renaming rule sets now correctly updates references to the updated rule set in file expressions

Before: The creation of some rules, including transform and adding a column types, failed.

Before: It is now possible to create all rule types

Before: For the Job Definitions Redwood_Convert_Excel_toRTX and Redwood_PA_Convert_Excel_toRTX, the IN_RANGE parameter was optional.

After: For the Job Definitions Redwood_Convert_Excel_toRTX and Redwood_PA_Convert_Excel_toRTX, the IN_RANGE parameter is now mandatory.

Before: User created tables could not have grants added to them using the Table Editor.

After: Users can now add/remove grants to tables they have created.

Redwood_FCA library should now have jsoup_.jar and commons-lang3_.jar which are needed for mail-reactor.

Before: Submitting Redwood_Convert_Excel_toRTX failed with class loading error NoClassDefFoundError: com/lmax/disruptor/EventTranslatorVararg when using POI as processing engine.
After: Redwood_Convert_Excel_toRTX can use POI as processing engine without class loading errors.

Before: The Home module had no custom application.

After: The Home module now has a custom application.

Before: A user could not edit the application or partition for a table after it had been created.

After: A user can now edit the application or the partition of an existing table.

Before: Functionality to loop over RTX tables in chains was only available through custom job definitions.
After: Functionality to loop over RTX tables in chains is available with two new system jobs. System_Loop_Over_Table takes an RTX table and executes the only job in the next chain step for each row in that table. It allows optional REL parameters to filter the rows and set the description for looped jobs.
System_Loop_Aggregate creates an RTX table with all parameters and their values of jobs in the previous chain step.

Before: Inserting a row with a context-click would always insert before the row.

After: There is an option to insert a new row before or after the selected row. There is also a keyboard shortcut to create a row after the cursor or at the end of the table.

Before: A table row would be deleted immediately.

After: The user is presented with a confirmation dialog before a row is deleted.

Before: Operators and description of REL Help are both list elements, separated by '-' character.

After: Operators and description of REL Help are displayed in separate columns of a table.

Before: The “create column” checkbox was ignored and the transform replace rule was targeting the new column.

After: The transform replace rule now targets the right column when the “create column” checkbox is unchecked.

Before: The home screen could only display extension points

After: The home screen can now load and display documents

Before: There is no indication whether a column is Mandatory or not.

After: There is a clear indication that a column is Mandatory in column header and in the tooltip.

Before: Not setting the Mail_Theme in FCA_ApplicationCustomizing lead to an exception.

After: Mail_Theme gets treated as “Default” if no value is set in FCA_ApplicationCustomizing.

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.

This fixes a bug in the LocalNode mechanism and as such is part of the Local View functionality introduced in https://redwoodsoftware-eng.atlassian.net/browse/ROSO-10022. This was not yet released, so exclude from release notes.

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: For the Job Definitions Redwood_Convert_Excel_toRTX and Redwood_PA_Convert_Excel_toRTX, the default value for the parameter SET_COLUMN_TYPES was “detect_types_from_values”. For Redwood_PA_Convert_Excel_toRTX it was not possible to set individual column types.

After: For the Job Definitions Redwood_Convert_Excel_toRTX and Redwood_PA_Convert_Excel_toRTX, the default value of the SET_COLUMN_TYPES parameter is set to “string_for_all_columns”. For Redwood_PA_Convert_Excel_toRTX it is now possible to set individual column types according to the input excel file (string, number, date, datetime, datetimezone).

Before: In Docker images that are used for containers running locally via run-redwood-platform the role redwood-administrator was missing.

After: The role was added to the Docker images so that the error Unable to persist: JCS-102014: The inbuilt system Role redwood-administrator cannot be modified doesn’t occur any more
Additional Note: Please ensure that the cloud environments that will get this upgrade provide the role redwood-administrator in the security backend

Before: A warning message appears when the edit rule is selected.

After: No warning message appears when the edit rule is selected.

Before: The table tree view list does not get updated when changes are made to the table's metadata or if there are new tables.

After: The table tree view list updates when there are new tables created and persisted, and if a table's metadata gets changed.

Before: Exports of both PDF and Excel would fail for burst rules and at the rule set level.

After: Exports of both PDF and Excel are now successfully generated for both burst rules and at the rule set level.

Before: Studio and Catalog Admin were shown on Home screen by default in a new RMF installation.
After: Studio and Catalog Admin are not shown on Home screen anymore by default in a new RMF installation and are also removed from the Home screen of an existing installation if not using a customized version of the Home_Modules table.

Before: Filters set on custom fields were not saved in filter profiles and unaffected by “Clear all filters” button.
After: Filters set on custom fields are now saved in filter profiles and get cleared by “Clear all filters” button.

Before: Inbox generated a wrong JobFile reference that is written to the OUT_UPLOADED_FILE parameter of the UserMessage job.
After: Inbox generates a correct JobFile reference that is written to the OUT_UPLOADED_FILE parameter of the UserMessage job.

Before: Nullpointer exception occured when the filter tables for Workbench and Inbox contained filter definitions values with [].

After: This nullpointer exception doesn’t occur any more.

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: You could still switch a Tasklist to be a Global Tasklist with the Global Close Template checkbox, even when the table FCA_SAP_OrgStructure was absent.

After: When the table FCA_SAP_OrgStructure is absent, the checkbox Global Close Template will be disabled.

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.

Before: if, in the Orchestrator, on the Security tab, you add a row, but dont set the user/role and try to save, the save will fail and two errors will be shown: "Error: invoke [s1].saveTemplate did not return a response" and an empty error.

After: if, in the Orchestrator, on the Security tab, you add a row, but dont set the user/role and try to save, the save will be successful (if there are no other errors). The row with no user/role set will just be ignored.

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.

Before: Tasks for local lists were skipped on submit when the corresponding local list in the Orchestrator was not explicitly opened and saved at least once.

After: Tasks for local lists are not skipped anymore on submit when the corresponding local list in the Orchestrator is not explicitly opened and saved at least once.

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.

Before: It was not possible to edit other parameters than "Skip" in a local task.
After: It is now possible to edit all parameters in a local task. Values derived from a global task are now styled slightly different like default values and in addition have the tooltip "Value derived from global task".

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 not setting a value for the parameter Execution in a Global Close Template, the default value “Local” was displayed but it was treated as “Global” and the corresponding tasks were skipped.

After: When not setting a value for the parameter Execution in a Global Close Template, the default value “Local” is displayed and now correctly treated as such and the corresponding tasks aren’t skipped anymore.

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: SAP User Details Synchronize process (FCA_SAP_UserDetails_Synchronize) failed because of the prefix “USER.” in the user name.

After: SAP User Details Synchronize process (FCA_SAP_UserDetails_Synchronize) now succeeds because the prefix “USER.” is removed from user names.

Before: Periods could be partly controlled with unfinished functionality referred to as Periodicity.

After: Periodicity has been removed from the UI. Instead there are now period groups.

• Period Groups are a named collections of numerical periods.
• Each Period Group should be unique in both its name and its periods.
• Each system has a set of default Period Groups defined.
  • These are stored in the Orchestrator_PeriodGroups scripting table.
  • This scripting table can be edited by clicking a button on the main/overview page of the orchestrator.
• Each task list can contain a collection of Period Groups.
  • Default Period Groups can be added to this collection by using the Pencil icon on the Period Groups tab on the edit page of the task list.
  • After adding, no link between the added Period Group and the default Period Group is maintained, so it can be changed at will.
• Each task in the task list can have Period Group property.
  • This property is visible if the containing task list has any Period Groups defined.
  • The editor for this property has a dropdown showing all Period Groups on the task list and any one of those can be set.
  • Setting a Period Group to a task is to be intepretted as “only run this task in the periods contained in the set Period Group”.

Before: Tasks in Orchestrator ended with status Completed although they were not submitted due to errors. These errors were only visible in the logs.

After: Tasks in Orchestrator now correctly end with status Error when there are errors.

Before: Resubmitting inside the Orchestrator would fail to set the Close Date parameter: "The value XXX is not a valid DateTimeZone".
After: This no longer happens, the Close Date parameter is properly filled.

Before: when the Orchestrator was opened on the edit page (skipping the overview page), the context menu entry “Add Process List” would be greyed out.

After: the context menu entry is now active and if you click it, the dropdown containing process-lists-to-add also correctly gets populated.

Before: The Runner did not show Runtime and nonDisplay parameters.

After: When viewing an already-submitted Process, the Runner now shows its Runtime parameters and shows its nonDisplay parameters if the ShowNoDisplayParameters user configuration option is set. When starting to submit a process in the Runner, it will stop showing Runtime and nonDisplay parameters (since these can not be manually set on submit).

Before: When a string parameter value for a task in the Runner was large and therefore only partially loaded, it was editable but shown in red.
After: string parameter values now have a "..." button which pops up an editor window to allow the editing of large parameter values more easily. When a string parameter value is large and therefore only partially loaded, the regular inline editor is disabled and when the "..." button is clicked the editor window pops up. In it, the parameter gets fully loaded and can be edited.

Before: When you make any change to the value of a parameter field in the Runner UI, it would immediately set that value to the parameter of the Process that is prepared on the server. This could be a performance burden depending on the process (parameter) definition.

After: We now no longer set the value to the parameter of the Process that is prepared on the server on any change in the UI, but only when defocussing the input field or when pressing enter.

Before: The Search on the toolbar was not doing anything.

After: The Search on the toolbar now searches across the table's cells for a value.

Before: The window would close if the user presses "cancel" with unsaved changes to the table.

After: If the user clicks on "cancel" when the table has unsaved changes, a prompt will appear to confirm the closure.

Before: Table editor takes a long time to open on a system with a large number of applications

After: Table editor can be opened faster on a system with a large number of applications

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: When switching to a successor/predecessor and viewing attachments the Workbench would refresh to the original task.

After: When viewing attachments the correct successor/predecessor is now displayed.

Before: Workbench reported an error when storing a filter for many parameters (> 1000 characters in corresponding filter markup code).

After: Workbench can handle filters with more parameters.

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: Workbench did not support Time, Date, DateTime, DateTimeZone and Number fields

After: Workbench will now correctly display Time, Date, DateTime, DateTimeZone and Number fields

Before: Chains that were created using a process template and then submitted without being added to a processlist were not shown in workbench, but counted towards the counter.

After: Chains that were created using a process template and then submitted without being added to a processlist are shown in workbench.

Standard BSC notification processes now have optional "Aging reference date" (REFERENCE_DATE) which can be used to define the date for aging calculations. If left empty, close date is used.

The new parameter expects the value in the format YYYYMMDD, eg 20221015

Before: Attachments once created could not have their attachment date changed
After: Attachment dates can now be changed once created

Before: When a user selected columns from a dropdown list, previously-selected columns would still appear as options.

After: Previously-selected will no longer appear as possible options when a user opens a dropdown list of columns

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.

Before: Task/Process nodes in a process list in the orchestrator would have the “Periodicity” property. When setting it, an autosuggested list of values would be supplied containing all periodicities defined in the system.

After: Process lists now have a new tab named “Periodicities”. This tab shows all periodicities assigned to the process list. Initially there are no periodicities assigned to a process list, but the tab also allows the user to add/remove periodicities to the process list. The autosuggested list in the “Periodicity” property on the Task/Process nodes will then only show the periodicities that are assigned to the process list.

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: Studio was only available for testing purposes as a car file that had to be imported manually

After: Studio beta can be downloaded and installed via the Redwood Catalog service.

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.

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.

Before:

Rejected Line items were not marked as reviewed and prepare have to mark them them rejected explicitly.

After:

Rejected line items are now marked as reviewed automatically as soon as approver rejects it.

Before: Table cells in the Balancesheet Reconciliation Line Items view could not be edited.

After: Table columns in the Balancesheet Reconciliation Line Items view can be configured to allow editing of table cells.

Note:
This version of the FDTA implementation requires the ERP AddOn SP03 or higher. The change is NOT backwards compatible.

Before: No stdeer.log file is produced when a transformer job completes execution with rules skipped.

After: A stderr.log is produced when a transformer job completes execution with skipped rules.

Before: RTXTypes weren't supported in Excel. All RTX values were exportd into General Type Cells within excel.

After: RTXTypes are supported in Excel. RTX values are now written in RTXTypes equivalent cells within excel.

Before: It wasn't possible to change the Name, Application, and Description of the DT within the UI.

After: It is possible to change the Name, Application, and Description of the Dt in the UI. 

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: The user is required to click on the text of an option to activate the option.
After: The entire highlighted section of an option will activate it.

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: No Support for output parameter existed

After: A new Rule called Output Parameter has been made available to allow users to set an output parameter of type string.

Before: Transformers automatically restart after an interruption.

After: Transformers do not automatically restart after an interruption.

Before: FA emails had a default theme, that could be swapped to a custom style by setting a new path in the “Mail_CSS” row of the FCA_ApplicationCustomizing table.
After: A new style document has been created and the row “Mail_Theme” has been added to the FCA_ApplicationCustomizing table that allows choosing between the old “Default” theme and new “Plutos” theme. The table now also has a “Mail_CSS_Plutos” row, in addition to “Mail_CSS”, that stores the path to the CSS of the new theme and allows changing the associated CSS of a theme by changing the path to another document.

Before: If a cell value is cut short, there was no tooltip for the cell to display its full value.

After: If a cell value is cut short, there is now a tooltip for the cell to display its full value.

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: Replying to or delegating a message from the Inbox without entering any text resulted in default messages being set.
After: Replying to or delegating a message from the Inbox without entering any text now does not result in default messages being set anymore and leaves the messages empty.

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:

• There was no native way to assign period-based timing to tasks.

After:

• Periods can be created and assigned to groups. Those period groups or Periodicities can be selected for tasks. Then users can submit tasks in a TaskList from the Orchestrator for a given Period then only the Tasks with a corresponding Period Group assigned will be scheduled. Other Tasks that don't have a matching Period Group will be skipped.

Before: New rows will have no value for their keys.

After: New rows created will have a generated key, either incremented from the previous row or based on the new row's data.

Before: A column header displayed a column name in its view.

After: A column header will display the column description if it exists, otherwise use its name.

Before: Dragging and dropping of rule sets to reorder their sequence was not possible.

After: Dragging and dropping of rule sets to reorder their sequence is possible.

To improve the performance of the Initialization Chain, several synchronizations have been made optional.

The default is to NOT synchronize these. If they are used, then they need to be enabled in application customizing as part of the upgrade procedure.

The following keys have been added:

SAP_Sync_Defparm_Table
SAP_Sync_Template_Table
SAP_Sync_Factory_Calendars
SAP_Sync_AbapQuery_Reports
SAP_Sync_AbapQuery_Workspace (Default G)
SAP_Sync_ReportWriter_Reports
SAP_Sync_DrillDown_Reports
SAP_Sync_Check_SAP_Time
FPA_Sync_Defparm_Table
FCc_Sync_Defparm_Table
FCc_Sync_Action_Table

All Job Definitions now have Actions (PreRunning, OnChange, PostRunning). The Triggers that where handling this have been removed.

This means that all custom definition (including duplicates made before this change) also need to have actions added to ensure action processing is done.

The Action specifications can be copied from one of the delivered Job Definitions.