Home > Forum > Processes > Start an automatic process on a schedule

Start an automatic process on a schedule
0

Hi,
I'm looking for ideas on how to start an automatic process on a schedule that checks each row of a dictionary that has 3 types of dates.
The goal is to automatically start another process when a specific date from the dictionary is reached.
How can this be implemented?
Thanks in advance!

Hi Radostina!
In your case, if you want to periodically check whether a process should be started according to the schedule based on your dictionary, you can use standard WEBCON actions, including

1. Recurring actions – here you can set a schedule, e.g., daily checks – https://docs.webcon.com/docs/2023R3/Studio/Workflow/Workflow_GlobalAction3/module_2_4_7_4_2

2. Start a subworkflow (SQL) – you can add this action in recurring actions, which can run tasks according to your description. In the action, you define the process/path/data to be completed – https://docs.webcon.com/docs/2023R3/Studio/Action/Workflow/StartManyWorkFlows/

In reply to: Krystian Golik

Hi Radostina!
In your case, if you want to periodically check whether a process should be started according to the schedule based on your dictionary, you can use standard WEBCON actions, including

1. Recurring actions – here you can set a schedule, e.g., daily checks – https://docs.webcon.com/docs/2023R3/Studio/Workflow/Workflow_GlobalAction3/module_2_4_7_4_2

2. Start a subworkflow (SQL) – you can add this action in recurring actions, which can run tasks according to your description. In the action, you define the process/path/data to be completed – https://docs.webcon.com/docs/2023R3/Studio/Action/Workflow/StartManyWorkFlows/

Hi Krystian,
Thank you for your time.
I have an additional question regarding the case, which needs to be organized architecturally.
The situation is as follows: this dictionary will store thousands of equipment records.
This equipment has a life cycle and deadlines that need to be monitored.
Will the proposed approach affect the stability of the platform? Should I look for another option for monitoring this equipment - for example, each item being a separate instance of a standard workflow process that remains active while the item's life cycle is monitored (which can last up to 10 years).
Which of the two possible solutions would you recommend?

In reply to: Radostina Mihaylova

Hi Krystian,
Thank you for your time.
I have an additional question regarding the case, which needs to be organized architecturally.
The situation is as follows: this dictionary will store thousands of equipment records.
This equipment has a life cycle and deadlines that need to be monitored.
Will the proposed approach affect the stability of the platform? Should I look for another option for monitoring this equipment - for example, each item being a separate instance of a standard workflow process that remains active while the item's life cycle is monitored (which can last up to 10 years).
Which of the two possible solutions would you recommend?

1. Will you keep this dictionary in WEBCON and will it be on a list of items with thousands of rows? If so, I would separate this issue because thousands of items on a form will not be efficient to edit.

2. A cyclical action with an SQL query will be efficient and fast, you can always divide it into checking interactions.

If you want my recommendation, I think a good approach would be to have separate instances for equipment and dates, and then check these forms to see if the date has expired and perform the appropriate actions.