Metis Smart Modeling - Configuration Manager - Revision history

PatrickG: /* Using a Configuration Package */

2014-01-13T15:41:57Z

Using a Configuration Package

← Older revision		Revision as of 15:41, 13 January 2014
Line 100:		Line 100:


-	Editing any of the objects related to the models will result in checking it out from the Package. This will prohibit other users from editing the same rules or mask for example. The User/Administrator can have a overview of the various 'reservations' on the '''Config Manager''' main screen.	+	Editing any of the objects related to the models will result in checking it out from the Package. This will prohibit other users from editing the same rules or mask for example. The User/Administrator can have an overview of the various 'reservations' on the '''Config Manager''' main screen. On top of that, each time the User validates a modification in any of the modeling elements, a confirmation window asks the user if he wants to "check the object back in". Answering "Yes" will immediately make the element available to other users.
		+
		+
		+	[[File:MSM_Attributes_Attributes_Delete.png\|center]]

	== Editing an existing Configuration Package ==		== Editing an existing Configuration Package ==

PatrickG at 15:34, 13 January 2014

2014-01-13T15:34:47Z

← Older revision		Revision as of 15:34, 13 January 2014
Line 5:		Line 5:


-	In order to work with the functionality, the User/Administrator has to create a Configuration Package which will include all model relevant data to be used by all the user in the group. This will create a set of data which can then selected at log-on and which stays totally separated from the main data set. Thus allows all the users in the group to implement new models or modify rules without affecting the the productive part of the database. Once all ~~modification~~ are done, tested and validated, the updated data set can be transferred back to the main database. Future modifications can then be bone on new Configuration Packages, which could be based on the main data set or or a previous package.	+	In order to work with the functionality, the User/Administrator has to create a Configuration Package which will include all model relevant data to be used by all the user in the group. This will create a set of data which can then selected at log-on and which stays totally separated from the main data set. Thus allows all the users in the group to implement new models or modify rules without affecting the the productive part of the database. Once all modifications are done, tested and validated, the updated data set can be transferred back to the main database. Future modifications can then be bone on new Configuration Packages, which could be based on to the main data set or or a previous package.


Line 12:		Line 12:

	Using the same '''central database''', each user included in the group of developers can log in and access a different Configuration Package and apply all the changes needed. It can be seen as different branches in a development environment. Each object ([[Metis_Smart_Modeling_-_Models\|Models]], [[Metis_Smart_Modeling_-_Group_of_Rules\|Groups of Rules]], [[Metis_Smart_Modeling_-_Rules\|Rules]], [[Metis_Smart_Modeling_-_Variables\|Variables]] or [[Metis_Smart_Modeling_-_Masks\|Masks]]) is "checked-out" when edited (reserved) by a User in order for no one else to interact with the same object. It is reserved for him exclusively. Only when he manually "checks it out" will that object be again available for edition by other users.		Using the same '''central database''', each user included in the group of developers can log in and access a different Configuration Package and apply all the changes needed. It can be seen as different branches in a development environment. Each object ([[Metis_Smart_Modeling_-_Models\|Models]], [[Metis_Smart_Modeling_-_Group_of_Rules\|Groups of Rules]], [[Metis_Smart_Modeling_-_Rules\|Rules]], [[Metis_Smart_Modeling_-_Variables\|Variables]] or [[Metis_Smart_Modeling_-_Masks\|Masks]]) is "checked-out" when edited (reserved) by a User in order for no one else to interact with the same object. It is reserved for him exclusively. Only when he manually "checks it out" will that object be again available for edition by other users.
		+
		+
		+	{{Note
		+	\| All "Checked-out" object form the logged in user and the others can be viewed from the corresponding menu. The ones belonging the current user can also be "checked back in" from this same place.
		+	}}
		+

	The Configuration Manager allows also to enforce versionning on all the model data to be made available in Metis Smart Suite. By creating ordered Packages, the User/Administrator can define multiple packages for all future versions of the models. The tool then allows to transfer updated part of a package to any of those packages in order to keep them all up to date and to have consistent data.		The Configuration Manager allows also to enforce versionning on all the model data to be made available in Metis Smart Suite. By creating ordered Packages, the User/Administrator can define multiple packages for all future versions of the models. The tool then allows to transfer updated part of a package to any of those packages in order to keep them all up to date and to have consistent data.


-	The list shown in the main window displays all the Configuration packages defined in Metis Smart Suite. It can be sorted alphabetically or by creation date using the small arrows in the table headers.	+	The list shown in the on the left hand side of the main window displays all the Configuration packages defined in Metis Smart Suite. It can be sorted alphabetically or by creation date using the small arrows in the table headers.


	[[File:MSM_Modeling_Config_Manager.png\|center\|600x400px]]		[[File:MSM_Modeling_Config_Manager.png\|center\|600x400px]]
		+
		+
		+	On the right hand side, the content of the Package is displayed based on the data structure of Metis Smart Suite. Showing all the models included in the package and all the elements (Masks and Group of Rules) linked to the model. This view allows the User/Administrator not only to have a detailed view of what the package contains, but also to see which object has been "ckecked-out" by himself or other users. The table shows a column with the following icons to distinguish between the various possibilities.
		+
		+	{\| class="wikitable centre" width="90%" style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: grey;"
		+	\|-
		+	! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" \| Type of reservation
		+	! scope=col style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" \| Icons
		+	! scope=col style="border-style: solid; border-color: grey; border-width: 0 0 1px 0" \| Description
		+	\|-
		+	\| width="15%" style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" \|
		+	'''Not "Checked-out"'''
		+	\| width="5%" style="text-align:center; border-style: solid; border-color: grey; border-width: 0 1px 1px 0" \|
		+	[[File:MetisSmartModelingRuleSIngle.PNG\|link=]]
		+	\| width="80%" style="border-style: solid; border-color: grey; border-width: 0 0 1px 0" \|
		+	The listed object or modeling element has not been "checked-out" by anyone and is available for edition.
		+	\|-
		+	\| width="15%" style="border-style: solid; border-color: grey; border-width: 0 1px 1px 0" \|
		+	'''"Checked-out by current user"'''
		+	\| width="5%" style="text-align:center; border-style: solid; border-color: grey; border-width: 0 1px 1px 0" \|
		+	[[File:MetisSmartModelingRuleSIngle.PNG\|link=]]
		+	\| width="80%" style="border-style: solid; border-color: grey; border-width: 0 0 1px 0" \|
		+	The listed object or modeling element has been checked out by the user currently logged in the application (user itself). It is avaibla for edition only by him and can be "checked back in" when the modifications are completed.
		+	\|-
		+	\| width="15%" style="border-style: solid; border-color: grey; border-width: 0 1px 0 0" \|
		+	'''"Checked-out by another user"'''
		+	\| width="5%" style="text-align:center; border-style: solid; border-color: grey; border-width: 0 1px 0 0" \|
		+	[[File:MetisSmartModelingRuleExternal.PNG‎\|link=]]
		+	\| width="80%" style="border-style: solid; border-color: grey; border-width: 0 0 0 0" \|
		+	The listed object or modeling element has been checked out by another user (some else). It cannot be edited by currently logged in the application (user itself) until it is "checked back in" by the "owner".
		+	\|-
		+	\|}


Line 25:		Line 63:
	== Creating a new Configuration Package ==		== Creating a new Configuration Package ==

-	In the '''Configuration Manager''' sub-menu, the "Add" button [[File:MetisSmartModelingAddButton.PNG\|link=]] located above the main list allows the user/administrator to create a new Configuration Package. When ~~it is~~ clicked, the '''Config Manager''' creation window opens, it allows to define all related information.	+	In the '''Configuration Manager''' sub-menu, the "Add" button [[File:MetisSmartModelingAddButton.PNG\|link=]] located above the main list allows the user/administrator to create a new Configuration Package. When clicked, the '''Config Manager''' creation window opens, it allows to define all related information.


Line 54:		Line 92:

	{{Note		{{Note
-	\| Once in Metis Smart Suite, the User can at all time check in which Configuration Package he is working by clicking on the '''About Smart Modeling''' menu in the upper part of the screen in order to open the '''About Metis''' window which will ~~explicitely~~ show which Configuration Package is being used.	+	\| Once in Metis Smart Suite, the User can at all time check in which Configuration Package he is working by clicking on the '''About Smart Modeling''' menu in the upper part of the screen in order to open the '''About Metis''' window which will explicitly show which Configuration Package is being used.


Line 61:		Line 99:
	}}		}}

		+
		+	Editing any of the objects related to the models will result in checking it out from the Package. This will prohibit other users from editing the same rules or mask for example. The User/Administrator can have a overview of the various 'reservations' on the '''Config Manager''' main screen.

	== Editing an existing Configuration Package ==		== Editing an existing Configuration Package ==

PatrickG at 14:11, 13 January 2014

2014-01-13T14:11:37Z

← Older revision		Revision as of 14:11, 13 January 2014
Line 40:		Line 40:

	Once all related mandatory and optional information (Comment) have been set, the new Configuration Package can be saved by validating the '''Config Manager''' window using the [[File:MetisSmartModelingOKButton.PNG\|link=]] button at the bottom of the window.		Once all related mandatory and optional information (Comment) have been set, the new Configuration Package can be saved by validating the '''Config Manager''' window using the [[File:MetisSmartModelingOKButton.PNG\|link=]] button at the bottom of the window.
		+
		+
		+	== Using a Configuration Package ==
		+
		+	Once a configuration package has been created by an Administrator, it is automatically made available to all the user who have access to the functionality. When a user with those privileges logs in Metis Smart Suite a windows is displayed allowing to select between the main database and the different packages.
		+
		+
		+	[[File:MSM_Modeling_Config_Manager_Login.png\|center]]
		+
		+
		+	Once logged in and that a package is selected, all modifications applied to the models information will be done in the selected package. Those changes will have no effect at all all other packages or the main database. The edition of the information is done in same way as when the Configuration Manager is not used, please refer to the corresponding chapter in the documentation.
		+
		+
		+	{{Note
		+	\| Once in Metis Smart Suite, the User can at all time check in which Configuration Package he is working by clicking on the '''About Smart Modeling''' menu in the upper part of the screen in order to open the '''About Metis''' window which will explicitely show which Configuration Package is being used.
		+
		+
		+	[[File:MSM_Modeling_Config_Manager_About.png\|center]]
		+
		+	}}


Line 66:		Line 86:


-	Once the warning is confirmed, the selected Configuration Package is removed from Metis Smart Suite and deleted from the Metis Database.	+	Once the warning is confirmed, the selected Configuration Package is removed from Metis Smart Suite and deleted from the Metis Database

PatrickG at 13:38, 13 January 2014

2014-01-13T13:38:49Z

← Older revision		Revision as of 13:38, 13 January 2014
Line 1:		Line 1:
	Metis Smart Suite includes, as part of Metis Smart Suite, a fully configurable product and services modelizing function. The whole concept behind this is described in details in the corresponding chapter. In large environments where Metis Smart Suite is implemented their may be several persons working on the various models to be used by the application. This could bring up problems if Metis didn't include a fully functional development environment for the various people in charge of the models. Based on '''advanced programming languages development environments''', Metis Smart Suite allows to work in groups on all the modelization aspects of the application.		Metis Smart Suite includes, as part of Metis Smart Suite, a fully configurable product and services modelizing function. The whole concept behind this is described in details in the corresponding chapter. In large environments where Metis Smart Suite is implemented their may be several persons working on the various models to be used by the application. This could bring up problems if Metis didn't include a fully functional development environment for the various people in charge of the models. Based on '''advanced programming languages development environments''', Metis Smart Suite allows to work in groups on all the modelization aspects of the application.

-	In order to work with the functionality, the User/Administrator has to create a Configuration Package which will include all model relevant data to be used by all the user in the group. This will create a set of data which can then selected at log-on and which stays totally separated from the main data set. Thus allows all the users in the group to implement new models or modify rules without affecting the the productive part of the database. Once all modification are done, tested and validated, the updated data set can be transferred back to the main database. Future modifications can then be bone on new Configuration Packages, which could be based on the main data set or or a previous package.

	[[File:DRAW_Config_Manager.png\|center\|600x400px]]		[[File:DRAW_Config_Manager.png\|center\|600x400px]]
		+
		+
		+	In order to work with the functionality, the User/Administrator has to create a Configuration Package which will include all model relevant data to be used by all the user in the group. This will create a set of data which can then selected at log-on and which stays totally separated from the main data set. Thus allows all the users in the group to implement new models or modify rules without affecting the the productive part of the database. Once all modification are done, tested and validated, the updated data set can be transferred back to the main database. Future modifications can then be bone on new Configuration Packages, which could be based on the main data set or or a previous package.
		+
		+
		+	[[File:DRAW_Config_Manager_2.png\|center\|600x400px]]

PatrickG at 13:24, 13 January 2014

2014-01-13T13:24:33Z

← Older revision		Revision as of 13:24, 13 January 2014
Line 1:		Line 1:
-	Metis Smart Suite includes, as part of Metis Smart Suite, a fully configurable product and services modelizing function. The whole concept behind this is described in details in the corresponding chapter. In large environments where Metis Smart Suite is implemented their may be several persons working on the various models to be used by the application. This could bring up problems if Metis didn't include a fully functional development environment for the various people in charge of the models. Based on advanced programming languages development environments, Metis Smart Suite allows to work in groups on all the modelization aspects of the application.	+	Metis Smart Suite includes, as part of Metis Smart Suite, a fully configurable product and services modelizing function. The whole concept behind this is described in details in the corresponding chapter. In large environments where Metis Smart Suite is implemented their may be several persons working on the various models to be used by the application. This could bring up problems if Metis didn't include a fully functional development environment for the various people in charge of the models. Based on '''advanced programming languages development environments''', Metis Smart Suite allows to work in groups on all the modelization aspects of the application.

	In order to work with the functionality, the User/Administrator has to create a Configuration Package which will include all model relevant data to be used by all the user in the group. This will create a set of data which can then selected at log-on and which stays totally separated from the main data set. Thus allows all the users in the group to implement new models or modify rules without affecting the the productive part of the database. Once all modification are done, tested and validated, the updated data set can be transferred back to the main database. Future modifications can then be bone on new Configuration Packages, which could be based on the main data set or or a previous package.		In order to work with the functionality, the User/Administrator has to create a Configuration Package which will include all model relevant data to be used by all the user in the group. This will create a set of data which can then selected at log-on and which stays totally separated from the main data set. Thus allows all the users in the group to implement new models or modify rules without affecting the the productive part of the database. Once all modification are done, tested and validated, the updated data set can be transferred back to the main database. Future modifications can then be bone on new Configuration Packages, which could be based on the main data set or or a previous package.
Line 6:		Line 6:


-	Using the same central database, each user included in the group of developers can log in and access a different Configuration Package and apply all the changes needed. It can be seen as different branches in a development environment. Each object ([[Metis_Smart_Modeling_-_Models\|Models]], [[Metis_Smart_Modeling_-_Group_of_Rules\|Groups of Rules]], [[Metis_Smart_Modeling_-_Rules\|Rules]], [[Metis_Smart_Modeling_-_Variables\|Variables]] or [[Metis_Smart_Modeling_-_Masks\|Masks]]) is "checked-out" when edited by a User in order for no one else to interact with the same object. It is reserved for him exclusively. Only when he manually "checks it out" will that object be again available for edition by other users.	+	Using the same '''central database''', each user included in the group of developers can log in and access a different Configuration Package and apply all the changes needed. It can be seen as different branches in a development environment. Each object ([[Metis_Smart_Modeling_-_Models\|Models]], [[Metis_Smart_Modeling_-_Group_of_Rules\|Groups of Rules]], [[Metis_Smart_Modeling_-_Rules\|Rules]], [[Metis_Smart_Modeling_-_Variables\|Variables]] or [[Metis_Smart_Modeling_-_Masks\|Masks]]) is "checked-out" when edited (reserved) by a User in order for no one else to interact with the same object. It is reserved for him exclusively. Only when he manually "checks it out" will that object be again available for edition by other users.

	The Configuration Manager allows also to enforce versionning on all the model data to be made available in Metis Smart Suite. By creating ordered Packages, the User/Administrator can define multiple packages for all future versions of the models. The tool then allows to transfer updated part of a package to any of those packages in order to keep them all up to date and to have consistent data.		The Configuration Manager allows also to enforce versionning on all the model data to be made available in Metis Smart Suite. By creating ordered Packages, the User/Administrator can define multiple packages for all future versions of the models. The tool then allows to transfer updated part of a package to any of those packages in order to keep them all up to date and to have consistent data.

PatrickG at 13:22, 13 January 2014

2014-01-13T13:22:54Z

← Older revision		Revision as of 13:22, 13 January 2014
Line 7:		Line 7:

	Using the same central database, each user included in the group of developers can log in and access a different Configuration Package and apply all the changes needed. It can be seen as different branches in a development environment. Each object ([[Metis_Smart_Modeling_-_Models\|Models]], [[Metis_Smart_Modeling_-_Group_of_Rules\|Groups of Rules]], [[Metis_Smart_Modeling_-_Rules\|Rules]], [[Metis_Smart_Modeling_-_Variables\|Variables]] or [[Metis_Smart_Modeling_-_Masks\|Masks]]) is "checked-out" when edited by a User in order for no one else to interact with the same object. It is reserved for him exclusively. Only when he manually "checks it out" will that object be again available for edition by other users.		Using the same central database, each user included in the group of developers can log in and access a different Configuration Package and apply all the changes needed. It can be seen as different branches in a development environment. Each object ([[Metis_Smart_Modeling_-_Models\|Models]], [[Metis_Smart_Modeling_-_Group_of_Rules\|Groups of Rules]], [[Metis_Smart_Modeling_-_Rules\|Rules]], [[Metis_Smart_Modeling_-_Variables\|Variables]] or [[Metis_Smart_Modeling_-_Masks\|Masks]]) is "checked-out" when edited by a User in order for no one else to interact with the same object. It is reserved for him exclusively. Only when he manually "checks it out" will that object be again available for edition by other users.
		+
		+	The Configuration Manager allows also to enforce versionning on all the model data to be made available in Metis Smart Suite. By creating ordered Packages, the User/Administrator can define multiple packages for all future versions of the models. The tool then allows to transfer updated part of a package to any of those packages in order to keep them all up to date and to have consistent data.

PatrickG at 13:08, 13 January 2014

2014-01-13T13:08:56Z

← Older revision		Revision as of 13:08, 13 January 2014
Line 6:		Line 6:


-	Using the same central database, each user included in the group of developers can log in and access a different Configuration Package and apply all the changes needed. It can be seen as different branches in a development environment. Each object ([[Metis_Smart_Modeling_-_Models\|Models]], [[Metis_Smart_Modeling_-_Group_of_Rules\|Groups of Rules]], [[Metis_Smart_Modeling_-_Rules\|Rules]], Metis_Smart_Modeling_-_Variables or [[Metis_Smart_Modeling_-_Masks\|Masks]]) is "checked-out" when edited by a User in order for no one else to interact with the same object. It is reserved for him exclusively. Only when he manually "checks it out" will that object be again available for edition by other users.	+	Using the same central database, each user included in the group of developers can log in and access a different Configuration Package and apply all the changes needed. It can be seen as different branches in a development environment. Each object ([[Metis_Smart_Modeling_-_Models\|Models]], [[Metis_Smart_Modeling_-_Group_of_Rules\|Groups of Rules]], [[Metis_Smart_Modeling_-_Rules\|Rules]], [[Metis_Smart_Modeling_-_Variables\|Variables]] or [[Metis_Smart_Modeling_-_Masks\|Masks]]) is "checked-out" when edited by a User in order for no one else to interact with the same object. It is reserved for him exclusively. Only when he manually "checks it out" will that object be again available for edition by other users.

PatrickG at 13:08, 13 January 2014

2014-01-13T13:08:23Z

← Older revision		Revision as of 13:08, 13 January 2014
Line 1:		Line 1:
	Metis Smart Suite includes, as part of Metis Smart Suite, a fully configurable product and services modelizing function. The whole concept behind this is described in details in the corresponding chapter. In large environments where Metis Smart Suite is implemented their may be several persons working on the various models to be used by the application. This could bring up problems if Metis didn't include a fully functional development environment for the various people in charge of the models. Based on advanced programming languages development environments, Metis Smart Suite allows to work in groups on all the modelization aspects of the application.		Metis Smart Suite includes, as part of Metis Smart Suite, a fully configurable product and services modelizing function. The whole concept behind this is described in details in the corresponding chapter. In large environments where Metis Smart Suite is implemented their may be several persons working on the various models to be used by the application. This could bring up problems if Metis didn't include a fully functional development environment for the various people in charge of the models. Based on advanced programming languages development environments, Metis Smart Suite allows to work in groups on all the modelization aspects of the application.

-	In order to work with the ~~functionnality~~, the User/Administrator has to create a Configuration Package which will include all model ~~relvant~~ data to be used by all the user in the group. This will create a set of data which can then selected at ~~logon~~ and which stays totally separated from the main data set. Thus allows all the users in the group to implement new models or modify rules without affecting the the productive part of the database. Once all modification are done, tested and validated, the updated data set can be ~~transfered~~ back to the main database. Future modifications can then be bone on new Configuration Packages, which could be based on the main data set or or a previous package.	+	In order to work with the functionality, the User/Administrator has to create a Configuration Package which will include all model relevant data to be used by all the user in the group. This will create a set of data which can then selected at log-on and which stays totally separated from the main data set. Thus allows all the users in the group to implement new models or modify rules without affecting the the productive part of the database. Once all modification are done, tested and validated, the updated data set can be transferred back to the main database. Future modifications can then be bone on new Configuration Packages, which could be based on the main data set or or a previous package.

	[[File:DRAW_Config_Manager.png\|center\|600x400px]]		[[File:DRAW_Config_Manager.png\|center\|600x400px]]
		+
		+
		+	Using the same central database, each user included in the group of developers can log in and access a different Configuration Package and apply all the changes needed. It can be seen as different branches in a development environment. Each object ([[Metis_Smart_Modeling_-_Models\|Models]], [[Metis_Smart_Modeling_-_Group_of_Rules\|Groups of Rules]], [[Metis_Smart_Modeling_-_Rules\|Rules]], Metis_Smart_Modeling_-_Variables or [[Metis_Smart_Modeling_-_Masks\|Masks]]) is "checked-out" when edited by a User in order for no one else to interact with the same object. It is reserved for him exclusively. Only when he manually "checks it out" will that object be again available for edition by other users.

PatrickG at 12:22, 13 January 2014

2014-01-13T12:22:47Z

← Older revision		Revision as of 12:22, 13 January 2014
Line 1:		Line 1:
		+	Metis Smart Suite includes, as part of Metis Smart Suite, a fully configurable product and services modelizing function. The whole concept behind this is described in details in the corresponding chapter. In large environments where Metis Smart Suite is implemented their may be several persons working on the various models to be used by the application. This could bring up problems if Metis didn't include a fully functional development environment for the various people in charge of the models. Based on advanced programming languages development environments, Metis Smart Suite allows to work in groups on all the modelization aspects of the application.

-		+	In order to work with the functionnality, the User/Administrator has to create a Configuration Package which will include all model relvant data to be used by all the user in the group. This will create a set of data which can then selected at logon and which stays totally separated from the main data set. Thus allows all the users in the group to implement new models or modify rules without affecting the the productive part of the database. Once all modification are done, tested and validated, the updated data set can be transfered back to the main database. Future modifications can then be bone on new Configuration Packages, which could be based on the main data set or or a previous package.

	[[File:DRAW_Config_Manager.png\|center\|600x400px]]		[[File:DRAW_Config_Manager.png\|center\|600x400px]]

PatrickG at 12:00, 13 January 2014

2014-01-13T12:00:39Z

← Older revision		Revision as of 12:00, 13 January 2014
Line 1:		Line 1:
		+
		+
		+
		+	[[File:DRAW_Config_Manager.png\|center\|600x400px]]
		+
		+
	The list shown in the main window displays all the Configuration packages defined in Metis Smart Suite. It can be sorted alphabetically or by creation date using the small arrows in the table headers.		The list shown in the main window displays all the Configuration packages defined in Metis Smart Suite. It can be sorted alphabetically or by creation date using the small arrows in the table headers.


-	[[File:~~DRAW_Config_Manager~~.png\|center]]	+	[[File:MSM_Modeling_Config_Manager.png\|center\|600x400px]]