#Task Management토론 중인 항목 3개

Hi Stephen, 

The standard Mark Complete quick action uses a fixed mini page layout, not a Lightning record page, so Dynamic Forms' conditional field visibility doesn't apply to it. That feature only works on full Lightning record pages (Record Detail/Field Section components in App Builder), not quick action modals. So there's no admin-only way to make Rejection Reason and Rejection Reason Other conditionally appear inside that specific modal. 

Your path forward: build a custom Screen Flow as a Quick Action (Object-Specific Action on Task, Action Type = Flow). In the flow: 

- Screen 1: Status picklist 

- Decision element checking Status = Rejected 

- Screen 2 (conditional path): Rejection Reason picklist, required 

- Decision element checking Rejection Reason = Other 

- Screen 3 (conditional path): Rejection Reason Other text field, required 

Replace the standard Mark Complete button with this custom action on the Task page layout/list view action bar (you can keep both if some users still just need simple Completed with no extra fields — the flow can handle both paths in one action). 

This is the standard, fully-supported way to get conditional required fields on a Task status change — no code needed, just Flow Builder.

I never even thought of this scenario :)

One thing I can think of is to create a screen flow with mandatory email fields (To address, subject, body). You can then add a Send email action to the flow after the screen and an Update record element to update the task you're on (you will need a record variable called recordId, spelled exactly like that, all in lower case except for the I).

You can now add a Quick action to the Task object and select the screenflow.

I've never tried this, but it should work, however, I don't think you can pick an email template this way, however, you could use some Text Template elements to create some templates users can choose from maybe in a drop down first, then the Body field could default to it

Hi,

Permission required is-

To enable recurring tasks:  Customize Application and Modify All Data

details:

https://help.salesforce.com/s/articleView?id=sf.tasks_enable_recurring_tasks_lex.htm&type=5

http://theblogreaders.com/create-recurring-series-tasks-lightning-experience-salesforce-classic/

Additionally, please check the access to fields

Hi Piyush,

Many thanks for responding.

I have looked at the object settings for profiles and permission sets but see no option to grant modify all access like other objects.  If you compare both below you will see for the account object that you can grant modify all but this option is not showing for the task object.

Account object

Task Object

Hi Evan,

It is possible, but I would do it in a flow rather than a process builder since they will be deprecated soon.

Create a record triggered flow on leads on creation and updates with a condition set to 'Agreed Next Action Date' Is null GlobalConstant.False

Make sure you select "Every time a record is updated and meets the condition requirements"

Now create a new variable> Formula returning Boolean:

OR(AND(ISNEW(), NOT(ISBLANK($Record> Agreed Next Action Date))),
ISCHANGED($Record> Agreed Next Action Date))

Add a decision:

Formual equals GLobalConstant.True

Then add a Create Record element to create your task and set the due date to 'Agreed Next Action Date' and the WhoId to the $Record> Owner and WhatId to $Record>Id

Set the values for more fields if needed (ie Subject)

Save and activate