Support 1

[Support 1]

We cannot reproduce the problem here. Does the error come up for all or only some messages?

If WriteIntoCell fails only with some messages, you may wish to send an email to support@advansyscorp.com . If this suits you, I suggest you attach to your email some sample messages that fail. Please note that Advansys treats client test data as strictly confidential.

Have you tried to use the .Text property instead of .Value?

Have you tried using my other suggestion, to replace carriage return/linefeed pairs by a space character? You could experiment with replacing vbCr and vbLf instead of vbCrLf.

I hope this helps you.

Advansys Support

[Support 1]

There are probably several ways you can do this. Here are two:

• Set the Excel cell wraptext to accept hard returns:

  ActiveSheet.Cells(0, 1).WrapText = True

• Before exporting to Excel, remove hard returns:

  iValue = Replace(iValue, vbCrLf, ” “)

I hope this helps you.

Advansys Support

[Support 1]

Thank you for your enquiry.

I created a Formativ applet to run your code. Then I opened the GroupWise rule editor (Tools | Rules | select rule | Edit…), and it displays the following filter expression:

Act on items where
(From  contains 'Admin User') OR
(From  contains 'FAX' and Subject  contains 'Received From')

I found that on sending a message with From = ‘Admin User’, the rule did nothing. Same with From = ‘FAX’ and Subject = ‘Received From Bill & Ben’.

Then I tried creating the same rule manually, using the rule editor. Same filter expression, same action, and it works!

I’m told that using parentheses in a filter expression, ie. with FilterGroupMarker() is flaky. It seems to work manually but not via the API.

The following modified version of your applet appears to do the job. As I understand your requirement, the resulting filter condition is not strictly correct (correctness requires parentheses). It just happens to work because of the order of terms in the expression.

  dim hFilter

  hFilter = GroupWise.FilterCreate(fttInbox, true)

  call GroupWise.FilterGroupBegin(hFilter, bopOr)
  call GroupWise.FilterSetText(hFilter, fldFrom, "Admin User", matSubtext, "", "")

  call GroupWise.FilterGroupBegin(hFilter, bopAnd)
  call GroupWise.FilterSetText(hFilter, fldFrom, "FAX", matSubtext, "", "")
  call GroupWise.FilterSetText(hFilter, fldSubject, "Received From", matSubtext, "", "")

  call GroupWise.RuleCreate("", "TEST", racNewItem, "", hFilter, btoDontCare)
  call GroupWise.RuleAddActionForward("", "TEST", "gwadmin", "", "", _
    "Forwarded by Fax Rule", "", "", "")

  ' Delete the filter handle
  GroupWise.FilterDelete(hFilter)

Interestingly, the above works even though FilterGroupEnd() is not used.

I hope this helps you.

Advansys Support

[Support 1]

This query has been answered by direct email.

Advansys Support

[Support 1]

This query is being answered by direct email.

Advansys Suppport

[Support 1]

Thank you for your enquiry.

Which version of Formativ Runtime do you have installed? To the best of my knowledge, the latest version has Quick Config loading solutions only in the Local folder. So if Add Signature.vbf is in the Common folder (and it will be if you chose to install for All Users), then it will not appear in Quick Config.

The documentation for the solution became outdated with the release of Formativ 1.6, and I apologize for the frustrating situation. In fact, I think the solution has created a completely different folder on your system.

Add Signature is designed to be used while composing a message. I suggest you open a new composing message, then click the Add Signature button on the window toolbar. It should display a popup with message “Unable to find the signature file…,” quoting the Signatures folder. Then move your userID.html file into the folder shown on the popup, and try again.

I hope this helps.

Advansys Support

[Support 1]

Thank you for your enquiry.

The following code sample uses the GroupWise Token API do create a mail message and change the item type to personal/posted.

  GroupWise.NewMail
  call GroupWise.ItemSetText("X00", itfSubject, "Test message", true)
  call GroupWise.ViewSwitch("", 276, "Posted Message")
  GroupWise.ItemSaveMessageDlg

It does not seem possible to create a personal message using the Object API alone.

I hope this helps.

Advansys Support

[Support 1]

Thank you for the additional details.

I suspect the reason Message Search fails for you is to do with search options on the Date and/or Advanced tabs. The checked options on all tabs are applied during a search.

I notice on the Advanced tab, the default Attributes are Archive and Directory. With Readonly unchecked, the search will exclude message files that are marked read-only, eg. on CD-ROM. So in this case, if the message(s) you are searching for are read-only files, Message Search will indicate nothing was found.

Could you check the Readonly checkbox, and try again?

It may be necessary to release a version update that avoids this problem in Message Search.

I look forward to seeing your results.

Advansys Support

[This message was edited by Support 3 on May 27, 2004 at 09:08 PM.]

[Support 1]

Thank you for your enquiry regarding Message Saver Pack. We value your feedback and will try to promptly resolve any problems.

I am not sure what you mean by “valid searches.” Could you describe the search behaviour you have seen in more detail? Perhaps with some examples of search text, and the search results?

Thanking you in advance,
Advansys Support

[Support 1]

Thank you for your enquiry.

Unfortunately we do not have a an immediate fix or automated workaround for this problem. In fact, the problem occurs when using the GroupWise Object API to select a message in a shared folder that was created by another user; there is no problem selecting a message in a shared folder which you own.

We are very busy with several projects just now, and we expect to look at this issue in early June, 2004. As soon as we have more information we will post it to this thread.

Advansys Support

[Support 1]

I think CurrentItem.To_ should be assigned a fully-resolved email address (or list of addresses), eg.

  CurrentItem.To_ = "johnfdoe@mortuary.com"

or

  CurrentItem.To_ = "'John F. Doe' <johnfdoe@mortuary.com>"

To do what you require (assuming your address book contains the entry “John F. Doe”), enter text directly into the To: field on the composing message view:

  call GroupWise.ItemSetText("X00", itfTo, "John F. Doe", TRUE)

I hope this helps.

Advansys Support

[Support 1]

You are most welcome, John H.

I agree: feedback and knowledge-sharing are very valuable to Advansys and our Formativ Users and Developers.

Regards,
Advansys Support

[Support 1]

Please refer to the other forum you posted this question to, for my response on this issue.

Advansys Support

[This message was edited by Support 3 on May 02, 2004 at 04:24 PM.]

[Support 1]

I think you are referring to a GroupWise Token API method for obtaining a message date, like:

  dim iDateStr
  iDateStr = GroupWise.ItemGetDate(...)

This method returns a string representation of the date. The Token API also has methods for parsing a date string eg. GroupWise.DateParseDay(), but I notice the online documentation is vague on how to get ItemGetDate() and DateParseDay() to agree on a date format.

We have only a little experience with handling these string-typed GroupWise dates. In fact, we strongly recommend that applet writers avoid processing string dates, due to the date format problem you have discovered.

It is simpler by far to work with a Date variable in your Formativ scripting, and to extract date components as necessary using VBScript functions like Day(), Month(), Year(). This is why the example applet in my earlier post uses the Formativ object model (Client.ClientState) to obtain a reference to the relevant message.

Note: if you have already obtained a message ID string using the Token API, you can obtain an object reference to the message as follows:

  dim iMessageID
  dim oMessage
  ' Initialize iMessageID
  ' ...
  set oMessage = GroupWise.Account.GetMessage(MessageID)

Note: you can find more information about the ClientState object in the Applet Structure section of the Formativ Programmers Guide.

Once again, thank you for drawing attention to this gotcha.

Regards,
Advansys Support

[This message was edited by Support 3 on April 21, 2004 at 09:00 PM.]

[Support 1]

Thank you for pointing this out; your suggestion works quite well. Its only limitation is that a Filed Item rule can’t work on messages that existed in the Portals folder prior to creating the rule.

Note that it’s possible to automate, with an applet, the creation of a Rule using the GroupWise Token API (the various .Rule…() methods). It could be useful for an administrator to publish such an applet to all users.

Regards,
Advansys Support

[Author]

Replies