Global Settings (All) MOD009ABF
Customizer → Master Data → Global Settings
Customizer → Module Customizer → Modules → Global Settings
In the Global Settings module, customizing objects are stored/managed
which can, e.g., be used in different Python macros and/or value ranges (like modules, OLEs, etc.) to ensure that they can easily be interchanged system-wide.
the settings of which (in the case of parameters) are to apply system-wide.
In the module, global settings are grouped in thematically suitable categories. Within the thematic categories the settings are displayed subdivided by class (object category).
The global settings contained in the PLANTA standard system must not be deleted.
in the Edit Global Settings module you can delete settings you defined yourself by simply marking and deleting them.
The global settings can also be configured via the environment variables. Schema:
planta__server__global_settingprefix and then the Python ID of the global setting. Read more on environment variables.Error rendering macro 'fontawesome-macro' : Page loading failedAt the moment, this cannot be used to set templates. Global settings which have been set via environment variables cannot be changed in the Global Settings module. When you try to change them anyway, a respective message is displayed.
Categories and Classes
The global settings are grouped in thematically suitable categories.
Within the categories, the global settings in this module are subdivided by so called so-called classes.
Module ID
Module variant ID
OLE object
Parameter
Startup module ID
Search results
Template
Dialog message ID
Symbol ID
In the Global Settings (All) module, the settings of all categories and classes are listed and can be edited by users with customizer rights.
The parameters of the following categories are also contained in separate Global Settings modules of the respective areas of application which can also be edited without customizer rights:
Classes: Module ID, Dialog message ID, OLE object, Parameters, Startup module ID
The following procedure exemplifies how to store a module ID in the global settings. For other classes, the procedure is identical.
Select Insert → Global Settings from the context menu.
The Edit Global Settings dialog module will be opened.
Allocate a name in the Name field.
Define a Python ID in the Python ID field.
Enter the module ID in the Alpha (120) field.
Select the requested class in the Class listbox, here "module ID".
Select the required project from the Category listbox.
If required, fill other fields.
Save.
#Auslesen einer Modul-ID
from ppms.global_setting import get_global_setting_value
module_id = get_global_setting_value(python_id='', attribute='alpha120')
The global_setting Python module is imported in order to be able to use the
get_global_setting_value()method.
Python IDs must be usable as Python literals. They must not contain any special characters, umlauts, spaces, etc.
Python IDs must be defined uniquely in the global settings.
Individual Python IDs must start with an L and the license number.
Example: L100_pr_datasheet
If the customizer does not set this manually, the system will set it automatically.
Classes: Module variant ID, Restrict filter results
The following procedure exemplifies how to store a module variant ID with its corresponding module ID in the Global Settings.
Select Insert → Global Settings from the context menu.
The Edit Global Settings dialog module will be opened.
Allocate a name in the Name field.
Define a Python ID in the Python ID field.
Enter the module ID in the Alpha (120) field.
Enter the module variant ID in the Parameter Alpha (120) field.
Select the requested class from the Class listbox, here "Module variant ID".
Select the required project from the Category listbox.
If required, fill other fields.
Save.
#Auslesen einer Modulvarianten-ID
from ppms.global_setting import get_global_setting_value
mv_id = get_global_setting_value(python_id='', attribute='parameter')
The global_setting Python module is imported in order to be able to use the
get_global_setting_value()method.
Python IDs must be usable as Python literals. They must not contain any special characters, umlauts, spaces, etc.
Python IDs must be defined uniquely in the global settings.
Individual Python IDs must start with an L and the license number.
Example: L100_pr_datasheet
If the customizer does not set this manually, the system will set it automatically.
Class: Template
Select Insert → Global Settings from the context menu.
The Edit Global Settings dialog module will be opened.
Allocate a name in the Name field.
Define a Python ID in the Python ID field.
Select the requested class in the Class listbox, here "Template”.
Select the required project from the Category listbox.
If required, fill other fields.
Save.
Refresh the module.
Click on
in the new global setting in order to open the Edit Global Settings dialog module.Store the template in the Template code parameter.
Save.
#Auslesen eines Template-Codes
from ppms.global_setting import get_global_setting_value
template = get_global_setting_value(python_id='', attribute='template_code')
The global_setting Python module is imported in order to be able to use the
get_global_setting()method.
Python IDs must be usable as Python literals. They must not contain any special characters, umlauts, spaces, etc.
Python IDs must be defined uniquely in the global settings.
Individual Python IDs must start with an L and the license number.
Example: L100_pr_datasheet
If the customizer does not set this manually, the system will set it automatically.
Global Customizing Parameters (Excerpt)
Below you will find a description of all relevant parameters from the Customizing area For a description of the parameters from the Project/Portfolio and PLANTA link areas, please refer to the separate Global Settings (Project) and Global Settings (link) topics
PLANTA customizer
Parameter name | Parameter ID | Meaning and values | Default values |
|---|---|---|---|
Python editor |
| Here you can specify the path for the editor which is, e.g., opened in the Modules module when you click on the Open Python macro editing button.
| C:\Program Files\Notepad++\Notepad++.exe |
Adaptive Cards
Parameter name | Parameter ID | Meaning and values | Default values |
|---|---|---|---|
Actionable Message Provider ID (originator) |
| The provider ID is used to assign the correct authentication service in order to avoid misrouting and security problems. | |
Activate Adaptive Cards |
| This parameter controls whether adaptive cards are activated or deactivated.
Error rendering macro 'fontawesome-macro' : Page loading failed Values
| 0 |
Miscellaneous
Parameter name | Parameter ID | Meaning and values | Default values |
|---|---|---|---|
Standard date format |
| Format which is used to interpret the date values specified in the Filter from / Filter to fields in the customizing in case a different date format than that used in the PLANTA standard customizing is to be used, or if you generally use different date formats in the application, e.g. when using a German and an English user interface. | |
PLANTA Protocol Name |
| Protocol which is used to open the desktop client via URL. For further information, see Application Link. | planta |
OpenAi API key |
| Token for authentication with the OpenAI API. If no token is configured, AI functions cannot be used. |