Support 1a

[Support 1a]

Thank you for your questions above. Yes, both the approaches mentioned are technically feasible.

I’ve included some sample code below to help illustrate a couple of points. Firstly, you’ll find some code showing how to attach an existing message to a draft email message. This could possibly be modified to attach a document reference (which is just a message sub-type) to a message. Secondly, the code also shows how to attach a file to a composing message:

' Create and send a message to the current user.
sub AttachMessage(aID)
 
  dim oGWMessage
  dim oNewMessage
 
  on error resume next
 
  if (len(aID) = 0) then
    exit sub
  end if
 
  set oGWMessage = GroupWise.Account.GetMessage(aID)
  if oGWMessage is nothing then
    msgbox "No existing GroupWise message found to attach"
    exit sub
  end if
 
  ' Note: Adding existing messages as an attachment was previously broken. Novell fixed this in
  ' GroupWise 6.5.2.
  if (GroupWise.EnvVersionName >= "6.5.2") then
    Set oNewMessage = GroupWise.Account.workfolder.Messages.Add("GW.MESSAGE.MAIL")
    call oNewMessage.Attachments.Add(oGWMessage, "")
  else
    set oNewMessage = oGWMessage.Forward
  end if
 

  call oNewMessage.Recipients.Add(GroupWise.Account.owner.emailaddress,,0)
  With oNewMessage
    .Subject = "With message attachment"
    .BodyText.PlainText = "This is the body"
  End With
 
  oNewMessage.Send
 
  set oNewMessage = nothing
  set oGWMessage = nothing
 
end sub
  
 
' Create and send a message to the current user. Attach a file from the file system.
sub AttachFile()
 
  dim oFileDlg
  dim oGWMessage
 
  ' Initialize the file open dialog
  set oFileDlg = Utilities.NewOpenFileDialog
  with oFileDlg
    .Title = "File to attach"
    .InitialDir = Utilities.GetDataDirectory
    .DefaultExt = "*.txt"
    .Filter = "Text file(*.txt)|*.TXT"
  end with
 
  ' Exit if the user press cancel from the file open dialog
  if not oFileDlg.execute then
    msgbox "No file selected to attached."
    exit sub
  end if
 
  ' Create a mail message and set the recipient to the login user.
  Set oGWMessage = GroupWise.Account.workfolder.Messages.Add("GW.MESSAGE.MAIL")
  call oGWMessage.Recipients.Add(GroupWise.Account.owner.emailaddress,,0)
 
  With oGWMessage
    .Subject = "With file attachment"
    .BodyText.PlainText = "This is the body"
  End With
 
  ' Attach the file
  call oGWMessage.Attachments.Add(oFileDlg.FileName, fgwFile, "")
  oGWMessage.Send
 
  msgbox ("Message sent with the following attachment: " & vbcrlf & oFileDlg.FileName)
 
  set oGWMessage = nothing
  set oFileDlg = nothing
 
end sub

I would probably recommend the second option – check the subject on send and prompt for input. (but there may be other factors I am unware of they make option 1 the more appropriate approach).

I hope this helps.

Advansys Support

[Support 1a]

Glad to be of assistance.

Version 2.0, scheduled for release at the end of this month, makes working with dialogs much easier. You’ll find a link to the download on our home page if you are interested.

Regards,

Advansys Support

[Support 1a]

Try this code. The Cmd variable needed to be set again down near dialog 2.

Regards,

Advansys Support

'*******************
'Global Constants
'*******************
 
Const cExit =999
Const cDlg1 =101
Const cDlg2 =102
 
'*******************
'Main Routine
'*******************
 
Sub Main(ClientState, GWEvent)
 
  Dim Dlg
  Dim Cmd
 
  '*******************
  'Dialogue 1
  '*******************
  Do
 
    set Dlg = Utilities.NewControlBoxDialog
    with Dlg
     .Caption = "Advansys Formativ"
     .Title = "Dialogue 1"
     .Description = "This is Dialogue 1."
    end with
 
    Cmd = cDlg1
 
    If Cmd = cDlg1 Then
     Select Case Dlg.Execute
       Case Btn1 Cmd = cDlg2
       Case Else Cmd = cExit
     End Select
    End If
 
    '*******************
    'Dialogue 2
    '*******************
    If Cmd = cDlg2 Then
     set Dlg = Utilities.NewControlBoxDialog
     with Dlg
       .Caption = "Advansys Formativ"
       .Title = "Dialogue 2"
       .Description = "Dialogue 2"
     end with
 
     ' ** Set the variable Cmd value to the button pressed **
     Select Case Dlg.Execute
       Case Btn1 Cmd = cExit
                 MsgBox("OK pressed")
       Case Else Cmd = cExit
                 MsgBox("Something else pressed")
     End Select
    End If
 
  Loop Until Cmd=cExit
 
end sub

[Support 1a]

Paul,

Thank you for your question. Unfortunately the trialware expiration cannot be reversed. If you wish to continue evaluating the software, could you please send an email to support@advansyscorp.com.

Thank you,

Advansys Support

[Support 1a]

We haven’t seen any reports like this. The symptoms you report could be indicative of a lack of resources. (i.e. user interface elements such as toolbar buttons dissapearing sometimes mean you are low on some resource).

Which version of Windows are you using? GroupWise is very resource hungry when it comes to certain windows resources. This can be compounded when used with a version of Windows that is resource-limited. The worst are Windows 95 and NT4.0, followed by Windows 98/ME.

Advansys Support

[Support 1a]

Unfortunately Novell don’t expose the native signature data to third parties. While we would dearly love to be able to access this data, our hands are tied for the moment.

All the other issues you raise are addresses in the new version 2.0 signatures applet. It includes a UI for creating both plain text and HTML signatures. You can download a beta from here. You’ll need to download both version 2.0 Runtime (or Admin or Developer, depending on your needs), as well as the V2 Business Solutions Pack.

Regards,

Advansys Support

[Support 1a]

Unfortunately you (nor us) have any control over the sequencing of the on send processing more so than is already exposed. We developed the ‘OnSend’ event to be triggered as late as possible in the send process (even later than is possible if you write a C3PO). GroupWise doesn’t provide third party developers any means to modify the process any further. If you needed to ensure you added your text at the very end of the message you would probably need to develop something that worked on the server (at the MTA level).

Regards,

Advansys Support

[Support 1a]

The only way to do this is via the Formativ Control Panel applet. Select the ‘User Interface’ tab, and select the applet to execute if no portals have been defined (you can also just supply the name of the applet without a path).

This action writes an encoded entry into the registry – see HKEY_CURRENT_USERSoftwareAdvansys Corporationformativ1.0Settings

Value: Portal Folder Default

You could have your installet write this value into the registry on setup.

I hope this helps.

Advansys Support

[Support 1a]

Hello John,

I’ve gone back and checked our change log. Prior to the 26th of November 2003, Formativ would sort items prior to insertion on a toolbar using the help hint. Due to problems and limitations with this approach (and feedback from a number of developers), we changed this behavour to sort by the physical applet file name.

You may wish to check the version of the FSE you are using, and download the latest version from our web site to see if that helps. I know this change is definitely in version 2.0 of the FSE, which is due for release in a couple of weeks.

Regards,

Advansys Support

[Support 1a]

Thanks for that hint John!

Advansys Support

[Support 1a]

Hello John,

Unfortunately no, this setting is not exposed to the portal. However, you may be able to do it via the Window registry. For example, see this Google thread.

I hope this helps.

Regards,

Advansys Support

[Support 1a]

Unfortunately it is not possible to specify where a button appears in relation to a pre-defined GroupWise button. This limitation is bought about by the unreliable means by which existing buttons need to be itentified. (for example, users may have dragged buttons off the toolbar).

The only positional feature currently available is based on the physical name of the applet, in that Formativ adds toolbar buttons based on alphabetical sorting of the physical applet name. This lets you specify the order your buttons appear in relation to other applets installed on the users machine.

I hope this helps.

Advansys Support

[Support 1a]

We agree this is not optimal. This issue will be addressed in a future release.

Regards,

Advansys Support

[Support 1a]

Thank you for your question below.

The only way to unassociate an object (regardless of whether it is a user, OU, Group or Organization) is to edit the objects ‘See Also’ property. You’ll see a reference to the configuration object. Removing this reference will unassociate the object from the configuration object.

We appreciate the lack of a ‘loop-back’ association mechanism cam make it difficult to identify associations between objects, and certainly makes it difficult (if not impossible) to remove the association programmatically. This is something we are looking at for a further release.

I hope this helps.

Advansys Support

[Support 1a]

Thank you for your enquiry below.

The optimal way to assign user-defined data to a message is to use the GroupWise custom field mechanism. Unfortunately, this only works for messages that already exist in the message store. When you are composing a new message, the message does not yet exist in the message store, and therefore you cannot use any of the Object API methods to add a custom field.

You do have a couple of options none the less. You could add an attachment to the message being composed that contained the classification information. You could also insert the classification information somewhere in the body (or subject).

You could also force the user to save the message into Work in Progress. This forces the message to be saved into the message store, at which point you could then add a custom field to the message that stored your classification information.

To answer your last question, pre-built Formativ functions cannot be overloaded to take different parameters. You would need to write your own extended methods, then call the original Formativ method at the appropriate time.

I hope this helps.

Advansys Support

[Author]

Replies