The flows you see in the Warehouse Mobile app for Business Central are built through configuration, not custom code. A generic mobile flow engine runs underneath, and the individual flows on top are setup data. This means you can adjust how the app behaves without a developer rewriting the application.
You can do a lot of the setup yourself. Many standard flows are locked so you cannot edit them directly, but you can copy a locked flow and change the copy to fit your process.
If you need deeper modifications, you contact Abakion or a consultant who understands the flow setup at this level.
The engine handles the heavy lifting. Only a few specific actions, such as posting, are built into the engine itself. Everything else is configured as flows.
Warehouse Mobile flows are built by configuration, not customization
All the different flows you see in the Warehouse Mobile app are done by configuration and not by customization. There is a large mobile flow engine beneath the surface, and the flows on top are essentially a setup. A lot of coding went into building the engine, but the individual flows are not code. They are configuration.
This keeps the app flexible. When you want a change, you do not need someone to rewrite the application. You adjust the setup instead.
How locked flows and copying work
You can do the setup yourself. A lot of the standard flows are locked, which means you cannot change them as they are. But you can copy a locked flow and make your changes on the copy. That way you keep the standard intact and still get the behaviour you need.
If you want modifications done at a deeper level, you can contact Abakion or a consultant who understands the flows and the modification logic at this level.
What a flow setup looks like in practice
Take the find item flow as an example. When you open the setup for that flow, you see the main lines describing what the app asks about and what happens on each line. It is a matter of complex setup, but it is all setup.
When you click a line, you get related mobile flow setups attached to it. How complex the configuration gets depends on the flow.
A purchase order flow, where you receive goods directly on a purchase order, is a good example of a more complex case. The setup has many lines, and each line can contain sub flows. One line grabs the purchase header, then the flow loops through all the lines, lets you enter the item number, and registers the quantity to receive.
What the engine handles versus what you configure
This is complex stuff to set up, but the point is that the engine behind it is built generically. Apart from the engine, only a few specific actions are built in, such as posting flows. Everything else runs as configuration.
The result is that the app stays open to modification even though the underlying logic is complex.
Q&A
Are the flows in the Warehouse Mobile app coded or configured?
They are configured. A generic mobile flow engine is coded underneath, but the individual flows you see in the app are setup data, not custom code.
Can I change the standard flows myself?
You can do a lot of the setup yourself. Many standard flows are locked and cannot be edited directly, but you can copy a locked flow and make your changes on the copy.
Who do I contact for deeper modifications?
You contact Abakion or a consultant who understands the flow setup and modification logic at this level.
What is built into the engine itself rather than configured?
Only a few specific actions are built into the engine, such as posting flows. The rest of the flows are configured as setup.
Why is the purchase order receiving flow more complex?
The purchase order flow has many lines, and each line can contain sub flows. It grabs the purchase header, loops through all the lines, lets you enter the item number, and registers the quantity to receive.