Because this is a complex features to implement, the best approach for developing your dynamic business rules is to adopt an incremental approach as you and business users of Oracle Commerce Workbench coordinate tasks.

It is also helpful to define the purpose of each dynamic business rule in the abstract (before implementing it in Developer Studio or Workbench) so that everyone knows what to expect when the rule is implemented. If rules are only loosely defined when implemented, they may have unexpected side effects.

Begin with a single, simple business rule to become familiar with the core functionality. Later, you can add more advanced elements, along with additional rules, rule groups, zones, and styles. As you build the complexity of how you promote records, you will have to coordinate the tasks you do in Developer Studio (for example, zone and style definitions) with the work that is done in Oracle Commerce Workbench.

Copyright © Legal Notices