Skip to main content

Subtasks for Processes workflow in Daymi

Kestutis Vansavicius avatar
Written by Kestutis Vansavicius
Updated over 4 months ago

Daymi now includes a new layer of processes workflow: subtasks. These allow you to structure your processes more effectively and in a better order.

What are we introducing?

The Processes workflow in Daymi has always consisted of:

  • Main process: The overarching workflow.

  • Subprocess: Steps within the main process, with descriptions.

Now, subtasks allow you to take the most critical actions from subprocess descriptions and turn them into actionable, trackable steps.
​

Use Cases

Regulatory reporting (e.g., FCA Returns)

If your organization tracks reporting schedules in Daymi, such as FCA return obligations, subtasks can streamline your workflow:

  • FCA returns involve numerous steps to meet regulatory requirements.

  • Instead of creating a separate subprocess for each step or overloading descriptions with details, subtasks allow you to organize key actions into a simple, trackable checklist.

Client onboarding or Fund launch

For workflows such as client onboarding or fund launches, subtasks provide a structured way to manage key steps:

  • Subtasks serve as a tick-off list for important actions tied to each subprocess, ensuring nothing is overlooked.

  • They help reduce the number of subprocesses and overly detailed descriptions, creating a more condensed, streamlined process.

  • This approach makes the entire workflow easier to work with while still capturing all critical steps.

Processes and Programs

Both types now include the subtasks functionality, which can be found in the process/program creation forms.
​
In the processes form, click the small arrow in the subprocess list near the subprocess name to open the description section and the subtasks list.
​


In the program form, they are located under the description section.
​


Not sure about the differences? Learn more here.

Templates

Subtasks are also integrated into templates:

  • Add subtasks when creating subprocess templates.

  • Modify (add or remove) subtasks during the deployment process for more flexibility.
    ​

Completing Subtasks

Completing all subtasks added to a subprocess does not automatically update the status of the subprocess. You still have to manually control the subprocess status and mark it as 'In Progress' or 'Done'.
​

However, when you press 'Done' you will be asked whether you would like to complete all subtasks as well.

History and Audit Trail

  • Subtasks do not appear in audit trail CSV reports or subprocess PDF reports.

  • Subtasks are logged in the sidebar history tab, where you can see who ticked them off and when.

  • For highly auditable steps:

    • Screenshots of the sidebar history are usually sufficient for audits.

    • 💡 For full traceability, consider building the step as a subprocess instead.
      ​

Did this answer your question?