How to Display Multiple Prices (Res/NR) in WebTrac 3.1
Problem
I know that WebTrac will charge different fees according to who is logged in (ie: a Resident versus a Non-Resident) but is there a way, by module, to display the different prices on the WebTrac search screen (item details)?
Solution
Yes, this is possible. In the Daily Processing Profile, there is a group of fields entitled 'Global Sales Model Household.' The fee codes and other characteristics of the primary member of the Model Households you link to each module determine the pricing that displays in WebTrac (and other) search results.
By linking multiple 'Model Households' to a module, you can display multiple prices for that module. Each Model Households linked will display a price in the Price column. You can link as many Model Households as you need. The reason you are allowed to build Model Households and link as many as you wish is to give the customer ultimate flexibility without needing to create a custom brochure.
Examples:
Park District A has a Resident Price and a Non-Resident Price for their activities, so they would create two Model Households, and link the proper Fee Code (Resident or Non Resident) to the primary member in each respective Model Household. They would link those Model Households to the Activity Module on the Daily Processing Profile. Finally they would re-label the Price column in WebTrac to indicate the different prices (Resident/Non-Resident) and it would look like the screenshot attached.
Park District B may have Resident, Non-Resident and School District prices, so they would create three Model Households, and for each household, set the primary member's fee code to represent that fee type. Link those three models in the Daily Processing Profile, and re-label the Price column accordingly.
Park District C has Resident/Non-Resident Prices for Pass Management, but for Activity they have Resident/Non-Resident/Member Prices. They would setup Resident and Non-Resident Model Households and link to Pass Module (like Park District A). Then they would create a Model Household for Member and actually issue the primary person in that household a pass that never expires, thus making them a perpetual 'member'. They'd link the three Model Households to Activity Module in Daily Processing Profile.
If Park District D has a senior discount for patrons over 65, they could create a Model Household where the primary member is age 65+. The possibilities are endless.
Key Notes:
1 The order that you link the households in the Daily Processing Profile is the order that the prices will display. So be aware and choose them from the picklist in the order you wish them to display.
2 The User that is set as the 'Run as' on the 'SearchIndexBuilder' scheduled event is the User whose Daily Processing profile is used. (In the future, this will likely be changed to look to the User on the WebTrac Interface Parameter, but for now this is how it works.)
3 After setting this up, the Search Indexer will not automatically re-index all records, so you will not see the new prices immediately. You can re-index all records by going to Scheduled Events Maintenance, click 'Add Misc Event', choose Search Index Builder from the Scheduled Program and click 'Create All Index Records.' You can cancel out of this. That will create an event to 're-index' everything and should make the prices show once the SearchIndexBuilder process completes. It can take a while the first time. You would do this after you update and link the Model Households. From that point forward, individual activities are re-indexed automatically after price changes are made.
See Attachment: Untitled.jpg