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 Modeling and UI
Created by Guest
Created on Feb 13, 2023

Request add support to poll variables data on run time while running the state

If I'm a Rhapsody developer, I would change the implementation as follows. On any change of a variable via GUI, I would add an internal loop to update all states etc. If the related variable is declared volatile, the compiler is informed to consider any changes of this variable outside the Rhapsody model. This was my initial assumption on how variable update via GUI is working.

Idea priority Medium
  • Guest
    Reply
    |
    Jun 28, 2023

    I also fully support this idea. Another use case, I detected during development of simulation models.

    In SysML the choice pseudo state (in Rhapsody Condition Connector) decides the outgoing transition to take by dynamic, run-time conditions. Also I would expect that the corresponding actions are evaluated at run time. If I have a sequence of transitions with choices then I would expect that the action of transition INTO a choice would effect the guards of the OUTGOING transitions of that choice. This sees to be currently not the case.

    E.g. in my example I have an INGOING transition into a choice with event(value)/(params->value; LocalVar=value;)

    I would expect that in the OUTGOING transition I could have a guard [LocalVar == someCondition] and this is taking the up-to-date value from the ingoing transition. Indeed this is NOT the case. There will be a delay of 1 tick. To take the up-to-date value I would always need to use params->value. This is for my understanding not in line with SysML, so I really strongly support the enhancement (not only for GUI).

  • Admin
    SANTHARAM SUNEEL
    Reply
    |
    Mar 13, 2023

    Hi,

    Thank you for bringing this to our notice.
    We had an internal discussion on the way it was design.
    State machines in Rhapsody are event driven and are compliant with UML definition.
    Currently there is no plan to support guards and execution trigger.

    Hence, we cannot take this suggestion forward.

    Regards,

    Suneel…

    PS:

    It is possible to create such a system by customizing code/framework.
    I suggest you take this up with IBM Services Team.

  • Guest
    Reply
    |
    Feb 14, 2023

    Upload of models is not supported, so I add only a screenshot of the model.

  • Guest
    Reply
    |
    Feb 14, 2023

    I fully support this idea.

    Let's assume a state chart is active and a guard with a condition on a variabel prevents transition to an other state. If you change that variable via GUI knob (so that the transition should happen), in fact nothing happens. Currently, the state has to be re-entered to recognize the changed guard condition! This not expected behavior.

    See attach model for reference.