Hyperon concepts

Profiles

What are profiles in Hyperon?

Simply put, a profile in our environment is the entire data module, where the domain and context are directly assigned to the profile end cannot exist without it.

All the profiles existing in the environment are listed above the toolbar. Profile, selected in this field, is available for edition, its' domain, context and regions.

Each user can edit only one profile at a time. But whenever you see fitted  viewed profile can be changed.

There is no limit for number of profiles in one environment, but each of them will have only one domain and one context. We can have many profiles, because we create them to be able to use a given environment in many configurations. Each profile has its own inputs and outputs.

Thanks to the profiles, we can easily switch between the configurations we are interested in. For companies that want to agilely manage and use their products, this is a big advantage.

Profiles and business

 

From a business point of view, the profile allows us to separate projects. As each project has its own independent configuration, in practice it happens that one profile is created for one project. It often happens that a client have several applications connected to one Hyperon environment. Each application will call up one of the profiles. It is also possible for an application to call more than one profile. That’s  good for the application to call at least one, it is a recommended solution because it gives more possibilities to the user.

Since the context and the domain are the components of the profile, application only from the profile will be able to call the domain and the context.If we create a profile, it can exist without the domain and context, but the domain and context cannot be outside the profile.

Good to know

Within Hyperon Studio, multiple profiles can be defined, allowing the use of one environment for as many configurations as needed.

Each profile contains its own definition of inputs and outputs for the client application and its own parameterization.

What does this mean for the user's application architecture?

Only one Hyperon Runtime Library is needed even in a multi-profile environment.

The application can switch between profiles at runtime, a restart is not necessary.

How to create profiles in Hyperon

In the main toolbar, choose 'TOOLS'  and then click 'Profiles' 

And  set a name to the new profile, click a 'SAVE' button.

That is how the profile is created but it is not everything that can be configurated in this screen… In addition, we can choose a tag that will be associated with our profile and it will be set automatically for elements created in that profile. 

If you want to find out what tags are read more here.

 

Select a default profile TAG

The view of the created profile with default tag set.

If we select the checkbox below, we can set tag BIG automaticallyfor each  new parameters and/or functioncreated within given profile.

The other two flags are used to filter the view of the list of the parameters or function respectively. Then the default TAG ('BIG') will be set as a filter to selected view.

For example

We choose and save check box 'use this tag to filter functions in this profile'

 

And when we go to 'Parametrization' and 'Functions'  we will see that tag 'BIG' is set as a filter for the list of the functions.