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

Order workflow ist not exposed #21

Closed
clicktrend opened this issue Apr 24, 2017 · 1 comment
Closed

Order workflow ist not exposed #21

clicktrend opened this issue Apr 24, 2017 · 1 comment
Assignees
Labels

Comments

@clicktrend
Copy link
Contributor

Accessing /api/rest/latest/orders/752 does not expose "workflow" anymore. Break after upgrading to Oro Platform version 2?

@24198
Copy link
Contributor

24198 commented May 3, 2017

Hi @clicktrend,

Thanks for reporting! We've come to the realisation that the Worfklow is not assigned to an entity anymore and our tests failed to catch this case. We did however just pushed a change which exposes the 'workflowItems' again. Since the upgrade to 2.0.0 we also had to take into account that there could be more than workflow assigned on a single entity so the key 'workflowItem' and 'workflowStep' are deprecated since the last push and being replaced by a single key 'workflowItems' with the key 'currentStep' which is the step the workflow is in at that very moment.

Now all we have left to do is update the bridge to comply with this new key.

Kind Regards,

Jaimy Casteleijn

@24198 24198 closed this as completed Sep 21, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants