Skip to main content
Veylo can read low-code applications it didn’t build. Before anyone changes a configuration, you can find out how an application already running on your platform actually works, and keep a record of it. There are two ways to do it. Ask the builder when you want answers to specific questions or documentation of the live application. Give it to the CAB when you want a structured blueprint to plan larger work from.

Asking the Builder

1

Connect the builder to the application

Open a Low Code project and connect it to the environment where the application runs. Each platform’s overview covers what the connection needs: TAP, ServiceNow, Salesforce, and PowerApps.
2

Ask how it works

Ask the questions you’d otherwise answer by clicking through the configuration: which table a form writes to, what triggers a workflow, which roles can approve a request.
3

Ask for documentation

Ask the agent to document the application, or one part of it: “Document the intake workflow, including every status and who can move a request between them.” It produces documentation you can review, edit and keep.
Ask before you change. A question about what a change would touch costs far less than unpicking a change that touched more than you expected.

Giving It to the CAB

1

Gather the configuration and installation files

Use the files your team already moves between environments, such as from Dev to Test. They describe the application as it’s actually deployed.
2

Upload them to the CAB

In CAB Configuration, add the files under Upload Documents or Source Code. The CAB reads them the way it reads source code. See Supported input types.
3

Generate and review the blueprint

The blueprint maps the application’s data model, forms, workflows, roles and business rules. Review it the way you would any blueprint, and correct anything it got wrong. See Editing your CAB.
Add whatever documentation you have alongside the files, even if it’s out of date. The CAB cross-checks the two, and each fills gaps in the other.

Putting It to Work

Either way, the work that follows starts from what the application actually does, not from what someone remembers it doing.
  • Enhancement. Plan new capability against the real data model and workflows, then turn the blueprint into Tickets. See CAB to Ticket conversion.
  • Support. Answer “why does it do that?” from the configuration itself, and keep the answer as documentation.
  • Modernization. Use the blueprint as the starting point for rebuilding the application, on the same platform or another one. See Feed an existing system into a CAB.

Your Next Step

Choose your platform

What each low-code platform supports, and where direct configuration stops.

Check what the CAB accepts

The file types the CAB can read.