| SAP ECC Addon | Coments: IMPORTANT TO READ | Component |
|---|---|---|---|
1 | New functionality to activate and disable alams instances at the object level ( seat, file, record, batch, etc). | Due to this new functinality, if this version is installed in a product where where it previously existed with a previous version (1.0 or 1.1) the following report must be executed to activate all instances of objects in this product: /EDGE/RP_AL_ACTIVA_INSTANCES. If this action is not performed, once version 2.0 is imported the product alarms will be with the instance off. | New functionality |
2 | Column width adjustment on the alarm monitor. |
| Correction |
3 | Translation of the product into English |
| New functionality |
4 | When creating alarms for other products in the alarm folder, they take into account the IDs of the already parameterized products. It should consider only those of its own product. |
| Correction |
5 | When an alarm is first created on a product, the alarm ID was born with 2 instead of 1. |
| Correction |
6 | If on the monitor there was a result of alarms that were erased (because seats were erased) when you hit the update button it kept the result of the alarms erased. |
| Correction |
7 | When an alarm was deleted from the parameterization, it did not properly clear instances of alarms and notifications. | Instances of alarms and notifications could still be viewed in the database table and on the monitor after clearing an alarm. With this correction the alarm instances of objects (seats, edocuments, etc.) are erased with the deletion of the alarm line in the parameterization table, In addition, a pop-up is added so that the user can confirm that he wants to delete them since that means deleting all instances of alarms and notifications that exist. | Correction |
8 | Using SAP calendars for expiration alarms. | A new "Factory calendar" field is added in the initial conditions of the expiry alarms (only this field is visible for this type of alarm). | New functionality |
9 | The ALV catalog of the b+ Alarms monitor can be modified from the product object class. | Method MODIFY_CAT. | New functionality |
10 | When an alarm was sent and escalated, the first time it was sent to the scaled recipients, but the next shipments were back to "normal" users. |
| Correction |
11 | Once the alarm was created, the "Scaled List" field could not be changed. |
| Correction |
12 | Adjust in the fields of the alarm monitor selection screen. Both descriptions and search aids. | The fields in the selection screen can be modified from the class of the product object. MODIFY_FIELD_SCREEN method. For search aids the MODIFY_SEARCH_HELPS method is created in this same class. In this method you can assign a structure and a field, which will take the search help and will be the one you use for that field on the b+ Alarms monitor. | Correction |
13 | The attachment excel could not be extended to seats with fields from table 901 in client with includes Z. |
| Correction |
14 | Validation so that the recipients list does not allow to associate nonexistent role in the alarm settings. |
| Correction |
15 | Error in notifications for alarms without scaling list or with value 0. | When there is no parameterized scaling list in an alarm, it escalated to the second notification, because it considered that the number of notifications was 0 and after a notification considered that it had to scale. When scaling, try to do so to a list that did not exist (empty) and there was an error in sending notifications. | Correction |
16 | A dump was generated when launching the report creating alarms and notifications with a list of recipients without assigned users. | The error is controlled so that a dump does not occur and leaves a message in the log. | Correction |
General
Contenido
Integraciones