IBM Sterling Ideas
Submit new product ideas for IBM Sterling solutions. Before you submit, please review existing ideas; if an idea close to yours already exists, it's better to add comments or vote on the existing idea. We will review your ideas and use them to help prioritize our product development. Best of all, the portal will automatically update you when the status of your idea has been changed.
IBM is transforming its request for enhancement (RFE) process. The purpose of the transformation is to provide a more consistent experience for you to submit requests and to enable IBM product owners to respond to your requests more quickly. For more information click here.
Connect with IBM experts and your peers on the
Supply Chain Collaboration Community and the Order Management Interest Group
The "Activity Services" APIs at /activities/ and /activityinstances/ are hardcoded to only act upon Portal activities. Attempting to use them to retrieve instance details of Provisioner activities results in 404 errors.
The API needs to be able to retrieve details of Provisioner activities. This would enable better reporting and alerting functionality:
1) Alerts/logging from Provisioner activities
Using "ActivityContext/ParticipantActivityKey" during activity execution would allow us to retrieve activity details (e.g. instance key, rollout name, etc) for logging or alerting from inside the activity. We can push status updates to external tools or to email alerts so Sponsor Admins can troubleshoot easily.
2) Integration with other reporting tools
We would like to integrate with other reporting tools to provide other views of PEM activity status, as well as pulling in data from other sources to combine with PEM activity status.
This would let us build a solution with a broad view of an onboarding solution, and not have to login to multiple places to manually view or export reports.
Note that this functionality is already possible for Portal activities.
Other activity-related APIs are able to access Provisioner activities:
Activity Definition Services (/activitidefinitions/)
* Defaults to acting upon both PEM and PP activities, and has an input parameter "application" to specify which.
Participant Activity Services
* Requires activityInstanceKey, and can act upon both PEM and PP activities
This request is to allow the "Activity Services" APIs to access PP activities like these other APIs.
How will this idea be used?
Updating the APIs will enable better alerting, logging, and integration to external reporting tools.
|What is your industry?||Non-Industry Specific|
|What is the idea priority?||Medium|