Action "Token: set context" with option to only expose specific tokens

Created on 22 May 2025, 12 days ago

Problem/Motivation

The "Token: set context" action always passes all available token data to the child processes, which could lead to unintended behaviour (eg. same token name used in child process).

Steps to reproduce

Proposed resolution

Add an optional text input to specify a list of token names to expose as context for child processes.

Remaining tasks

User interface changes

API changes

Data model changes

Feature request
Status

Active

Version

3.0

Component

Miscellaneous

Created by

🇩🇪Germany mxh Offenburg

Live updates comments and jobs are added and updated live.
Sign in to follow issues

Comments & Activities

  • Issue created by @mxh
  • 🇩🇪Germany jurgenhaas Gottmadingen

    This may be related to Make custom events re-usable for rendering and other event types Active .

    How about taking this even a step further: instead of providing a list of token names, we could also allow for a yaml style mapping of destination token names with values from the current context. That would allow models to use their own token names, but when it comes to re-use custom events or sub-processes, they can map their own tokens names to those that are used by the custom event.

Production build 0.71.5 2024