Merative Ideas Portal

Shape the future of Merative!

We invite you to shape the future of Merative, 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 Merative team to refine your idea

Help Merative prioritize your ideas and requests

The Merative 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 Merative 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 Merative, 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.


Merative External Privacy Statement: https://www.merative.com/privacy

Add a new idea Subscribe
Status Not under consideration
Categories Social Program Management Platform
Created by Guest
Created on Jul 21, 2016

RELATED IDEAS

Cannot refresh a page submitted to itself

Currently when an Action.do page is loaded in the main content panel (for example when a search page is submitted) it is not possible to use the page refresh button or the user Preferences dialog. In this scenario when a modal is opened from the tab-level Actions menu then any action controls that rely on the o3rpu parameter will not refresh the parent page.

We need to make it possible to refresh the page in this scenario, whether the refresh is caused by explicit refresh or from a modal (user pref or other) submit. Any data entered in the form or search results will be lost by the refresh. We have enhancement request TEC-3314 to make it possible to preserve the data and search results.

Analysis:
The RPU is traditionally maintained in the page URL through links in the application and therefore handled by the LinkTag. One other factor that comes in are the modal dialogs, but even here the RPU is in a traditional (pre-V6) C�ram application maintained by the LinkTag, because any modal dialogs are still opened from UIM pages.
But in V6 there is a whole new kind of links, which are defined and generated outside of UIM - they are the menu and navigation links defined in the UI configuration. These are links in Actions menu, Shortcuts panel, application banner and in custom renderers.
All these do not have automatic access to the standard RPU as maintained by the LinkTag so they have to set the RPU using a different approach. The approach is to determine what was the previous page in the flow and set RPU to the corresponding URL. The previous page URL is determined by reading the window.location.href property of the main content panel iframe.
This works mostly fine, except in cases where server side redirect takes place in the main content panel, because in such situation the window.location.href property points to a wrong page. The RPU is then set incorrectly and page flow is broken.
This is the case for our Action pages where after page submit the response body contains the next page in the flow, but the window.location.href property still point to the *Action.do URL the page was submitted to.
If instead of using window.location.href we had a different means of determining the previous page in the flow, the problem would be solved and the infrastructure would always know where to return to.
Given the V6 application consists of many different iframes the best choice would seem to be to create an application-wide variable (in the top window context) that would be updated with RPU by code generated into any page that loads in the main content panel. This mechanism would work even for server side redirects taht currently cause problems.
The variable would be then checked instead of the window.location.href property and used to set RPU for pages.

Customer Name Ontario - Ministry of Community and Social Services
  • Attach files
  • Guest
    Reply
    |     Mar 26, 2020

    Hi Vikum,

    We have evaluated your request and have determined that it cannot be implemented at this time.

    Your request may be resubmitted for consideration after 12 months from the date of decline.

    Thank you for your interest in the Cúram SPM product.
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |     Aug 5, 2016

    Hi,

    We acknowledge that this is a valid enhancement request. It will be considered for inclusion in a future release of the product. Thank you for your interest in the Cúram product.

    Thanks,
    Eloise O'Riordan, Cúram SPM Offering Management team