NXT handles inactive appeals much more restrictively than database view. While database view just gives a warning when an inactive appeal is used, NXT blocks batch submission entirely unless the appeal is removed or updated. This is a problem for recurring gifts, which must retain their original appeal for our reports—so twice a month, I delete 30+ appeals in NXT and re-enter them in database view. Aligning NXT with database view’s approach would eliminate unnecessary work and reduce risk of error.
We have a similar issue with the appeal that is recorded on our RG records. This appeal is the acquisition source and could be a specific appeal from over 20 years ago. We use the acquisition source in our reporting, so don't want to lose this information.
At the same time, we do not want this appeal to be active so that is shows in the active appeal list when entering new gifts. With the current functionality, we are unable to change the appeals to inactive as the batch approval will fail. It would be ideal if Inactive values do not affect batch approval and processing.
We definitely need to allow inactive appeals when processing gifts in NXT, especially with automated Recurring Gifts. It is important for us to be able to report on what previous appeals ended generating even after years. It shows impact. The end date to an Appeal is useful for us to keep historical information.