Skip to Main Content
Cloud Platform

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

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 a notification 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.

If you encounter any issues accessing the Ideas portals, please send email describing the issue to for resolution.

For more information about IBM's Ideas program visit

Status Not under consideration
Workspace UrbanCode
Categories Deploy
Created by Guest
Created on Feb 1, 2016

Remedy Plugin: Use a Change Request ID in place of Entry ID

Basically, the problem with the plugin is related to the Check Step.

1. The documentation for usage is vague and incomplete. This causes several issues related to the setup. If the values in the command step are not formatted correctly, the workflow log indicates a cryptic error message that is largely unhelpful to resolve the initial issue. At first it was not apparent that the plugin step was connecting to the Remedy Server, but a review of the plugin code indicated successful connection.

2. On review of the code, the plugin step requires a the Remedy "Entry ID". The entry ID is not a user field; it is a Remedy Internal value that is not accessible or immediately visible to Remedy End users. The Change Request Identification number is one of the primary fields associated with the primary Entry Field. The plugin for Remedy should find the Entry ID by the publicly known "Change Request ID" number.

3. The plugin step for check data will fail on a non equivalent condition. This is a major assumption that is largely invalid for some values of interest within the plugin. Remedy is complete change control system that also contains fields and logic to govern when changes are intended to be executed. In this case, two data fields related to the change start and end times would be of interest and compared to the scheduled deploy time.

Basically, if the plugin could just get data from Remedy by the Change Request ID (as opposed to Entry ID, which is NOT a user known value) and then provide the data as output properties, a secondary step could perform the necessary logic for comparison.

Idea priority High
RFE ID 83319
RFE Product UrbanCode Deploy
  • Admin
    Osman Burucu
    Jun 22, 2022

    Thank You for entering and providing information to this RFE. Due the age and changes in the products over time additional functionality was introduced which could help to adress this RFE, this RFE will be closed.

    Please provide a new RFE based on the latest versions if needed

  • Guest
    Nov 1, 2016

    I also came across similar issue while using Remedy plugin for uDeploy. - where plugin was searching with entry ID, instead of Infrastructure change ID.
    If we have another plugin to fetch Entry ID from an Infrastructure Change ID, this plugin to work seamlessly.

  • Guest
    Mar 24, 2016

    Although the theme of this request is consistent with our business strategy, it is not committed to the release that is currently under development.