Read event inputs in next activity? about elsa-core HOT 1 OPEN

To read the "input" field of an event triggered using the API, you should ensure that the input is being passed correctly and that the JavaScript expression used to access the input is valid. The expression getInput("__EventPayloadWorkflowInput") should indeed retrieve the event payload if it's been set correctly.

However, the error "Cannot read properties of null" suggests that at some point, the input being accessed is null. This could happen if the event is triggered without the expected input or if there's a mismatch in the input key being used.

Here are a few steps you can take to troubleshoot this issue:

1. Verify that the event is being triggered with the correct input payload. Ensure that the JSON being sent with the event contains the "input" field with the expected data.

2. Check the workflow definition to ensure that the input is expected under the key __EventPayloadWorkflowInput. If the key is different, you should use the correct key in your getInput() function.

3. If you are using a JavaScript expression in an activity to access the input, make sure that the activity is configured to handle the input correctly. For example, if you're using a WriteLine activity, the Text property should be set to a JavaScript expression that correctly accesses the input.

4. Ensure that the version of Elsa you are using does not have any known issues related to event inputs. You can check the Elsa GitHub issues page for any related bug reports or updates.

5. If the issue persists, consider reaching out to the Elsa community or support with details of your workflow definition and the steps you've taken. They might be able to provide more specific guidance based on the version of Elsa you are using and the exact workflow configuration.

If you provide the version of Elsa you are using and more details about the workflow definition, I might be able to give you a more precise answer.

This comment was generated by Glime.

from elsa-core.