Today, there is no way to cleanly reuse a conditional application to truly preserve the configurations.
Here are all the caveats if a client were to reuse a conditional today.
The name of the current conditional will reflect onto all previous, archived cycles that used that Conditional. For example, even if the name was at one time Music, if it gets changed to Science it will reflect as Science on the archived Application.
This new name will also reflect onto all of the Opportunities “Source”. For example, if the “Music Scholarship” was once associated with the Music Conditional and this Music Conditional changed to Science Conditional the Source will change to “Science Conditional” even if the Opportunity is archived.
The Associated Opportunites tab will contain a list of all Opportunities that were associated which could get quite messy.
No one will know that this Conditional was reused and once Conditional X and is now Conditional Y.
We are going (and are beginning) to have clients who want to repurpose their conditional applications because they found a new/better use case or because the initial admin left and the new admin has a new/creative idea for it.
Thank you for your consideration. Please let me know if you have any additional questions or concerns.
Employee Name | Monika Spreitzer |
Client Name "shard name" | ou, uwyo, southalabama, uic, usm, cmc, bahamaseducation |
User | Opportunity Admin, System Admin |
Functional Unit | Conditional Application |
Please add CMC to list of clients who would like this functionality changed.
UCCS wants this as well.