Allow for characteristic cards to be tracked through multiple queues.
When a referral is denied, expired, snoozed, or has any movement between community queues, the characteristic card will disappear. The tracked characteristics will not move from one queue to the next. Given that a community has multiple queues, the user can not search client by a characteristic when the referral has been created from a denied referral, expired or snoozed referral.
Example: The characteristic card follows the referral until it expires, is denied, or snoozed. When a new referral is created from an expired/denied/snoozed referral, it looses the characteristic card, when added to a different community queue.
Adele Campbell
shared this idea
As part of our ongoing efforts to build the best feedback platform for you, ideas that have not received a vote or comment in the past year have been set as “Archived.” Please feel free to resubmit this idea using this submission guide.