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,
Post an idea
Upvote ideas that matter most to you
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
Hi Kyle,
We acknowledge that this enhancement request has been accepted for consideration. It may not be delivered within the release currently under development however the theme is aligned with our current multi-year strategy and will be considered for a future release.
IBM may consider and evaluate any RFE Community feedback for this request through activities such as voting.
IBM will update this request in the future.
Thank you for your interest in the Cúram product.
Shane McFadden, Cúram SPM Product Management team
Good afternoon, Shane--apologies for the delayed response here.
Our understanding with the disposedDateTime field is that it is overwritten when the case is re-opened then disposed in a different way (application case initially withdrawn, reopened by user then Authorized).
1. Idenfitfy existing pending Application
2. Withdraw the Application
3. Reopen the Application
4. Authorize the Application
If the field is overwritten, the disposedDateTime would only show us the date/time of the most recent disposition (the Authorization in the scenario described above). The concern is that we would not be able to easily determine the time for the application withdrawal.
Can you confirm that our understanding of the disposedDateTime field behavior is correct?
Thank you,
Kyle Marshall
Hi Kyle,
The entities that store the date for when an application program is authorized, withdrawn, or denied have a relationship with the IntakeProgramApplication database table, which includes a disposedDateTime field that is in date/time format.
Given that this field gets set when a particular program on an application gets disposed (approved, denied, withdrawn), we would like to understand whether this might serve as an alternative way to store/retrieve the time element to meet your requirements?
Thank you,
Shane McFadden, Cúram SPM Product Management team
Hi Kyle,
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