2024.3

If you have customized any of the changed reports noted in the lists below, you can examine the changes in these reports by customizing and/or examining the original report.

If you are looking at a J1 Desktop report, select the <Original> report and click the Customize button to copy the updated report into the module report PBL. You can then compare the updated original report with your previously customized version and decide if you want to re-customize the original or to modify your customized version.

If you are considering a JICS report, find the location of the report pbl and the name of the report by checking the UI Configuration in the J1 Desktop software. Then use InfoMaker to navigate to and compare the original report and your customized version. Decide if you want to re-customize the original or to modify your customized version by making similar changes.

For J1 Web reports, check the C:\Program Files\Jenzabar\J1 2024\Web\Plugin\Application.json file to find the location of the xxWebReport.pbl files, where xx is the module prefix. This location is defined during the install. In the future, if you have customized the report, use InfoMaker to navigate to and compare the original report and your customized version. Decide if you want to recustomize the report as a copy of the original or to modify your customized version by making similar changes. See Working with Reports in J1 Web for more information.

The Original versions of Additional Reports are installed to an “Original Additional Reports” subfolder of the J1 program folder and are copied from there to the location specified during the install. In an update, only any completely new PBL files are copied to the specified Additional Reports location from the J1 program folder location.

If you modify an Additional Reports PBL but need to view or revert to the original version later, it can be found in the subfolder of the J1 programs folder.

In the event a change to an Additional Reports PBL is made, the modified version is available in the subfolder of the J1 programs folder.

The J1 installer has the ability to detect whether a custom forms PBL file has already been updated to the current version and avoids performing this update again.

Most of the installer runs with elevated privileges, which may allow it to update files that the current user could not otherwise modify, such as the contents of the Program Files folder. The forms update process, however, runs with the privileges of the current Windows user. Jenzabar recommends that someone logged in as a user who has permissions to update the Custom forms files run the installer first.

Once these shared files are updated, installing the update on subsequent computers will not attempt to repeat the update process. This is because the installer, when it first performs the PBL modification process, marks that PBL so that, for every other installation done at the customer site, this form update process does not execute and therefore will not provide an error for a user without elevated privileges. If the service pack is first installed by a user who does not have permissions to update the Custom form files, that user will receive a warning message communicating the fact that the custom forms have not yet been updated to the version that matches this service pack.

If you use a silent install process on all other client machines, the INSTALL_CUSTOM_FORMS=0 silent install parameter accomplishes the same result. However, by doing the step above, you have removed the need to include the INSTALL_CUSTOM_FORMS=0 silent install parameter but you still may continue to use it.