You create a style in the Styles view of Oracle Commerce Developer Studio.

A style serves three functions:

Rule properties are key/value pairs typically used to return supplementary information with promoted record pages.

For example, a property key might be set to "SpecialOffer" and its value set to "BannerAd.gif".

As Oracle Commerce Workbench users and Developer Studio users share a project with rule properties, it is easy for a key to be mis-typed. If this happens, then the supplementary information represented by a property does not get promoted correctly in a Web application. To address this, you can optionally create property templates for a style. Property templates ensure that property keys are used consistently when pipeline developers and Oracle Commerce Workbench users share project development tasks.

If you add a property template to a style in Oracle Commerce Developer Studio, that template is visible in Oracle Commerce Workbench in the form of a pre-defined property key with an empty value. Oracle Commerce Workbench users are allowed to add a value for the key when editing any rule that uses the template’s associated style. Oracle Commerce Workbench users are not allowed to edit the key itself.

Furthermore, pipeline developers can restrict Oracle Commerce Workbench users to creating new properties based only on property templates, thereby minimizing potential mistakes or conflicts with property keys. For example, a pipeline developer can add a property template called “WeeklyBannerAd” and then make the project available to Oracle Commerce Workbench users. Once the project is loaded in Workbench, a property template is available with a populated key called "WeeklyBannerAd" and an empty value. The Oracle Commerce Workbench user provides the property value. In this way, property templates reduce simple project-sharing mistakes such as creating a similar, but not identical property called "weeklybannerad".

Copyright © Legal Notices