The Email Tool is found in FMP layouts and tabs corresponding to proposals and reviewers.
Using peer reviewers as an example, you can use the email tool to send email either to an individual reviewer or a found set of reviewers, such as those whose active roles include 'Peer Reviewer'.
Clicking 'This Reviewer' or 'Found Set' generates a pop-up window where you select an email template to send.
If you need to edit an existing template or add another, click 'Add / Edit Templates'.
Each template needs a description, recipient group (To), subject, and message; Cc and Bcc are optional.
You may add a single attachment to either a template or to the set of emails you're about to send, by clicking the red 'paper-clip' button. This form of attachment does not involve the file being uploaded to the server, but rather retrieved via the local path specified, so only provide a local path when attaching a file. If you have difficulty attaching a file from its original location, copy the file to your desktop and try attaching the file from there.
Coding subjects and messages to be database-driven is complicated, but powerful. The best method by which to learn how is to look at the existing templates already in your system. The most common error people make when coding these fields, however, isn't in using functions, but rather forgetting to encapsulate all static text.
Issues With Windows - Email Tool
Microsoft Outlook doesn't trust any other program to send mail, even if you tell Outlook to do so. So if you choose to send email to a found set of individuals, it will ask you to confirm every single one of them. A solution is being sought.
To change the PI of a proposal, go to either the Pre-Proposal or Full Proposal FMP layout and select an investigator as PI.
This cannot be done if the proposal was already promoted to PM.
This action updates tables where the proposal PI is noted, as well as fields reflecting investigator type for the investigators involved. Changing the PI for a full proposal record will propogate to the pre-proposal phase (if applicable), and vice-versa. The proposal ID (e.g. Bray_1234) is NOT changed. If the new PI doesn't have a password, the system automatically assigns one to them. A new password can either be sent to the new PI by the Administrator, or retrieved via the 'Retrieve Password' link on the log-in page.
The Investigators portal in the Pre and Full Proposal FMP layouts can only be used to assign a non-PI as PI for a proposal, not to change a non-PI to another type of non-PI (e.g. Co-PI to Associate).
Proposal data may be duplicated by using the 'Duplicate Proposal' button available in Pre-Proposal and Full Proposal FMP layouts.
This duplication process only includes data (cover page or 90-2 info, budgets, and investigator association), not accompanying documents that were uploaded for the proposal.
To duplicate a proposal:
Call (e.g. RFP FY2014 - Internal)
Title (remove '[duplicate]' and rename as appropriate)
Start Date (e.g. 2/1/2014)
Comp Date (e.g. 1/31/2018)
The duration applied to each duplicated budget worksheets also needs to be updated, which can be done either by the Admin or the PI who's responsible for the proposal.
This is a system parameter ("current_FY_global") that indicates to the eSG system what the current Omnibus Cycle (or Funding Year) is, and affects the output of time-dependent information in 90-4s, 90-2s, and other forms and pages. For example, it affects the set of funding years that are compiled for Overall 90-4 forms. eSG Administrators manage this value in FMP configuration; see FMP Interface Configuration - RFP.
URLs for web interfaces used in RFP component of eSeaGrant
: Registration
: Pre-Proposal, Full Proposal, and Rebuttal submission
: Administrative Review
: Pre-Proposal Review
: Peer Review
: Panel Review
RFP FMP interface naming convention: <SG program acronym>_RFP_<version date> (e.g. "MITSG_RFP_23_June_2014")
RFP FMP Users
Super-Admin (full access)
password: *ask*
Admin (record read/write; no design access; no versioning authority)
password: *ask*
User (record read/write, excl. passwords; no design access; no versioning authority)
password: *ask*
Reader (record read-only, excl. passwords; no design access; no versioning authority)
password: *ask*