Environment variables

[jhoetter]

Is your feature request related to a problem? Please describe. I work with Symanto's API to enrich my textual data with e.g. communication style or personality traits. I store the token in my functions, but that feels cumbersome to manage as soon as I have multiple heuristics, all calling the same token.

Describe the solution you'd like A simple Python script or YAML/JSON file which I can use to access environment variables. Lookup lists could be displayed here, too (if they are not far too large)

Describe alternatives you've considered See above - writing the tokens into each specific function

Additional context -

[JWittmeyer]

Possible solution (since yml/json files might have some issues) create table "project_constants" with id, project_id, name, python_access, type, data

• project_id -> indexed but no f-key since might be GLOBAL (decision between global & project-specific values)
• name -> string field to identify the data
• python_access -> variable name used in python to access the value (unique per project_id)
• type -> e.g API_TOKEN
• data -> token value abc123

The data from the table should be prepared for the exec env on demand similar to lookup lists.

//possible addition: options column

• options -> JSON field with options for that constant

  • e.g. "HideInApplication" -> not visible in the UI after it is set and only passed through the backend (might cause some issues since the code would still be able to access the value e.g. with a print)

• type GLOBAL_FUNCTION (evaluated once before the exec env)

• type RECORD_FUNCTION e.g. for a general exclusion criteria performed per record (lambda record: not " no " in record["text"].text.lower())