General information
Contents
In this section, we explain the functions of K3.veranda that go beyond the basic version.
We are continuously developing this configurator. It may be that features are already available in the software that are not (yet) described in this help. All changes can always be found in Release-CHANGELOG.
The main topics beyond K3.Veranda basic are:
- Roof types such as cubic systems or carports.
- Coverings such as slatted roofs, solar, trapezoidal or corrugated sheet metal coverings.
- Shading such as under-roof and on-roof awnings or pleated blinds and fabric blinds.
- Side elements such as wedges, sliding doors, frame walls or vertical awnings.
- Lighting with configuration options for LED spotlights and LED strips.
- Display options with night mode, light colors or settings for dimensional chains.
- An area for clarifying frequently asked questions.
Preparation
Our K3.veranda is based on our K3 configuration core. This means that in the admin area the functions that are also used in other configurators. However, it is important to understand the differences for the other use cases.
Essentially, the difference to a "normal configurator" is the 3D scene - i.e. the 3D model of the Terrace roof plus the surroundings (house, garden, etc.). The 3D scene of K3.veranda is individually programmed and only reacts to special inputs.
The programmed 3D scene only reacts to created features to which special keys are assigned.
This is the only way for the 3D scene to know which information can be found in which feature.
To customize the 3D scene for yourself, you must therefore use these keys - and to access them, you must
activate Entwickler-Modus
in your profile (otherwise you will not see these keys at all).
**To do this, please go to your profile, activate the developer mode via the switch of the same name
and save **
To check whether you can now see keys, edit the entry for the height of the roof in your configurator. You will find the feature in the "Dimensions" step as "Height". Click on the pencil next to the feature name to edit the feature. In the sidebar that opens on the right, you will now find an input field "Key" which should contain the content height. If you do not see this field, you have not yet switched on developer mode - or perhaps you have not saved in the "Options" dialog after switching it on?
The height of the terrace roof only changes because the 3D scene can read the input of the field with the key "height" can read out. If you remove the "height" from the field, the height will no longer adjust. In the further course of this tutorial, we will get to know many other fields that must be given corresponding Keys, otherwise they will not be read out.
Since the 3D scene is individually programmed and overwrites the standard K3 scene, the usual model actions of the usual model actions of the K3 within K3.Veranda do not work. The available model upload and functions linked to it, such as printing, therefore have no effect within a K3.Veranda configurator has no effect whatsoever.
Important functions: Features, values and attributes
The 3D scene must read the keys at various points in order to react to them. Keys can be found at:
- Features: The 3D scene searches for features with specific keys.
Example: The 3D scene finds the selection "Model selection" by searching for the key model selection. - Values: The 3D scene finds the selected value of a feature via the key of the currently selected value of the feature
of the feature.
Example: the 3D scene shows a plaster façade by selecting the value<Liste> "Fassade" [facade]
for the feature PROTECTED_2 the value"Rauputz" [putz]
is selected. - Attributes: The 3D scene must know which attributes are set for this value.
Example: the 3D scene learns the mullion cross-section for a cubic roof by reading the attribute "Mullion" (log) of the value "Cubic system" (qubus) of the feature "Model selection" (model selection) - note: models and materials can also have keys, but this is irrelevant for the veranda configurator irrelevant for the veranda configurator
In the following, we will use the following spellings for features, their values and attributes:
- Feature:
<typ> "Modellauswahl" [modellauswahl]
,
where- type is the type of the feature, i.e
Liste
,Farben
,Zahl
,Text
,Ja/Nein
,Bild
,Information
andKomponenten
- model selection the name of the characteristic and
- modellauswahl is the key of the feature.
- type is the type of the feature, i.e
- Value:
"Kubisches Dach" [qubus]
where:
- cubic roof is the name of the value ("display") and
- qubus is the key of the value
- Attribute
<typ> "Pfosten" [log]
,
where- type is the type of the attribute, i.e.
mehrsprachiger Text
,nicht übersetzter Text
orZahl
; - "Post" is the name of the attribute and
- log is the key of the attribute.
- type is the type of the attribute, i.e.
Important difference name / key: in principle, you can choose any name for an attribute. So if you think your customers will get on better with "roof type" than with "model selection", you can rename the attribute Rename the feature. However, you may then find that in this documentation References to the original name in this documentation, which are then not (or no longer) called that in your configurator and are therefore more difficult to find.
However, the 3D scene searches specifically for keys. So if a feature does not have the correct key, it will not be found and the corresponding control function using this feature does not. Different capitalization, a space in between or a hyphen are enough to cause the search to fail a hyphen is enough to cause the search to fail. So please make sure that you spell the key exactly as specified here, exactly as specified here. Key is therefore to be understood literally - a key does not have to fit approximately, to open a lock, but exactly...
Functions in different license models
K3.Veranda is available in different license models.
These models offer a different range of functions.
In the course of further customization, you may reach a point where your entries have no effect on the 3D scene have no effect on the 3D scene despite the correct assignment of keys. In this case, you are not using you are not using the right license for your project.
You will find small references to the required license in the feature descriptions if they are not included in all licenses:
Contact
If you have any questions, please contact us directly by e-mail: support@objectcode.de