0
Application variables cannot be marked as required
Source: twentyhq/twenty#25837 · opened by @emmanuelhb56
What happens serverVariables have carried isRequired since they existed. applicationVariables never did — even though those are the ones each workspace has to supply for itself: its own tenant id, its own credentials, whatever an app cannot ship a default for. Once an app is installed, a workspace that is one credential short looks exactly like a finished one. Every variable renders the same, nothing distinguishes "not filled in yet" from "not needed", and the logic function simply receives an empty string. Why it matters Running a single app across several workspaces, there is no way to tell which installations are still missing their credentials without opening each one and knowing, from outside the product, which keys mattered. The failure is silent: the app looks installed and behaves as if it were configured. What would resolve it Let an application variable declare isRequired, the same way a server variable already can, and surface how many required var…
No pledges yet. Be the first to back this.
Comments
Similar requests
Feature Request: Error Nodes for Workflows
1 vote · 0 comments
Save custom values in settings to be used anywhere
1 vote · 0 comments
Email Webhook Sync on gmail 📨
4 votes · 0 comments
[Workflow] API keys variables
1 vote · 0 comments
Enhancing Twenty for Supabase Compatibility: Custom Database Configurations, Schema Adjustments, and S3 Storage Integration
5 votes · 0 comments
No comments yet.