Skip to Main Content
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

Status Not under consideration
Created by Guest
Created on Jul 21, 2016

Page name is not added as the first parameter when a redirect to ResolvePage.do is invoked

The customer requires that where a redirect to ResolvePage.do is invoked (for the purposes of re-directing again to a page player page). That
i) page=X is supplied as a parameter
ii) That page=X is supplied as the first parameter.

The PMR states that the page name should be supplied and should be "valid". This may prove more of a challenge as there is currently no straightforward mechanism to determine (on the client side) whether a given page name is valid. This part of the requirement TBC with customer.

This issue is important to the customer as it affects the patterns they use to decide which pages are included and which are excluded by SiteMinder security policy i.e. is the user required to supply a login to SiteMinder or not.

This work should be undertaken in conjunction with GUM-3861 & GUM-3862. This feature should be configurable with the default being not to change the current URLs. It may be important to preserve the URLs in their current form in case other customers are relying on the URL format in their SSO/Security configuration.

Estimate is provisional based on very cursory examination of changes required:
- Changes needed to PagePlayerAction to use new url utility (see below)
- Changes needed to Resolve.jspx to use new url utility (see below)
- New utility required that can take a set of parameters and (configurable) order them according to a constraint, e.g. always put page parameter first.
- Changes needed to multiple .jspx files (use the above utility) e.g. ExitIEGScript.jspx, ExitTriage.jspx, FinishIEGScript.jspx, ScreeningApplyOnline.jpx, ResolveInternalLink.jspx, ResolveSaveScreening.jspx, ScreeningApplyOnline.jspx, SetupIntake.jspx, SetupMotivation.jspx, SetupScreening.jspx, SetupTriage.jspx, StartNewIntakeApplication.jspx, StartNewScreening.jspx

Customer Name New Zealand MSD
  • Attach files
  • Guest
    Reply
    |
    Apr 6, 2020

    Hi,

    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 6, 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