Por mariogarcia t’s a maintenance nightmare. You have 20 reports to automate… are you going to build 20 orchestrations? And what if the user asks to change the data selection? Back to editing, exporting, and importing! Does this pain sound familiar?
Well, in last week’s post, we saw how to read Processing Options on APPs (thanks for the comments!). And right after, one of you wrote on LinkedIn to me (a huge thanks for that contribution!) and reminded me of something key: “Mario, you can do that for UBEs too!”
And he was absolutely right. You can not only read… you can execute.
I went “messing around” in the AIS Server REST APIs again, and sure enough, there they were—two gems that change everything:
This is a game-changer, folks. Forget about creating one orchestration per report.
With …/discover, you can “discover” ANY UBE. The API returns a JSON with its Processing Options, their current values, data selection, and sequencing.
With …/execute, you can run that UBE.
And here comes the magic!
You can take the output from discover, change the PO values, add a data selection and pass it all to execute.
The result?
And yes, just like last time, you can use this directly with the OpenAPI connector (since Tools 9.2.5.5) or a REST connector. You can even call it from Postman or external apps.
Now, the Proposal:
Last week I didn’t get enough responses from you… so this week I’m upping the ante!
Get motivated and write in. If I see enough Repplys, or “I want those examples” down below .
…I will make a full post on JDEList and upload the example files for BOTH functionalities:
The ball is in your court!
Now I’ll ask you: What’s the most “stubborn” or complex UBE you’ve ever had to automate?
Tell me about your battle!