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
Post 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,
Post an idea
Upvote ideas that matter most to you
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 product management 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 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.
Why does Controller SaaS enable sessions to remain open on screen and give the appearance of SaaS connection, when in fact they are deactivated or disconnected sessions?
For example, where the user ignores the “idle timer expired” prompt and Controller screens are not removed from screen, only the “idle timer” prompt disappears. The user can then be left with the impression that they are still connected to Controller SaaS and can continue to work, subsequently incurring error messages when they seek to save data, run reports or similar.
The process for re-accessing Controller SaaS where sessions have timed out is currently documented, as detailed on the following IBM article >> https://www.ibm.com/support/pages/idle-timer-expired-message-when-using-controller-cloud-if-user-does-not-press-keyboard-or-mouse-over-30-minutes. This guidance works in practice, but it does not account for all instances of user experience. It all also does not explain the need to kill all active Controller and Citrix applications when a session is stuck in a deactivated or disconnected status, typically through ending tasks on Task Manager. An action that is difficult for users, particularly where they are not familiar with the services needing to be identified and stopped.
Do not place IBM confidential, company confidential, or personal information into any field.