Support 3

[Support 3]

We have updated the solution (http://www.advansyscorp.com/forums/topic/4901057941/) and will send you shortly the updated version through email.

Regards,
Advansys Support

[Support 3]

We have updated the solution (http://www.advansyscorp.com/forums/topic/4901057941/) and will send you shortly the updated version through email.

Regards,
Advansys Support

[Support 3]

We are currently modifying the Personalized Emailer solution to support the Base64 encoding, the current version only support the “quoted-printable” encoding. This issue was reported by the following thread:
http://www.advansyscorp.com/forums/topic/1171013841/

Basically, in your Mime.822 file, if the “Content-Transfer-Encoding:” is not “quoted-printable” then the solution will not replace the marker (e.g [C006: TBRTB], [C005: TAKATA], etc). We are hoping the current fix will solve this issue and we may be able to send you an update early next week.

Regards,
Advansys Support

[Support 3]

Sorry for the delay.

Are you refering to the “Message Viewer” (http://advansyscorp.com/formativ_pack_message_saver.htm) or “Archive To Go Viewer” (http://advansyscorp.com/atg-index.htm)?

Message Viewer display a FML file, from address and other fields shows like GroupWise message. You can not select multiple FML files and open in Message Viewer.

“Archive To Go Viewer” shows snapshot of a GroupWise mailbox.

Please let us know if we misunderstand your enquiry.

Regards,
Advansys Support

[Support 3]

Thanks for your feedback.

Regards,
Advansys Support

[Support 3]

See the sample code below to access the categories from an address book entry. See the Object API for more information (http://developer.novell.com/documentation/gwobjapi/index.html?gwobjenu/data/h7ikbsqg.html).

  
 dim oBook
 dim oEntry
 dim oCategory

 set oBook = GroupWise.Account.AddressBooks.item("Test Book")

 set oEntry = oBook.AddressBookEntries.Item(1)

 for each oCategory in oEntry.Categories
   msgbox oCategory.name & oCategory.Primary
 next

 set oCategory = nothing
 set oEntry = nothing
 set oBook = nothing

Hope this helps.

Regards,
Advansys Support

[Support 3]

We are not sure about any work around. May be you should post a message to the Novell Developer Support (http://forums.novell.com/category/developer.tpt) for any advice.

Regards,
Advansys Support

[Support 3]

This is one of the limitation to the GroupWise API to not allow to move attached message. Not sure about whether there is any method exists in SOAP API.

Just to see whether any changes in GW 7.0.2, I have tried the following sample code to move the attached message (I have a plain text message with an embedded message) but it failed with error message “An invalid argument was passed in the function call.”. I have comment-out the code to move the root message which works.

  
  dim oMsg
  dim oSourceFolder
  dim oDestinationFolder

  ' Destination folder
  set oDestinationFolder = groupwise.account.allfolders.itembyname("Notes")

  ' selected message which contains the attach message.
  set oMsg = client.clientstate.commandmessage

  ' Access message source folder
  set oSourceFolder = oMsg.EnclosingFolders.item(1)
  msgbox "Source Folder: " & oSourceFolder.name

  ' Access the attach message
  set oAttachment = oMsg.attachments(1)
  msgbox "Attachment: " & oAttachment.displayname

  ' Move the attach message to a destination folder (DOES NOT WORK)
  if (oAttachment.ObjType = 2) then
    msgbox oAttachment.message.messageid
    call oSourceFolder.messages.move(oAttachment.message.messageid, oDestinationFolder.messages)
  end if

  ' Works: Move root message to destination folder
  'call oSourceFolder.messages.move(oMsg.messageid, oDestinationFolder.messages)

  set oDestinationFolder = nothing
  set oSourceFolder = nothing
  set oAttachment = nothing
  set oMsg = nothing

As this type of enquiry is related to the groupWise API, you may consider to post a message to the Novell Developer Support forum (http://forums.novell.com/category/developer.tpt).

Regards,
Advansys Support

[Support 3]

I don’t think you can access the Birthday field as the field object type is reserved. See the following thread for more information about this issue:
http://www.advansyscorp.com/forums/topic/9331070501/

In Formativ, you have option to use the native GroupWise address books object or the Formativ wrapping of the address books object. See the comments from the Formativ Language guide:

quote:

---

Property AddressBooks
Read only property which provides access to the Formativ AddressBooks object.

Syntax
groupwise.AddressBooks(): Addressbooks

Value
This is a Read Only property. It returns a variable of type Addressbooks.

Remarks
This object represents the Formativ wrapping of the GroupWise address books. It is provided in order to make it simpler to access fields, especially in multi-lingual GroupWise clients. If you require access to the native GroupWise address books object model, access the GroupWise.Account.AddressBooks property.

---

Regards,
Advansys Support

[Support 3]

Sorry, we haven’t received any email from you. Please re-send the email to support@advansyscorp.com.

Post a message into this thread that you have sent the email so that we can confirm.

Regards,
Advansys Support

[Support 3]

We looked at the issue and found the following behaviour:

If you use the UTF-8, GroupWise use base64 encoding in Mime.822 file. Current version of the Personalized Emailer only support the quoted-printable encoding so if base64 encoding is used then the Personalized Emailer unable to replace the special marker (e.g. [[NAME]], [[First Name]], etc). Please see below a sample of Mime header with base64 encoding.

Mime.822 file with UTF-8 encoding

quote:

---

Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: base64
Content-Disposition: inline; modification-date=”Tue, 23 Apr 2007 23:50:22
+1000″

RGVhciBbW05hbWVdXQ==

---

The Personalized Emailer solution need to updated to support base64 encoding. We have added this issue and enhancement request into our database.

In the meantime, you can use IS0-8859-15 encoding. You need to change the default Mime Encoding to “ISO Default” (Tools- Options – Send – Send Options – MIME Encoding – ISO Default), change the message view encoding by right mouse clicking on the message body then select a encoding. ISO-8859-15 should support the copy rights icon (keystroke: Alt+0169). See the Character Map utility (Start Menu – Programs – Accessories – System Tools) for more keystroke.

Character Map utility, when you click on the character you want to see, in the right hand corner of the screen, it shows you the shortcut keys to type the character directly in your program. To use the shortcut keys, first, make sure you Num Lock is on. Next, hold down the Alt key plus the numbers to create the character. For example, to type the character selected in the above screen, type Alt+0233. When you release the Alt key, the character will appear.

Hope this helps.

Regards,
Advansys Support

[Support 3]

We have tested the solution against GW 7.0.2 (build date: 06/04/07). This solution is working in our environment although we think it require enhancement to specify the charset type.

This solution use fixed “charset=iso-8859-1” and we think it should let end user to change the charset type for the META tag. Our GroupWise encoding is set to IS0-8859-15, you can change the message view encoding by right mouse clicking on the message body then select a encoding.

You can also set the default send message encoding by changing the Tools – Options – Send – Send Options – MIME Encoding.

Whats is your encoding? Please let us know if we have misunderstood you. To clarify the issue, please provide steps to re-produce.

Regards,
Advansys Support

[Support 3]

We have tested the Add On Directory facility on GroupWise client 7.0.2 (build date: 06/04/07) and unable to re-produce the behaviour you have described.

Please make sure the addon.cfg file is valid. See the Distribution Kit documentation (http://www.advansyscorp.com/formativ/formativ%20distribution%20kit.chm) for more information. To isolate the problem, I will suggest you to install the GroupWise client then install Formativ Runtime in a test machice.

Look forward to hear from you. Please let us know if you have any questions.

Regards,
Advansys Support

[Support 3]

Thanks for letting us know about the error. We will test the addon option against GW 7.0.2.

Are you able to execute the stand alone Formativ Runtime installer without the addon option?

Regards,
Advansys Support

[Support 3]

We have demonstrated many GroupWise-based solutions and customization techniques at BrainShare. You can download the example source from the following url:
http://www.novell.com/coolsolutions/trench/14532.html

To consume Web Service in Formativ, I will recommend you to look at the example applet “Dilbert Web Service.vbf” and “Web Service Signature.vbf”.

Hope this helps.

Regards,
Advansys Support

[Author]

Replies