SAP Cloud Platform Integration finalizes Web Application for Integration Developers

Hi Federico,

please find my responses below.

Thanks & regards,

Andreas

1. 1. Copy and paste disappears (losing time on repeatedly operations)
      A: We deliver copy / paste for Integration Flows with our 1808 increment (will reach customer systems by 29-Sep), followed by same for resources, mappings & model steps.
   2. If you create objects and sometimes they appears on design but they can’t be clicked / removed, just cancel work and start again (losing time)
      A: Please create support ticket with reproducible example.
   3. No GIT / SVN integration, remove save as version and put automatic save as new version with automatic versioning like build level growing
      A: We target to deliver GIT integration in Q1 2019.
   4. Undo? where is undo?
      A: Valid feedback. We target to deliver it, schedule to be concluded.
   5. Drag and drop is slow to be activate and sometimes doesn’t works
      A: Please create support ticket with reproducible example.
   6. No improves for xslt transformation with java function calls, only on message mapping, very uncomfortable with big transformations and debug is very hard on it, we use it only for quick transformation and java functions calls.
      A: We start to support xslt 3.0 with our 1808 increment. Will reach customer systems by 29-Sep.
   7. Please put scheduling outside workflow, sometimes we need to schedule a quick run or change it without edit / and save it.
      A: Has nothing to do with our UI technology. You may use our remote API’s to trigger actions from outside the system.
   8. Palette is very uncomfortable, leave parts opens like in Eclipse
      A: Valid feedback. Will consider it downstream but it’s not scheduled yet.
   9. Xml editor, xslt editor, json editor are improved in Eclipse, on web ui they are not so useful, syntax checking, formatting, find, replace and diff options are slowly or absents.
      A: Valid feedback. Will consider it downstream but it’s not scheduled yet.
   10. Channel template removed, so every connection need to be create from scratch, losing time and create more errors on developing / modifying.
       A: Will be addressed via (1).
   11. If you want to debug, test connections and check running you need 3 windows opened.
       A: Correct.
   12. Tracing must be improved, you can’t resolve data problems on huge run with this interface, same problem on eclipse.
       A: We focus all ongoing tracing improvements in our web app. We run a customer engagement initiative to get more detailed feedback. We would like to involve you in this initiative if ok for you.
   13. Deploying on draft? Can’t find production state.
       A: Please provide more details/context on this.
   14. If you want to revert a single resource can you?
       A: Please provide more details/context on this.
   15. Slow slow and slow, can’t work with a 5-10 seconds interface.
       A: Please create support ticket with reproducible example.
   16. Can’t work offline, try to transform this web app in a progressive app. (copy from Microsoft office 365 way)
       A: Correct, you can’t work offline with our WebUI. We have no plans to transform the web app in a progressive app.
   17. Why successfactors connector can’t see tenant successfactors environment directly from interface instead put all information again?
       A: Please provide more details/context on this.
   18. Why you didn’t improve standard channels connector on eclipse instead to spend a lot of time in an old style web application? Improve stability of plugin, or create a standalone application like Android Studio (Google Developers are different from us)?
       A: Because majority of our end users are Integration Developers appreciating the simplicity of a web app. Consequently we focus all our efforts on our web app.
   19. Browser compatibility isn’t an issue, how to manage errors from interface if interface doesn’t work to send you state of program?
       A: Please provide more details/context on this.
   20. Eclipse isn’t best I know, but this web interface isn’t ready for develop big workflows for integration very complicated solutions.
       A: Thanks for sharing your opinion.
   21. Put in this web UI, mock data for light runs (like Boomi do).
       A: Has nothing to do with our UI technology. Still it’s valid feedback. Will consider it downstream but it’s not scheduled yet.
   22. Put context menu for quick working on developing.
       A: Please provide more details/context on this.
   23. Multiple selection / Align are missing
       A: Multiple selection is supported in our web app. Auto-alignment wasn’t supported in Eclipse neither.
   24. Tracing for debug very awful, I came back to old bad trace system to resolve a problem.
       A: Duplicate to (12).
   25. XSL errors need to checked on node Tail Log, no logging available on web interface to help us to resolve.
       A: Alternative is to access the VM log via our web app.
   26. Duplicate resources very slowly, check diff from different versions is very difficult.
       A: Should be simplified with (3) using e.g. GIT tools.
   27. Run One remove, I can’t understand why.
       A: Please provide more details/context on this. We haven’t removed it.
   28. Can’t copy from another project resources and items directly.
       A: We enabled resource copy from other Iflows in the resource view with our 1804 increment (available on customer systems since 09-June)
   29. OData adapter problem with paging not resolved (probably less important)
       A: Has nothing to do with our UI technology. Please provide more details/context on this. We don’t get your point.
   30. You can’t use back button to come back from internal frames, every time it return to
       A: Please use our bread crumbs for the time being. We will enable back button support in Q4 2018.
   31. Create an Mobile APP to monitor runs for tenants you have in your S-USER.
       A: Thanks for the proposal. We have no current plans to do so.