Alternative behavoir of button Send in Task item

  • Thread starter Thread starter Alexey Yukhovich
  • Start date Start date
A

Alexey Yukhovich

Hello, All!

How I make it?

Help me, please.




With best regards, Alexey Yukhovich. E-mail: (e-mail address removed)
 
Hi Sue,

Sue Mosher said:
Make what?
Click to expand...

There is a trouble with our store Outlook sends Task request
even if Task saving is failed.(Some requred fields is mising and so on)
Even if i try to cancel saving in the form's OnWrite event it does not work.
We need first check if the Task can be properly saved and if it failed
cancel the request sending.

We tried to Advise Send Button for the task but without success.
Advising SaveAndClose works well.
It seams the Send button for the Tasks has very special behavior.

May be you can give as some tips.

As a last way we can try to workaround that via windows message hooking
but maybe there is easier way to do that.

WBR
Henry
 
A task request item does not fire a Send event; this is a known issue.

Are the required fields all set up with control-level validation?
 
No
That is standard fields like Subject start date and so on.
Can I customize first page of Standard Task Form ? I think I can't.

But there is some other errors possible like something wrong on the server
side.
So what we should do in this case.
Request is sent but Task is not saved so is not exist.
That is wrong.

Any ideas how to workaround ?
The only i have to hook pressing send button somehow.

WBR
Henry
 
No, you can't customize the first page, but you shouldn't need to just for
validation. Try adding the fields you want to validate to any customizable
page, which you can hide from the user. Set the validation on those controls
on the custom page.

What kind of errors do you suspect on the server?

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
No, you can't customize the first page, but you shouldn't
need to just for
validation. Try adding the fields you want to validate to any customizable
page, which you can hide from the user. Set the validation on those controls
on the custom page.
Click to expand...
Thanks for the tip.
What kind of errors do you suspect on the server?
Click to expand...

f.e. trivial Server Internal Error (we using WEBDAV)
IMessage::SaveChanges returns an error but Task request is
sent anyway.

WBR
Henry
 
In what way are you using WebDAV for this project? I thought we were talking
about a custom Outlook form.

Did you try the validation technique I suggested?
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
In what way are you using WebDAV for this project?
I thought we were talking
about a custom Outlook form.
Click to expand...
We using WEBDAV in the our IMsgStore implementation.
So all that problems concerns working with our Store.
Did you try the validation technique I suggested?
Click to expand...
Not yet because of form cache problems in Outlook 2003.
We reimplemented some functionality like objects and
folders permissions in add-in.

So I should deny sending Task request if the Task itself
is not properly saved.

WBR
HEnry
 
So this is a custom store that you're working on? That wasn't clear from
your original message.

You'll have to decide how you want to handle the task request issue. All I
can tell you is that the item will be sent before it's saved, but no Send
event fires.

--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
 
Hi Sue,
So this is a custom store that you're working on? Exactly.

That wasn't clear from
your original message.
Click to expand...
You'll have to decide how you want to handle the task
Click to expand...
request issue.
All I
can tell you is that the item will be sent before it's saved, but no Send
event fires.
Click to expand...
That is sad :(

So I think that is because you can't assing task to
yourself.
Is Task saved or not it does not matter for you because
you'll be notified by additional email about it state or
etc.
Task request is sent to ther executor(s) and local copy
will be created in the executor's default task folder.

In the public folders you can't assign Task to smb.

Our server is more like public folders. So you have to
create a Task only once and it will be visible for all
recipients of that Task.
Sending request is more like notification about new or
modified Task.

What do you think about why Tasks have such differend
behaviour ?

WBR
Henry
 
Back
Top