Impact

This function can be used to determine the impact of a message.

Functionality

This function requires a communication with a central web service, which is provided by IBITECH. All IBI-aws applications need access to this web service for this purpose. No sensitive data is stored on the web service, only anonymized (hashed) values are transmitted. The call takes place exclusively over an https connection and only if this function has been activated.

Depending on the corresponding setting, the number of those who are affected by a message fragment (e.g. message, early warning or resolve message), to whom it was displayed or who have read it is determined. A specific check, e.g. whether someone in particular is affected, is not possible.

For detailed information see Detailed functionality

IBI-aws Admin

The impact of a message is shown in the Impact column inside the message overview.

When Refresh Impact is clicked in IBI-aws Admin, one request to the web service will determine the impact of all selected messages.

The Impact column may contain the following information:

Impact column content	Conditions
`-`	The impact of the message will not be determined
^Unpublished	The impact of the message will be determined The message has never been published
`Pending`	The impact of the message will be determined The message is active The Impact property has not been updated yet
`Refresh required`	The impact of the message will be determined The message is already expired The Impact property has not been updated yet
`#Number "Read"# \| #Number "Dispayed"# \| #Number "Affected"# (temporary)`	The impact of the message will be determined The Impact property has been refreshed The request time was less than [message end + 1 day]
`#Number "Read"# \| #Number "Dispayed"# \| #Number "Affected"#`	The impact of the message will be determined The Impact property has been refreshed The request time was after [message end + 1 day]

IBI-aws Client / IBI-aws MobileClient

Per message fragment, an anonymized confirmation is generated for each activated impact level at the corresponding point in time and, as far as possible, transmitted to the web service in bundled form.

If the IBI-aws Client / IBI-aws MobileClient cannot establish a connection to the web service during a transmission of the bundled confirmations, the transmission is repeated at regular intervals until it is successful.

The status of the transmission is saved accordingly and can thus be repeated even after a restart of the application.

Affected

The confirmation for "Affected" is created if, after evaluation of the message file, a message fulfills all stored restrictions except for the applications.

In the IBI-aws MobileClient, the message file is evaluated when the application starts. This evaluation is repeated whenever changes to the category subscriptions are detected.

Displayed

The confirmation for "Displayed" is created for the IBI-aws Client when a message fragment is displayed.

In the IBI-aws MobileClient this confirmation is created when a message fragment is visible in one of the available lists.

Read

The confirmation for "Read" is created for the IBI-aws Client when a message fragment viewed for the first time is closed.

In the IBI-aws MobileClient, this confirmation is created when a message fragment is displayed in the message details.

Enable the feature

How to enable/disable this feature or set the impact level is explained at Extended.

If the clients don't have direct internet access in your network, the access to web service URL needs to be activated (proxy-/ firewall exception).

Request the current impact

How to request the current impact is explained at Refresh Impact