We have created a solution containing both pro code and low code, AI, Microsoft APIs and third party tools.
Code App for collection Dream Project request
Power Automate that uses Dataverse, OneFlow, AI Builder, Outlook and Link Mobility actions
Model-driven app as an backoffice app to follow up project. Perfect low code app for managing dream project requests.
OneFlow Portal for managing contracts
A go through of the solution
The Code App is vibe coded using TypeScript and React and used for collecting Dream Project requests. This creates a Dataverse record that triggers a power automate flow that creates a contract in OneFlow. Pure pro code as far as the eye can see 👀
Further, we created a Power Automate flow that gets triggered when a new Dream Project is created and this automates our contract process by using OneFlows actions for creating the contract and adding the customer to the contract. LINK Mobility and Outlook action are used to send an SMS and email to the customer responsible for quick follow up and contract validation before sending it. This is a perfect combination of pro code and low code.
The flow looks like this.
The AI Prompt looks in the Power Automate looks like this and this is sendt til the AI Prompt.
The “Run a prompt” action sends the data to the prompt below and gets the outline for the contract details back. And, we are using this in the contract generation.
We used Template Groups in OneFlow to populate documents from power automate.
The fields are created in the OneFlow portal. These must be created and added to the template before they are available in the power automate flow.
The fields are added to the Template in OneFlow like this.
After sending the contract out from the OneFlow portal the customer gets and email that they can sign.
The contracts looks like this after been generated by the Power Automate flow. The description is generated using AI Prompts feeded with data from the dream project request from Dataverse.
The LINK Mobility
We are using the LINK Mobility Action in Power Automate that lets us send SMS with ease using a source number, platform id and partner id and a phone number to send the SMS to. This works like charm.
The SMS that is sent looks like this:
Business value: The tools helps as stich our solution together and improve the value for our customers by providing faster contract creation and automation, and notification by SMS for quick follow up by customer success manager.
Claims:
Stairway to Heaven
In our contract generation flow we are using three Microsoft APIs for solving our business need
Dataverse API
AI Prompt API
Outlook API
Thieving bastards
Using OneFlow and LINK mobility as payable third party solutions to improve our business process by using existing tools in the marked that is developed by marked experts and that keeps being updated and improved.
OneFlow
Using OneFlow for contract generation and posted on LinkedIn
LINK Mobility
Using LINK Mobility for notification to customer success mangers and more SMS notification in an upcoming sprint. And posted on LinkedIn
Power User Love
By combining the power of pro code for more customizable look, feel and usability for collecting data and using low code apps for backoffice project follow up with a more fix look and feel with drag and drop.
Code App using TypeScript and React for more control over the user interface and interactivity:
Using Model-driven app as a backoffice with more “strict” look and field, but perfect for following up and adding data.
Every time someone places an order in the CCCP Factory Portal, a Power Automate flow triggers automatically and sends a contract to the customer via Oneflow’s API. No manual work. No email chains. Just automated contract generation and signing.
How It Works
Step 1: User places order on the Resources page (wheat, potatoes, carrots, etc.) Step 2: Order gets created in Dataverse Step 3: Power Automate detects the new order (trigger: “When a row is added”) Step 4: Flow calls Oneflow API to generate contract with order details Step 5: Contract sent to customer’s email via Oneflow Step 6: Customer signs on any device (desktop, mobile, tablet) Step 7: Signed contract triggers next steps in the flow (payment processing, fulfillment)
Why Oneflow?
We needed seamless document collaboration and signing. Oneflow’s API made it simple to integrate with our Dataverse/Power Automate setup. The contracts are dynamic, they include order details, customer info, line items, and totals pulled directly from our data.
The Result
Orders in our portal now have a complete contract lifecycle:
Order placed → Contract generated
Contract sent → Customer notified
Contract signed → Order validated
Validated order → Payment & fulfillment will later triggered (yet to come)
All automated. All integrated. All working seamlessly with Oneflow’s modern signing solution.
This document describes the integration between oneFlow and Power Automate used within a Dynamics 365 Model-Driven App.
1. Selecting a Bid on the Project Form
On the Project form, when a user selects and specifies a Bid, this action serves as the trigger for the Power Automate flow.
2. Power Automate Flow Execution
Once the Bid is selected, a Power Automate flow is automatically triggered. The flow creates the contract from a template in oneFlow, specifies the participant, and publishes it.
3. Contract Creation and Sending for Signature
After the contract is created from the template, the flow sends the contract to the Wandering Trader specified in the Bid via email.
4. Sign Contract
The contract then can be signed by the Wandering Trader.
🪄 Claiming the OneFlow Sponsor Badge – A Wizard’s Journey 🏅✨
Here’s a glimpse into how we 🧙♂️, have used OneFlow’s tools to conjure something truly extraordinary.
OneFlow – The Enchanted Contract Master 📜✨
Welcome to the modern age of contract signing, where OneFlow transforms dull parchment into living, collaborative scrolls that can be signed seamlessly on any device. 🖋️ Whether you’re sealing a pact between Death Eaters or approving an Order of Doom, OneFlow ensures your contracts are as smooth as unicorn hair. 🦄✨
How We Cast the Spell
With OneFlow’s API, we created a spellbinding process to manage contracts for the sinister “Order of Doom.” Here’s how we conjured this masterpiece:
1. The Birth of an Order of Doom 💀🖋️
When a Power Page user (a dark wizard in disguise) creates a new Order of Doom in Dataverse, the spell is cast!
A cloud flow retrieves:
The wizard’s credentials (so we know who summoned the order 🧙).
The chilling details of their request.
2. Summoning the Contract 🔮📄
The cloud flow calls forth OneFlow’s API, using a mystical template pre-crafted in the OneFlow portal.
A contract is conjured between the Dark Ledger Party (us) and the requester (them).
The enchanted scroll is sent via owl 🦉—or email (muggles might not appreciate owls)—for e-signature.
3. Signing and Sealing the Pact ✍️⚡
A child flow monitors the pact’s status like an Auror watching for dark magic.
Once both parties have signed the contract, the spell completes:
An owl-email confirmation is sent to the requester. ✉️🦉
The signed scroll is attached to the timeline of the Order of Doom in Dataverse, ensuring it’s securely stored in the Ministry’s records (or our shadowy vaults).
Why This Wizardry Works
🧙♂️ Effortless Automation: The contract lifecycle is handled faster than a Hippogriff in flight.
🔮 Crystal-Clear Transparency: Both parties are guided through the signing process as if by the Marauder’s Map.
📜 Centralized Magic: Every contract is neatly stored, ready for future spells (or audits).
✨ Spellbinding Innovation: By fusing Power Platform and OneFlow API, we’ve created a process worthy of Dumbledore himself.
Greetings, wizards, witches, and potion enthusiasts! ✨
In the ever-evolving wizarding world of ACDC 2025, Team PowerPotters of House Slytherin has conjured up a seamless solution for managing potion production approvals. By combining the modern magic of Power Automate and Oneflow, we’ve ensured that every potion brewed in our automated system is backed by a binding contract—because even wizards know the importance of proper documentation!
Here’s how we’ve harnessed Oneflow to craft a streamlined, contract-driven workflow that ensures accountability, precision, and a touch of Slytherin cunning.
🪄 The Problem: Brewing with Oversight
When dealing with potions that could range from mundane health elixirs to potentially world-altering concoctions, it’s essential to have a robust approval process in place. This required us to:
Automate Contract Creation: Trigger contract generation whenever a potion production request is initiated.
Enable Digital Approval: Ensure the contract is signed to approve production before any ingredients are consumed or recipes executed.
Integrate with Our Existing Workflow: Seamlessly connect Oneflow contracts to the potion production triggers from our Raspberry Pi system.
🧙♂️ The Solution: Oneflow Meets Power Automate
We designed a Power Automate flow to manage the entire lifecycle of potion production approvals. Let’s break it down:
Triggering the Flow:
The process begins with the Raspberry Pi detecting a potion creation request. This is often initiated when a user physically interacts with the Pi, signaling the system to begin brewing.
Sorting Data:
The incoming data from the Pi (e.g., potion name, required ingredients, quantity) is processed in JSON format to ensure everything is orderly and ready for the next step.
Contract Creation:
The flow automatically connects to Oneflow, generating a contract titled “Elixir Ordre” with all relevant details pre-filled:
Workspace Name: The designated potion lab.
Template: A standardized approval template tailored to potion production.
Contract Details: Key information about the potion request, including names, quantities, and timestamps.
Delivery for Approval:
The contract is delivered to the appropriate authority (e.g., Professor Snape or a designated Potion Master) for digital signature, ensuring the process is both quick and secure.
Next Steps:
Once the contract is signed, the system allows potion production to proceed, ensuring no unauthorized brews wreak havoc in the wizarding world!
✨ Why This Solution Shines
Efficiency: Automating contract creation and approvals saves time, eliminates manual errors, and ensures every potion is backed by a legally binding agreement.
Compliance: Integrating Oneflow ensures proper oversight, keeping potion production safe, secure, and accountable.
Slytherin Strategy: True to our house, this solution is ambitious, resourceful, and ensures that every step of the process is carefully controlled.
🐍 Why We Deserve the Oneflow Badge
By combining Oneflow with Power Automate, we’ve created a system that brings the wizarding world’s potion production in line with modern business practices. Here’s why we believe this integration deserves the Oneflow Badge:
Seamless Integration: From Raspberry Pi triggers to contract approvals, the workflow is fully automated and cohesive.
Real-World Application: This isn’t just a proof of concept—it’s a functional system that ensures every potion brewed is safe, approved, and documented.
Digital Innovation: Leveraging Oneflow for automated contract creation and digital signatures showcases the potential of modern tools in a magical setting.
🔮 Join the Journey
With every potion brewed and every contract signed, we’re proving that the intersection of magic and technology is where true innovation happens. Follow our journey as we continue to enchant ACDC 2025: acdc.blog/category/cepheo25.
Our solution would not be possible wihtout the hard work and dedication of our sponsors solutions, enabling magical abilities we would not be able to reproduce and transforming our solutions with wizardy love.
Link Mobility
Our first process is to send an Owl with the letter to invite prospective wizards and witches to their school. If the wizard is an area which doesn’t have good owl coverage, due to extreme weather conditions, muggle political infighting or just too far away, we send them a text with their invite
This is done via Link Mobility in Power Automate, utilising their API to send out an invite to our Static Web App Portal.
This is received by prospective sorcerors as a text message
Oneflow
Once the prospective candidate has filled out their details and qualified for the next stage, we need to get agreement from their parents or guardians to allow them to attend wizarding school, and ensure they agree to go to diagon alley to get the wizarding items to prepare the new wizard for school.
This is enabled by the Contract templates and capablities of Oneflow solution.
Firstly we set up a template, then using their API, create a contract based on that template. and sent to the parent of the prospective students.
The parents then get to sign in to Oneflow to enter their details as well as the students and confirm they agree to the terms, all seamless!
Resco
For Resco, we had an abundance of choice to use their PCF components. This control bring usability to the platform easily.
We embedded the multi attachment uploader into our applicaiton process, allowing uploading of many documents all at once in an easy and user friendly manner.
PCF Gallery
Finally, not content with just those 3, we have used a PCF control from the PCF Gallery. This control is a Tag Picker, which allows quick and easy association and disassociation of records via the many to many relationship.
We used this to allow a simple, user-friendly process to associate characteristics to our potential sorcerors.
