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 Apr 7, 2020

RELATED IDEAS

The client has a requirement to remove workflow deadlines only if they are associated with 'CLOSED' tasks.

The client has a requirement to remove workflow deadlines only if they are associated with 'CLOSED' tasks. A hookpoint is requested in DeadlineScanner.processOneExpiredDeadline() method to implement this requirement compliantly.


Detailed steps to reproduce the issue in an out-of-the-box environment

[As admin user]
01) Login as "admin" user and select "My Tasks" under "inbox" in shortcuts
02) Create a new task with the deadline date as today and assign to workqueue
03) Trigger the OOTB batch ProcessTaskDeadlines.

[As developer]
01) Please note that the Tasks which were not 'CLOSED' were removed.

If the issue cannot be replicated in an out-of-box environment, describe the detailed steps that are necessary to help emulate the customized environment in order to highlight the underlying out-of-the-box issue

N/A

Details of any on-site investigations that have been done

N/A


Description of any workarounds / potential solutions that are being used

MO have previously worked around this issue by non-compliantly customizing the OOTB method WorkflowDeadline.remove() to execute the remove operation only if the associated tasks are 'CLOSED'


configreport.zip file created by running the Cúram configreport Ant target.

N/A

Customer Name Missouri
  • Attach files
  • Guest
    Reply
    |     Sep 17, 2020

    Hi Maribeth/Jason,

    We have reviewed your enhancement suggestion. Based on the information provided, our understanding of your request is as follows:

    Add a hookpoint to the ProcessTaskDeadlines batch that would allow filtering of the set of items to be processed by the batch.

    The theme is aligned with our current multi-year strategy for our product and we have accepted your suggestion as a consideration for a future release. Not all items under consideration will make it into a release. As plans are confirmed, you will be notified when a specific release includes this enhancement.

    Thank you for taking the time to share your ideas with us. We are committed to involving our users in building our product roadmap and appreciate your suggestions.

    Regards,
    Shane McFadden, SPM Offering Management team
    You can find more information on the request process here.

  • Jason Blackerby
    Reply
    |     Aug 24, 2020

    Hi Shane,

    I reached out to the State to try to get a better understanding of the business case around leaving expired deadlines in place for open tasks. The answer I was given was that by keeping the expired deadlines in place caseworkers could see which tasks were past due and could prioritize these past due tasks. If the deadlines were removed and new ones inserted, validations in OOTB would force them to be in the future giving the false sense that the caseworker is never running behind on any task and could potentially result in past due tasks being worked after tasks that are newer.

    It is not that we necessarily even want to process the deadlines for these tasks. They are being picked up by the query that drives the ProcessTaskDeadlines batch. Perhaps a better ask would be for a hookpoint to the batch itself after the set of WorkflowDeadlineIDs is converted to an instance of BatchProcessingIDList that would allow filtering of the set of items to be processed by the batch? This could be a generally useful hookpoint in all OOTB batches.

    Best regards,
    Jason

  • Guest
    Reply
    |     Apr 23, 2020

    Hello. Thank you for your response. I am still waiting to hear from the developer regarding your query. As soon as I hear back from him, I will post his response here.

    Regards,

    Maribeth Kane

  • Guest
    Reply
    |     Apr 10, 2020

    Hi Maribeth,

    In order to evaluate your request, we require that you provide more detail so that we can fully understand your requirements.

    1. The OOTB DeadlineScanner.processOneExpiredDeadline() removes deadlines that have expired (not related to the status of the task on which the deadline has been specified for). Therefore, if the deadline has expired it is processed and removed.
    2. The idea behind this is that a workflow deadline can specify a deadline handler function that executes the business logic associated with the deadline when the deadline is being processed after it has expired. This business logic can be as flexible as required (i.e. specify another deadline, perform some logic on the new deadline time, write or edit other records, etc.). But in all cases, the original deadline is removed as it has expired.

    Therefore, can you outline the business case here as to why you do not want to remove expired deadlines for "OPEN" tasks?
    Is it because you do not want to have to re-insert new deadlines for those tasks?
    What occurs to these deadlines which have expired for open tasks in your current customization?
    Specifying a deadline on a task means that that work should have been completed on that task by that time so are you stating that you want to process those deadlines but not to remove them (just reset the deadline time to a time in the future so that it is picked up again and processed sometime in the future etc.)?

    Thank you,
    Shane McFadden, Cúram SPM Product Management team

  • Guest
    Reply
    |     Apr 8, 2020

    Hi Maribeth,

    Thank you for your enhancement request.
    We require some further analysis to determine whether or not this enhancement can be considered in a future release.
    I will provide another response when our investigation is complete.

    Thank you,
    Shane McFadden, Cúram SPM Product Management team