Task Message based on custom form goes to Inbox

[Don Wilkinson]

Sue and the gang,

I've created a new custom form (just prepopulates some text in the body and
sets the Category - nothing fancy) based on the default Task form. I've
published the form (IPM.Task.HelpDeskRequest) to the Task folder of a
mailbox. I can call the form programmtically or create an item via Choose
Form and it works great. New document goes to the Task folder.

But, when I publish/copy it to the Organizational Library the created items
land in my Inbox, not in the Tasks folder.

Clue?: the icon is the Post icon, not the Task icon.

Thanks!
Don

 

[Don Wilkinson]

Check to see if the form has one-offed. Open one in the Inbox and look at
the
MessageClass field. If the form is one-offed it will not have your form
name
there.

I created a test document. I tried to determine the message class by
looking at Properties, etc. I did not find it. So, as an experiment, I did
Publish Form. In that dialog, it did show the message class as "IPM.Task" -
which is missing the custom class designation "IPM.Task.HelpDeskRequest".

How does one avoid/fix this "one off" problem?

Thanks!
Don

 

[Hollis Paul [MVP - Outlook]]

But, when I publish/copy it to the Organizational Library the created items
land in my Inbox, not in the Tasks folder.

Check to see if the form has one-offed. Open one in the Inbox and look at the
MessageClass field. If the form is one-offed it will not have your form name
there.

 

[Hollis Paul [MVP - Outlook]]

In that dialog, it did show the message class as "IPM.Task" -
which is missing the custom class designation "IPM.Task.HelpDeskRequest".

How does one avoid/fix this "one off" problem?

Take a look at this thread:

http://www.outlookcode.com/threads.aspx?forumid=4&messageid=17284

And search around on this site and perhaps www.slipstick.com.

 

[Don Wilkinson]

Take a look at this thread:

http://www.outlookcode.com/threads.aspx?forumid=4&messageid=17284

And search around on this site and perhaps www.slipstick.com.

Thanks Hollis,
it was a one-off problem. Don't know how. I think I may have
experiementally used the "Save Definition with Form" checkbox once, and then
reverted it. But I gather the damage was done, as it were.

I deleted the Form, flushed the forms cache (just to be sure), recreated the
form and published it. It tests fine!

Don

 

[Hollis Paul [MVP - Outlook]]

I deleted the Form, flushed the forms cache (just to be sure), recreated the
form and published it. It tests fine!

That is what you have to do. It is a real pain on complicated forms. I kept a
minimum of three generations of the form when I was developing custom forms,
and publish again with the slightest change.