You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This question comes out of a concern raised in the 7/17 brainstorming session that we may want the content of notifications to be different for projects where the applicant is DCP. This raises a broader question about conditions under which we want notifications to be different or even skipped based on details about a given project.
Questions:
Are the there any details about a project besides public status and public visibility that should affect whether a notification is triggered or the contents of the notifications?
If so, what are they and which, if any, are required for an MVP.
Based on conclusions here, we may create separate follow up question Issues.
The text was updated successfully, but these errors were encountered:
No project-specific conditions should cause a notification to be skipped
Template text for projects may be different for applications depending on whether or not DCP is the appilcant
For DCP applicant projects, email should include link using the same URL that ZAP Search uses in the "Learn more" button - dcpAdditionalpublicinformation. This field in ZAP is used for some private projects but we should only use it for DCP-applicant projects
This question comes out of a concern raised in the 7/17 brainstorming session that we may want the content of notifications to be different for projects where the applicant is DCP. This raises a broader question about conditions under which we want notifications to be different or even skipped based on details about a given project.
Questions:
Based on conclusions here, we may create separate follow up question Issues.
The text was updated successfully, but these errors were encountered: