Precedent Workflows > Reschedule events created from a precedent workflow


Reschedule events created from a precedent workflow

The scheduling of appointments and tasks is based on their chain's anchor event, chosen when the workflow precedent is applied.

For example, a precedent might include a chain of 4 steps, in which the 2nd step is the anchor step. Step 2 could be Closing. Step 1 is  scheduled to start prior to Step 2, and Steps 3 and 4 afterward.

Once the precedent has been applied and events appear in the Tasks or Appointments list on the file:

        Reschedule the anchor event – All not-yet-done tasks and future appointments in the chain will be automatically rescheduled as appropriate. For example, if Step C is moved up a month, then its prior and following steps are also moved up a month.

        Reschedule a non-anchor event – That step will no longer be under workflow control—it won't be automatically rescheduled if you later reschedule the anchor event.

        Reschedule event from outside of Amicus (e.g. in Outlook or on your smartphone) – This change is not kept. Amicus will revert the event back to its original date (and you'll be notified by email).

Precedent Workflow Controls

A prompt alerts users when an attempt is made to change the associated file on a task or appointment that was created from a workflow.

Additional prompts appear if the original file no longer exists or has been renamed.

        What are precedent workflows?

        Create a precedent workflow

        Customize precedent workflow features


Amicus Cloud (July 2023)

Copyright