Creating a new Announcement

The Experience→User Engagement page is where you manage all the Sentiment, Info Surveys and Announcements that have been created in Experience. You can easily see for each engagement the Options that it has been configured with, what Management Groups it has been assigned to and whether it's Enabled or not. In the picture opposite, you can see the state following on from the Getting feedback via Info Surveys scenario.

Click the New Engagement button to begin.

Announcements

In contrast to the survey types, Sentiment Survey and Info Survey, Announcement type engagements are used solely to broadcast information to end-users. You can still gather the results of sending the announcement, but this is only done to check that the information has been received.  Announcements don't contribute to the Sentiment Score.

The picture opposite shows the Announcement type selected.

Names, Announcement Titles and Descriptions, Footer Notes, Read more links, Deadlines and Priorities

Having selected the Announcement type, the next steps are to set a Name for the announcement, the Announcement Title and Announcement Description that will frame the purpose of the announcement. You can also optionally add Footer Notes, which can provide additional information in the announcement itself, and a 'Read more' link, which can provide additional information for the announcement in the form of an externally available web page.

The Name for an Announcement is not stored as a metric that Experience can then report on. The Name must be unique amongst all the Engagement names that have been defined for Experience, but does not have to avoid other Metric names. For example, unlike Sentiment Surveys, Network on its own could be used as the Name for an announcement, even though this is already a metric that Experience reports on. It is best to choose a good name for the announcement that reflects the type of information being broadcast, so that it reminds you of its purpose if you encounter it on the User Engagement page at a later date, in this scenario the EUC manager names the survey: Adobe Reader Update.

The Announcement Title provides the headline for the information you are trying to get across to the end-user, if the headline has not been thought through carefully you will likely confuse your end-users and fail in your objective. In our scenario, the EUC manager sets the question to: Your Adobe Reader needs to be updated 

The Announcement Description is displayed to the end-user just below the Announcement Title and should provide additional context. Use it to answer the likely questions that will arise from the announcement and provide some guidance as to what the user should expect. Here, the EUC manager sets the Announcement Description to: We've noticed that you are running an older version of Adobe Reader. Due to documented issues related to that version, we are going to upgrade to the latest version on your device.  This sets the scene for why the action is being taken and gives a small indication on how it will increase the security on the end-user's device.

Footer Notes let you optionally provide additional bullet-points that emphasize your message. These are displayed in the announcement beneath the Announcement Description. In our example, the EUC manager adds Your copy of Adobe Reader is over 10 years old! as a footer note. This highlights just how out-of-date the installed version is and brings the message home that it needs to be replaced.

Optionally, the 'Read more' link field can be set, which adds the text Click here to find out more to the announcement. The user can click on this link to find out related supplementary information. In our scenario, the EUC manager has found a page on a vulnerabilities listing site that deals with the particular version of Adobe Reader. That way the end-user can click on the Click here to find out more link in the announcement and check for themselves the vulnerabilities that are present on their device - because that version of the software is installed - again reinforcing the idea that an upgrade is required.

Setting the Sender Details

Announcements are a direct communication to your end-users, you will likely want that communication to be as well-received as possible. Part of that process is to provide information about exactly who wants the communication to be made. In this example it will be the ACME IT department who will take the action, but in another scenario, the announcement could just as well have been sent on behalf of the CEO for the company. You can imagine how this would affect the processing of the information by the end-user when they receive the announcement.

The EUC manager enables the Show Sender Information toggle, sets the Name/Department field to ACME IT and the optional Designation/Description to Security Enhancement, because that's the name of the project they are taking this action under. They also badge the announcement with the ACME logo to make it official and give it the company seal of approval.

The Actions section comes last in the Announcement Engagement editor. Here you can provide additional URLs tied to buttons, that can be triggered by clicking on each button - or in the case of the Primary Action button (the first one on the list), by hitting the <enter> key. For example, you may have set up a registration page on your company intranet that can be triggered by a URL. In this case you could create a Please register announcement, add a Custom Actions button called Register and set that to the URL. When an end-user subsequently receives the announcement asking them to register, they click on the Register button and it takes them to the registration page via the provided URL.

A second option, if your organisation allows is to provide a link to an App Store or Service Catalog, to allow users to update the software themselves.

In our scenario, the EUC manager doesn't have any Custom Actions they want to add to the announcement so they leave this section blank. 

Saving the new announcement

When you're happy with the settings you've made in the survey editor you can click Save to commit the changes and continue to the next step. The picture opposite shows the new announcement added with no Management Groups set and not yet enabled.

Setting the Management Groups for the new announcement

Announcements don't have a default Management Group, so one must be assigned before the survey can be enabled and then deployed. For this announcement, the EUC manager already has an Old Adobe Reader Installed Management Group defined that targets the devices they have identified where the old version is installed. They now need to set that as the Management Group for the announcement.

To do this:

1. They select the survey and then click the Assign Mgmt Grp button.

2. In the Assign Management Groups popup subsequently displayed, they type Adobe into the search field and then select Old Adobe Reader Installed from the list of matching Management Groups. This gets added to the New Management Groups field.
3. They click Save to assign the Management Group.

Enabling the new announcement

New engagements are not enabled by default. Before they can be deployed, they must be explicitly enabled, providing an additional gateway that prevents the engagement being sent out too soon before it's ready.

To enable the new announcement the EUC manager:

1. Selects the checkbox at the left-hand end of the announcement's entry in the Engagements table and then clicks the Enable Selection button.

2. Doing this displays an Enable Selection confirmation popup that you must acknowledge before the selected engagements are actually enabled. Click Yes to confirm the operation and No to cancel it.

Deploying the new announcement

So the new announcement has the Old Adobe Reader Installed Management Group assigned and has also been enabled, it can now be sent to the end-users' devices by clicking the Deploy button, which will send the announcement to all the devices in the selected Management Group, that are currently or subsequently connected to Tachyon.

It is usually good practice to test the engagement on a few machines first before deploying to All Devices. This lets you see how the engagement will appear to your end-users and gives you the opportunity to debug the text and options before deploying to a wider audience. Doing this involves assigning a different Management Group to the survey that targets the selected test devices.

In our example, which only involves a few devices anyway, to keep things simple we can get away with sending the announcement out without testing, so the EUC manager clicks the Deploy button.

An Engagements Deployment popup appears that shows the changes that will be deployed when the Yes button is clicked. The EUC manager reads the list carefully, sees that the only changes are the ones related to creating, assigning Management Groups and enabling the Adobe Reader Update announcement and clicks Yes. Subsequently, a notification will appear showing that the policy changes are being applied to the Tachyon Agents.

What the end-user sees

When the 1E Client is installed on a network device, by default it also adds an icon to the notification area that displays the Real-Time Control Center (RTCC). Initially the icon may be hidden, but may be dragged onto the taskbar to make it always visible. When an end-user clicks on the notification icon they will see the Announcements and Surveys that have been deployed to the device.

When does the announcement appear?

To minimize the disruption to the end-user of having an announcement pop up when they're busy using the computer for other things, the 1E Client has a few heuristics that govern when the notifications appear. These measure and compare things like: whether the user is currently interacting with the device, how long it has been since they stopped interacting with the device, how long the notifications should wait before re-displaying if the user didn't respond to the last time it was displayed. These various options interact to essentially display the notification in the sweet spot between the user not actively doing something and the user having left their device.

Announcements are also accessible from the Real-Time Control Center, which allows the end-user to access them directly at any time.

Interacting with the announcement

In our scenario, the deployed announcement pops up on an end-user's device. They can see from the announcement title that their Adobe Reader needs to be updated, and from the description text, why this is necessary and what is going to happen. A footnote on the announcement highlights the fact that the installed version is over 10 years old.

The announcement has been configured with a URL that links to a page with more information. Clicking on the Click here to find out more link opens the linked page in their default browser. Here, they can read more about the vulnerabilities associated with the installed version of adobe reader and along with the description and footnote in the announcement feel re-assured that upgrading is the right choice.

Viewing the announcement responses

The Adobe Reader Update announcement has been deployed and end-users have begun to respond, the EUC manager wants to monitor those to see who has read the announcement. For an announcement the only place the responses can be viewed is from its details page, you get to this by clicking on the link for the announcement in the Name column of the Engagements table on the User Engagement page.

In the picture opposite, the EUC manager has clicked on the Adobe Reader Update link to display its details page. Here, they can see that a user has submitted a response. Dismiss in this case is likely a good response to the announcement, indicating that the end-user has at least looked at the announcement and clicked the Dismiss button.

After a number of responses have been made, a clearer picture of the current user behavior appears. Most of them have clicked the Dismiss button, and just one has clicked Later to receive the announcement at a later time.

Finally, the EUC manager checks the results again and sees that all the targeted end-users have responded. They can now go ahead and remediate the Adobe Reader issue knowing that the affected users have been notified.