Release 10.5.0.5
This release upgrades the Apama-ctrl microservice to use Apama 10.5.0 Fix 12 (which is the same as Apama 10.5.3.3).
Fixes
| Component | Description | Issue |
|---|---|---|
| Apama-ctrl microservice | onGeofenceCreateAlarm and onGeofenceSendEmail smart rules behaved incorrectly when updates were received without location information. This problem has now been resolved. |
PAB-1699 |
Release 10.5.0.4
This release upgrades the Apama-ctrl microservice to use Apama 10.5.0 Fix 8 (which is the same as Apama 10.5.2.1).
Release 10.5.0.3
Fixes
| Component | Description | Issue |
|---|---|---|
| Apama-ctrl microservice | Apama applications would not function correctly when the logged-in user is logged in via OAuth. This would most commonly occur with users logging in via Software AG Cloud. This problem has now been resolved. | PAB-933 |
| Apama Analytics Builder | A simpler mechanism is now used to stop simulation playback. This should prevent intermittent problems when starting models in simulation mode shortly after stopping a simulation. | PAB-953 |
Release 10.5.0.2
Fixes
| Component | Description | Issue |
|---|---|---|
| Apama Analytics Builder | A race condition was fixed which could lead to exceeding the configurable limit on the number of active simulation models. | PAB-865 |
| Apama Analytics Builder | The maxSimulationSecsDelay property is now excluded from the check on whether a model has been modified while it is active, as it is valid to change this even when a model is active. |
PAB-878 |
| Apama Analytics Builder | The managed object name is now correctly escaped in the Analytics Builder palette, which prevents potential cross-site scripting attacks. | PAB-879 |
| Apama Analytics Builder | The documentation of the Alarm Input block has been updated. It now recommends to set the Ignore Timestamp parameter if the Acknowledged or Cleared alarm status is used (as the alarm's creation time is used as the source timestamp). | PAB-902 |
| Apama Analytics Builder | If the Apama-ctrl microservice was configured to use an alternative source for simulation data, the username and password settings were incorrectly applied to look for extensions in the Cumulocity IoT inventory as well. This has been corrected to always use the platform credentials. | PAB-932 |