From Static Structure to Living Process
You have now built the complete static structure of your📋 Function—the data model, the process flow, and the screens for data entry. Now, it’s time to make this structure intelligent. Automation is the nervous system that connects these parts and makes your process run itself.
This step leverages the Universal Automation LEGO piece to create rules that handle repetitive tasks, ensuring your process is not only consistent but also highly efficient.
Every automation rule in Luklak follows a simple but powerful principle: Trigger → Condition → Action. This can be translated as: When event A happens, if condition B is true, then perform action C.
The Three Types of Automation Rules
As an architect, your first decision is to choose the right type of rule for the job. Luklak provides three types, each triggered in a different way.Background Rules
System-Driven. These rules run automatically in the background without any user interaction.
Triggers: An
Use Case: Automatically assign a new
Triggers: An
Object is created/updated, a specific time is reached (e.g., every Monday at 9 AM), or an external webhook is received.Use Case: Automatically assign a new
Lead to a sales representative the moment it’s created in the system.Workflow Rules
Process-Driven. These rules are tied directly to your
Trigger: An
Use Case: When a
Workflow and execute when an Object moves into a specific Status.Trigger: An
Object enters a Status like IN REVIEW.Use Case: When a
Deal enters the “Proposal Sent” Status, automatically create a follow-up Task for the account manager, due in 7 days.Object Action Rules
User-Driven. These rules appear as buttons in an
Trigger: A user manually clicks the action button.
Use Case: A “Request Escalation” button that, when clicked, re-assigns a
Object’s action menu, allowing users to trigger complex automation on demand.Trigger: A user manually clicks the action button.
Use Case: A “Request Escalation” button that, when clicked, re-assigns a
Support Ticket to a senior manager and updates its priority to “Critical”.Building Your First Automation Rule
Let’s build a common and usefulWorkflow Rule: when a Task is moved to the IN REVIEW status, it will be automatically assigned to the “Project Manager” Role.
What’s Next?
YourFunction now has a powerful automated engine running under the hood. The next step is to design the “cockpit”—the interfaces that your team will use to view and interact with the data this intelligent process generates.