Skip to content

GGCE 2024.4.0 update

We are happy to announce the 2024.4.0 release of GGCE.

Please check the complete list of changes at:

The main new feature in 2024.4 is support for customizable workflows, as well as the form for editing trait observations, canceling actions, improvements in Generating SMTA, **Notifications ** for assigned actions, and other features and improvements listed in the complete list of changes.

Bugfixes:

  • Add a dialog to select the status of the Order Items
  • In vitro: Respect auto-deducted flag of source inventory
  • Cooperator form: enable editing of Easy-SMTA PID
  • Fixed bug in loading order request items (filter not respected)
  • Enable sorting by location in Retrieval list
  • Added forms for editing trait observations.
  • All action grids and schedules support filtering for assignee and include canceled actions.

Database changes:

  • Added workflow_* tables (workflow support)
  • Added workflow_step_id to all _action tables (workflow support)
  • Added is_done to all _action tables (for canceling actions)
  • Added authorized_official_cooperator_id to order_request (for SMTA/MTA generation)

Defining workflows

Administrators can define custom action workflows. To add a new action to the workflow, click and drag from the connector of the origin action and release the mouse button on the canvas. This will open a dialog to add a new action. Double-click on an action to edit the details. Use backspace to remove a step or a connection.

image

Starting workflows

A workflow can be started on any accession, inventory, order request, order item or viability test in GGCE.

Editing trait data

image

Canceling actions

Actions in GGCE could be scheduled/pending, started, or completed. We added a mechanism that allows users to cancel actions instead of deleting them from the database.

image

Generating SMTA

Following your feedback about the pilot SMTA generation in 2024.3 and in collaboration with ITPGRFA we revised how SMTA generation works in GGCE.

  1. There is no change for SMTA for individuals/private persons.
  2. SMTA with organizations requires:
    • Easy-SMTA PID of the Final recipient is sufficient. Easy-SMTA will automatically use the data associated with the recipient PID when provided.
    • When PID is not available, you must associate the authorized official (AO) with the request. This must be a person-type cooperator (with lastname, firstname, organization, email, and address).
Edited by Juan Carlos Alarcon Maldonado
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information