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
At enactment, a decision workflow does not support the setting of:
• Task priority
• Task initial comments
• Biz object associations
In fact task priority is hardcoded in the OOTB DecisionActivity code.
This means that the client has to write additional custom code to have a post processing step after the workflow has completed to set the above appropriately.
This in contrast to a generic task workflow which supports the setting of all the above at enactment. As the decision workflow creates a task, it shold support the client required settings for these task attributes at enactment without a custom post processing step.
According to PD support this is 'as designed' so rather than a miss/defect, the request to support this needs to be enhancement.
Attached a PDF of the PMR and some additional screenshots.
Customer Name | Scottish Government |
Persona Based Summary
As the system I want to be able to set appropriate task variables before enacting a decision workflow so that I don't have to have an additional custom post processing step to set them. |
|
Market Segment | Eligibility & Entitlement |
Type of Request | Idea |
Market Opportunity
Provides more flexibilty in the product and would be consistent with the other areas of the workflow framework that supports task setting of attributes at enactment. Less custom effort for the client and easy to "sell" it to existing and new clients. |
|
Usage frequency + #/type of users impacted
Tasks are used significantly in the SG solution but this decision workflow is a great way of ensuring client advisors have performed required actions associated to the task. We expect it will used more and more as an alternative to a normal task, provide better/easier MI on what actions a client advisor made. |
|
CURAM:Workarounds + Proposed Solution
There is a custom post processing step that involves 2 actions: |