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 Future consideration
Created by Guest
Created on Jul 21, 2016

Require deferred processing to use multiple underlying JMS queues

Currently the deferred processing and workflow infrastructure use a single JMS queue for each 'business' queue:
DPEnactment, DPError, CloseTicket, DispatchTicket,
WorkflowEnactment, WorkflowError
In PMR 85535,999,649 the customer is requesting the ability to split the current traffic in DPEnactment among different queues because one particular deferred process - PERFORM_DEFERRED_RECALCULATIONS_FROM_PRECEDENT_CHANGE_SET
(PCS for short) - accounts for a large proportion of the messages on the queue in both number of messages and length of processing time per message.
A side effect of this is that sometimes shorter lived deferred processes are spending a long time in the queue. If the longer running PCS deferred processes were moved to a separate queue it may alleviate the delays caused to other messages.

Customer Name Ontario - Ministry of Community and Social Services
  • Attach files
  • 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