In the each new levels of patch, Sage do bring the new changes and hot fixes that needs to be identified and needs to be monitored that might hamper the existing customization when the upgrade patch is executed.
To avoid this we should need to understand what new changes or hot fixes sage has deployed in the newer patch level. According if that clashes with the existing customization then we need to handle it prior deploying the patch.
When the each new version is released the Sage do provide release notes that needs to gone through. But rather than going through each patch level, now sage has provided the new independent utility as Patch finder.
The Patch finder is the new component present in the installable which needs to be installed by the below steps:
There is the zip file which holds the patch finder exe as shown below:
Once the folder is unzipped we will be able to see the X3 Patch finder exe in that particular folder.
We need to run the exe, that will land you to the below independent utility as shown below:
In the above UI we need to select the Product and release: From release and the destination release. The next filter we can manage is Modules on which we need to monitor.
Next set of filter can be applied is at the level of changes brought in version as follow:
Type of filter
This filtration would be applied on the do we need to consider the Bugs in the reports, new enhancement brought that might bring the table level or architecture changes. Do need to consider Entry points that newly introduced or any other changes that are brought.
Search fields and criteria:
Search field filtration would help to understand the changes related to Object, Key or all fields needs to highlight in the upgrade the version.
We can put filtration on the specific object filtration also.
Once we are all set for to filter the data, we would need to hit on the Search button.
Below is the report will help you identify the component and holds the below column.
Key: We will identify the key that fix will identified, each fix has its own key to identify the issue.
Type: Enhancemenyt/ Bug
Summary: Explanation of the fix.
Product area: Module on which modification is present.
Object: modification on TRT,tables screen or any other if present. If we go to the TRT and search the Key we will be able to trace the modification easily.
Release: In which release the fix is been applied.
This will help us to understand the in which the medication is done. We can expo-rt the data in the CSV, PDF, EXCEL or print as per the button on the tops.
We can also copy the entire data and paste on the notepad.