Templates: from micro to macro

One of the core development principles behind our platform is productivity, and, as we are all aware, successfully reusing, or repurposing, work is one of the most effective ways of progressing towards that goal.

In order to achieve this, we’ve developed a simple “Import – Export” system, placed on our “Modeler Area” (image below), that allows you to export and import your model across tenants, in a matter of seconds.

As complexity varies, your reused model can be imported to achieve all kinds of simple functionalities, like Web Components (graphics, buttons, etc), but it can also allow you to import fully functioning systems, essentially enabling you to duplicate and use them as you see fit, whether it is the basis for your new software product (check our Partner’s page for more info), or a starting point for adjustments or other needed, separate, branches of development.

Templates follow the exact same structure of our platform, separating your work into folders of JSON files that, when imported, will build all aspects of the application for you. There are two main folders in a Template file, where you’ll be able to find all exported elements, behaviours and configurations:

  • Model: where you’ll find all the tenant’s modelling entities and behaviours;
  • Tenant Security: where you’ll find all the tenant’s security configurations; 

Inline with our productivity pledge, we’ve created a dedicated Template sharing repositoryon Github, where you can find, and contribute to, our community template list.

As our platform continues to grow, productivity features such as Templates, or accelerators (see blog post), will be our main focus moving forward, and we have a lot of exciting times ahead for 2019.

Don’t forget to follow us on LinkedIN or Twitter, and subscribe to our weekly newsletter, so you don’t miss a single piece of news about our platform.