Comparing content versions for an update

By using a directory comparison tool, such as the suggested KDiff3, you can see a list of Infor content version components, by type and name, that conflict with your customized components. After you identify the components, there are various ways to get the content back in sync. We recommend that you use the layout, FDF, and page editors provided in the Portal Manager.

Follow these steps to compare content versions using KDiff3:

  1. One by one, export these content versions: the original, or base, Infor content version; the new Infor content version; and your custom content version that was created from the base Infor version.
  2. Extract each content version .zip file to a separate directory: Infor Base, Infor Update, and Custom.
  3. Start Kdiff3 and specify the Infor Base directory for A, the Infor Update directory for B, and the Custom directory for C. Click OK. When the status dialog box opens, click OK.
  4. All portal component directories are shown in the results. You are primarily concerned with column C, which represents the custom content version.

    If column C shows a green or black box, it means there are no customized components in the directory that have a conflict with the updated Infor content version. No action is required.

    If Column C shows a yellow box, it means components in that directory have been customized and they were also changed by Infor in the latest version. You can expand the component directory and scroll through the list to find the components that have a conflict. They too will have a yellow box in column C. Double-click a component to see more detail about the differences.

  5. At this point, we recommend that you open the Portal Manager for a development portal with a new custom content version activated to contain the updated customizations. You can then work with the various identified components under Content Development. Remember that in order to view or edit components from a specific content version, that content version must be activated under Portal Configuration > Content Activations. Refer to the portal customization guide for information about using the component editors in the Portal Manager.