OpenTokens: Token Actions

OpenTokens™: Token Actions

The OpenTokens™: %ACTION()% tokens support the actions listed below. The token is structured like this:

%ACTION(action_code|parameter_list)%

Parameters

action_code required literal action code, see a complete list: OpenTokens™: Token Actions

parameter_list optional literal additional parameter(s), depends on specific OpenTokens™: Token Actions

Or the actions can also be used in the OpenTokens™: %VAR()% tokens, using this structure:

%VAR(mivavariable|action|format|parameter_list)%

%VAR(dbfield|action|format|parameter_list)%

%VAR(specialcode|action|format|parameter_list)%

The following actions are available:

BESTSELLER|position does a lookup for the top sellers product (position "1" is top seller) then follows OUIPROD lookup above

CAT|category_code calls Customer_Category_Find_Code

EXCLUDE|product_code_list sets up an exclude list that is used by the RANDOMPROD, RANDCATPROD and RANDOMCAT actions to exclude the products (or categories) that are specified in the list. For convenience, the exclude list continues thru the end of the screen, and must be blanked out to "turn it off", if desired (ie: %ACTION(EXCLUDE|pc1,pc2|RANDOMPROD|1|EXCLUDE|)%)

OUICAT|category_code does above CAT and MvFIND NAME="OUI_Categories"

OUIPROD|product_code does above PROD and MvFIND NAME="OUI_Products"

PROD|product_code calls Customer_Product_Find_Code, OUI_Display_Price and CurrencyModule_AddFormatting

RANDCATPROD|catprodslot|category_code|product_count does a lookup for a random product, limited to the specified category and assigns it to the specified category-product slot, then follows OUIPROD lookup above (all catprodslot "1" is same product). Specifying the # of products in the category (prodcnt) will improve the speed/performance of this action.

RANDOMCAT|catslot does a lookup for a random category and assigns it to the specified category slot, then follows OUICAT lookup above (all catslot "1" is same category)

RANDOMPROD|prodslot does a lookup for a random product and assigns it to the specified product slot, then follows OUIPROD lookup above (all prodslot "1" is same product)

XCFIELDS|customer_id reads the custom customer fields into the g.OUI_XCustomers structure, using the field code as the member name. The field "prompt" is also loaded into the g.OUI_XCustomers_Prompts structure, also using the field code as the member name.

XCFIELDS_WRITE|customer_id saves the custom customer fields from the g.OUI_XCustomers structure (using the field code as the member name) into the actual custom fields.

XCATFIELDS|customer_id reads the custom category fields into the g.OUI_XCategories structure, using the field code as the member name. The field "prompt" is also loaded into the g.OUI_XCategories_Prompts structure, also using the field code as the member name.

XCATFIELDS_WRITE|category_id saves the custom category fields from the g.OUI_XCategories structure (using the field code as the member name) into the actual custom fields.

XORDFIELDS|order_id reads the custom order fields into the g.OUI_XOrders structure, using the field code as the member name. The field "prompt" is also loaded into the g.OUI_XOrders_Prompts structure, also using the field code as the member name.

XORDFIELDS_WRITE|order_id saves the custom order fields from the g.OUI_XOrders structure (using the field code as the member name) into the actual custom fields.

XPFIELDS|product_code reads the custom product fields into the g.OUI_XProducts structure, using the field code as the member name. The field "prompt" is also loaded into the g.OUI_XProducts_Prompts structure, also using the field code as the member name.

XPFIELDS_WRITE|product_code saves the custom product fields from the g.OUI_XProducts structure (using the field code as the member name) into the actual custom fields.