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
Hello - the web service step as an action is an awesome addition! I did notice that the step results after a web service step complete only contain the Webservice Function: data error exception fields. This seems to mean that look up fields from any previous steps are not available in subsequent steps, although they are still listed under 'Available fields' in the form when adding more steps. You can do a look up on the original event again but I don't believe that is intended/doesn't work that way with other action types?
Attaching a workflow as an example. Should work as is to test on a site with a least one course (id=2) and the Course Creator role (role id =2). On user creation it looks up the user, runs a WS action, looks them up again, and assigns a role.
Import workflow
Create a user
Verify user added to course 2 via a WS action and assigned role 2 via a role assignment action
Edit the workflow, and remove the "look up again" step
Rerun the workflow or create another user
Observe the the enroll via WS action works but role action errors since the user_id lookup field is not present
Hi @thebenkahn, thanks for the great bug report. We have just hit this internally, and Ive nailed the error down to some dodgy open transaction handling, and some weird behaviour from the Moodle WS API. I should have this fixed soon.
Hello - the web service step as an action is an awesome addition! I did notice that the step results after a web service step complete only contain the Webservice Function: data error exception fields. This seems to mean that look up fields from any previous steps are not available in subsequent steps, although they are still listed under 'Available fields' in the form when adding more steps. You can do a look up on the original event again but I don't believe that is intended/doesn't work that way with other action types?
Attaching a workflow as an example. Should work as is to test on a site with a least one course (id=2) and the Course Creator role (role id =2). On user creation it looks up the user, runs a WS action, looks them up again, and assigns a role.
Webservice_Testing_20220519_1834.zip
The text was updated successfully, but these errors were encountered: