We have over 500 Final Reports coming in, we review them in batches as they are coming in and find many with issues (they didn't attach the right item, their budget didn't add up etc) and many without issues. If we could mark some as 'Reviewed - has issue with budget', 'Reviewed - has issue with financial statements' etc, then we can bulk email groups of them according to issue. Even just 'Reviewed - has issues' would be good. They are not "Done" but they are "Reviewed" unlike the rest.
Also our dashboards pull and list the Final Reports/Requirements by retrieval date and as ones we had to "send back for resubmission" DO have a retrieval date, they show up in the dashboards whether or not they re-submitted and this adds confusion. It is very hard to tell them apart, so if they could be somehow labelled or shown to be different, that would also be good.
Hi Violet.
I believe that a Requirement custom field could address your first issue.
Regarding your second issue:
There is a field in the Requirements record called Resubmission_Application_ID. You can use this field in Advanced Searches to determine the Publication for Resubmission and resubmission status of a Requirement.
The values in this field can be as follows:
NULL - the Requirement has never been Republished for Resubmission.
Zero - The Requirement has been Published for Resubmission and has been resubmitted.
Any other number - The Requirement has been Published for Resubmission, and has not yet been resubmitted.
So, to find all Requirements Published for Resubmission, and not yet submitted, you would use this in the Advanced Search:
ISNULL(Activities.Resubmission_Application_ID, 0) <> 0
You can exclude Requirements that have been Published for Resubmission and not yet resubmitted from your Received Requirements list by adding to in your Received Requirements not yet Done search, for example:
Not (Activities.Received_Date Is Null) AND Activities.Done_Flag = 0 AND ISNULL(Activities.Resubmission_Application_ID, 0) = 0