Curam by Merative Ideas Portal
Hide about this portal
Shape the future of Curam!
We invite you to shape the future of Curam, 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 Curam team to refine your idea
Help Curam prioritize your ideas and requests
The Curam 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
Request has been addressed locally and can be closed.
Potential ability to share as a state-shared asset should other clients make similar request.
John Sweeney
Offering Manager
Social Programs
Update on 05-24-16
Updating from the comment made on May 5th.
This is a candidate for our Q4 release this year.
Understanding the requirements outlined in RFE #87046 Application Submit Failure Errors, we recognize this as a valid enhancement request and will update status as appropriate through the RFE tool as work towards delivery of this feature progresses.
This is the approach we are currently exploring with no release version and/or release date yet identified:
________________________________________________________________________
Currently, the CGISS application script does not have the validations that are available on the evidences. Hence there are scenarios where the information from the script fails to create evidences on submission. As the CGISS script is based on IEG, the configuration needs to be updated to cater for the validations and attribute mapping to the evidences. This item is currently not on the priority list as there are other roadmap items of higher priority that are planned to be implemented, and it is possible for the customer to address the reported issue through IEG configuration updates. In addition to this, there may be additional attributes added by the customer to the script, so they can ensure that the script works end to end, including mapping information to evidences on submission.
Based on the recent RFE submission from DC, our recommendation is to work to resolve validation issues by implementing the validations necessary to ensure that an application can be submitted with better, more intuitive messaging/notifications back to the end user.
________________________________________________________________________
We do not have a target release for this feature, but the next planned release is in Q4 2016.
Understanding the timing of the DC solution release, this Q4 release will not meet customer need and we recommend the customer should start implementing these validations now, locally, and in line with their evidence design which the OOTB implementation would not fully take into consideration.
Attachment (Use case): Snippets of error logs for Application Submission Failure errors from DC.