Token and queue

Created on 26 August 2024, 8 months ago
Updated 12 September 2024, 8 months ago

Problem/Motivation

After lots of try and documentation / issue reading, I cant't find how you use the token in the ECA processing queued task.

Steps to reproduce

I use the action "enqueue a task" after a user creation and I send [user] in the tokens to forward. Indeed the user data are in the queue data context.

Then I use the ECA processing queued task event, but can't find a way to retrieve data.

Any advice ? Thanks a lot !

Proposed resolution

Remaining tasks

User interface changes

API changes

Data model changes

💬 Support request
Status

Fixed

Version

2.0

Component

Code

Created by

🇫🇷France eme

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

Comments & Activities

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

    When using the Enqueue a task action to put something into the queue, you can provide a comma separated list of token names into the Tokens to forward field. Note, this is asking for a list of token name, not tokens.

    All the token names you put into that field will then be known to the process that executes the queue.

    If you want to read more about token, i.e. also the difference between tokens and token names, you may find the Tokens chapter useful.

  • Status changed to Closed: works as designed 8 months ago
  • 🇫🇷France eme

    Of course I read your documentation ;-)

    First issue is I've put brackets into the "tokens to forward", but another one is that if you put user in the token to forward, it won't be available as the current user will be used instead. Therefore I've created a new token where I stored the user but on another name.

    Thanks for your early reply.

  • Status changed to Fixed 8 months ago
  • 🇩🇪Germany jurgenhaas Gottmadingen

    First issue is I've put brackets into the "tokens to forward"

    Yes, that about the difference between "token" and "token name" that we tried to explain in the documentation. Maybe that needs some clarification there?

    another one is that if you put user in the token to forward

    The user token is special such that each event, which starts an ECA process, automatically sets that token to the current user.

    Setting the status of this issue to fixed so that issue credits can be earned.

  • 🇫🇷France eme

    Yes indeed for the difference token / token name, I think you can in the description add juste "without brackets" (as you did on other fields) and that will be the end of such question !

  • Automatically closed - issue fixed for 2 weeks with no activity.

Production build 0.71.5 2024