CMS fat client - Cronologia

Renato.daverio: /* Personal Filter */

2015-11-30T11:35:16Z

‎Personal Filter

Renato.daverio: /* Quick Filter */

2015-11-30T11:34:55Z

‎Quick Filter

Renato.daverio: /* Tracking Console View */

2015-11-30T11:34:39Z

‎Tracking Console View

Renato.daverio: /* Configuration */

2015-11-30T11:34:07Z

‎Configuration

Renato.daverio: /* Impact Console View */

2015-11-30T11:33:01Z

‎Impact Console View

Renato.daverio: /* Message Rules */

2015-11-30T11:32:13Z

‎Message Rules

Renato.daverio: /* Impact Console Settings */

2015-11-30T11:31:13Z

‎Impact Console Settings

Renato.daverio: /* Relationship rules */

2015-11-30T11:24:06Z

‎Relationship rules

Renato.daverio: /* Objects rules */

2015-11-30T11:23:30Z

‎Objects rules

Renato.daverio: /* Reporting Engine */

2015-11-30T11:22:43Z

‎Reporting Engine

@@ Riga 1 761: / Riga 1 761: @@
 Here user may do the following:
-•	Configure filtering criteria
+* Configure filtering criteria
-•	Save configured filter as new
+* Save configured filter as new
-•	Update existing personal filter
+* Update existing personal filter
-•	Reset screen by pressing “Reset” button
+* Reset screen by pressing “Reset” button
-•	Apply filter by pressing “Ok”
+* Apply filter by pressing “Ok”
 Personal filters are persisted on server and available per user. User may apply configured personal filters directly on tracking console view by selecting it in “Filter” drop-down:

@@ Riga 1 752: / Riga 1 752: @@
 ==== Quick Filter ====
 By pressing “Toggle QuickFilter” button, user will see filtering options above list header and two new buttons:
-•	Apply QF – to apply quick filter
+* Apply QF – to apply quick filter
-•	Drop QF – to drop quick filter
+* Drop QF – to drop quick filter
 If user presses “Toggle QuickFilter” again, filtering options and new buttons will be hidden.

@@ Riga 1 743: / Riga 1 743: @@
 It draws tracking records generated according to configured active tracking rules. Here user may:
-•	Delete one or many selected records by pressing “Delete” button
+* Delete one or many selected records by pressing “Delete” button
-•	Delete all records by pressing “Delete All” button
+* Delete all records by pressing “Delete All” button
-•	Filter records using “Quick Filter”
+* Filter records using “Quick Filter”
-•	Filter records using “Personal Filter”
+* Filter records using “Personal Filter”
-•	Click “Entity ID” column on any record to open corresponding entity’s content window
+* Click “Entity ID” column on any record to open corresponding entity’s content window
-•	Double-click record to see changed fields (if configured in tracking rule)
+* Double-click record to see changed fields (if configured in tracking rule)
-−
 ==== Quick Filter ====
 By pressing “Toggle QuickFilter” button, user will see filtering options above list header and two new buttons:

@@ Riga 1 689: / Riga 1 689: @@
 === Configuration ===
 Before using tracking functionality, user shall configure tracking rules. Tracking rules allow defining what shall be audited and can be configured for the following entities:
-•	Objects
+* Objects
-•	Models
+* Models
-•	Folders
+* Folders
-•	Object Occurrences
+* Object Occurrences
-•	Relationships
+* Relationships
-•	Relationship Occurrences
+* Relationship Occurrences
 Corresponding menu items allow opening the list of tracking rules: Settings > Tracking > [entity name].
@@ Riga 1 714: / Riga 1 714: @@
 The following entities have content windows:
-•	Object
+* Object
-•	Model
+* Model
-•	Folder
+* Folder
 Tracking records of the other entities:
-•	Object Occurrence
+* Object Occurrence
-•	Relationship
+* Relationship
-•	Relationship Occurrence
+* Relationship Occurrence
 Are available via popup menu “Tracking”, which is accessible from the model, object or folder content windows (corresponding tab):
@@ Riga 1 727: / Riga 1 727: @@
 ==== Event Types ====
 The following table depicts the event types available for tracking functionality, as well it shows for which entities event types are available and possibility to track changed fields per event type:
-Event Type	Object	Model	Folder	Object Occurrence	Relationship	Relationship Occurrence	Supports Field Values Tracking	Description
-Created	yes	yes	yes	yes	yes	yes	no	Recorded when entity created
+[picture]
 === Tracking Console ===

@@ Riga 1 674: / Riga 1 674: @@
 It draws messages generated according to configured active message rules. Here user may:
-•	Change Impact Console refresh rate
+* Change Impact Console refresh rate
-•	Update settings by pressing “Paging” button
+* Update settings by pressing “Paging” button
-•	Freeze/Unfreeze console
+* Freeze/Unfreeze console
-•	Right-click any message to perform the following activities:
+* Right-click any message to perform the following activities:
-o	Localize object
+  * Localize object
-o	View object attributes
+  * View object attributes
-o	View history
+  * View history
-o	Make exploration model
+  * Make exploration model
-o	View message rule, the message is based on
+  * View message rule, the message is based on
 = Tracking =

@@ Riga 1 650: / Riga 1 650: @@
 For message rule user may define:
-•	Name of message rule
+* Name of message rule
-•	Font format, which will be used when drawing message in console
+* Font format, which will be used when drawing message in console
-•	Message template, it is possible to insert object attributes in form ##AttributeName## inside message template, later it will be replaced with value of corresponding attribute; button “Accept” allows to validate message template
+* Message template, it is possible to insert object attributes in form ##AttributeName## inside message template, later it will be replaced with value of corresponding attribute; button “Accept” allows to validate message template
-•	Status, active/inactive; if message rule inactive, no message will be generated for this rule
+* Status, active/inactive; if message rule inactive, no message will be generated for this rule
-•	Trigger, this is a condition, which will be validated before generation of the message. If it is true, message will be generated:
+* Trigger, this is a condition, which will be validated before generation of the message. If it is true, message will be generated:
 Message rules may be defined at different levels:
-•	Attribute Template Management, user shall open wizard with menu item Tools > Attributes Management > Attribute Template Management and open Model/Object tab:
+* Attribute Template Management, user shall open wizard with menu item Tools > Attributes Management > Attribute Template Management and open Model/Object tab:
 When object type and attribute selected, tab Messages is available on right pane. Here user may create/update/remove message rules. If defined, messages will be generated each time the object or attribute changed for the objects of selected object type and belonging to the selected model type.
-•	Model, user shall right-click on empty space of model design window and select Object Messages menu item to access message rules management functionality:
+* Model, user shall right-click on empty space of model design window and select Object Messages menu item to access message rules management functionality:
 If defined, messages will be generated only for the objects belonging to the selected model.
-•	Object, user shall right-click on object and select Object Messages menu item to access message rules management functionality:
+* Object, user shall right-click on object and select Object Messages menu item to access message rules management functionality:
 If defined, messages will be generated only for the selected object.
 In last two cases, Model and Object levels, message rules may be managed for available objects’ attributes:
-−
 ==== Impact Console View ====
 Impact Console is available through menu item View > Impact Console:

@@ Riga 1 640: / Riga 1 640: @@
 Here user may define:
-•	Background color for the Impact Console
+* Background color for the Impact Console
-•	Paging settings in the form N1, N2, .., Nm, All , where N1 < N2 < … < Nm and All is the last item, not mandatory
+* Paging settings in the form N1, N2, .., Nm, All , where N1 < N2 < … < Nm and All is the last item, not mandatory
-•	The maximum number of messages available to view
+* The maximum number of messages available to view
-•	Sound alert, this shall be “wav” file, the sound will be played as soon as new messages appear in Impact Console
+* Sound alert, this shall be “wav” file, the sound will be played as soon as new messages appear in Impact Console
 As well, user may activate Impact Console. If activated, system will start generating messages according to configured message rules.

@@ Riga 1 615: / Riga 1 615: @@
 ==== Relationship rules ====
-•	It is not allowed to make a loop between objects with “impacts” relationship, otherwise it will not allow to calculate objects’ statuses.
+* It is not allowed to make a loop between objects with “impacts” relationship, otherwise it will not allow to calculate objects’ statuses.
-•	Relationships can be clustered or non-clustered. Clustered relationships have “Is Cluster” equal to true and “Cluster Name” set to the cluster the relationship belongs to. When defining “Cluster Name” user may select one of existing value or type new one and press Enter, in this case new cluster will be created.
+* Relationships can be clustered or non-clustered. Clustered relationships have “Is Cluster” equal to true and “Cluster Name” set to the cluster the relationship belongs to. When defining “Cluster Name” user may select one of existing value or type new one and press Enter, in this case new cluster will be created.
-•	Non-clustered relationships have “Performance Impact” always equal to 100%.
+* Non-clustered relationships have “Performance Impact” always equal to 100%.
-•	Clustered relationships, included in the same cluster, shall have summary “Performance Impact” not greater than 100%.
+* Clustered relationships, included in the same cluster, shall have summary “Performance Impact” not greater than 100%.
-•	Clustered relationships, included in the same cluster, shall have the same target object.
+* Clustered relationships, included in the same cluster, shall have the same target object.
 Impact Chain Actions and Tasks
 The list of actions is available through menu item Tools > Actions:
@@ Riga 1 626: / Riga 1 626: @@
 And this action shall include at least one task of type “Impact Chain Calculation”:
-−
 === Impact Console ===
 Impact Console is a window containing messages generated when Objects or Attributes are edited. Before using Impact Console it shall be configured and turned on. Only users having appropriate rights can configure and/or view Impact Console, these rights can be granted with user management functionalities:

@@ Riga 1 608: / Riga 1 608: @@
 ==== Objects rules ====
-•	Result Status of object is “UP” in case both, Defined Status and Depending Status are “UP”; otherwise it is “DOWN”. As soon as Result Status of any object changes its value, the event “Object Result Status Updated” is raised, which can execute corresponding action if configured.
+* Result Status of object is “UP” in case both, Defined Status and Depending Status are “UP”; otherwise it is “DOWN”. As soon as Result Status of any object changes its value, the event “Object Result Status Updated” is raised, which can execute corresponding action if configured.
-•	Depending Status is calculated based on “impacts” relationships. Depending Status is always “UP” in case there are no incoming relationships for the object. Depending Status is “DOWN” in case incoming relationships have source objects with Result Status “DOWN” and these relationships are not clustered. Depending Status is “UP” in case all incoming relationships have source objects with Result Status “UP” and these relationships are not clustered. Depending Status is “UP” in case at least one incoming relationship have source object with Result Status “UP” and this relationship is clustered and has Performance Impact greater then 0%.
-•	Defined Status is set be the user, when changed, Depending Status and Result Status of object are calculated and updated.
+* Depending Status is calculated based on “impacts” relationships. Depending Status is always “UP” in case there are no incoming relationships for the object. Depending Status is “DOWN” in case incoming relationships have source objects with Result Status “DOWN” and these relationships are not clustered. Depending Status is “UP” in case all incoming relationships have source objects with Result Status “UP” and these relationships are not clustered. Depending Status is “UP” in case at least one incoming relationship have source object with Result Status “UP” and this relationship is clustered and has Performance Impact greater then 0%.
 ==== Relationship rules ====

@@ Riga 1 293: / Riga 1 293: @@
 It is a set of views, which allow defining data to be reported within specific context and building different filtering conditions. Additionally, Reporting Engine allows managing templates (predefined report settings, which can be saved and loaded), it is available from menu item: Tools > Reports > Reporting Engine > Report Template Management, see Templates.
 Available Reporting Engine views are:
-•	Symbol Entity View
+* Symbol Entity View
-•	Occurrence Entity View
+* Occurrence Entity View
-•	Relationship Entity View
+* Relationship Entity View
-•	RelOccurrence Entity View
+* RelOccurrence Entity View
-•	Folder Entity View
+* Folder Entity View
-•	Model Entity View
+* Model Entity View
 All views have similar functionalities; the only difference between them is data which can be filtered in reported. View looks like shown on the screen below:
 === Common functionalities ===
 Every view has a set of functionalities:
-•	Export to Excel
+* Export to Excel
-•	Export to XML
+* Export to XML
-•	Columns
+* Columns
-•	Sort order
+* Sort order
-•	Filter
+* Filter
-•	Add attribute
+* Add attribute
-•	Load
+* Load
-•	Save
+* Save
-•	Templates
+* Templates
-•	Reporting View
+* Reporting View
 ==== Export to Excel ====
@@ Riga 1 377: / Riga 1 377: @@
 ==== Reporting View ====
 Reporting view has some advanced functionalities:
-•	Grouping/Ungrouping
+* Grouping/Ungrouping
-•	Editing
+* Editing
-•	Sorting
+* Sorting
 Note. These functionalities don’t affect excel and xml files, which user gets when exporting data.
@@ Riga 1 385: / Riga 1 385: @@
 In our example we selected Symbol Entity Report and specified the following columns to be included in report:
-•	Symbol (Identifier, Name, Type)
+* Symbol (Identifier, Name, Type)
-•	Symbol Folder (Identifier, Name)
+* Symbol Folder (Identifier, Name)
-•	Model (Identifier, Name, Type)
+* Model (Identifier, Name, Type)
 Every symbol (i.e. object) is independent from the model and linked to the model only if occurs in it (has an occurrence), but every symbol has parent folder (when symbol is created it is linked to folder automatically). So resulting report looks like the following:
@@ Riga 1 405: / Riga 1 405: @@
 === Symbol Entity View ===
 The list of sections (tabs) which can be used in this view for selecting Columns and defining Filter:
-•	Symbol
+* Symbol
-•	Symbol Folder
+* Symbol Folder
-•	Variant
+* Variant
-•	Variant Folder
+* Variant Folder
-•	Related Symbol
+* Related Symbol
-•	Related Symbol Folder
+* Related Symbol Folder
-•	Related Symbol Relationship
+* Related Symbol Relationship
-•	Model
+* Model
-•	Model Folder
+* Model Folder
 === Occurrence Entity View ===
 The list of sections (tabs) which can be used in this view for selecting Columns and defining Filter:
-•	Occurrence
+* Occurrence
-•	Symbol
+* Symbol
-•	Symbol Folder
+* Symbol Folder
-•	Model
+* Model
-•	Model Folder
+* Model Folder
-•	Related Occurrence
+* Related Occurrence
-•	Related Occurrence Symbol
+* Related Occurrence Symbol
-•	Related Occurrence Symbol Folder
+* Related Occurrence Symbol Folder
-•	RelOccurrence
+* RelOccurrence
-•	RelOccurrence Relationship
+* RelOccurrence Relationship
 === Relationship Entity View ===
 The list of sections (tabs) which can be used in this view for selecting Columns and defining Filter:
-•	Relationship
+* Relationship
-•	Source Symbol
+* Source Symbol
-•	Source Symbol Folder
+* Source Symbol Folder
-•	Destination Symbol
+* Destination Symbol
-•	Destination Symbol Folder
+* Destination Symbol Folder
-•	Model
+* Model
-•	Model Folder
+* Model Folder
 === RelOccurrence Entity View ===
 The list of sections (tabs) which can be used in this view for selecting Columns and defining Filter:
-•	RelOccurrence
+* RelOccurrence
-•	Relationship
+* Relationship
-•	Source Occurrence
+* Source Occurrence
-•	Source Occurrence Symbol
+* Source Occurrence Symbol
-•	Source Occurrence Symbol Folder
+* Source Occurrence Symbol Folder
-•	Destination Occurrence
+* Destination Occurrence
-•	Destination Occurrence Symbol
+* Destination Occurrence Symbol
-•	Destination Occurrence Symbol Folder
+* Destination Occurrence Symbol Folder
-•	Model
+* Model
-•	Model Folder
+* Model Folder
 === Folder Entity View ===
 The list of sections (tabs) which can be used in this view for selecting Columns and defining Filter:
-•	Folder
+* Folder
-•	Parent Folder
+* Parent Folder
 === Model Entity View ===
 The list of sections (tabs) which can be used in this view for selecting Columns and defining Filter:
-•	Model
+* Model
-•	Model Folder
+* Model Folder
-•	Variant
+* Variant
-•	Variant Folder
+* Variant Folder
 = Import From Excel =