This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision |
| 2000_concepts:0900_prod_feats:0700_setting_initial_values [2022/08/21 22:47] – ↷ Page moved from docs:2000_concepts:0900_prod_feats:0700_setting_initial_values to 2000_concepts:0900_prod_feats:0700_setting_initial_values administrator | 2000_concepts:0900_prod_feats:0700_setting_initial_values [2026/08/13 03:10] (current) – ↷ Links adapted because of a move operation 0.0.0.0 |
|---|
| Usually such initialisatuion on is performed by the administrator of the system, who does it once before the majority of users access the system. | Usually such initialisatuion on is performed by the administrator of the system, who does it once before the majority of users access the system. |
| |
| //**Aware IM**// includes the predefined business object ''SystemSettings'' that can help in setting the initial values of the application. The ''SystemSettings'' business object is automatically included in all business space versions – it has a number of predefined attributes and configurators can also add their own attributes. The instance of the SystemSettings object can be created by the administrator of the system or created automatically by rules. The interesting feature of the ''SystemSettings'' object is that there can only be one instance of this object in the system – //**Aware IM**// will not let you create the second instance. This makes it possible for //**Aware IM**// to always keep this single instance in the [[docs:2000_concepts:0800_data_processing:0100_rule_evaluation:0100_context|Context]] and configurators can use this object anywhere in business rules or inside tags without having to worry about placing this instance in the Context first. | //**AwareIM**// includes the predefined business object ''SystemSettings'' that can help in setting the initial values of the application. The ''SystemSettings'' business object is automatically included in all business space versions – it has a number of predefined attributes and configurators can also add their own attributes. The instance of the SystemSettings object can be created by the administrator of the system or created automatically by rules. The interesting feature of the ''SystemSettings'' object is that there can only be one instance of this object in the system – //**AwareIM**// will not let you create the second instance. This makes it possible for //**AwareIM**// to always keep this single instance in the [[2000_concepts:0800_data_processing:0100_rule_evaluation:0100_context|Context]] and configurators can use this object anywhere in business rules or inside tags without having to worry about placing this instance in the Context first. |
| |
| The SystemSettings object essentially lets you use its attributes as parameters of the application. For example, if the application that you configure includes document templates that have logos of the end users you may want to let the system administrator provide the logo of the specific end user before this user starts working with the system. You can solve this by adding ''LogoImage'' attribute of the Picture type to the SystemSettings object and design document templates to contain the reference to this attribute (''%%<%%<SystemSettings.LogoImage%%>%%>'') rather than providing the specific image in the document template. You will then define the menu item (for the system administrator only) that will create the instance of the SystemSettings object and bring up its form. The administrator will use this menu item and provide the specific image as the value of the “LogoImage” attribute. | The SystemSettings object essentially lets you use its attributes as parameters of the application. For example, if the application that you configure includes document templates that have logos of the end users you may want to let the system administrator provide the logo of the specific end user before this user starts working with the system. You can solve this by adding ''LogoImage'' attribute of the Picture type to the SystemSettings object and design document templates to contain the reference to this attribute (''%%<%%<SystemSettings.LogoImage%%>%%>'') rather than providing the specific image in the document template. You will then define the menu item (for the system administrator only) that will create the instance of the SystemSettings object and bring up its form. The administrator will use this menu item and provide the specific image as the value of the “LogoImage” attribute. |