Component Portability

LeapFrogBI account administrators configure project lifecycles in the project console.

Each connection contains a definition for each lifecycle.

After creating all of the required project components, developers deploy the project to the target lifecycle.

All packages include a pointer to the lifecycle environment variable which provides connection details for the LeapFrogBI console database.  The environment variable name is based on the lifecycle abbreviation as defined by account administrators.

Built components can be migrated without creating a new build as long as each destination has the same environment variable as the original build’s lifecycle.

The configuration must be built for each target environment.  This ensures that connection details such as server name and database names are defined for the target environment.

Note:  Built packages include schema names.  If schema names should change in target lifecycles, then a new build is required.

In the most common scenario where each environment is identical developers can build once and deploy to each environment.  Each lifecycle requires a separate configuration which provides lifecycle specific configuration.

What We Do

We provide SMBs with custom data analytics services.

Built to Spec
We design custom solutions.

Low Cost per User
Empower as many report users as you like.

You Own It
Everything from the data solution to reports is yours to keep.

No upfront costs and no long-term commitment.

Available 24/7
We monitor and maintain everything 7 days a week.

Unlimited access to a team of data experts.

Find out how 
our clients
are getting

10x ROIwithin 6 months


Become Part of the LeapFrogBI Community

Join our newsletter to receive our latest insights and articles on automated, customized reporting in the healthcare industry.


Have any questions? Reach out to us, we would be happy to answer.