{{indexmenu_n>1}} ====== Notifications ====== \\ With notifications the end user can get information in a visual and interactive way of what is happening below the application. So that, when it gets important data operations in the application do not leave messages or take the application to important places. \\ \\ The types of notifications are two: \\ - Integrated with the Appwizard menu. - By free and autonomous control, where the developer has the total control.\\ \\ ===== Special Replica Event REPLICA OK ===== \\ We can capture the event when an operation enters by replica in a certain table of the database, in a specific node that is defined within the enterprises collection. \\ \\ ... ... ===== Integrated with the Appwizard Menu===== \\ These notifications are linked to the collection that are called from the Appwizard menu through a series of attributes. \\ \\ For this case, a //coll// like this one will be created: The related attributes are: === Notify === \\ Attribute with which we indicate the framework that is a notifications collection and has to be checked every time it replicates in order to see if it meets the SQL of such collection and notify the user about such event. \\ \\ === Notify_counter === \\ It makes a counting about the elements of that collection. If this attribute is not specified, instead counting the elements of that collection, it is necessary to check if there are elements. === Notify_coll === \\ It is the name of the secondary collection that will be used for edition. If this attribute is not specified, the collection which defines these attributes will be edited. Usually, when we want to count the elements of a collection (in order to see the notices) it is notably faster counting a collection with a very simple SQL like the one of the example and at the time to edit, we call to the collection which will have the complex **SQL**. This collection must be called from the Appwizard. === Notify_title === \\ If this attributte is specified, it will be the text which appears identifying the notice, otherwise it will be the **caption** attribute used to notify at the appwizard. \\ ===== By free and autonomous control where the programmer has the full control ===== \\ For this type of notifications we use the **maintenance node**, with which maintenances in background will be launched and we will be able to use to show the messages we need.\\ \\ With this type of notifications, the programmer has the full control. They are useful to be used when an application without appwizard has be created and the entry is made through **“entry-point”**.\\