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 Future consideration
Categories Social Program Management Platform
Created by Guest
Created on Jul 21, 2016

RELATED IDEAS

There is no documentation on the workflow triggers for the OOTB product

There is currently no documentation on the workflow triggers for the OOTB product.

Workflow can be triggered by: - using the EnactmentService API (most common) - via events (using event configuration whereby is an event is raised, config data is examined and the specified workflow is enacted). - via a subflow (parent workflow kicks off a child workflow etc.)

There is no current mechanism for determining within the code base where these mechanisms are used and hence where in the process, workflows are enacted. We need to document the triggers for all of the OOTB tasks and notifications.

The customer has raised an enhancement request for this level of documentation. Their business has requirements for documentation of every Task/Notification with the trigger and Workflow. Ex: the workflow "READYFORDETERMINATIONTASK" creates the "Ready for Determination" task, which is triggered by the user clicking the "Ready for Determination" action on the Income Support Application tab action menu.

A common issue that clients face is that post go-live they are overwhelmed with number of Tasks and Notifications that are generated by the system. Having this documentation would help to better address this during the functional design. Given the number of OOTB Workflows, Tasks, and Notifications, this is not a simple analysis.

There have been discussions on the WWIC regarding this topic. https:w3-connections.ibm.com/forums/html/topic?id=66d4c354-1c3a-4ad5-9f83-c4cb464e885c

Customer Name District of Columbia - Washington
  • Attach files
  • Guest
    Reply
    |     Feb 22, 2017

    Attaching the PMR #19600,004,000 to this enhancement request from Arkansas.

  • 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