You are here: Getting started > Release notes

Release notes

Journal Entry Management v1.4.0

Released January 2018

New features and improvements

  • After you publish a solution, you can now open it in the Excel Add-in directly from Studio. JIRA WIN-13988
  • Journal Entry Management now has a Run tab. JIRA WIN-14975
  • The Publish Solution command has moved to the Run tab. JIRA WIN-14978
  • You can run scripts in Debug mode. JIRA WIN-15118, WIN-8762
  • You can choose between the run options Run Specified Rows, Run Only Error Rows, and Run Only Unprocessed Rows. JIRA WIN-8761
  • You can use the Preserve header item formatting option to avoid writing over customized formatting for headers. JIRA WIN-15052, WIN-11552
  • The extended log for validation is now written for Journal Entry v9.x solutions. JIRA WIN-14406
  • Solutions that use BAPI_ACC_DOCUMENT_POST now take the user name directly from the solution properties. JIRA WIN-14635

Bugs fixed

  • You can now set an option to preserve formatting when writing headers. JIRA WIN-11552
  • You can now work with protected sheets. JIRA WIN-15421, WIN-11127, WIN-8746
  • Posting result is now returned to the correct row in solutions that have column-based mapping. JIRA WIN-15317
  • Extra characters are no longer returned in extended log messages for validation. JIRA WIN-14230
  • Full file names are now shown in the log viewer and properties for Journal Entry v9.x solutions. JIRA WIN-13857
  • Park is no longer available for Batch mode scripts. JIRA WIN-11865/WIN-15766
  • Journal Entry 9.x solutions that have the First line item contains header amount property checked now insert the split row at the top of each chunk. JIRA WIN-14810
  • Journal Entry 9.x solutions now return Extended Log information. JIRA WIN-14406
  • Runners can now perform single-company posts in BAPI solutions that were configured for multi-company posts. JIRA WIN-14690
  • Check boxes in the Properties panel must be clicked explicitly (clicking near the check box will not check or uncheck it). JIRA WIN-17698

Known issues

  • The Journal Entry 9.x and Journal Entry Management Excel Add-ins cannot be active at the same time. For help with deactivating the 9.x Excel Add-in, see the Compatibility section in About Journal Entry Management. JIRA WIN-13339
  • Auto map does not work the same way that it did in Journal Entry 9.x. Instead, it stacks some headers and can cause conflicts. It is not recommended in this version.
  • Journal Entry Management does not support scripts that were recorded in GUI Scripting mode.
  • DMS attachment mode is not currently supported. JIRA WIN-12432
  • Custom LOVs for custom fields and LOVs that depend on the values of other fields are not supported.
  • Multithreaded online validation is not supported for SAP systems that do not have Winshuttle Function Module (WFM) v11.3.0 installed. If WFM is installed on the system, multi-threaded processing happens automatically in the background.
  • If conditions that include document values in the header must be mapped to the same cell or column for document balancing. JIRA WIN-14166
  • Runners must specify the skip field indicator in the Excel Add-in. JIRA WIN-13888
  • In the FBD1 template, the lookup values are not opening up for the Exchange Rate field. JIRA WIN-13306
  • Complete extended log messages are not written to the Extended Log column when running validation. JIRA WIN-16566
  • Run actions cannot be performed from within Studio for non-English language versions; run actions can be performed from the Excel Add-in. WIN-20013
  • Journal Entery v9.x scripts cannot be scheduled from JEM Excel Add-in. WIN-18219
  • When posting column-based scripts, JEM is exceeding the specified document length. WIN-17694
  • Start row can be changed even after script has been submitted to Foundation. WIN-18561

Journal Entry Management v1.3.0

Released June 9, 2017

This is not a general-availability release.

Features

Solution authors can re-customize Journal Entry 9.x scripts and save them as Journal Entry Management v1.0 solutions.

Known issues

  • The Journal Entry 9.x and Journal Entry Management Excel Add-ins cannot be active at the same time. For help with deactivating the 9.x Excel Add-in, see the Compatibility section in About Journal Entry Management. JIRA WIN-13339
  • Auto map does not work the same way that it did in Journal Entry 9.x. Instead, it stacks some headers and can cause conflicts. It is not recommended in this version.
  • The preservation of existing workbook formatting is not respected in this version.
  • Debug mode is not supported.
  • Journal Entry Management does not support scripts that were recorded in GUI Scripting mode.
  • DMS attachment mode is not currently supported. JIRA WIN-12432
  • Custom LOVs for custom fields and LOVs that depend on the values of other fields are not supported.
  • Multithreaded online validation is not supported for SAP systems that do not have Winshuttle Function Module (WFM) v11.3.0 installed. If WFM is installed on the system, multi-threaded processing happens automatically in the background.
  • JEM 1.3.0 does not work with password-protected workbooks.
  • The Debit/Credit Indicator field cannot be set in solutions created from scripts that were recorded in Transaction v10.x or earlier, because the data type is not compatible. To update the data type, click Synchronize. JIRA WIN-18541
  • If conditions that include document values in the header must be mapped to the same cell or column for document balancing. JIRA WIN-14166
  • Runners must specify the skip field indicator in the Excel Add-in. JIRA WIN-13888
  • Complete extended log messages are not written to the Extended Log column when running validation. JIRA WIN-16566