Support 1a

[Support 1a]

I’ve just created a couple of simple example applets, and are unable to reproduce the problem you describe.

Here’s my code that sends myself an email message of the custom message class GW.MESSAGE.MAIL.EMPPROC:

Sub Main(Client, GWEvent)

  dim objDraft
  dim objEmail
  dim objRecipient

  set objDraft = GroupWise.Account.MailBox.Messages.Add("GW.MESSAGE.MAIL.EMPPROC", 4)
  objRecipient = objDraft.Recipients.Add(objDraft.Sender.EmailAddress,,0)
  objDraft.Subject = "This is a custom message of class GW.MESSAGE.MAIL.EMPPROCs"
  objDraft.BodyText.PlainText = "This is the body text of the email message"
  set objEmail = objDraft.Send

End Sub

Running this results in a new email message appearing in my mailbox.

I then create a new applet in which I defined a new message class of GW.MESSAGE.MAIL.EMPPROC, and defined an integration against the GW.MESSAGE.MAIL.EMPPROC OnOpen event. I indicated that I wanted to replace the GroupWise event. Here’s the very simple applet code that is executed when the GW.MESSAGE.MAIL.EMPPROC OnOpen event is triggered:

Sub Main(Client, GWEvent)

  if GWEvent = "GW#C#OPEN" then
    MsgBox "Display the portal"
  end if

End Sub

When I open any ‘standard’ email message, the message box is not displayed (in fact, the applet isn’t executed as it’s integrated against the custom message class). When I open the message I created with first example applet shown above, the message box is displayed.

I don’t know why you would see your applet being executed when you open a standard email message – you might want to re-check your integrations. You could also email a copy of your configuration information to support@advansyscorp.com and we’ll take a look. From GroupWise, select Help|About Formativ. When the about dialog appears, select the configuration tab, then press the copy to clipboard button. Paste the contents of the clipboard into an email message to the above address.

Advansys Support

[Support 1a]

Unfortunately you cannot specify the location of the context menu entry with the current version of Formativ. It is added to the end of the existing entries.

Advansys Support

[Support 1a]

quote:

---

1) Replace the current edit control for new messages?

---

If you mean replace the text edit control used in GroupWise compose view dialogs then no, the forms designer will not do this. The form designer lets you create completely new event driven forms. It is not designed to replace elements within existing GroupWise forms and dialogs.

quote:

---

2) allow additional code to be run as a user types into a control.

---

Code could be executed as a result of changes detected in a control element appearing on a new Formativ form, but not within an existing GroupWise form or dialog.

If my understanding is correct, you wish to automatically save GroupWise draft messages periodically as a user enters text using the standard GroupWise email compose views. Unfortunately the forms designer will not help you with this requirement, nor will Formativ in general. Such a low-level feature would need to be built directly into the GroupWise client by Novell.

Regards,

Advansys Support

[Support 1a]

I would expect this should be possible. An applet could be written that, when executed automatically on GroupWise startup, would create the rule. An entry could then be written (possibly to the account) indicating the rule exists. This entry would be checked by the applet each time it ran to ensure multiple copies of the rule were not created.

The applet could then be pushed out via eDirectory to the appropriate users. You would need a copy of Formativ Admin to manage eDirectory management, and a copy of Runtime on each machine that needed to run the applet.

I hope this helps. Please let me know if you require any further information.

Advansys Support

[Support 1a]

Roger,

Thank you very much for taking the time to provide your detailed suggestions. We always welcome feedback and suggestions from our user base, and your suggestions are warmly accepted.

I’ve added your ideas to our enhancement database. We draw upon this information whenever a maintenance release or new version is planned, so it will be seriously considered at the appropriate time.

Once again, thank you for taking the time to share your ideas.

Kind rehards,

Advansys Support

[Support 1a]

We are currently beta testing a new Outlook Migration tool that will supercede the Cool Solutions version. You can download a copy by clicking here.

Advansys Support

[Support 1a]

We are having problems duplicating what you are experiencing. Would you please be able to email complete samples of what doesn’t work to support@advansyscorp.com. Please include the image file(s) being used. Could you also let me know which version of GroupWise you are using.

Regards,

Advansys Support

[Support 1a]

Dear Kate,

Thank you for the sample applets. We could see two issues that would cause problems:

1) A raw RTF string was being assigned to the Msg.BodyText property. However, the .BodyText property interprets any string assigned to it literally. You need to use the Msg.BodyText.RTF property. (.RTF accepts an RTF string).

2) When an item is being composed, it does not yet exist in the message store. This means you cannot use the Object API to access it. Instead, you use the ‘token’ approach, where unfortunately the Msg.BodyText.RTF property is not available. The GroupWise.ComposingItem property actually gives you a ‘wrapped’ message object that differs from the one where you are able to use the Msg.BodyText.RTF approach. When dealing with composing messages, you need to use formatting commands to apply the appropriate text styles. For example:

    Call GroupWise.NewMail
    Call GroupWise.SwitchToRTFView
    
    ' -----   Set the subject --------    
    Call GroupWise.FocusSet(fcsSubject, "")
    Call GroupWise.TypeText("This is the new subject")
    
    
    ' ----- Set the message body --------
    Call GroupWise.FocusSet(fcsMessage, "")
    Call GroupWise.TypeText("This is plain")    
    
    ' Bold
    Call GroupWise.FontBold(True)    
    Call GroupWise.TypeText("bold")
    Call GroupWise.FontBold(FALSE)
    
    ' Italic
    Call GroupWise.FontItalic(True)    
    Call GroupWise.TypeText("italics")
    Call GroupWise.FontItalic(FALSE)    

We have updated your example applets accordingly and sent them to you via email.

Advansys Support

[Support 1a]

I have asked an Engineer to look at your sample. We’ll report back ASAP.

Advansys Support

[Support 1a]

Always happy to help.

Advansys Support

[Support 1a]

Thanks – I have asked one of our engineers to take a look.

Advansys Support

[Support 1a]

Kate,

1.6.0.7 didn’t change anything related to RTF output, so I suspect the 6.5 SP1 build. Could you please send a copy of your applet to support@advansyscorp.com and I’ll test it in-house.

Advansys Support

[Support 1a]

I have seen this happen with beta versions of 6.5 SP1, but the problem seemed to ‘dissapear’ from my machine a few builds prior to the official SP1 release from Novell.

I’ll try to duplicate it in-house and report it Novell. Unfortunately, I suspect it’s going to be something Novell will have to fix. I’ll advise my finding via email and in this forum.

Advansys Support

[Support 1a]

Thank you for your suggestion for Distribution List support. We are currently reviewing our applet offerings, and agree this would be a worthwhile enhancement.

While I cannot provide concrete timeframes, I suspect we may be able to provide an update within this quarter. Please keep an eye on the web site for announcements.

Advansys Support

[Support 1a]

The AXT file in the Distribution Kit just runs the formativruntime.exe setup program and passes several parameters to it. I suspect if you use only the AXT, and don’t import any registry entries or other files, you should be successful.

Advansys Support

[Author]

Replies