Difference between revisions of "Cascade Weight"

From TMM Wiki
Jump to navigationJump to search
m
(No difference)

Revision as of 16:05, 21 November 2008

NATS 4
Members Admin
The Members Admin
View Member Details
Add Member
MySQL Auth
Mod Authn DB
Multisite Access
Member Logging
Member Password Retrieval
OpenID Connect
Mod Auth OpenIDC
ID Numbers
Billers Admin
The Billers Admin
Biller
Biller Fees
Taxes
NATS Cascades
Add Cascade
Cascade Weight
Autocascade
Hidden Cascades
Geo-Targeting Cascades
Post-Biller Templates
HTTPS Gateways
Timed Cascade Rules
Upgrade Plus
Token Plus
Gateway One Step Join
Extra Biller Fields
Send Information To Special Biller
Setting Rules
Cross Sell Supported Billers
Upsell Supported Billers
Packageplus Supported Billers
Tokenplus Supported Billers
NATS 3
Billers Admin
Biller
Cascade
NATS Cascades
Adding Cascades
Biller Cancel Promotions
Cascade Weight
Autocascade
Hidden Cascades
Geo-Targeting Cascades
Type-In Cascade
Post-Biller Templates
Extra Biller Fields
HTTPS Gateways
Payment Deduction
Timed Cascade Rules
Multiple Biller Accounts
Upgrade Plus
Adding a Biller

How do I use the Weight setting of a Cascade? The cascade weight field lets NATS randomly switch between two or more cascades.

Finding the Weight setting

Go to the Billers Admin and Edit the desired cascade.

If more than one cascade exists with the exact same description, then NATS selects which cascade to use when the join form loads. This selection is based on the total weight of all cascades that share a description. Figure 1.4 depicts how this process works:

Figure 1.4 - When NATS Selects a Cascade

Figure 1.4 provides an example cascade scenario that involving three cascades all with the same description and different weight values. Since they all have the same description, NATS creates a "pool" of all the cascades. This "pool" contains 75 copies of the Third Cascade, 100 copies of the Second Cascade, and 50 copies of the First Cascade for a total of 225. After NATS creates this pool, it randomly selects which cascade to use from said pool, which means that the more "entries" that there are in this pool for a single cascade, the more often it will be selected.