You’re in the zone. The groove. Making an SAPUI5 app that is just the bee’s knees. The cat’s meow. It’s got all the pieces that the end-user wants, with a design that knocks their socks off. Dropping tight functions like they’re no big deal. The result is a beautiful, fast, slick app. Everyone loves it. Promotions all around!
And then your end-user champion approaches you with that look in his eye. That look that says “I’m about to ask you something that I think you’ll hate”. He tells you that on the item entry screen, when users select “Non-billable expense”, they need to see information that, for legal reasons, requires three separate calls to different OData APIs. Only after stitching these calls together on the client side can users truly get the best information for making critical decisions.
So you need to call three different OData APIs and wait until they all return before proceeding? And your end-user champion thought this would be hard?
You smile confidently, and surf reddit.com for an extra half hour. Because with Promises, you’ve got this.