March 2023 Updates

by Michael Parsons

In March 2023, we introduced default journals to make building single-journal ledgers simpler and smoother. Significant additions were also published to the docs site.

What's Changed

  • Default journals in every ledger. In many cases, users only need a single journal, so now every ledger will contain a default journal (with code DEFAULT). This also simplifies many common queries by making the journalId filter option optional - it will use the default journal if not provided.
  • New Journal.code field, an optional unique code for journals.
  • Support for Global Object Identification in the GraphQL API. All persistent core accounting models in the GraphQL schema now implement the Node interface, meaning that they have a globally unique id field and can be queried using the global Query.node field.
  • Integrated timestamps into transactional operations: mutation operations committed within the same transactional context will have the same created and modified timestamps in the same way that Postgres now() and CURRENT_TIMESTAMP works.
  • Configurable account sets with AccountSetConfig. For now, the config only has one option enableConcurrentPosting that optimizes the account set for a ridiculously high rate of entries written. The tradeoff is that read operations for balances become much more expensive and slow; to be used with caution.
  • Regional WAFs are deployed in every account/region.
  • Suite of Tutorials published on the docs site, including the "Twisp 101" tutorial and a set of "Foundations" tutorials covering the basic operations for the ledger.
  • Additional reference documentation on the API covering concepts like pagination and the various error types.

View the full changelog at