IBM Sterling Ideas
Shape the future of IBM!
We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:
Post your ideas
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.
Start by posting ideas and requests to enhance a product or service. Take a look at ideas others have posted and upvote them if they matter to you, 1. Post an idea 2. Upvote ideas that matter most to you 3. Get feedback from the IBM team to refine your idea
Help IBM prioritize your ideas and requests
The IBM team may need your help to refine the ideas so they may ask for more information or feedback. The offering manager team will then decide if they can begin working on your idea. If they can start during the next development cycle, they will put the idea on the priority list. Each team at IBM works on a different schedule, where some ideas can be implemented right away, others may be placed on a different schedule.
Receive notifications on the decision
Some ideas can be implemented at IBM, while others may not fit within the development plans for the product. In either case, the team will let you know as soon as possible. In some cases, we may be able to find alternatives for ideas which cannot be implemented in a reasonable time.
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.
|What is your industry?||Non-Industry Specific|
How will this idea be used?
Updating the APIs will enable better alerting, logging, and integration to external reporting tools.
Do not place IBM confidential, company confidential, or personal information into any field.