New Feature Request: Custom Task Fields For Action Plan / Action Plan Templates

[ebradley54]

Is your feature request related to a problem? Please describe.
This is not a problem/issue/bug, just a missing feature.

Describe the solution you'd like
When creating a new Action Plan or Action Plan Template, we would like to include custom fields in the Task definition. While we discourage the use of process-specific custom fields in order to avoid the relatively low limits for Activities, we do have a need for some custom dependent picklists that we use across record types. One possible solution could be to leverage custom metadata types to maintain a list of field API names that are displayed dynamically in your VF page override. Specifying column order, record type, and inclusion of dependent picklists would be ideal (i.e. picklist value dependencies based on record type and controlling picklists should be accurately reflected).

Describe alternatives you've considered
Combining values into the standard Type field is an option for some of the data, but our users prefer picklist dependencies over longer value lists, and we try to avoid additional record types when we can. We also will not put data into the Type field that does not belong there, so it will not solve all of our use cases. As a custom alternative, we could supplement the existing functionality by creating new custom fields on APTemplateTask to house the custom field values and update the new Tasks accordingly whenever it is related to an APTask. This would not be an ideal user experience though because it is a disjointed process to generate the data instead of doing it all from the Template creation page.

Additional context
Add any other context or screenshots about the feature request here.

[dschach]

This is a good request, and one day I want to make the page far more flexible - and even use standard page layouts with lightning components embedded. The page has quite a few describe calls so it pulls from the Task available picklist values. I will keep this open, but for now, it may be best for you to build your own before save flow that can use the Lookup on Task to pre-fill fields based on various values, such as looking up the tree from Task to APTask to APTemplateTask. Then you can fill your own custom fields on that object through list views, probably, and have those referenced to your Tasks.

I like the idea of displaying specific fields and values on the AP Task List section; I don't know how to make that scale at this time. Let's keep this open and see where this goes once I transition to LWC from VF.

[ebradley54]

Thanks for the response David. We have already transitioned away from the managed package to modify the VF page so it will accept queue assignment at the Template level, this was the most critical need for us. If the need to use custom fields becomes more urgent, we will likely rebuild in LWC as well unless you get to it first. We try to stick to managed versions wherever possible just couldn’t quite make it work for our users this time around. Take care and thanks again, Gene

…

On Sat, Sep 3, 2022 at 4:53 PM David Schach ***@***.***> wrote: This is a good request, and one day I want to make the page far more flexible - and even use standard page layouts with lightning components embedded. The page has quite a few describe calls so it pulls from the Task available picklist values. I will keep this open, but for now, it may be best for you to build your own before save flow that can use the Lookup on Task to pre-fill fields based on various values, such as looking up the tree from Task to APTask to APTemplateTask. Then you can fill your own custom fields on that object through list views, probably, and have those referenced to your Tasks. I like the idea of displaying specific fields and values on the AP Task List section; I don't know how to make that scale at this time. Let's keep this open and see where this goes once I transition to LWC from VF. — Reply to this email directly, view it on GitHub <#49 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALJ4V4VEV4S25ETKTP237D3V4PCHLANCNFSM546Z7ORA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[dschach]

I'd love to see what you've done - if you'd like to submit a PR, I can cherry-pick that into the next version.