![]() |
![]() |
![]() |
|
![]() |
|||
![]() |
|||
![]() |
GoLive 6 Dynamic Content Samples | ||
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
![]() |
||||||
Main View | Administration View | How it Works | ||||||
![]() |
||||||||
![]() |
|
A. Dynamic table to display form errors. B. Error message. C. Form controls for entering credit card and billing information. D. Form submission button. Content SourcesThere is a single content source, the Order Form. AAll of the checkout pages have a similar design. There is an orange section at the top to display errors, and then a form for entering or changing order information. The errors are displayed using a dynamic table bound to the Order Form/Order Errors content source. This content source gives a list of all the errors. If there are no errors, then the dynamic table has now rows and is invisible. Otherwise there is one row per error message. BThe error text is bound to the Error Message field of the Order Form/Order Errors content source. CThe form controls are all simple bindings to the appropriate fields in the Order Form. Every Custom Merchant provider offers a different set of fields, so you'll need to tune your checkout pages to your provider. To create a radio button control, you create one button for each possible value, and then bind them all to the same field. At runtime, the radio button that corresponds to the current value is selected. In this example the list of credit cards is known ahead of time. The Stories/Edit page shows how to construct a radio button control dynamically when the list of choices is stored in a database. DThe Continue button submits the user's billing information using the Update Order Form action. If there is an error, it redisplays the current page so that the user can fix the problem. Otherwise it goes on to the Place Order page. |