Fusion Fame Mapper Configure - Revision history

Vmurrell at 09:01, 1 July 2024

2024-07-01T09:01:57Z

Vmurrell: /* browser_lang_en.json */

2023-10-06T10:41:45Z

‎browser_lang_en.json

Vmurrell at 10:38, 6 October 2023

2023-10-06T10:38:53Z

Vmurrell: Created page with "Category:FFM Install Fusion Security Manager (FSM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be ed..."

2023-10-06T10:34:33Z

Created page with "Category:FFM Install Fusion Security Manager (FSM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be ed..."

New page

[[Category:FFM Install]]
Fusion Security Manager (FSM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be edited using a simple tool such as notepad as long as you use the correct json syntax.

[[File:FSM Config Files.png|800px]]<br>

=== siteconfig.json ===
Defines where the API will find the connected Fusion Registry and defines which Locales are supported and generates a language picker in the User interface. For example:

{
"ServicesAPI" : "http://localhost:8063/FusionRegistry/ws/fusion/info/product",
"Locales" : ["en"]
}

'''Adding additional locales'''
Add the appropriate code as show below
"Locales" : ["en", "he", "ru"]

=== browser_lang_en.json ===

The browser_lang_[locale].json file contains a map of property name to human readable label, for example:
"menu.security.structure.read" : "Structure Read",

The Language configuration file is used to decode labels on the User Interface. Any metadata (Dataflows, Concepts, Codes) used by FSM come from the web service, requested in the selected locale - as such the language configuration file does not play a role in decoding values in the retrieved metadata.

← Older revision		Revision as of 09:01, 1 July 2024
Line 1:		Line 1:
	[[Category:FFM Install]]		[[Category:FFM Install]]
		+
		+	'''New in Regnology Release R1.1.0.00 July 2024<br>'''
		+
		+	The site config file now includes additional lines to enable you to set colours (for example the banner).
		+
		+	{
		+	"ServicesAPI" : "http://localhost:8080/FusionRegistry/ws/fusion/info/product",
		+	"Locales" : ["en", "fr"],
		+	"BrandingStyle": {
		+	"background":"#9fd3c7",
		+	"color":"white"
		+	}
		+	}
		+	Note that you can use a hex code or text.
		+
		+	'''Previous Versions'''
		+
	Fusion Fame Mapper (FFM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be edited using a simple tool such as notepad as long as you use the correct json syntax.		Fusion Fame Mapper (FFM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be edited using a simple tool such as notepad as long as you use the correct json syntax.

@@ Line 19: / Line 19: @@
 The browser_lang_[locale].json file contains a map of property name to human readable label, for example:
-   "menu.security.structure.read" : "Structure Read",
+   "menu.famemapper.dataflows" : "Mapped Dataflows",
 The Language configuration file is used to decode labels on the User Interface. Any metadata (Dataflows, Concepts, Codes) used by FFM come from the web service, requested in the selected locale - as such the language configuration file does not play a role in decoding values in the retrieved metadata.

@@ Line 1: / Line 1: @@
 [[Category:FFM Install]]
-Fusion Security Manager (FSM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be edited using a simple tool such as notepad as long as you use the correct json syntax.
+Fusion Fame Mapper (FFM) contains two Configuration files which are in the dist/properties folder. These are in .json format but can easily be edited using a simple tool such as notepad as long as you use the correct json syntax.
-[[File:FSM Config Files.png|800px]]<br>
+[[File:FFM Config Files.png|800px]]<br>
 === siteconfig.json ===
@@ Line 21: / Line 21: @@
    "menu.security.structure.read" : "Structure Read",
-The Language configuration file is used to decode labels on the User Interface. Any metadata (Dataflows, Concepts, Codes) used by FSM come from the web service, requested in the selected locale - as such the language configuration file does not play a role in decoding values in the retrieved metadata.
+The Language configuration file is used to decode labels on the User Interface. Any metadata (Dataflows, Concepts, Codes) used by FFM come from the web service, requested in the selected locale - as such the language configuration file does not play a role in decoding values in the retrieved metadata.