March 2024 GMAS Release

February 22, 2024

The March 2024 release will be available on Monday, March 11th. The focus of this release includes updating and enhancing screens related to requesting signatures, converting Changes to existing segment requests to the updated GMAS interface as well as performance improvements and bug fixes.

Signatures

Related resource: Signature Job Aid

Requested by:  Central offices

Reason:  

  • The current process for setting and changing required signatures was not well known
  • Required Signatures lacked flexibility
  • Converting this module helps the GMAS convert work move forward

Enhancements: 

  • Added the ability to set signature requirements by request type.
    • Offers flexibility if different roles are required to sign off on different types of requests.
  • Added the ability for creating different pre-award related roles within the central offices so that not all individuals are listed as a Central Administrator.
    • Differentiating between pre-award roles will allow for better configurations across different request types ensuring the correct central person defaults to sign off.
  • Converted the Internal organization home page.
  • Converted and combined the Request Signatures Screens.
    • Added ability to change defaulted person up until they sign.
  • Added ability to remind signatory to sign.
    • New “Send reminder” button on signature panel opens email client with prepopulated email, that includes the attestation language, to remind signatory that they are required to sign
  • Retirement of 4 screens used in the previous signature workflow

 

Changes to existing segment requests

Related resource:  Internal and Change Requests Job Aid

Requested by:  Central offices, departments, and schools


Reason:  

  • Converting this module helps the GMAS convert work move forward

Enhancements: 

  • Converted five of the remaining eight Changes to existing segment requests
    • Converted screen will show when bundling converted request types. If request is bundled with any non-converted type, the old request screen will still be used.
  • Newly converted Changes to existing segment requests:
    • Pre-award expenditures
    • Carryforward
      • Created ability to take money from multiple “from periods”
    • No-cost extension
      • Created ability to extend period within segment dates so that year logic extensions are possible
    • Interfaculty involvement at no additional cost
    • Early termination
  • Remaining Changes to existing segment requests types will be converted in next release
    • Change PI, Equipment Rebudget, Rebudget Restricted Categories

 

Other enhancements

  • Performance Enhancements to reduce load time on large projects
  • Created ability to edit dates before editing budget on proposal home
  • Changed “Mailing instructions” field to say “Submission instructions”
  • Added a link to the associated subrecipient record from the accounts screen for subaccounts.

Bug fixes 

  • Fixed issues with date pickers
  • Fixed bug that prevented event from generating when creating a Sub at no cost request
  • Updated Request and transaction monitoring dashboards to sort project numbers properly

Technical upgrades​ 

  • Enhanced ECRT code to fix GitHub security warnings to upgrade Bouncy castle to 1.76
  • Refactored code on Changes To Existing Segment Request Home
  • Update OAIR Delete Job to treat "'null' is null or not an object'" as a success
  • Update OAIR Delete Job to treat "Cert cannot be withdrawn in state 'Withdrawn'" as a success
  • Upgraded JCraft JSch in GMAS to latest version
  • Retired Apigee API ats-gmas-estr-SearchServices
  • Upgraded frontend-maven-plugin 1.6 to 1.12.1 (ui-skin)
  • Implemented Sun Editor to replace CK Editor

 

An additional small release was needed to fix a few small bugs related to this release. The changes went live on Friday, March 22. The changes included:

  • Fixing an issue navigating to requests that included more than one Interfaculty Addition from the same Org 
  • Correcting an issue with routing required signatures within WYSS
  • Sending notifications to signatories added after the initial Lock and Route