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 John,
We have not received the additional information we previously requested from you that would allow us to fully understand and evaluate your enhancement request. Since we have not received the information within the 30 day timeframe, we are closing this request.
If you are able to provide the additional information in the future, please open a new enhancement request and we will be glad to review. We do appreciate the time you take to share your ideas with us and utilize your inputs to improve our product offering.
Thank you,
Shane McFadden, SPM Offering Management team
You can find more information on the request process here.
Hi John,
We have not heard from you since posting our recommendation on Sept 1. Please let us know if there is some customer requirement that we are not considering or some other reason why the documented approach could not be adapted. If we do not hear from you by Oct 1 we will assume the information provided was satisfactory and we will close the request.
Thank you,
Shane McFadden, SPM Offering Management team
You can find more information on the request process here.
Hi John,
We understand the business need to deliver Presumptive Eligibility (PE) MHN Application for the customer. Based on our understanding of this application, we feel this should be a new program type that would utilize the existing Application Case type. We do not feel that a new case type was appropriate to deliver the customer requirements and will most likely result in many further customizations points. Please review the documentation outlined below and let us know if there is some customer requirement that we are not considering or some other reason why the documented approach could not be adapted.
The following is a link to the Intake business guide that describes the full Intake process which is fully supported with the Application case type.
https://www.ibm.com/support/knowledgecenter/SS8S5A_7.0.10/com.ibm.curam.content.doc/CommonIntake/ctr_CommonIntakeBusinessGuide.html
The following is a link to the configuration guide for Intake that will include setting up a new program:
https://www.ibm.com/support/knowledgecenter/SS8S5A_7.0.10/com.ibm.curam.content.doc/CCIConfiguration/ctr_CCIConfigurationGuide.html
Thank you,
Shane McFadden, SPM Offering Management team
You can find more information on the request process here.
Hi Shane,
This has been configured using APPLICATIONCASEADMIN entity only, Please see the attached ApplicationCaseAdmin.dmx file. As the custom case type name is "Presumptive Eligibility (PE) MHN Application Case", we have to non compliantly customize the access restricted ProgramTypeValidationHelper class to add a check in crossEntityValidate() method.
Thank you,
John Coombes
Attachment (Description)
Hello,
This has been configured using APPLICATIONCASEADMIN entity only, Please see the attached ApplicationCaseAdmin.dmx file. As the custom case type name is "Presumptive Eligibility (PE) MHN Application Case", we have to non compliantly customize the access restricted ProgramTypeValidationHelper class to add a check in crossEntityValidate() method.
We are in a transition period, where I will be taking PMR/RFE responsibilities going forward.
Thank you,
John Coombes
Attachment (Description): As indicated.
Hello. Following is feedback from our developer. Also attached is the file mentioned. Please let me know if you have further questions.
Regards,
Maribeth Kane
Configuration was added to ApplicationCaseAdmin. Please see attached.
Hi Maribeth,
In order to evaluate your request, we require that you provide more detail so that we can fully understand your requirements.
It would appear from what's described in this request that this is a customer-specific type of application case and if so, why haven't you configured this using the APPLICATIONCASEADMIN entity?
You seem to be adding your new application case type of MOPEAPPCASE to the general case type code table, when really it is just another type of application case as configured using the APPLICATIONCASEADMIN entity?
Let me know your feedback or any further information you can share in order to resolve this request.
Thank you,
Shane McFadden, Cúram SPM Product Management team
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