Support 1a

[Support 1a]

One of our engineers has supplied the following code to save an item to the Work In Progress folder. Once saved, you could add a custom field using the Object API:

  dim oMsg
  dim iMsgID
  dim iFolderPath
  dim iCounter
 
  ' Save the composing message to WIP folder
  iFolderPath = groupwise.account.owner.displayname & "" &_
  groupwise.account.workfolder.name
 
  Groupwise.ItemSaveMessageDraft(iFolderPath)
 
  ' Get the message ID from view
  iMsgID = groupwise.ItemMessageIDFromView()
 
  ' Some message with large attachments can take some time to save.
  iCounter = 0
  do while iMsgID = "X00"
    utilities.Timer(1)
    utilities.DoEvents()
    iMsgID = groupwise.ItemMessageIDFromView()
    iCounter = iCounter + 1
 
    ' Exit, if we do not get the proper message id
    if (iCounter >= 10) then
      exit do
    end if
  loop

  if iMsgID = "X00" then
    msgbox "Message ID not valid."
    exit sub
  end if
 
  ' Get the saved message
  set oMsg = nothing
  set oMsg = groupwise.account.getmessage(iMsgID)
 
  if oMsg is nothing then
    exit sub
  end if
 
  msgbox oMsg.subject
  set oMsg = nothing

Another approach might be to attach a specially named and encoded file attachment to the draft message. The attachment would contain the ID information you need to associate with the message.

The term ‘current message’ means either the message being composed, or the currently selected message.

I am not aware of any fields you can access when working with a composing message that won’t be obtrusive to the user. In the past we have done similar things by adding encoding to the end of the body text of the composing message. I don’t know if this would be acceptable in your case.

I hope this helps.

Advansys Support

[This message was edited by Support 3 on July 07, 2005 at 05:05 PM.]

[Support 1a]

This is possible technically. You would need to write an applet that used a Trusted Application to log into each account in the system. Once logged in, you would need to access the Frequent Contacts address book and process it for duplicates.

I hope this helps.

Advansys Support

[Support 1a]

Thank you for your posting. Here is an excerpt from the readme.txt

Prior to official component documentation becoming available from Advansys, advanced developers may wish to access the following sources for documentation:

The components on the Standard, Additional, Win32, System and Dialogs tabs of the component palette are documented in the Borland Delphi VCL help file. This can be downloaded from:
ftp://ftpc.borland.com/pub/delphi/techpubs/delphi6/d62pro.zip

The components of the Enhanced tab of the component palette are documented in the Raize Components Trial Help files. This can be downloaded from:
http://www.raize.com/DevTools/RzComps/DemoTrial/RC3Trial.zip

The components on the Netware, LDAP and NDAP tabs of the component palette are Novell’s ‘ActiveX Controls for Novell Services’. Documentation for these components can be found at: http://developer.novell.com/ndk/activex-index.htm.

The components on the GroupWise tabs of the component palette are Novell’s ‘GroupWise Controls for ActiveX’. Documentation for these controls can be found at: http://developer.novell.com/ndk/gwactive.htm.

Regards

Advansys Support

[Support 1a]

This error means the Object API hasn’t returned an object to you. In this case, the Object API doesn’t return an AddressBookRights collection unless the address book has actually been shared with someone. You need to check if the AddressBookRights object is ‘nothing’ before accessing it.

Here’s some example code:

dim oBook
dim oRights
 
set oBook = groupwise.account.addressbooks.item("Test")
 
msgbox oBook.Name
 
set oRights = nothing
set oRights = oBook.AddressBookRights
 
if oRights is nothing then
  msgbox "No object"
else
  msgbox "object"
end if

set oRights = nothing
set oBook = nothing

I suspect the same issue may be behind the missing address book problem you encountered. If the book has been deleted (or is otherwise unavaible), the Object API will return an empty object. You need to check this before attempting to access the returned objects properties.

I hope this helps.

Advansys Support

[Support 1a]

Regarding question (1), once you have acquired an instance of the wrapped Address book object, (i.e. the gwBook from ‘For Each gwBook in gwBooks’), you need to access the native Object API address book object. You can do this via the .Object property). Once you have access to the native Object API address book property you can access the AddressBookRights property. This is a native Object API property documented by Novell. See: http://developer.novell.com/ndk/doc/gwobjapi/index.html?gwobjenu/data/h7ikbsqg.html

I hope this helps.

Advansys Support

[Support 1a]

In regards to question (2) above, here’s some code that may help:

  dim oBook
  dim oEntry
  dim oMailAddress
  dim iEmailAddresses
 
  set oBook = groupwise.account.addressbooks.item("Test")
 
  ' Iterate through each Address Book Entry
  for each oEntry in oBook.AddressBookEntries
    iEmailAddresses = ""
 
    ' Iterate through each EMail Address object of the address book entry
    for each oMailAddress in oEntry.EMailAddresses
      iEmailAddresses = iEmailAddresses & oMailAddress.MailAddress & vbcrlf
    next
 
    msgbox "Address Book entry: " & oEntry.displayname & vbcrlf & iEmailAddresses
  next
 
  set oMailAddress = nothing
  set oEntry = nothing
  set oBook = nothing

This code uses native access to the Address books collection, as opposed to the wrapped collection. You need to pass it a book name.

I’ll post something regarding question (1) shortly.

I hope this helps.

Advansys Support

[Support 1a]

This question will be answered via direct email.

Advansys Support

[Support 1a]

Thank you for your posting above.

We strongly recommend against using Word as a HTML editor. Word creates HTML that is generally unsuited for use with GroupWise, and in some cases is incompatible with the way GroupWise handles HTML. This probably accounts for the missing graphic.

The only way to avoid the signature graphic being an attachment is to create the HTML so that it points to the image on a server. The easiest way to do this is to use the insert remote image feature of the multiple signatures applet HTML editor. You cannot do this using Word.

I would be happy to take a look at your signature Word document and possibly convert it to HTML. If you would be interested in this, please email support@advansyscorp.com.

You will find the documentation for Multiple Signatures available via the Help button on the main solution dialog, and from a start menu link.

I hope this helps.

Advansys Support

[Support 1a]

I’ll make a note of your request for when resources become available.

In terms of your question about linking email URLs to portals, if you mean you want to click a URL contained in an email and have a portal automatically activated, unfortunately the answer is no. In order to provide this type of functionality we would have to create a mechamism that would allow applets to run in response to HTML events. This is something we want to avoid from a security perspective. Please let me know if I have misinterpreted your question.

I would need more information about your objectives in regards to showing a URL as an XML page.

Regards,

Advansys Support

[Support 1a]

Unfortunately our custom development resources are assigned to other projects, and we would not be able to quote on this job in the near future. I would suggest you contact a Formativ development partner, one of which should be able to assist. You can access the full list at:

http://www.advansyscorp.com/formativ_partners_developers.htm

Regards,

Advansys Support

[Support 1a]

We should be able to come up with an easier way to set this up for 2000 users. We’ll contact you by direct email.

Regards,

Advansys Support

[Support 1a]

Unfortunately this solution doesn’t have an applet-based calendar date information location override. The only way you can configure each workstation to look at the same shared location is to pre-configure the applet INI file, the distribute the INI file to each users’ workstation.

Approxiamately how many users would you need to do this for? We might be able to come up with something else if required.

Regards,

Advansys Support

[Support 1a]

Thanks for the update.

Advansys Support

[Support 1a]

Unfortunately the trial period cannot be extended once it expires. Are you able to install on another machine to complete your evaluation of the software?

Advansys Support

[Support 1a]

I understand this defect has been fixed in the soon to be launched GW7. We have asked that Novell port this fix back to GroupWise 6.5.

Please remember this is a defect in Novell GroupWise, not Formativ, and that we have no control over if/when Novell fix the bug. Given a resolution is very important to you, you may wish to consider reporting this defect to Novell directly. The more reports Novell receives, the more likely they are to do something about it. The defect you need to report is in the token called ItemAttachmentGetCurrentIndex().

Regards,

Advansys Support

[Author]

Replies