mirror of
https://github.com/SuiteCRM/SuiteCRM.git
synced 2026-03-02 19:16:58 -05:00
Better Workflow scheduling options #4130
Labels
No labels
Area: API
Area: Campaigns
Area: Cases
Area: Clean Up
Area: Clean Up: Performance
Area: Dashlets
Area: Databases
Area: Developer Tools
Area: Elasticsearch
Area: Elasticsearch
Area: Emails
Area: Emails:Campaigns
Area: Emails:Cases
Area: Emails:Compose
Area: Emails:Config
Area: Emails:Templates
Area: Environment
Area: Installation
Area: Language
Area: Mobile
Area: Module
Area: PDFs
Area: PHP8
Area: Reports
Area: Studio
Area: Styling
Area: Upgrading
Area: Workflow
Area:Activity Stream
Area:Calls
Area:Import
Area:Projects
Area:Search
Area:Surveys
Area:Themes
Area:Users
Branch:Hotfix
Good First Issue
Hacktoberfest
Help Wanted
PR:Community Contribution
PR:Type:Enhancement
Priority:Critical
Priority:Important
Priority:Moderate
Severity: Major
Severity: Minor
Severity: Moderate
Status: Requires Code Review
Status: Requires Updates
Status: Stale
Status: Team Investigating
Status:Assessed
Status:Fix Proposed
Status:Needs Assessed
Status:Requires Automated Tests
Type: Bug
Type:Deprecated
Type:Discussion
Type:Duplicate
Type:Invalid
Type:Question
Type:Suggestion
Type:Suggestion
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/SuiteCRM-SuiteCRM#4130
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @pgorod on GitHub (Nov 22, 2019).
Issue
This is a suggestion for a feature which comes form this discussion #3806, I think it shouldn't get lost as I often see requests for similar things in the Forums, and I believe this is relatively easy to implement.
The problem
Workflows job is typically executed once per minute. If you want to do something only once per hour, day, month, etc., you have to play with some field to store whether it has run already in the current period or not; and have a condition break the execution if it has. This is inefficient in terms of performance, and cumbersome and confusing to set up.
You can also just set up a custom scheduler job in PHP, but this is a show-stopper for users who are not programmers and want to stick to the Workflows UI.
The proposed solution
I have a suggestion for a design to solve this same problem, with a generic solution, and I believe it isn't too much work to develop:
RunasOnly From Specific Scheduler JobAdd SchedulercalledRun Specific Workflowwith parameter letting you choose existingOnly from Specific Scheduler JobWorkflows from DropdownThis way the full possibilities of
crontabsettings could be applied to any specific Workflow.Note that we already have a
Process AOW WokflowScheduler job, but it runs all the Workflows, not a specific one.@pgorod commented on GitHub (Nov 22, 2019):
A slightly easier to make UI, although not as good, would be to just dump all the Workflows into the existing
Jobdropdown.So in that version, there wouldn't be a second dropdown for the specific job selection, you would just add all existing Workflows in the
jobdropdown, after the others, with aWorkflow:prefix, like this:@turtlemenace commented on GitHub (Jul 1, 2021):
This would be a powerful feature.