In the Legacy Portal, if we needed to change the due date for a published requirement form, we could simply adjust/modify the due date in the Requirement Record. In the new Applicant Portal, we do not have that ability. Instead, we must set one standard due date for all records of the requirement form in the Program Workflow settings but we are unable to override those dates if we need to make an adjustment or provide a deadline extension for a specific applicant. As a result, the due dates we see/set in the Requirement Record now have no correlation to the true published due date.
We need to have the ability to modify/override the due dates again like we did in the Legacy Portal.
This is a huge problem for us as well. We frequently have timeline amendments that push due dates on a case-by-case basis. For now, we are still using the requirement due date (and not the form due date - we didn't set one when we set up the Program in the new portal) but this date doesn't appear anywhere in the grantee portal because it's a field on the Request/Requirement. Blackbaud told us to put the due date field in the form itself so that when grantees open it, they see it, but this is cumbersome and not a good solution.
This is necessary - no-cost extensions are literally part of why you have grants management system. How did you decide to remove this?????????? Did anyone consider grants when they made the new system?
Yes. There needs to be a closer connection between the requirement form and the requirement record. The due date set on the workflow should become the default due date on the requirement. Then let us change the requirement date if needed for specific situations.
This is a huge problem for us. We must be able to customize reporting dates by grant and not by form (our projects all have different duration).
This is a significant problem
Oh absolutely. I have users who need requirement dates changed all the time.