Support 1

[Support 1]

I am not aware of any GroupWise API that reports the active date/time format. Unfortunately, it seems the only available option is the token:

  GroupWise.PrefDateTimeFormat()

You can use this token to force the formats (presumably using the notation in the Customize Regional Options dialog in Windows). More useful though would be a way to make GroupWise use the System formats by default. Unfortunately, I do not know of a way to do this by way of a scripted solution.

Regards,
Advansys Support

[Support 1]

I am glad to have been able to help.

Another option, that avoids potential internationalization problems, is:

  call GroupWise.ViewOpen(vwtCalendar, TRUE, "")

Regarding the date format issue, I am not sure what you mean by ‘wrong under certain circumstances.’ As I understand it, GroupWise always uses the formats specified on the Format tab of the Date Time Options dialog. If the default is the US date format, this is a flaw; I would expect the default format to follow the System format.

Please see your Forum thread GroupWise vs system date format for further comments on the date format.

Regards,
Advansys Support

[Support 1]

Thank you for your enquiry.

In the following, I make the following assumptions; that you require:

• a new button on the GroupWise client main toolbar;
• the appointment to be selected in the message list;
• clicking the new button opens a calendar view matching the appointment start date.

'-------------------------------------------------------------------------------
const VIEWTYPE_CALENDAR = 1

Sub Main(Client, GWEvent)

  dim iStartDate
  dim oMessage

  ' Suppress error handling on .CommandMessage if no message is selected.
  on error resume next

  set oMessage = nothing ' initialize to something we can compare
  set oMessage = Client.ClientState.CommandMessage

  ' Turn on error handling.
  on error goto 0

  if oMessage is nothing then
    MsgBox("There is no message selected.")
  else
    ' Ensure it's an appointment.
    if InStr(1, oMessage.ClassName, "GW.MESSAGE.APPOINTMENT", vbTextCompare) = 1 then
      iStartDate = oMessage.StartDate
      call GroupWise.ViewOpenNamed("Appt (sm)", VIEWTYPE_CALENDAR, "")
      call GroupWise.DateAbsoluteGoTo(Day(iStartDate), Month(iStartDate), _
        Year(iStartDate))
    else
      MsgBox("Your selected message is not an appointment.")
    end if
  end if
  set oMessage = nothing

End Sub
'-------------------------------------------------------------------------------

You can see the available view names, like ‘Appt (sm)’, listed in the drop-down menu of the Open Calendar button on the GroupWise toolbar.

I hope this helps.

Advansys Support

[Support 1]

You are right about this being an XML issue. We have done some testing, and have managed to reproduce the problem. The problem is to do with characters treated as ‘special’ by XML.

We have updated the applet (Template System) to provide support for these special characters. It will be made available for download from here within the next few days. In the meantime, you can obtain a copy of the applet by sending an email to support@advansyscorp.com.

Thank you again for your valuable feedback.

Regards,
Advansys Support

[Support 1]

Dear Stewart,

Thank you for you enquiry. Unfortunately there is no dedicated, self-contained reference for learning Formativ solution development.

I would suggest that you use the following resources, remembering also that the quickest way to learn is by doing – ie. create your own applet exercises.

• Formativ Programmers Guide;
• Reference: Formativ Language Guide. It’s particularly worth studying the Utilities object, and the FileSystemUtils and StringList objects;
• VBScript in a Nutshell, by Childs et al, O’Reilly & Associates, Inc. We have found this to be both concise and comprehensive on the language;
• Reference: VBScript Language Reference (bundled with Formativ Developer/Admin);
• Reference: Novell GroupWise Object API. It’s particularly worth studying the Account and Message objects, and the Filter Expression reference;
• Reference: Novell GroupWise Token API;
• The example solutions at Formativ Applet Central;
• Use the Search feature in these Support Forums to review discussions on a specific issue;
• Post your queries to these Support Forums.

I hope this helps.

Regards,
Advansys Support

[Support 1]

Dear Matt,

Thank you for your enquiry. We are not aware of this problem with the Template and Signature Solutions.

I need a bit more information, please:

• Does this problem occur with an HTML-format composing message? (A wild guess at a solution: perhaps you could solve this problem by using the HTML 4.0 entity reference “&” instead of “&”.)
• I don’t understand what you mean by “&” can be used instead, ie. how should it be used?

Regards,
Advansys Support

[Support 1]

Thank you for your enquiry.

I think you are referring to the popup context menu that appears in the attachments pane of the message view.

Unfortunately, RemoveMenuItem does not work with context menus. You may wish to look into disabling the Windows ‘Open With…’ dialog, though I do not know if this is possible.

Regards,
Advansys Support

[Support 1]

We have received more information on this from Novell. It seems that,

quote:

---

since the remote (or caching) database has no connection to the Domain or Post Office databases, there is no way to get the Distinguished Name.

---

It may be worthwhile coding your applet to allow for both online or remote/caching modes. This probably means using the VBScript statement

  on error resume next

to suppress standard error-handling, so that your applet can control its user interface elegantly in all situations.

I hope this helps.

Advansys Support

[Support 1]

I created a simple test applet that calls Groupwise.Account.DistinguishedName. Using this in caching mode leads to the GroupWise API raising the following error:

quote:

---

Account.Object
[text snipped]
The root account is remote.

---

This behaviour appears to be a defect in the GroupWise API. Unfortunately, all we can do is to inform Novell of this. We will post an update to this thread when we have more information.

Advansys Support

[Support 1]

Thank you for your enquiry.

This error most likely is caused by changing the filename of the applet. We have a new version of the applet that should be posted to Cool Solutions within the next week.

In the meantime, I will send you the updated applet by direct email.

Advansys Support

[Support 1]

It is possible that your installation of Formativ has no obvious GroupWise integrations. For example, if you are using Formativ Express/Runtime, and no installed applet has an integration with GroupWise. With Formativ Developer/Admin, the GroupWise client should include a new ‘Applets’ menu, and a toolbar button to launch Formativ Central.

Regardless of your edition of Formativ, the GroupWise Help menu should have the item About Formativ… If it is there, please send us your Formativ configuration. To do so, select About Formativ… and when the dialog appears, go to the Configuration tab. Then click the button Copy to clipboard and paste the text into your reply. (We prefer that you email us configuration data directly, to support@advansyscorp.com .)

Advansys Support

[Support 1]

In the past we’ve had reports of other strange behaviours in Formativ that went away after reinstalling. I’m not familiar with Workshare but the scenario is all too common: installing software on MS Windows breaks an existing software installation.

Thanks for letting us know how it went.

Regards,
Advansys Support

[Support 1]

I do not know what is causing this strange behaviour.

Could you send us your Formativ configuration? To do this, go to the Help menu on the GroupWise client, then select About Formativ… When the dialog appears, go to the Configuration tab, click the button Copy to clipboard then paste the text into your reply. We would prefer that you send an email to support@advansyscorp.com.

Thanking you in advance,
Advansys Support

[Support 1]

We have added your suggestion to our wish list for discussion with Novell at BrainShare.

Thanks for the additional feedback.

Kind regards,
Advansys Support

[Support 1]

Thank you for your query.

The technique required to create email in a proxy account is similar to that from your previous post on EmailAddress from ProxyAccount.

Here is an example:

' This example assumes the GroupWise client has been proxied to another account.
Sub Main(Client, GWEvent)

  dim oAccount
  dim oDraft
  dim oSent

  set oAccount = Client.ClientState.CurrentAccount
  set oDraft = oAccount.WorkFolder.Messages.Add("GW.MESSAGE.MAIL", fgwDraft)

  call oDraft.Recipients.Add(oAccount.Owner.EmailAddress, "NGW", fgwTo)
  oDraft.Subject.PlainText = "This was created using Formativ"
  oDraft.BodyText.PlainText = "This is the body text of the email message"
  set oSent = oDraft.send

  set oSent = nothing
  set oDraft = nothing
  set oAccount = nothing

End Sub

I hope this helps.

Advansys Support

[Author]

Replies