List of changes for portingset: 9.3e ------------------------------------------------------------------------ r2019_3: # 81471 (BDUX77946): Cloud Platform Manager V1.0 Date: Tue, 26 Nov 2019 13:31:36 +0100 Created on: r2019_3 Type: bugfix _Problem Description (Customer terms)_ Cloud Platform Manager V1.0 _Affected Executables_ bshell6.2 cld_platform_mngr cld_landscaper _Motive source_ JIRA:LND2-29250 ------------------------------------------------------------------------ r2019_3: # 81405 (BDUX77791): D704185: Sales Contract - Terms & Conditions Link results in Database Error 221 Date: Thu, 21 Nov 2019 10:30:31 +0100 Created on: r2019_3 Type: bugfix _Problem Description (Customer terms)_ Sales Contract - Terms & Conditions Link results in Database Error 221 _Test Procedure_ Sales Contract - Terms & Conditions Link A regression test has been enhanced to verify that a record can be linked to/unlinked from an object. _Affected Executables_ Bshell ------------------------------------------------------------------------ r2019_3: # 81300 (BDUX77729): Totals not correct after changing layout in Report Designer Date: Mon, 11 Nov 2019 16:57:07 +0100 Created on: pset2019_4 Type: bugfix _Problem Description (Customer terms)_ When a report is created which displays totals by production order. When printing this report standard in LNUI, the behavior is correct. When printing the report to Report Designer and modifying the height of the specific layout (or any other change not related to the total field), the total calculation is not correct anymore. It seems that changing a layout in Report Designer has an impact on the total calculation. In our opinion, this is not correct. This is a result of the combination of the print condition and the calculation in the personalization (as the layout with the filed is personalized as well) _Workaround_ NA _Test Procedure_ change something in the report to make a personalization with totals, like printing in bold. _Affected Executables_ repgen _Motive source_ InforXtreme:675840 ------------------------------------------------------------------------ r2019_3: # 81275 (BDNT77584): split minmax init into mininit and maxinit Date: Thu, 07 Nov 2019 09:16:52 +0100 Created on: r2019_3 Type: bugfix _Problem Description (Customer terms)_ First "total by order" always print 0 in "Quantity Delivered" column. _Workaround_ Do not have a min and a max on the report. _Test Procedure_ have report with both min and max and see that only one is correct. _Affected Executables_ Repgen _Motive source_ InforeXtreme: 681879 ------------------------------------------------------------------------ r2019_3: # 81243 (BDUX77690): Call Graph Profiler: disable jump.retry.point for PROFILE_TRAMPOLINE Date: Fri, 01 Nov 2019 16:24:48 +0100 Created on: Mussorgsky Type: bugfix _Problem Description (Customer terms)_ Sometimes the bshell can start looping or crashing when using PROFILE_TRAMPOLINE=retry.* _Workaround_ Don't use PLATFORM_TRAMPOLINE=retry.* _Affected Executables_ bshell6.2 ------------------------------------------------------------------------ r2019_3: # 81164 (BDUX77621): Bugfix: overwriting string literal Date: Thu, 24 Oct 2019 15:10:41 +0200 Created on: r2019_3 Type: bugfix _Problem Description (Customer terms)_ Some code overwrote a string literal if it was called with a nullptr. This has been changed. _Test Procedure_ Built with the dev6. ------------------------------------------------------------------------ r2019_3: # 81141 (BDNT77570): mb.type: allow void argument, especially string array Date: Tue, 22 Oct 2019 16:27:47 +0200 Created on: r2019_3 Type: enhancement _Problem Description (Customer terms)_ Bshell function mb.type now accepts void argument, in order to allow to determine the type (sb or mb) of an unallocated based string array. _Motive source_ TCS:800-232020 ------------------------------------------------------------------------ r2019_3: # 81071 (BDNT77329): file.mv should move file with read permissions if directory permissions are correct. Date: Tue, 15 Oct 2019 16:17:47 +0200 Created on: Mussorgsky Type: bugfix _Problem Description (Customer terms)_ the file.mv does not move the file when permissions of file is read only and the directory permissions are correct. _Workaround_ change permissions or do a copy/remove action. _Test Procedure_ execute the file.mv function on a file with only read permissions, but the directory permissions full. _Affected Executables_ bshell _Motive source_ InforXtreme:697598 ------------------------------------------------------------------------ r2019_3: # 80995 (BDUX77446): add TMP and TEMP so logic service will pass it to the bshell Date: Tue, 08 Oct 2019 13:23:11 +0200 Created on: r2019_3 Type: bugfix _Problem Description (Customer terms)_ When we try to use Excel device for personalized reports in Report Designer, then the Excel file generated is with zero size. The issue appears only to users who do not have local administrator right on LN Server or are not connected via SSO. _Workaround_ Set the variables in the bse_vars _Affected Executables_ blogind _Motive source_ InforXtreme:698561 ------------------------------------------------------------------------ r2019_3: # 80874 (BDNT77266): convert2unicode: converting more than one table with the same bdbreconfig-worker Date: Tue, 17 Sep 2019 13:54:20 +0200 Created on: r2019_3 Type: bugfix _Problem Description (Customer terms)_ Conversion to unicode is converting the same table multiple times. _Test Procedure_ A new test has been added, which converts two table two times. The second time using only one worker. Before the change in this project this test failed. _Affected Executables_ bdbreconfig ------------------------------------------------------------------------ r2019_3: # 80824 (BDNT77205): Problem starting BW when startup parameter contains a dot Date: Fri, 06 Sep 2019 12:49:30 +0200 Created on: r2019_3 Type: bugfix _Problem Description (Customer terms)_ BW is started through a commandline. When one of the extra arguments on this commandline contains a dot this argument is treated as a BW configuration file. An error message is given such as: "Could not load configuration file ...". _Motive source_ InforXtreme:697332 ------------------------------------------------------------------------ r2019_3: # 80780 (BDUX77139): Bic: Use of non-existing SQL bind variable with enum keyword name should give compile error Date: Fri, 30 Aug 2019 10:36:34 +0200 Created on: Mussorgsky Type: bugfix _Problem Description (Customer terms)_ If an enum keyword is, by mistake, used as a bind parameter in a SQL statement, then bic should give a compile error. For example, the following should give an error: :txfrc.doty.order This error is not detected by bic, but running the program fails because the variable "txfrc.doty.order" does not exist. _Test Procedure_ See Problem Description (Customer Terms). A regression test has been added. _Affected Executables_ bic _Motive source_ InforXtreme:686136 ------------------------------------------------------------------------