A strategy can be a reusable or centralized piece of logic that can be referred to by one or more strategies.
- The strategy referred to by the sub strategy component has the external input option switched on (context menu). This external input connects to the starting components that define the reusable chain of components.
- In another strategy, the sub strategy refers to the reusable strategy and it is driven by other components. When you run this strategy, the use of this sub strategy components results in effectively replacing the sub strategy component with the chain of components that are propagated through the referenced strategy.
- Strategy rule form - Completing the Strategy tab
A strategy is defined by the relationships of the components that are used in the interaction that delivers the decision. The Strategy tab provides the facilities to design the logic delivered by the strategy (the strategy canvas) and to test the strategy (the Test runs panel).
- About Strategy rules
Strategies define the decision that is delivered to an application. The decision is personalized and managed by the strategy to reflect the interest, risk, and eligibility of an individual customer in the context of the current business priorities and objectives. The result of a strategy is a page (clipboard or virtual list) that contains the results of the components that make up its output definition.
- Completing the Strategy rule form
Strategy rules - Completing the Create, Save As, or Specialization form
- Strategy rule form - Using the Strategy Properties tab
The Strategy Properties tab displays details of the strategy's applicability in the decision hierarchy and the properties available to the strategy:
- Declare Trigger form - Completing the Pages & Classes tab
Use this tab to list the clipboard pages referenced by name in the Triggers tab. See How to Complete a Pages & Classes tab for basic instructions.