2026.14 Infrastructure Changes
1 min read
Changes on Application environment
Change | Environment Variable Name | Application Default Value | Example | Required | Applications | Short Description |
|---|---|---|---|---|---|---|
Added |
|
|
| false |
| Enable insertion of rows in Agentic Table before or after a selected row. |
Added |
|
|
can also be scoped by company id’s: | false |
| Enable rendering of images and files in new iFrame with code toggle. html rendering via reflector. |
File Access Migration Update
As part of this release, a file access migration in backend-service-ingestion will be executed for all customers, regardless of whether the File Access feature is currently enabled.
The data migration will initiate automatically during the deployment. This process updates existing indexes to support the new file access structure. It can take a bit longer than usual for the migrations step of the service to finish. The expected duration is approximately 10 minutes per 1 million chunks, depending on your environment size and file volume.
Switch from npx to pnpm exec in migration hooks
To improve consistency and performance across Node-based tooling, migration hooks have been updated to use pnpm exec instead of npx.
What changed:
Previous command used
npxto invoke Prisma migrations.New command uses
pnpm execto invoke the same Prisma migration task.
Action required:
Update your migration hook commands from npx to pnpm exec.
Replace all occurences of
npx prismawithpnpm exec prisma
Example (backend-service-ingestion):
hooks:
migration:
command: |
cd /home/node/app/services/node-ingestion/prisma; npx prisma migrate deploy --config ../prisma.config.ts;replace with
hooks:
migration:
command: |
cd /home/node/app/services/node-ingestion/prisma; pnpm exec prisma migrate deploy --config ../prisma.config.ts;Author | Solution Engineering |
|---|