More Than a Process: A Source of Truth
A well-designed workflow is more than just a process map; it’s a rich source of data that tells the story of how your business operates. Every time anObject changes status, Luklak records that event, creating a complete audit trail.
This historical data is the key to unlocking deep insights into process efficiency, bottlenecks, and conversion rates. This guide covers how to analyze both the present state and the past journey of your Objects.
Analyzing the Present: Querying Current Status
The most common type of reporting is based on where yourObjects are right now. Using UQL in filters and dashboards, you can get a real-time snapshot of your operations.
Querying by Status:You can filter forObjectsin a specific custom status you created.- Example:
status = "AWAITING_CLIENT_FEEDBACK"
- Example:
Querying by Status Category:For a broader, cross-functional view, you can query by the system category.- Example:
status.category = "IDLE". This would find all Objects that areON_HOLD,AWAITING_FEEDBACK, etc., across the entire company, regardless of their specific status name.
- Example:
Uncovering Insights: Analyzing Workflow History
The real magic happens when you analyze the journey of your Objects over time. Luklak’s UQL allows you to query the complete history of status changes, enabling true process analysis. Here are the key UQL operators for historical queries:
[Image Placeholder: A clean graphic illustrating a workflow history query. It could show a timeline for an Object with status changes, and a UQL query box highlighting the ‘Changed from X to Y’ logic.]
Practical Application: Measuring Sales Conversion Rates
Let’s apply this to a real-world scenario. Imagine a sales workflow with the following statuses:NEW_LEAD → CONSULTATION → PROPOSAL_SENT → WON.
The Business Question: “How effective are we at converting leads who have had a consultation into receiving a proposal?”
The UQL Solution: The Changed from operator is perfect for this.
- Create a
Countergadget to count all Objects thatWere in "CONSULTATION". Let’s say the result is 100. - Create a second
Countergadget using the query above (status changed from "CONSULTATION" to "PROPOSAL_SENT"). Let’s say the result is 42. - From this, you can see your conversion rate for this stage is 42%.