Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove Monitoring Level option from StartOrder-call #17

Open
johannesheucher-gip opened this issue Jan 20, 2023 · 0 comments
Open

Remove Monitoring Level option from StartOrder-call #17

johannesheucher-gip opened this issue Jan 20, 2023 · 0 comments

Comments

@johannesheucher-gip
Copy link
Contributor

At the moment, there is the option to pass a Monitoring Level along with the startOrder call. This has the effect, that the executed order respects that Monitoring Level. In contrast to that, all induced orders won't use that Monitoring Level but that defined in their respective Order Type. This makes the feature of passing a Monitoring Level along with the startOrder endpoint kind of powerless and misleading.
Additionally, it should not be the responsibility of the GUI to define a Monitoring Level for an executed order (and much less at the time of calling the order).
This should only be defined by the respective Order Type.

Exceptions

There are use cases, where the Monitoring Level should be passed during execution, e. g. for the Workflow Launcher or for Order Input Sources.

Proposed Solution

Remove the Monitoring Level option from the startOrder call and find a way to cope with the exceptions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant