Differences
This shows you the differences between two versions of the page.
rtd_manual_ch_12_interfacing_with_other_applications [2012/12/27 11:42] mark [RTD API - FUNCTIONS REFERENCE] |
rtd_manual_ch_12_interfacing_with_other_applications [2012/12/27 11:45] (current) mark [OTHER FIELDS] |
||
---|---|---|---|
Line 61: | Line 61: | ||
Be sure everything works as expected before deployment. Verify using the SIMULATE button! | Be sure everything works as expected before deployment. Verify using the SIMULATE button! | ||
You can fill the "Order ID" field with a valid ord# you have. | You can fill the "Order ID" field with a valid ord# you have. | ||
- | Clicking the button, you will see a pop-up that will show all the fieldsnames and values your actual | + | Clicking the button, you will see a pop-up that will show all the fieldnames and values your actual |
setup would have created on that order submittal. | setup would have created on that order submittal. | ||
In the pop-up you will also see the option of testing a real send to your page: | In the pop-up you will also see the option of testing a real send to your page: | ||
Line 187: | Line 187: | ||
One of the most interesting uses of external variables is to give you a way to "connect" you own system | One of the most interesting uses of external variables is to give you a way to "connect" you own system | ||
with RTD. | with RTD. | ||
- | Let's suppose you do have your own ecommerce site, and you link RTD just to create the design. | + | Let's suppose you do have your own eCommerce site, and you link RTD just to create the design. |
When design is submitted from RTD, you can use the "External Notification on Submittal" to lead your | When design is submitted from RTD, you can use the "External Notification on Submittal" to lead your | ||
customer back to your site but... how to know what he ordered into RTD? | customer back to your site but... how to know what he ordered into RTD? | ||
Line 221: | Line 221: | ||
will be returned as "product_id" value | will be returned as "product_id" value | ||
- if you call again RTD by add-in &extvar_product_id= to the url, "product_id" value will simply be | - if you call again RTD by add-in &extvar_product_id= to the url, "product_id" value will simply be | ||
- | nullifyed | + | nullified |
* STEP 3: USING AND APPLYING RULES TO THE PRICING MATRIX | * STEP 3: USING AND APPLYING RULES TO THE PRICING MATRIX | ||
And finally, how to see external variables rules in action! | And finally, how to see external variables rules in action! | ||
Line 255: | Line 255: | ||
add => 1 | add => 1 | ||
cmd => _cart | cmd => _cart | ||
- | businness => yourpaypalemail | + | business => yourpaypalemail |
currency_code => USD | currency_code => USD | ||
bn => PP-ShopCartBF | bn => PP-ShopCartBF | ||
Line 267: | Line 267: | ||
- "amount" as the value for "ORDER: Total Order Price" | - "amount" as the value for "ORDER: Total Order Price" | ||
As you can see, you now miss some fields which are not part of the generator: | As you can see, you now miss some fields which are not part of the generator: | ||
- | add, cmd, businness, currency_code, bn=PP-ShopCartBF, no_shipping and no_note | + | add, cmd, business, currency_code, bn=PP-ShopCartBF, no_shipping and no_note |
To pass them to the PayPal script, you can use "Custom Params". Here's how they should be compiled | To pass them to the PayPal script, you can use "Custom Params". Here's how they should be compiled | ||
for this example: | for this example: |