Skip to Main Content
IBM Sustainability Software - Ideas Portal


This portal is to open public enhancement requests against the products and services belonging to IBM Sustainability Software. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


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:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Categories Workflow
Created by Guest
Created on Apr 14, 2022

manual input node should allow many actions lines to same next node

If I have a Manual Input where the user chooses a description to set the priority or impact level, an Action Line is required for each option to be presented to the user. An action for setting the value is then put on each line, and that makes sense. However, Maximo requires that each of those lines have a different target node.

Given a minimal scenario with 3 choices, our workflow would require 5 or 6 nodes and 8 or 10 action lines, depending on if we have one line go straight to Stop:

1 Start
1 Action Line
1 Manual Input
3 Action Lines, 1 per choice
2 or 3 "True" Condition Nodes with a condition of 1=1
4 or 6 Action Lines, 2 per choice that leads to a Condition
1 Stop

If this idea was implemented, the same scenario would be simplified to require 3 nodes and 4 action lines:

1 Start
1 Action Line
1 Manual Input
3 Action Lines, 1 per choice
1 Stop

Some customers use True Condition Nodes to document what the action lines do. So, a related change should be to allow some text from the Action Line properties to be shown on the canvas.

Idea priority Medium
Needed By Quarter
  • Guest
    Reply
    |
    Jul 7, 2022

    OK I will close this one and perhaps need to open a case on your step 9. Thanks

  • Guest
    Reply
    |
    Apr 28, 2022
    1. System Information

      1. MaxDemo

      2. IBM Maximo Asset Management 7.6.1.2 Build 20200715-0100 DB Build V7611-01

    2. Log in as WILSON

    3. Create WF Process MITEST

      1. Description: Manual Input test

      2. Object: WORKORDER

    4. Canvas starts with:

      1. Start node: START 1

      2. Stop node: STOP 2

    5. Drag a Manual Input node onto the canvas between START 1 and STOP 2

      1. Node appears to be named "Input" on the canvas. However, switching to the Process tab shows it was called INPUT 3, and on switching back to the Canvas tab the name in the canvas changes to INPUT 3.

        1. Odd, but not what this RFE is about.

    6. "Right drag" to create action lines:

      1. from START 1 to INPUT 3

        1. black arrow appears between the nodes

      2. from INPUT 3 to STOP 2, to create first choice

        1. black arrow appears between the nodes

      3. from INPUT 3 to STOP 2, to create second choice

        1. black arrow appears between the nodes

    7. Go to Process tab

    8. In the Process Nodes table, select INPUT 3

      1. The Actions table shows two actions with STOP 2 for the To Node

    9. On the Actions table, click New Action > Positive

      1. Expected Result: A third choice / Action should have been created.

      2. Actual Result: Error: BMXAA7121E - The action cannot be added because there is no valid target available for the action.

      3. Click OK

    10. Click Save

    11. Go to Canvas tab

    12. Right drag from INPUT 3 to STOP 2 to create a third choice

    13. Click Save

    14. Click Validate

    15. Click Enable

    16. Click Activate


    I'm glad that Steps 6.c and 12 worked for me, this time. However, the error on Step 9 should still be addressed.

  • Guest
    Reply
    |
    Apr 27, 2022

    In my 7612 vm, I created a process where a manual input has 3 conditional actions that all have the same stop node target (also tried task node). Worked as expected... Can you elaborate on the use case a bit more please? Maybe I missed a step. thanks...