SalesforceLabs / ActionPlansV4

Action Plans encapsulates best practices into reusable task templates.
https://salesforcelabs.github.io/ActionPlansV4/
BSD 3-Clause "New" or "Revised" License
21 stars 11 forks source link

Create Action Plan From Template apex action in flow creates tasks without dependencies #151

Open irinaIvanova97 opened 1 year ago

irinaIvanova97 commented 1 year ago

Describe the bug When creating a new action plan from template with the apex action "Create Action Plan From Template", the tasks related to the record are created all at once even though there is a dependency defined in the template.

To Reproduce Steps to reproduce the behavior:

  1. Go go Action Plan Templates
  2. Create new template
  3. Populate name
  4. Create new task with sample subjects and days after "1", priority normal, send email true, reminder true
  5. Create a second task with sample subjects and days after "1", priority normal, send email true, reminder true. On the controlling task select the task created in the previous step.
  6. Save
  7. Create new record-triggered flow on lead creation.
  8. Call the apex action "Create Action Plan From Template" with the current record id and template name passed
  9. Activate flow
  10. Create lead record
  11. Lead has 2 task created and assigned to the record

Expected behavior The record to have only the first task, since the second one is dependent on the first and should be generated only after the first one is completed.

Screenshots image image

Environment (please complete the following information):

charliel1981 commented 5 months ago

Hello,

i believe i got to the bottom of this issue with workbench. You might find that you originally created an AP and deleted rows of tasks out (potentially in the classic UI - as i did) and the dependencies didnt adjust as they should have. If you use workbench and look at the action plan template using LabsActionPlansAction_Plan_Templatec as the filter to the template, more than likely you will see that the LabsActionPlansDependentc may not be correct!

You can then use workbench to fix this issue by updating the record.

This worked for me, hope it helps anyone with the same issue