Evergreen IFS Rest Odata calls
In the IFS Odata Connector we would benefit from first of all identification of all Odata projections used in a a flow and secondly to scan the IFS APIBreakingChanges release files to find out and mark Flow objects if there has been a change in any projection.
There are two different APIBreakingChanges files:
- Between Service Updates within a functional Release
- Between Functional releases.
See attached examples.
Klas KLASMAN
shared this idea
We regret to inform you that this feature request has been declined. Our product team has determined that it is not aligned with our product roadmap or does not bring enough value to our platform to justify its implementation. We appreciate your continued feedback and look forward to hearing about future ideas.
That said, in Flow Connect, we have an Extension on Flow Connect that does just this. Please see our help documentation on this extension for IFS Cloud.
https://docs.novacura.com/marketplace-documentation/flow-platform-extensions/explore-extensions/ifs-api-change-impact-analyzer/documentation
-
As Paul mentions this is an alternative route that might be easier to implement. Extract a list of projections and methods used within an customer Flow solution, use this list and compare the IFS API specification between the two IFS cloud versions. This way we can be proactive and we could easily find what needs to be updated in den OData calls.
By comparing the IFS specifications, not the OData connector configurations, this solution could perhaps work for both Flow Classic and Connect.
-
Is there a way to look at the specifications of the projections and cross reference which projections are used inside of all the Flows?
