Production order
Produces a batch from the bill of materials: components are deducted from stock, the shop floor logs hours via mobile phone, and upon completion, the batch's actual cost (materials consumed + hours) is compared against the BOM's standard cost. The finished product enters stock at actual cost.
What you find on this screen
A portrait of the screen, read from the screen itself — it changes when the screen changes.
Available actions
Test against the contract
The list shows
ResourceActionDecisionWhy
Form fields
NomeNome da extensão em desenvolvimento, do jeito que ela vai aparecer na loja.
DesenvolvedorQuem está construindo a extensão nesta caixa de areia.
VersãoVersão que está sendo testada antes de ir para revisão.
DescriçãoO que a extensão pretende fazer; é este texto que a revisão lê primeiro.
SituaçãoEm rascunho, em revisão ou publicada. Na caixa de areia a extensão não toca dado de cliente.
Registrada emQuando esta versão foi enviada para a caixa de areia.
Start here
O que esta tela responde
Whether an extension does what it promises — and only what it promises. The sandbox exercises, resource by resource and action by action, what its permissions contract allows, against synthetic data.
What this screen is
A safe space, with SYNTHETIC DATA, for the developer to test an extension against its permissions contract before trusting it. Choose a published extension and see, resource by resource and action by action (READ / WRITE), what the contract ALLOWS and what it DENIES — including the effect of the approval limit on a test amount. It's the same default-DENY decision of the single authorization point, exercised without touching any real tenant data.
How to
What this screen answers
An extension may have the right to read a resource and not to write to it. The sandbox shows both answers per resource, because that's exactly where the unpleasant surprise lives — the extension that only "queries" and issues a write request.
Rules
Dado sintético, sempre
No real data from your company enters here. That's what makes the test safe to run before trusting: you find out what the extension would try to access without it accessing anything at all.
Frequently asked questions
Which question this screen answers
How do I test what an extension can and cannot do, with no risk to my data? Choose a published extension and the sandbox exercises, resource by resource and action by action (READ / WRITE), the same default-DENY decision of the single authorization point — showing what the permissions contract ALLOWS and what it DENIES, including the effect of the approval limit on a test amount. Everything runs on synthetic data: no real tenant data is touched in the exercise.
Was this article helpful?
In the same module: Extensions2
Tenka Academy
Explore the AcademyStep-by-step learning paths for your industry, inside the platform.