separated all kanban boards into a main navigation element
added number of days since a compound has been at the current status to the compound kanban board
changed all kanban boards to display the assignee in the corner, instead of the author
changed all kanban boards to display “None” columns by default – so records with missing details are not hidden initially
changed the visualization of user names throughout the application, so that authors are in a rectangle shape with full name, while assignees are in a circlular avatar with initials
compound list view has now a sorting dropdown in the corner which allows putting e.g. most voted compounds at the top
fixed an issue with compound kanban boards which prevent cards from being fully draggable – dragging only worked by title, now the entire surface is draggable
fixed an issue with single step reaction analysis that prevented the component panel from appearing below the compound editor
single compound view now has a description field with rich text support, and the kanban board has been extended so that mouse over tooltips of compounds display these compound descriptions
fixed an issue with tag creation which prevented showing case insensitive matches from being displayed
added OpenIDConnect support to the authentication options to work with Keycloak or Auth0
fixed an issue with accessing the SAML service metadata descriptor endpoint, as a result of it, the URL of it changed. for details please see the configuration guide
resolver plugins can now by used on the hypothesis sketcher
quick search in the toolbar now finds compounds by virtual IDs after synthesis completed (and real corporate IDs have be assigned)
fixed an issue with the hypothesis sketcher were drawing arrows was not possible from right to left
fixed an issue with the single compound view where the list of compounds could be infinitely scrolled
changed the logic associated with tag filtering such that space characters within your tag (during a search) do not result in 2 partial query conditions
fixed an issue with uploading plain text files that cannot be categorized by the browsers into any mime type
adjusted the look and feel of filtering and sorting options in design set overviews for easier access
added a new role based access control system to the application that allows assigning users to groups, and limiting what actions are permitted for these groups. For details please see the configuration guide
adjusted the absolute time displayed in tooltips to always include calendar year
improved the layout of kanban boards to keep row and column headers in the view while scrolling
fixed an issue where the value of a text filter is not displayed in the text field after reloading a search page
fixed an issue where PowerPoint documents generated by the application, opened in JChem for Office displayed a warning while editing
changed the rendering method of plugin documentations from plain text to HTML. For details please see the respective developer guides
changed the URL scheme used by the structure upload API. For details please see the REST API documentation
with the retirement of JChem Web Services Classic, Design Hub now requires JChem Microservices DB, IO, Structure Manipulation and Markush Enumeration modules, so new configuration options have been created to configure the location of these modules. For details please see the configuration guide
adjusted the layout of hypotheses editing on small screens
hypothesis pages can now be reordered by drag & dropping them
AWS S3 based filestore is now available using the filestoreImplementation option. For details please see the configuration guide
improved the performance of file attachments across the application by generating and loading thumbnails of images where possible
the admin area now supports changing JChem Microservices DB molecule type and forcing the resyncronization of PostgreSQL content to JMS DB if needed
users can now register API keys to access the applications's public API. For details please see the API documentation
Design Hub has been upgraded to NodeJS v12 which delivered higher performance and easier memory configuration. For details please see the NodeJS release news
fixed an issue where an admin flash message / banner has overlapped content in the application
fixed an issue where a freshly created compound tag was not visible in the list of autocomplete suggestions on subsequent tag creation
fixed an issue where the compound list didn't properly display the priority of each compound
plugins now display short error messages straight from the problem source if the results cannot be fetched to prevent displaying inconsistent results or empty screens when an error occurred
compounds can now be starred (watched) in all views to easily gather updates made on them
improved the error messages displayd during design set sharing
adjusted the layout of large kanban boards so that column headers stick to the top of the screen
search results can now be paged based on the number of estimated hits
fixed an issue where an unordered SQL query mixed up the result of design set sharing
dropped the /databases volume declaration of the docker image of Design Hub
an administrative panel is now available where configuration of content statuses, Marvin JS toolbar details, JChem Microservices addresses and user flash messages / banner messages can be configured
from this version anonymous daily aggregate statistics are now collected in a PostgreSQL database schema called usage. Migration from the previous JSON file store is handled automatically by the database-migrator module
fixed an issue where deleted compounds were counted in the statistics of a design set
adjusted the layout so that virtual / real compound IDs no longer overlap with portions of the compound 2D image
a dashboard is now available as the starting page of the application with latest designs, latest comments and updates from projects you track
it is now possible to load plugins from remote sources where the plugins implement a simple REST API matching the concepts of previous NodeJS plugins. For details, please see the respective developer guides
from this version PostgreSQL database schemas are used to store data corresponding to a domain configured in Design Hub. The migration from the public schema is automatically handled by the database-migrator module, but if the pre-programmed conditions are not met, instructions will be printed in the console
fixed an issue where periodic check in the external registry only processed the first compound of a batch
active session data is now stored in a PostgreSQL database schema called session