Page tree
Skip to end of metadata
Go to start of metadata

Highlight of the release

  • Detail view for records (or forms)

Detail View / Forms

We're introducing a "detail" view.

  • It lets you see one record, vertically.
  • It's great because records now have a permalink!

 

Improvements

  • PLAYSQL-222 - Getting issue details... STATUS  In the setup, we require a schema name when in spreadsheet mode (read-write). The reason is, if there is no schema name, the last schema will be used, and if it's a JNDI connection pool, the previous connection may have changed schemas.
  • PLAYSQL-222 - Getting issue details... STATUS  In the setup, we've fixed the space drop-down. It lets you set different connection details for a given space than the global connection.
  • PLAYSQL-219 - Getting issue details... STATUS  Fix a bug with the User picker and Page picker for cells. We've used the new menu/autocomplete API that we've created in PLAYSQL-194 (see below).
  • PLAYSQL-218 - Getting issue details... STATUS  Fix minor bugs for Internet explorer.
  • PLAYSQL-194 - Getting issue details... STATUS  The menu for the rows couldn't appear. We've replaced Confluence's default menu system with our own one, because the API changed too often and doesn't respond to Play SQL's needs.
  • PLAYSQL-206 - Getting issue details... STATUS  We use an external plugin named "PSEA" to export to Excel. The plugin is shared between Play SQL and Requirement Yogi, which decreases the memory requirements by 15Mb for instances where both are installed. PSEA must be present, and is installed when Play SQL is installed.
  • PLAYSQL-125 - Getting issue details... STATUS  is the issue for the delivery of the detail view / forms.

 

Issue list

Key Summary T Status Resolution Component/s
Loading...
Refresh

Upgrade notes

  • The "PSEA" plugin will be installed together with Play SQL Base or Spreadsheets. It is required. It performs the Excel exports.
  • As explained above, the Legacy SQL Macro is removed. Please do not upgrade if you still require it.
  • If you upgrade from Play SQL 2.6, there are new requirements:
  • If you upgrade from Play SQL 2.9, there are schema changes:

Known issues

Key Summary T Status Resolution
Loading...
Refresh

 

  • No labels