In May, we focused on making Scholarly more configurable, more responsive, and easier to tailor to institution-specific workflows.

App Upgrades

• There is now a special CV document type within My Documents

• Fixed a bug with deactivated users in an institution showing up in user-selection modals in the application

• Further enhanced our permissions structure to accommodate custom roles

CV Import & Faculty Activities Upgrades

• CV sections are now better targeted to institution-specific sections

• We fixed a bug where we no longer import data into archived faculty activities

• Added a boolean field type for faculty activities

• Created finer-grained control over the display of faculty activity fields and where they are displayed

Workflow Upgrades

• Select questions can now have conditional values in workflows

• Workflows can now be sent back, even if they are completed

• Introduced a new voting question type

• Enabled emails sent from workflows to use HTML and not just plain text

Reporting & API Upgrades

• Grids now load in realtime

• Grids now respect per-institution custom field configurations and order

• Grid export filenames now contain the institution name, record type, and date of the export

• The API now returns a clear error when attempting to set the calculated start and end dates of a faculty activity

• Fixed a bug where we would not fire webhooks when record custom field values being updated in certain situations

• Fixed a bug where Scholarly would return a 500 status code if filters were malformed

Taken together, these updates give institutions more control over permissions, cleaner reporting, and smoother workflow execution.

That’s a wrap for May! Questions or feedback? Your account team is here to help at support@scholarlysoftware.com. See you next month!