Changelog

What changed across the platform, the runtime, TAF Studio, TAFI, the SDKs and the APIs.

Release notes

These are development updates merged into the platform's shared development branches, listed by date. Formal versioned release notes are coming soon; where a package has a real version number it is shown.

Development updatePlatformAPI

Approval configuration fixes

Fixed

  • Approver resolution by role now respects the environment the request belongs to.
  • Corrections to how approval processes are configured.

Breaking changes

None.

Development updatePlatformAPI

Virtual URL runtime, lifecycle creation route and clearer errors

New

  • Virtual URL runtime: call your no-code endpoints at /vu/..., pin a call to a release with X-Release-Id, and download the app's OpenAPI 3.1 document.
  • POST /api/v1/blueprints creates a lifecycle with its statuses and transitions in one call.
  • POST /api/v1/appobject/flags turns entity features on or off after registration.

Improved

  • Requests for an entity that does not exist now return 404 Not Found.
  • Token refresh is bound to a tenant the user belongs to.
  • Screen definitions carry their names; SQL Server column defaults are handled when tables are created.

Breaking changes

None.

Development updateStudioTAFISDK

Studio fixes, TAFI knowledge base in the gateway, client SDK slices

Improved

  • TAF Studio: fixes from end-to-end testing against real applications.
  • TAFI gateway: the knowledge base ships with the gateway, and notifications can target roles.
  • Client SDK: generic data, identity, workflow and other slices merged to the main branch (0.x).

Breaking changes

None.

Development updatePlatformAPIStudio

Role recipients for notifications and authenticated in-app sockets

New

  • Notifications can be sent to everyone in a role.

Improved

  • The in-app notification socket authenticates the user on the handshake.
  • Script checks return clear HTTP status codes.
  • The TAF Studio knowledge base now includes more than 600 documents.

Fixed

  • Reports show values from nested lookups.
  • Workflows that run after a transition read the latest version of the record.

Breaking changes

None.

tab-sdk 0.0.74PlatformRuntimeSDK

Sign in with Microsoft, recurring billing and bulk status changes

New

  • Sign in with Microsoft for organisations, with a tenant-admin setup page.
  • Recurring subscription checkout.
  • TabSdk.transition.bulkUpdateStatus moves many records to a status in one call.

Breaking changes

None.

Development updatePlatform

Approvals that start when you are ready

New

  • An approval process can wait until someone raises the request, instead of starting on every write, so records can stay in draft.

Breaking changes

None.

Development updatePlatformRuntimeSDK

Find and remove orphaned entities

New

  • List entities whose table or view no longer exists, and remove them with a dry run first.
  • TabSdk.app.getOrphanedAppObjects and unregisterAppObjects.

Breaking changes

None.

Development updateRuntime

Share action follows the entity's sharing setting

Improved

  • The Share action appears only on entities that allow sharing.

Breaking changes

None.

Development updateRuntimeSDK

Copy permissions between roles

New

  • Create a role from an existing one and copy its permissions.
  • New roles without a source get default access.
  • TabSdk.role for role permission setup, and TabSdk.billing for billing.

Breaking changes

None.

Development updateRuntimePlatform

Report schedules as records

New

  • Report schedules are stored as records, with each run's outcome shown.

Breaking changes

None.

Migration guides

No changes so far require a migration. When one does, its guide will be linked here and in the release entry.

Known issues

  • Push notificationsThe push channel is not yet available for delivery. Use in-app, email or SMS.
  • Resending failed notificationsFailed email and SMS deliveries are recorded but not resent automatically.
  • Runtime languageThe runtime interface is in English; language switching is coming soon.
  • New screens and menusAfter publishing a new screen, users may need to reload the app to see it in menus.

Stay current with TechAppForce development

One email when something changes that developers should know about.

  • New APIs
  • SDK updates
  • TAF Studio releases
  • TAFI updates
  • Tutorials
  • Developer events