Support 1a

[Support 1a]

You are welcome.

Advansys Support

[Support 1a]

The installer has been updated to not display the documentation when a silent installation is performed. Please download the solution again (ensuring your cache is clean), then try again.

Please let me know if this update solves your problem.

Regards,

Advansys Support

[Support 1a]

Not without modifying the installation itself. I’ll log this as a defect. Thanks for bringing it to our attention. Please watch this thread for details on when an update becomes available.

Regards,

Advansys Support

[Support 1a]

All the path registry entries are strings.

I have looked at the project source code, which indicates a change was made a some point to fix the location of the following paths:

– Applet Cache
– Encoded Applets Output
– Flexalock Applet Output

These are fixed (relative to the variable starting point).

The encoded and flexalock applet folders are only relevant (and created by) Studio and Creator. Why do you want to change the location of these folders? We have never received any requests that these two folders be configurable.

Advansys Support

[Support 1a]

I don’t think you can do this. I suspect a ListView would be a better option. Set its ViewStyle property to vsReport, then use the Columns property to specify the column names.

Advansys Support

[Support 1a]

Thanks for the tip regarding how you work around the bug!

Advansys Support

[Support 1a]

Thanks MA.

Advansys Support

[Support 1a]

Thanks for the update. I’ll contact you via email with a debug version you can try.

Advansys Support

[Support 1a]

ExpandedRecipients is a property of the Mail object in the Object API. Like all Object API objects, you cannot use them until a message physically exists in the data store. In other words, you cannot create a message in the GroupWise client and expect any Object API methods to work until the message has at least been saved as a draft message. (Hence to the reference to the draft messages in the documentation).

Here’s some sample code that saves a composing item as a draft message, then displays the value of the ExpandedRecipients property. Please note this is sample code, not production code.

  dim oMsg
  dim iMsgID
  dim iWIPPath
 
  ' Save the draft message to the Work in Progress folder
  iWIPPath = GroupWise.Account.Owner.DisplayName & "" & GroupWise.Account.WorkFolder.Name
  groupwise.ItemSaveMessageDraft(iWIPPath)
 
  ' Calling ItemMessageIDFromView immediately after GroupWise.ItemSaveMessageDraft
  ' can result in an X00 ID.
  iMsgID = GroupWise.ItemMessageIDFromView
  iBreakCount = 0
  while (iMsgID = "Token failed execution!") or (iMsgID = "X00")
     Application.ProcessMessages
     utilities.Timer(1)
     Application.ProcessMessages
     iMsgID = GroupWise.ItemMessageIDFromView
     iBreakCount = iBreakCount + 1
     if (iBreakCount > 10) then
       exit sub
     end if
  wend
 
  set oMsg = GroupWise.Account.GetMessage(iMsgID)
  Set oRecipients = oMsg.ExpandedRecipients
 
  For Each oRecipient in oRecipients
    msgbox oRecipient.displayname
  Next
 
  set oMsg = nothing

Advansys Support

[Support 1a]

No emails have been received from you since we send you this information.

Could you please expand upon what you mean by ‘it doesn’t work’. This is certainly the mechanism Formativ uses to determine paths. Specific information is required in order for me to provide further assistance.

Advansys Support

[Support 1a]

This was answered by direct email on the 11th of November. Is this a duplicate post?

Regards,

Advansys Support

[Support 1a]

How are you triggering the forward or reply? There is a known issue in GroupWise 6.x.x (I’ve not looked to see if they’ve fixed it in 7 yet) that causes the reply/forward events to be fired twice if you use the Reply/Forward drop down button menu from the item view toolbar. It fires only once if you reply/forward _without_ using the drop down menu button. Unfortunately, as a third party we are powerless to detect and work around this bug.

Novell have certainly been made aware of this issue.

Advansys Support

[Support 1a]

Unfortunately I don’t think the custom field idea will work. You can only add a custom field to a message once it exists in the message store. When you are composing a message, but have not saved it to Work in Progress, the message does not exist in the message store, and therefore cannot be accessed via the Object API .The Object API is the only way to add a custom field to a message.

Regards,

Advansys Support

[Support 1a]

You could probably determine this by looking at the BoxType property of the message. If it was ggwDraft (4) you would know it was a draft message.

See http://developer.novell.com/ndk/doc/gwobjapi/gwobjenu/data/hvdi8k74.html#hvdi8k74 for more information.

Which version of the GroupWise client are you using?

Regards,

Advansys Support

[Support 1a]

This has more to do with how different email applications interpret and render HTML. GroupWise is responsible for the generation of the native MIME representation of the message, which is certainly a valid file.

Another possibility is that certain email applications are stripping out (or hiding) embedded images as a security measure. For example, the Mozilla email client will not display HTML images unless you explicity request that it does. This is a security and privacy feature.

Regards,

Advansys Support

[Author]

Replies