Introducing Laguna 9.9, Moxo’s latest release that redefines workflow automation with features designed to optimize efficiency, clarity, management and control in complex workflows. From the introduction of Shadow Flow for simplifying complex workflows with parallel supporting processes, to Workspace Variables for driving efficiency with dynamic values, and Conditional Branches for smarter, more streamlined workflows, these updates elevate both internal and client-facing experiences.
Laguna 9.9 empowers businesses to better manage and streamline complex workflows, ensuring smarter and more efficient operations. Watch our video overview or dive into the detailed feature breakdown below to learn more:
Shadow Flow
Shadow Flow is an innovative capability designed to manage complex workflows by enabling parallel supporting workflows that operate alongside the primary workflow. Whether managing internal steps, coordinating parallel approvals, or collaborating with external stakeholders, Shadow Flow provides a seamless way to execute parallel processes, selectively controlling visibility into certain aspects of the flow, without disrupting the main workflow.
What Shadow Flow does
Shadow Flow allows businesses to run dependent workflows in parallel to the primary flow, offering the flexibility to either keep certain processes hidden or selectively visible to roles based on the context. Using the Flow Template Builder under the "Control" section, users can drag and drop Shadow Flow to define where parallel processes should occur without interrupting the workflow.
Key benefits
- Enhancing efficiency: Parallel workflows reduce bottlenecks and speed up task completion.
- Improving coordination: Designated roles can collaborate efficiently on parallel shadow flows without disrupting the primary workflow.
- Maintaining focus: Participants see only their tasks, ensuring a streamlined experience.
- Simplifying complexity: Manage intricate workflows with clarity and precision.
How it works
- Tailored visibility: Shadow Flow engages designated roles, invisible to unnecessary participants.
- “Wait” for Shadow Flow: Users encounter a “Wait” step while teams complete parallel tasks, notifying flow participants that the process isn't stalled, but that other tasks are currently being completed before the next step.
- Trigger dependent actions: Once a Shadow Flow completes, subsequent steps in the main flow can commence.
- Parallel processing: Multiple workflows can run simultaneously, enhancing efficiency.
Use cases
- Onboarding simplified: Internal tasks, like implementation prep or compliance reviews, run parallel to client-facing onboarding steps.
- Document review: Multiple departments can assess documents independently before the primary workflow can proceed. For example, sensitive information can be collected in a Shadow Flow by appropriate roles without visibility in the primary flow if necessary.
- Product deployment management: Backend configurations are completed without interrupting the primary workflow.
Note:
- Shadow Flow can only be created within the Flow Template Builder. (Shadow Flow cannot be used in instant flows, runtime workspaces or live workspaces.)
- Data from the main flow is available to Shadow Flow via DDR.
- Users cannot create a Shadow Flow within another Shadow Flow.
- Saving a flow as a template does not save Shadow Flow steps.
- Users can include multiple Shadow Flows within a single main flow.
“Wait”
“Wait” ensures workflows only proceed when a specified third party action, like a payment confirmation, or a shadow flow process is completed. “Wait” is designed to clearly indicate a waiting stage in the workflow so all parties know there is something that needs to happen before the flow proceeds.“Wait” improves process transparency by notating to everyone in the flow that there isn’t a “stall” but rather that there is something in progress. This capability also helps to prevent errors and missed steps, keeping everything in the flow on track.
Key benefits
- Control: Ensures workflows only proceed once actions through a third party or shadow flow are completed.
- Transparency: Clearly indicate when a process is in a necessary holding phase.
- Error prevention: Minimizes risks of proceeding with incomplete or incorrect information.
- Time management: Optimizes workflow timing with precise triggers, preventing unnecessary steps or delays.
How it works
Add “Wait” to your workflow and define the required external action (e.g., payment confirmation, document upload, or data update) or Shadow Flow action that needs to occur before your workflow can continue. The workflow pauses with a “Wait” notification until this action is complete.
Example use case
- Accounting firms: Pause workflows with “Wait” until payment confirmations are received via Stripe.
Key features
- External trigger-based: The flow only proceeds once the specified external action (e.g., payment, document upload, data update) or Shadow Flow action is completed.
- Success or failure:“Wait” will result in either a Success (Completed) or Failure (Canceled) outcome, depending on whether the required action was completed.
- Editing and deleting: Only the authentication owner can edit the “Wait” step within the workflow.
- Mobile app limitations: Editing the “Wait” step is not supported in the mobile app at this time, but all other actions are available on desktop.
Workspace Variables
Workspace Variables enable custom data to be passed when starting a flow and referenced throughout actions, branches, and automations using Dynamic Data Reference (DDR).
What Workspace Variables do
Workspace Variables are dynamic values that can be used in Moxo workflows to tailor the experience based on the data provided. They serve as placeholders for values referenced in automations, actions, and branches, helping to create more efficient and data-driven workflows. Workspace Variables can use DDR to trigger actions and send updates to third-party systems. This ensures seamless integration and automation by enabling dynamic updates, such as syncing data to CRMs or triggering notifications in external platforms.
Key features
- Variables are DDR-only, not UI-level filters.
- Pass values during workspace creation or via incoming webhooks (future update).
- Available for Flow Workspaces and visible only to internal users, ensuring privacy. (Not accessible with Instant Flows or Shadow Flows.)
- Workspace variables can be referenced using DDR in Shadow Flows
Use cases
- Automated project updates: Add details about a project in a project management system under a specific project ID. For example, if you enter a Jira project ID as a Workspace Variable (e.g., Jira project ID #XYZ), you can use this variable to dynamically send flow data to that project ID in Jira at the appropriate step in the workflow.
- Pre-fill form fields: Populate client intake forms dynamically based on pre-existing data.
- CRM integration: Automate updates to deal records based on flow progress.
- Conditional logic: Adapt workflows dynamically with data-driven branches.
Workspace Tags
Workspace Tags are used to filter timelines and associate multiple workspaces with specific accounts or projects. Some common tag use cases include:
- Account name
Tags can be used to group workspaces by specific accounts, enabling quick access and efficient management. For example, if you're managing multiple clients, you can create tags like "Acme Corp" or "Global Tech" to filter workspaces by account. - Account tier/segment
Segment workspaces by account tiers, such as "Enterprise," "SMB," or "Startup." This helps prioritize workflows and allocate resources effectively based on client importance or revenue potential. - Health score
Use tags to track the health of client relationships. For instance, you can create tags like "At Risk," "Healthy," or "Needs Attention" to monitor and act on accounts based on their status. - Project category
Organize workspaces by project types, such as "Onboarding," "Support," or "Implementation." This simplifies navigation and allows teams to quickly filter for relevant workspaces tied to specific business processes.
Workspace Tags make it easier to organize and locate relevant workspaces by applying meaningful labels, enabling efficient timeline filtering and streamlined association with key accounts or initiatives.
Conditional Branches
Conditional Branches introduce advanced rule creation that goes beyond simple decision-making, allowing workflows to adapt dynamically based on DDR, flow steps, action details, or multiple data-driven conditions. This capability ensures that workflows can accommodate complex scenarios with greater precision, tailoring actions and paths to meet specific requirements. As a more versatile replacement for Alternate Branches, Conditional Branches dynamically add actions only after pre-defined conditions are met. This ensures that actions for the selected path are displayed only when relevant, creating a cleaner and more intuitive workflow.
Key enhancements
- Dynamic action display: The correct actions for the selected path only appear once the conditions have been met. This creates a cleaner, more intuitive flow by hiding irrelevant paths and actions until they are triggered, a key difference from previous Alternate Branch behavior.
- Simplified logic: A streamlined if-or-else framework, eliminating the complexity and confusion of managing main and side branches in previous systems.
- Enhanced capabilities: Goes beyond form-based conditions, allowing dynamic decisions based on multiple conditions, enabling smarter, more flexible workflows.
- Dual branching: Users can now add multiple Conditional Branches within a single flow. Each Conditional Branch can support up to two distinct paths—Branch 1 and Branch 2—between any actions, offering greater workflow customization.
- DDR Compatibility: Leverage DDR for branching conditions, enabling workflows to adapt dynamically to data inputs, ensuring tailored, data-driven paths.
Use cases
The Conditional Branch feature delivers transformative value across various industries by enabling optimized workflows tailored to unique needs:
- Finance and accounting: In a wealth management workflow, a different path appears in the flow based on the trade amount. For example, if a trade exceeds a certain value, an extra approval step is triggered for senior management, while smaller trades follow the standard process.
- Client onboarding: In an onboarding workflow, the next steps change based on the package a client selects. For example, if a client chooses a specific package in their onboarding form, a corresponding set of onboarding steps automatically appears, ensuring the right process is followed based on their selection.
Conditional Branch vs. Decision Branch
Conditional Branch: Operates automatically, with the platform executing actions based on pre-configured conditions. It evaluates inputs, such as form values or DDR rules, and seamlessly moves to the appropriate next step without requiring any user intervention. The correct actions for the selected path only appear once the conditions have been met, creating a cleaner, more intuitive flow by hiding irrelevant paths and actions until they are triggered.
Decision Branch: Depends on user input to determine the next step in the workflow. Unlike the automated logic of the Conditional Branch, the Decision Branch requires users to make an active choice, guiding the workflow based on their selection.
Note:
- Existing templates with Alternate Branches will continue to operate seamlessly and can be edited or deleted, however, users will no longer be able to add new Alternate Branch steps.
Rename "Workspace Properties" to "Workspace Tags"
Workspace Properties are now called Workspace Tags, providing better categorization across multiple workspaces.
Reposition Template Metadata and Workspace Details
Template metadata and workspace details are now accessible via the Settings icon in the top navigation bar, centralizing all template-related information and ensuring quicker and more efficient template management.
Forms Phase 3 Enhancements
Forms Phase 3 introduces updates to enhance functionality and usability:
- Extended Form Elements: Includes new file upload and formatted paragraph content elements for streamlined data collection and clearer communication.
- Expanded Character Limits: Heading descriptions now support up to 1,000 characters for detailed instructions.
- Default Values: Predefine values in selection fields for faster form completion.
- Enhanced Logic: Smarter conditional logic enables dynamic form behavior.
- Template Saving: Save forms as reusable templates in the Flow Template Builder.
These updates streamline form creation and improve user experience.
Flow Role Usage Experience Tuning
The updated Flow Role Usage Experience enhances flexibility and efficiency in template creation by introducing two key capabilities. Roles can now be left unassigned when starting a flow, allowing for assignment later during runtime. Additionally, users can set a default assignee for a role when creating a template, eliminating the need to manually assign the same person each time the template is used. These updates simplify role management, improve workflow adaptability, and reduce repetitive tasks, ensuring a more streamlined and efficient user experience.
Acknowledgement Step Enhancement
Now, when an Acknowledgment is assigned to a Client Group in Moxo, any member of the group can review and acknowledge it—ensuring that all assigned users can take action until one member completes it for the group. This update prevents the acknowledgment from being assigned to a single user once someone starts reviewing it.
Multiple Google Calendar Support
Manage appointments across multiple Google Calendars with the updated Time Booking action.
Experience the power of Laguna 9.9
Laguna 9.9 brings unparalleled flexibility, precision, and efficiency to workflow management. With its advanced capabilities like Shadow Flow, Workspace Variables, Conditional Branching, and improved forms, organizations can simplify complexity and achieve new levels of operational excellence. Discover how Laguna 9.9 transforms workflows into seamless, data-driven experiences for both internal teams and clients.
