Arena PLM connector
Read and update items, bills of material, change orders and quality records
Authentication
API key
A long-lived key issued by the vendor. Stored encrypted and never exposed to agents, prompts or logs.
Requires a vendor administrator to issue a key with the permissions the WorkStream needs.
Configuration fields
- API key
- Region or base URL
- Account or workspace identifier
How VeroTX governs the Arena PLM connector
- Credentials are held in the platform credential vault. Agents never see them.
- Every call runs as a step in a versioned WorkStream Playbook, so the rules that apply are the rules that were published.
- Actions that cross a policy threshold stop at a tollgate and wait for the named approver.
- Each call is written to the Execution Ledger with the inputs, the result and the Playbook version in force.
What the Execution Ledger records for a Arena PLM call
- 1
Credential resolved
API key credential released from the vault to the connector runtime. The step never sees the secret.
- 2
Action called
A WorkStream step called Arena PLM with the inputs recorded on the step, under the Playbook version in force.
- 3
Policy evaluated
Thresholds on the step were checked. Anything over the limit stops at a tollgate and waits for the named approver.
- 4
Result written
The response from Arena PLM, the timing and the Playbook version were written to the Execution Ledger.
Where this connector is used
Product records, bills of material, change orders and release control.
Other plm and engineering connectors
See it run
Connectors only matter inside a WorkStream. The product tour walks a request from intake through a tollgate to a recorded result.