Flex Package and Subscription Summary

One of our subscription-heavy resident groups has recently had us set up a flex package.  They're used to seeing the subscription summary screen.  With a flex package order, they are unable to set the season or status.

Is this normal?  Is something set up incorrectly?  

Parents Reply
  • A few options come to mind:

    Order Category is a useful high-level field because it's included in the Order Search screen and a few reports. You could use this to label orders that need action, and reset the field to (none) or another value when complete. The values come from TR_ORDER_CATEGORY.

    The Special Request screen is available for all package and performance line items and includes a notes field, a category dropdown, and other seating request fields. This can be useful if you want to use the notes field for a specific purpose separately from the order notes field, and when there is a lot of products in the order. 

    Customer Service Issues can be configured to require the selection of a package (specifically, in TR_CUST_ACTIVITY_TYPE). This can be part of a workflow where you record some notes that require action, review open actions with the View All Customer Service Issues screen, and then mark them closed when completed. 

    And as Amber mentioned, constituencies are a great way to mark subscribers in general, and you might want a special constituency for these folks. The Manage Constituency utility can be scheduled to automate the application and removal of constituency codes based dynamic lists of constituents with the flex package in their Package History.

Children
No Data