You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When creating an action, I lost several hours working out why it was not running.
It turns out that the action name must match the name of the JS function for it to run.
Describe your ideal solution
This is all very counter-intuitive. Why even allow naming an action if its name can be derived directly from the JS method name anyway?
Secondly, allowing creating a name for the action implies that you can use some kind of human-readable name such as "Flatten all roles" and then use a camelCase name for the JS method "flatRoles" etc.
Can I suggest either separating the requirement for these to be the same, which would allow more descriptive human readable names. Alternatively, put a note on the "create action" modal popup stating this name field must match the JS function.
Thanks
Version
2.51.0
Environment
Self-hosted
Acceptance Critiera
Add note to the ZITADEL management console, that the name and function in the javascript have to be the same
Example:
The text was updated successfully, but these errors were encountered:
Hei @benr77
Thanks for adding the issue. It is absolutaly valid, and I think its not really intuitive, that they have to match.
However, as we are currently implementing our new actions v2 I think it doesnt make sense to change that in the current implementation.
You can find the new implementaction for tracking here: #7235
I
It looks like v2 is still some way off. I would still recommend adding a textual note at least to the modal popup, simply reiterating the required matching of name and function name. This would not change the v1 behaviour but will likely save users a lot of frustration.
Preflight Checklist
Describe your problem
When creating an action, I lost several hours working out why it was not running.
It turns out that the action name must match the name of the JS function for it to run.
Describe your ideal solution
This is all very counter-intuitive. Why even allow naming an action if its name can be derived directly from the JS method name anyway?
Secondly, allowing creating a name for the action implies that you can use some kind of human-readable name such as "Flatten all roles" and then use a camelCase name for the JS method "flatRoles" etc.
Can I suggest either separating the requirement for these to be the same, which would allow more descriptive human readable names. Alternatively, put a note on the "create action" modal popup stating this name field must match the JS function.
Thanks
Version
2.51.0
Environment
Self-hosted
Acceptance Critiera
Example:
The text was updated successfully, but these errors were encountered: