Support 1a

[Support 1a]

You won’t be able to access the command message in the OnSend event, because at that time the message does not yet exist in the message store.

Here’s some sample code I put together that illustrates one way to access the attached message body text. This code contains only basic error checking, but it should point you in the right direction:

Sub Main(Client, GWEvent)

  dim iCount
  dim iIndex
  dim iMsgID
  dim iBody

  ' Check we have a composing message available.  They have a message ID of "X00"
  if GroupWise.ItemMessageIDFromView <> "X00" then
    MsgBox "No composing message"
    exit sub
  end if

  ' Look for any message attachments
  iCount = GroupWise.ItemAttachmentGetCount("X00")
  if iCount > 0 then
    for iIndex = 0 to iCount - 1
      if GroupWise.ItemAttachmentGetClass("X00", iIndex) = 2 then  ' 2 = Message type attachments
        iMsgID = GroupWise.ItemAttachmentGetName("X00", iIndex)
        MsgBox "Message ID: " & iMsgID,0,"Found Message Attachment"
        iBody = GroupWise.ItemGetText(iMsgID, 10) ' 10 = body text
        MsgBox iBody,0,"Here is the body text"
      end if
    next
  end if

End Sub

I hope this helps.

Advansys Support

[Support 1a]

Thank you for your question below.

As far as I am aware there is no 100% reliable method by which you could determine if the original message is attached (or inlined) in the current message.

You would probably need to iterate through the attachments collection of the current message looking for attachments of type message. For each message attachment found, you would need to make a determination if the message looked like the original. The subject may be the only common information you could use.

If no message attachments were found, you would then search the body text of the current message looking for inline message text, extracting the subject, and making the same evaluation. Again, the reliablity of this technique is unknown.

In both cases you’ll want to work with the CommandMessage object obtained via:

Set Msg = Client.ClientState.CommandMessage

This will give you a true Object API message object, making it easy to access it’s attachments collection, etc.

I hope this helps.

Advansys Support

[Support 1a]

It might be best to take this discussion offline. As I can’t locate an email address in the forum, could you please send a message to support@advansyscorp.com and we’ll discuss further details and pricing.

Regards,

Advansys Support

[Support 1a]

Dear Marco,

Unfortunately there is nothing you (or us) can do to decrease the time it takes to create items using Remote Mode. Internally, item creation is different when using Remote – requests need to be created. As we didn’t write GroupWise, I can’t give you any details of specific differences between online and remote mode for different message types or the setting of discrete properties. As far as Formativ is concerned, there are no differences between online and remote mode.

The only suggestion I can make is that you may wish to investigate the GroupWise.SendTask command, which creates a task in a single command. I haven’t tried it, but it uses the underlying token API, as opposed to the Object API.

Regards,

Advansys Support

[Support 1a]

Thank you for your enquiry.

It sounds like we could help, but would need to clarify some details to be sure. Formativ only works with the Windows 32-bit client, so if any of your users use WebAccess, the text wouldn’t be added to the subject. Likewise, if any users access your system remotely (i.e. from home computers), they would need to be using the Windows client and have Formativ installed. How sure do you need to be that every message has the given text in the subject?

Regards,

Advansys Support

[Support 1a]

This error has not been fixed in 1.6, and most likely won’t be. It may make it into version 2.0, but has been given a lower priority due to the new V2 Forms designer that eliminates this issue.

Version 2.0 is due for release in about 4-6 weeks.

Advansys Support

[Support 1a]

Dear Marco,

Thank you for your question. Unfortunately I don’t think you’ll be able to speed this up. When you use Remote Mode GroupWise needs to do significantly more work when you added a new message to the message store. (i.e. it needs to build remote requests and phsically write the entry to your remote database). Depending on the size of your Remote database, this is going to take some time.

I’ve had a look at your code, and can’t spot anything that looks slow. Unfortunately, I suspect the delay is just an unfortunate side effect of using Remote mode with the Object API.

Regards,

Advansys Support

[Support 1a]

While I am not familiar with McAfee VirusScan Enterprise, it sounds like it has disabled the Windows script host, components of which are used by Formativ. I would suggest you refer to the McAfee documentation, or contact McAfee directly to ascertain how to re-enable whatever component of the host it has disabled.

Advansys Support

[Support 1a]

To move a message between folders, move it from the old folder’s Messages collection to the new folder’s Messages collection. I have not tried it, but I expect it should also work with a shared folder. You need to use the Object API Folder.Messages collections to do this. See the Messages.Move method in the Object API documentation for more information.

You need to use the Administrative Object API to access distribution lists in Formativ. Click the link above for to access the documentation. Formativ creates an instance of the Admin API for you via the GroupWise.AdminObject language command. GroupWise.AdminObject returns an instance of the Admin API System object. From here you connect to the appropriate GroupWise Domain, then locate and use the Distribution List you are interested in. Note that you need to have the NetWare Client installed to use the Admin Object API.

I hope this helps.

Advansys Support

[Support 1a]

You need to use the draft message attachments property. Try something like (untested code):

' You need to grab the actual message object you want to attach.
' MyArray(3) here should hold the message id of the message you want to attach
set objMsg = iAccount.GetMessage(MyArray(3))

' Call the Attachments.Add method to add the actual message object
objMail.Attachments.Add(objMsg)

I hope this helps

Advansys Support

[Support 1a]

Hello Stuart,

Yes, it should be possible to modify your applet to forward messages to a designated account from the trusted application applet. You could call the .Forward method of the found message, which creates a draft message with the appropriate message attached, address the draft appropriately and finally call the send method. You could also create a new draft message, attach the appropriate message, and finally call send. You might want to also delete the sent item to remove evidence this procedure has been carried out if appropriate.

Feel free to post any code you are having problems with.

Regards,

Advansys Support

[Support 1a]

A test application has been sent to your registered email address.

Advansys Support

[Support 1a]

None that I am aware of. I’ll create a simple test application (standalone, no Formativ) and make that available to you. We have a public holiday here tomorrrow and on Monday, so I may not be able to get something to you until Tuesday.

Regards,

Advansys Support

[This message was edited by Support 1 on April 12, 2004 at 07:33 PM.]

[Support 1a]

Hello Stuart,

Could you please try the following to see if it helps:

1. Download the Trusted Application Binaries from http://developer.novell.com/ndk/gwtapp.htm

2. You will find a file called GWTApp.dll in this download. Copy this file over the top of the existing version you should find in your GroupWise application directory (probably “C:NovellGroupWise”)

3. Restart GroupWise and try again.

Novell updated this file, but didn’t change it’s version resource, meaning it may not have been updated when you last installed Formativ.

Please let me know how you proceed.

Regards,

Advansys Support

[Support 1a]

Hello Stuart,

I tried your code, and it worked for me once I created the trusted application object. However, the first time I tried it after creating the object it didn’t work – I observed the same behaviour you did. However, I tried it again and it work on subsequent attempts. Perhaps their is some latency involved in the installation of the trusted application object to the server? I would be interested to see if it works if you try it again. Please let me know.

If it still fails, could you please post a coy of the configuration information from the machine you are running this on so I can get a picture of your environment.

Regards,

Advansys Support

[Author]

Replies