About the development cycle

At a high level, this is the expected development cycle for a custom content version:

• Enable a test portal for development and create a new content version.
• Make and review modifications.
• Close the content version for development.
• Create a production portal.
• Add and activate the custom content version, as an override to the standard content version, in the production portal.
• When revisions are necessary, make a copy of the closed custom content version, giving it a new version number.
• Add the new version to a portal through content activation and enable it for development.

All of these tasks are described in the portal administration guide, beginning with the section about personalizing the portal. When personalizing or customizing portal content, these tasks are the same. If you already have users set up and a test portal enabled for development, as described in the portal administration guide, you do not need to complete these tasks again to further customize the portal.

Also be sure to review the portal documentation about updating content versions. Information is provided about how to use a comparison tool, such as KDiff3, to make sure Infor content version updates are kept in sync with your customized portal content. For on-premises environments, this information is in the portal installation guide. For cloud environments, this information is in the portal administration guide.