"Offered" Action with Message Deadline

I have created a very simple Office 2013 Standard installation scri-pt, this I wanted to “offer” to our users, a long with a “Nag” message to basically keep the offer on screen if they’ve not run the offer (after 7 days).

I had no problems getting the offer “balloon” to pop up, However in my test (by using a much shorter deadline timeout) I cannot get the message to show on screen at all (the offer balloon pop’s up no problems).

It “feels” like I’ve missed a client setting or something really obvious, but hey ho when you spend time staring waiting for the answer to appear, it never does!

any help would be appreciated

Thanks in advance
Chris

What are the current client settings you have deployed regarding “Client UI”?

I’ve not made any changes from the default client installation

You may want to check the “BES Support” site tasks for those with “Client UI” in the title. Enabling some of these features may help in the offerings.

1 Like

Thanks again for the reply.

I believe this is a known “bug” which I need to upgrade to get the newest features in 9.2 patch 6.

I’ll keep this thread updated for completeness

This is not a bug.

What you describe is not an Offer. An Offer is user initiated with possible notification of its existence.

What you are looking for is an action with a pre-action message that users accept. Don’t make it an offer to do this.

Thanks for the reply, I’ve unfortunately been tied up on another project, but back working on this one again.

I tried what you suggested, however after the initial balloon pop up, I still don’t get the message on screen at all - let alone “keep topmost” I’ve been using a 10 minute deadline for testing.

Unsure really what to try next, maybe I need to configure the client to pop up messages, but I cannot see anything obvious.

Regards

The messaging to keep top most is different than the balloon pop-up. It wouldn’t be an offer.

Yes - Indeed you nailed the problem, it was my understanding of the difference between “offers” and “messages”

All sorted now.

Thanks for the help.

1 Like

For clarification, Offers are always optional and are user initiated. Users can optionally be notified of their existence, but this doesn’t force them to use them at all.

“Messages” can be optional (allow the user to cancel) or mandatory (fire off after a deadline, or stay top most until user accepts), but are put in the user’s face, more or less requiring user response of some kind.

1 Like