Submit Feedback
Legacy Knowledge Base
Published Jun. 30, 2025

Configuring hard-coded Instance Setting properties in a Liferay SaaS environment

Written By

Justin Mann

How To articles are not official guidelines or officially supported documentation. They are community-contributed content and may not always reflect the latest updates to Liferay DXP. We welcome your feedback to improve How To articles!

While we make every effort to ensure this Knowledge Base is accurate, it may not always reflect the most recent updates or official guidelines.We appreciate your understanding and encourage you to reach out with any feedback or concerns.

Legacy Article

You are viewing an article from our legacy "FastTrack" publication program, made available for informational purposes. Articles in this program were published without a requirement for independent editing or verification and are provided"as is" without guarantee.

Before using any information from this article, independently verify its suitability for your situation and project.
Note: please note that Liferay has renamed its Liferay Experience Could offerings to Liferay SaaS (formerly LXC) and Liferay PaaS (formerly LXC-SM).

Issue

  • Some properties that can normally be configured through an Instance Setting in a local Liferay DXP environment are hard-coded in a Liferay Saas environment.
    • One example is the Journal Article Maximum Version Count

Environment

  • Liferay SaaS
  • Liferay DXP 7.4

Resolution

  • In order to change these properties in a Liferay Saas cluster, you can set the corresponding property in the portal-env.properties file, which will then change the property for the Instance Setting.
    • The property will still be uneditable through the UI
    • For example, if you would like to change the Journal Article Maximum Version Count to 5, you can set the following property in the portal-env.properties file:
configuration.override.com.liferay.journal.configuration.JournalServiceConfiguration_journalArticleMaxVersionCount=I"5"
Did this article resolve your issue ?
Legacy Knowledge Base
Did this article resolve your issue ?