Support 1a

[Support 1a]

Open the Formativ Windows Control Panel applet and ensure all the options under ‘Enable/Disable’ features are checked, then re-start the client. An early version of the 1.6 installer did not always maintain a setting that could cause this to happen.

Advansys Support

[Support 1a]

Novell currently only expose the Junk Mail settings via the following methods:

GroupWise.JMAddUserToPAB
GroupWise.JMBlockSender
GroupWise.JunkSender
GroupWise.TrustSender
GroupWise.JunkMailHandling
GroupWise.JunkMailSettings

These are documented in the Formativ Language Guide. I hope this helps.

Advansys Support

[Support 1a]

We will let you know when Novell release these fixes. They have been very responsive, so I suspect we will not have to wait too long.

Regards,

Advansys Support

[Support 1a]

The object you are working with in this case is actually a ‘Document Reference’ object, which is derived from the ‘Message’ object type. Look up DocumentReference in the Object API documentation. You notice it says at the top of the page it is a subtype of Message.

I hope this helps.

Advansys Support

[Support 1a]

Remember there is a different between a document reference object (which GetMessage() is going to return) and a document object.

Once you have an instance of your document reference object, you need to access it’s document property in order to work with the physical document.

Here’s some psuedo code:

set oDocRef = GroupWise.Account.GetMessage("abcdefg")
MsgBox oDocRef.Document.DocumentNumber

In your example code it appears you already have the Document Reference object (MyMsg.MessageID), so there’s no need to call GetMessage – it’s going to return the object you already have. All you need to do is reference the Document Reference’s .Document property.

I hope this helps.

Advansys Support

[Support 1a]

You could install the Business Solutions Pack with the ‘s’ switch to run the installation silently. Otherwise I suspect you would have to create an AXT snapshot. The ‘s’ approach is probably going to be easier.

Advansys Support

[Support 1a]

You would need to obtain the document reference enclosing folder object, read its name property, then recurse up through the enclosing folder properties until you get to the top of the account. Using this technique you could build a string representing the full folder structure to the document, i.e.

“UserNameDocumentsProject X”

Here’s some code you can use to access the enclosing folder of the selected message:

dim oMsg
  
  Set oMsg = Client.ClientState.CommandMessage
  
  ' Refresh the folders collection 
  groupwise.account.refresh
    
  ' The folder this item is contained in.
  if (oMsg.EnclosingFolders.count > 0) then
    msgbox oMsg.EnclosingFolders.item(1).name
  end if
  
  set oMsg = nothing 

To obtain the physical document via the message ID, I suspect you would need to use GroupWise.Account.GetMessage(MessageID) to obtain an instance of the document reference object, then save the current version out as you are currently doing.

I hope this helps.

Advansys Support

[Support 1a]

I received word from Novell this morning, who have confirmed two GroupWise bugs:

1) The send event is not fired when a posted task is re-saved. This only affects the ‘advanced’ method of intercepting the send event, used by Formativ. Novell have handed this over their ‘CPR’ team, so I expect this should be fixed fairly quickly.

2) The On Complete event fires twice when completing a posted (personal) task from the open calendar view. It doesn’t happen when you mark a group task complete, or mark either Group or posted tasks complete in other views. This problem exists in both GroupWise 6.0x and 6.5. Novell have already fixed this problem in 6.0.4. 6.5 SP1 is about to be released, and no other fixes are likely to be incorporated, so this one will have to wait for 6.5 SP2.

Novell will let me know when both of these are fixed, at which point I’ll let you know. In the meantime, I’m afraid there is not really anything we can do to help work around these problems.

Regards,

Advansys Support

[Support 1a]

Have a look at the:

GroupWise.FocusSet(Place eControl, ControlName String)

method in the Language Guide. This is used to change the input focus on the currently open view.

To set the focus to the message field, trying something like:

GroupWise.FocusSet(fcsMessage,"")

I hope this helps.

Advansys Support

[Support 1a]

Thank you for your continued feedback and support.

Regards,

Advansys Support

[Support 1a]

Thank you for your question below. The applet code is not implemented differently on different operating systems. However, I cannot say how the GroupWise client operates under different versions of Windows.

If we assume the GroupWise client works the same way under Windows 9x and 2K, something else must be different. To assist further, could you please advise:

1) Are you accessing the same GroupWise account on both Windows 2000 and 9x?

2) Do you have the same version of the GroupWise client installed on both machines? What version is it? (Version, Date and Language)

3) When you say Windows 9x, do you mean 95 or 98?

4) Do you know if you are actually obtaining the appropriate address book entry on 9x? Perhaps you could simplify that part of your code which locates the user to be something like:

for each objAddressBookEntry in AddressBook
   if objAddressBookEntry.UserID = usr then
      MsgBox objAddressBookEntry.Title
   end if
next

As your code stands at the moment, you can’t actually tell if you are first obtaining an address book entry.

Advansys Support

[Support 1a]

This applet stores the junk-mail list, content-list and the subject-list files locally. The applet uses these files to build the junk mail rules. When a user changes from there desktop to laptop, the settings files are not being transferred. This causes the applet to re-build the rules again (deleting any previous rules), using the settings files that exist on the notebook at the time the applet is executed.

The only work around to this problem currently is to manually (or otherwise) copy the appropriate files from the desktop-notebook-desktop – not particularly elegant. We do have plans to possibly upgrade this currently free applet to use another system to save settings that travels with the account. I don’t have any delivery dates for this at the moment.

Advansys Support

[Support 1a]

Formativ 1.6.0.1 is now available from the download page. This build fixes the issue desribed above.

Advansys Support

[Support 1a]

Ralf,

GroupWise events do not fire when an item is programmatically created – they only fire when a user manually creates an item in the client. This is the way GroupWise is designed. You would need to modify your creation routine to perform the appropriate processing on the item as part of the creation process.

The On Send event does not execute when you re-post an existing item because you are not actually sending the item – you are re-saving it. This is the way GroupWise is designed. Nonetheless, I agree it would be useful to have an ‘On Re-save’ event exposed by GroupWise that we could use. I’ll make a formal request to Novell in this regard today.

I will also report the dual firing of the On Complete event when a task view is opened to Novell today.

Regards,

Advansys Support

[Support 1a]

I have confirmed this behavior as a bug – Power Users should not be seeing this message. This has been fixed, and will be made available in the next 24 hours from the download page.

Advansys Support

[Author]

Replies