Application properties and concept components

e-Commerce applications, such as Infor e-Commerce, are programmed with features that can be activated and deactivated individually, depending on the specific requirements of the application you are developing. Unlike feature elements (see Feature elements), application properties are evaluated when your application is deployed, so code for disabled features is not even present in the deployed presentation.

The following mechanisms enable application property settings to control the features of your presentation:

• All of the code responsible for creating a particular feature is nested within Concept Components on each relevant page. Each Concept Component is then assigned to a boolean application property. If its application property is set to "false", then the component will be removed during deployment, thereby removing all of the code nested within the component.

• You can also assign each page to an application property. If a page’s application property is disabled, then the entire page will not be deployed.

When the boolean value of an assigned application property is "false", then, it is disabled and its pages and Concept Components will not be present in the deployed application.

In Infor e-Commerce, for example, the default application includes several application properties established for the purpose of implementing features. Relevant groups are named to identify a type of features; the elements of each area establish individual options.

See the documentation for your web application for a description of the various application properties.