CoreMedia Studio supports a variety of IBM WCS preview functions directly:
Time based preview (time travel)
When a preview date is set in CoreMedia Studio, it sets the virtual render time to a time in the future. If the currently previewed page contains content from IBM WCS, it is desirable that also these content reflects the given preview time. That could be a marketing spot containing activities with different validity time ranges. A specific activity could be valid only after a certain time or a marketing teaser that announces a happy hour could be another example.
If such data is requested from IBM WCS within the context of a CoreMedia page, the preview date is also sent to IBM WCS as a genuine IBM WCS preview token. The IBM WCS recognizes the transmitted preview date and renders a control on top of the page that lets you inspect the currently active settings. Figure 5.25, “Time based preview affects also the IBM WCS preview” gives an example.
Customer segment based preview
![[Note]](../common/images/fep7plusbutton.png)
The commerce segment personalization is not available in IBM WCS (FEP6).
Another case where editors need preview support is the creation of personalized content. That is, content is shown depending on the membership in specific customer segments. In addition to the existing rules, you can define rules that are based on the belonging to customer segments that are maintained by IBM WCS. These commerce segments will be automatically integrated and appear in the chooser if you create a new rule in a personalized content. For a preview, editors can use test personas which are associated with specific customer segments.
Figure 5.26, “Test Persona with Commerce Customer Segments” shows an example where the test persona is female and has been already registered.
Such preview settings apply as long as they are not reset by the editor.
The test persona document can be created and edited in CoreMedia Studio. The customer segments available for selection will be automatically read from the IBM WebSphere Commerce Server.
Personalized content based on commerce customer segmentation rules can be used in both, the content-led scenario and the commerce-led scenario. If the CoreMedia CAE is rendering IBM WCS content, like catalog items or marketing spots, the given user ID is also sent to the IBM WCS. So all content that is received from the IBM WCS is delivered within the context of the current IBM WCS user.
The IBM WCS segments that the current user belongs to are available during the rendering process within a CoreMedia CAE. Thus, content from the CoreMedia system can also be filtered based on the current IBM WCS segments.
In the other direction, if the personalized content is integrated within a content fragment on a IBM WCS page, the current IBM WCS user is also transmitted as a parameter. Thus, the CoreMedia system can retrieve the connected customer segments from the IBM WCS in order to perform commerce segment personalization within the supplied content fragments.
B2B Contract based preview
CoreMedia Adaptive Personalization has been extended to support a personalized site preview for B2B contracts from IBM WCS. A two-step configuration needs to be applied in order to use the B2B contract based preview within Studio. See Section 5.7, “Enabling Contract Based Preview” to learn how to enable contract based preview.
 |  |  |
 |