Skip to main content

Subprocess expiration

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

One of the primary purposes of Daymi is to provide clients with a complete audit trail, containing a detailed history of all their processes.

To support compliance regulations and maintain a reliable record of historical actions, we've ensured that users cannot change the state of processes after a specified period, which can be set by each organization.

Default configuration

By default, it's not possible to change the status of a subprocess that has passed its active period:

  • Daily processes: 7 days after the deadline

  • Weekly/Bi-weekly: 14 days

  • Monthly/Bi-monthly: 60 days

  • Quarterly: 180 days

  • Yearly: 365 days

One-time or ad hoc processes don't have these restrictions.


Custom expiration term

We can adjust these rules to allow users to change the status of a subprocess for an extended period, enabling status changes beyond the usual timeframe.

If you'd like us to configure this setting for your organization, please contact us, and we’ll set up the new rules. Note: These adjustments will apply to all processes according to the rules you specify.

  • Configuration can only be changed by the Support team at Daymi, shoot us an e-mail at [email protected] 📧.

  • Provide us with a number of calendar days to extend the deadline term with (consider the optimal number of days, including weekends and holidays).

  • Expiration cannot be applied to Once frequency processes since you can always change their status.

Did this answer your question?