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
In the api definition API class when we load the dependencies we don't check if the flow steps are disabled or not. Or should consider it and filter it.
Here is an example:
I don't have the java script policy. However, I disabled it so I should not have an exception saying Policy ... can not be found in policy registry ( in the backend logs ) when I deploy it and try to call it using postman or even the debug mode in the next versions.
Same for the Flows if a flow is disabled I should not consider it.
The text was updated successfully, but these errors were encountered:
Issue verified and confirmed as fixed.
Policies and flows that are disabled are now successfully ignored and calls are still executed successfully.
Verified on envir 3.10
Description
In the api definition
API
class when we load the dependencies we don't check if the flow steps are disabled or not. Or should consider it and filter it.Here is an example:
I don't have the java script policy. However, I disabled it so I should not have an exception saying
Policy ... can not be found in policy registry
( in the backend logs ) when I deploy it and try to call it using postman or even the debug mode in the next versions.Same for the
Flows
if a flow is disabled I should not consider it.The text was updated successfully, but these errors were encountered: