When you install Warehouse Mobile as an app in Business Central, it ships with a default setup that gives you ready-made flows for your warehouse operations. The flows are built as configuration, not code, which means you can change how they behave without touching any customizations or development.
Underneath the app sits a mobile flow engine that contains all the predefined flows, including sub flows for processes like receiving on a purchase order. The setup is complex, but it is configurable.
If you need an extra field in a flow, a different posting date behavior, or a change to a description on a posted document, you do not need a developer to write code. Contact us and we can adjust the flow through the setup instead.
Warehouse Mobile installs with a default flow setup out of the box
When you install Warehouse Mobile as an app, it comes with a default setup. That default equals the flow you see when you start using the app. A lot of setup work has already been done to create all the flows you need in a typical warehouse scenario.
The important thing to understand is that this is a setup, not a coding thing. The mobile flow is an engine sitting beneath the app, holding all the configuration. Because of that, you can modify the flow without making any customizations to the code.
How the mobile flow engine is structured
If you look into the mobile flow engine, you will find a lot of flows defined there. They include sub flows and several layers of configuration. It is complex material, and we are honest about that. We are not going to teach the full setup in a short video, only show you that it is possible.
As an example, the warehouse functionality includes a flow for receiving from a purchase order. You can open that specific flow, called receive on purchase order, and see exactly what it does step by step.
What the receive on purchase order flow actually does
Most people will not need to understand every detail, since it is a setup thing rather than something you work with daily. But to give you a sense of it, the receive on purchase order flow runs through a series of selection processes.
- It selects a purchase order using fields from the purchase header.
- It chooses a posting date.
- It blanks the quantity to receive, with actions tied to that step.
- It uses sub functionalities for posting and related steps.
Behind the scenes, a purchase flow like this looks complex. That complexity is what makes the flow flexible.
Changing a flow without customizing the code
The point of building the flows as setup is that you can make corrections without development. Say you want an extra field in the loop when you receive a purchase order. Or you want to use a customized field, change the purchase description on the posted document, or adjust some other behavior.
You do not need to customize your code to do any of this. Contact us, and we can help you make the change through the setup instead.
Q&A
Is Warehouse Mobile configured through code or setup?
Warehouse Mobile is configured through setup, not code. The mobile flow engine sits beneath the app and holds all the predefined flows. This means you can modify the flows without making any customizations to the code.
What do I get when I install Warehouse Mobile as an app?
You get a default setup that includes all the flows you need for a typical warehouse scenario. The default flow is ready to use as soon as you install the app.
Can I add an extra field to a flow when receiving a purchase order?
Yes. You can add an extra field, use a customized field, or change behavior such as the purchase description on the posted document. This is done through the flow setup, so no code customization is required. Contact us and we can help you make the change.
What does the receive on purchase order flow do?
It runs through several selection processes. It selects a purchase order using fields from the purchase header, chooses a posting date, blanks the quantity to receive, and uses sub functionalities for posting and related steps.