Reference
Numerous Architecture

Numerous architecture

This article describes the numerous platform from a high altitude perspective. It describes how things – objects on the platform – are related and how numerous tools are created and used.

Tools and scenarios

Tools and scenarios

On the numerous platform you create tools and run those tools in scenarios. Tools are basically apps on the platform and contain configuration of code to be run within the app and an app builder for configuring a data model and interactive visual app elements. A scenario is where you run your tool(app). Scenarios references a tool and you can synchronize changes from the tool to the scenario. You can think of scenarios as an instance of a tool. Every time you create or update a scenario you copy the configuration from the tool to the scenario.

The link between scenarios and tools makes a powerful application where you can work on both your tools and run scenarios independently and thereby separate the development of tools and the use of tools in scenarios.

Tools

Tools and scenarios

Tools contain jobs, which hold the configuration for code to be run, and components which holds the data model and the visual UI elements of the app.

Components are a way to declare your data model for your tool in combination with visual UI elements. You can create advanced data models using components, sub-components and container components and you have many ways to adapt the interactive aspects of your model by setting default values and behaviors of your components.

Tools contain jobs. Jobs is the reference or container of your code to be run on the platform. A tool can have as many jobs as you need and each job can be run independently of other jobs in the sequence that makes sense when using the tool in the scenario.

Scenarios

Tools and scenarios

A scenario is where you run your tool. Scenarios live within groups within projects within workspaces. This means that you have many possibilities to organize your scenarios in a structure that fit your projects and your organization.

A scenario is an instance of a tool. This means that your scenario will stay the same even if the tool is changed. To get updates from the tool you need to manually synchronize the changes. Changes are merged into the scenario meaning that configurations and changes in parameters are kept as long as those elements are still in the tool. Read more about merging tool changes here.

Putting it all together

Tools and scenarios

Combining the above described architecture gives us the complete platform. With tools you build engineering applications that are used and organized in scenarios. This complete architecture can conform to many types of projects and organizations, where different groups of users use different parts of the platform.