Jump to: navigation, search

New in This Release

This page provides information about new features and enhancements of Genesys Pulse.

Changes Introduced in Release 9.0

Release 9.0.000

  • Genesys Pulse can be started only in a standalone mode with its own Application configuration object. Genesys Pulse version 9.0.0 can not be used as a plugin of GAX.
  • Ability to fetch historical data series in Genesys Pulse User Interface Extension. Refer to Genesys Pulse User Interface Extension for more information.
  • Limits for both personal Widgets and Dashboards (including wallboards). This functionality is supported by new configuration options on the Annex tab of the Access Groups:
    • max_tabs_per_user
    • max_widgets_per_user
  • Ability to specify thresholds for alerts in decimal numbers.
  • If the user has no access to the selected objects in the view or headline of the widget, instead of showing "Object Unavailable", Genesys Pulse displays other objects from the selected objects in the widget.
  • Advanced Alert capabilities. To enable this feature you need to properly deploy and run services and set the value of the Genesys Pulse option [pulse]/enable_advanced_alerts to true. After enabling this feature the Advanced Alerts section is displayed on the new Alerts tab, using which users can specify conditions for an alert and the email address for sending this alert.
    This feature has the following limitations:
    • Alert conditions use the new formula definition format. In this format, values of statistics and formulas are accessed by their alias and not through the global Data object.
      For example:
      Result = Login_Time <= 200;
      instead of the old format
      Result = Data.Login_Time.Value
    • Alert conditions can only use statistics of primitive data types and other alert conditions; it is not possible at the moment to create Alert conditions that depend on:
      • Statistics of the complex data type, like current state
      • Changes-Based and No Notification statistics
      • Regular formulas
      • Object properties
    • At the moment alert conditions cannot use special built-in functions (like GetFirstUDValue()) and functions provided by the gts.js script that available to regular formulas.
    • It is only possible to configure new standalone services using configuration files.
    • There is no HA and horizontal scaling in new services used for this feature.
    • As long as the alert condition is stored as javascript code and parsed in order to get condition builder, the original condition's syntax cannot be preserved; therefore, the condition's code can be reformatted/simplified when the builder mode is on.
    • New standalone services are AlertProcessor, Formula Processor, and StatServer Data Provider.
  • Display format Status. This new display format is applicable only for statistics using Statistical Type ExtendedCurrentStatus. It allows to specify values displayed for the status (icon, name, media, duration) and to select current status statistics on any chart.
  • An option for statistics with display format Status to show "Do Not Disturb" status with its duration.
  • New logic to update and format heartbeat files. The heartbeat file is always updated, thus the Genesys Pulse Collector configuration option heartbeat/heartbeat-success-condition is discontinued. The content of a heartbeat file is in JSON format. The heartbeat file includes the following information:
    • Current timestamp.
    • Startup timestamp.
    • Current uptime.
    • State of connection to Configuration Server.
    • State of connections to Stat Servers.
    • State of connections to DB Servers.
    • Snapshot writing status.
    Example:
{
	"currentTimestamp": 1521835976,
	"startupTimestamp": 1521835950,
	"uptime": 26,
	"connectionStatus": {
		"configServer": {
			"connected": true,
			"instance": "primary",
			"lastConnectionTimestamp": 1521835952
		},
		"statServer0": {
			"connected": true,
			"lastConnectionTimestamp": 1521835956
		},
		"statServer1": {
			"connected": true,
			"lastConnectionTimestamp": 1521835956
		},
		"dbServerConnection": "all"
	},
	"snapshotWritingStatus": true
}
  • New command line option -startup_heartbeat_file specifying which heartbeat file to use before Genesys Pulse Collector can read regular heartbeat configuration options from its Application. This option has only one parameter providing a path to the heartbeat file.
  • An automatic reopening of statistics that failed to open due to recoverable Stat Server error. Stat Server release 8.5.108.15 or later is required.
    New Genesys Pulse Collector configuration option in the [statistic-request-handling] section controls timeout for reopening statistics in such cases:
    • open-stat-retry-timeout
      Valid Values: 1-3600
      Default Value: 30
      Change takes effect: After Restart
       Specifies the timeout in seconds, that Genesys Pulse Collector waits before attempting to re-open a failed statistic if Stat Server indicates that the error is recoverable.

Feedback

Comment on this article:

blog comments powered by Disqus
This page was last modified on June 25, 2018, at 13:23.