So, the other day I was “in the trenches” with this. Tired of manual searching, I decided to put an end to it and started tinkering (as we love to do 😄) with the AIS Server REST APIs.
And surprise! 🎉 I found this hidden gem in the AIS REST APIs:
Get Processing Options v2 – v2/poservice
It’s a service that feels tailor-made for us. You send it the application and the version, and it returns a clean JSON with all the processing options and their values. Pure magic! ✨
And here’s the best part:
Since Tools Release 9.2.5.5, this is ridiculously easy to use in Orchestrator.
You don’t even need to manually configure the connector to call the API. Just:
Create a new Open API connector
Select the Local AIS option
From the list, choose:
"poservice"(or"v2/poservice")Done! ✅ The connector automatically prepares the JSON body for you.
Just pass the app name and version as input, test it, configure the response to map the values you need, and you’re good to go
You can also do this in earlier Tools Releases versions by configuring the connector as a REST API and setting up the call manually.
The benefits are obvious:
✅ No more BSFN hunting: Save hours of frustration
✅ Universal: Works for ANY application
✅ Robust & Supported: It’s a native AIS function, not a weird workaround
I’ve built a super simple example to demonstrate it.
Here’s the deal:
If you’re interested in getting the example to import and test it, just reply to this message.
If I see enough interest, I’ll upload it to JDE List so everyone can download it from there and—bonus—we keep the forum active! 🙌
Now I ask you:
What’s the craziest “hack” you’ve built just to read a Processing Option?
I’d love to hear your story! 🛠️
