Support 1a

[Support 1a]

Unfortunately I cannot reproduce this using your applet. The data is correctly encrypted and decrypted using 0 and the values you provided for the low and high keys.

I wonder if using the Clipboard is a factor. Here is the code I used to test the method, which uses a MsgBox to outout values. I would be interested to see if this works for you:

Sub Main(Client, GWEvent)

   dim aPlain
   dim iHighKey
   dim iLowKey

   sPlain = "this is just an example"
   iHighKey = 145
   iLowKey = 1234

   sEncrypt = utilities.DESEncryption(fEncrypt, iHighKey, iLowKey, sPlain)
   sDecrypt = utilities.DESEncryption(fDecrypt, iHighKey, iLowKey, sEncrypt)
   MsgBox("sPlain = " & sPlain & vbCrLf & "sEncrypt = " & sEncrypt & vbCrLf & "sDecrypt = " & sDecrypt & vbCrLf)

End Sub

Advansys Support

[Support 1a]

As mentioned above, most message properties are read only when accessing incoming & sent items – including Task priority. Attempting to set such properties on a readonly item will result in an exception, which is why the rest of your code does not execute.

TaskPriority can be set for draft & personal messages only. Here is some code…

if (mMsg.BoxType = fgwpersonal) or (mMsg.BoxType = fgwDraft) then
  mMsg.TaskPriority = 2
end if

Advansys Support

[Support 1a]

Unfortunately GroupWise doesn’t expose the MIME representation of every message – most internal messages, for example, won’t have a MIME representation.

Access to MIME data for messages that do expose them is limited. The MIME data needs to be accessed via the MIME.822 attachment where they exist. You need to save the attachment to disk, then manually process the file. Note you cannot edit a MIME file of a received message then re-attach it to the same message. You would have to re-create the message from scratch – a non-trivial excercise.

None of these limitations are related to Formativ – this is just the way the GroupWise client works.

Regards,

Advansys Support

[Support 1a]

When you are working with messages in the message store, you generally use the standard Object API objects. The Object exposes all the properties you need. The Task object is documented here:

http://developer.novell.com/ndk/doc/gwobjapi/index.html?gwobjenu/data/h7ikbsqg.html

The Body property is exposed on the Message Object type (Task is a sub-class of Message). Message is documented here:

http://developer.novell.com/ndk/doc/gwobjapi/index.html?gwobjenu/data/h7ikbsqg.html

Note you can only change the body and priority of Posted items – these properties are going to be read-only on a non-poseted item.

I hope this helps.

Advansys Support

[Support 1a]

Excellent! Please let us know if you require any further assistance.

Regards,

Advansys Support

[Support 1a]

This should be possible using the NativeInterface property of a portal. The nativeInterface property gives you the IWebBrowser2 interface for the portal, which in tern has an ExecWB() method. You can use this method to print the contents of the portal.

Here’s an example:

Sub Main(Client, GWEvent)

   dim iPortals
   dim iPortal1
   dim iret

   Set iPortals = GroupWise.PortalManager.Portals
   Set iPortal1 = iPortals.Item("PORTAL1")

   If iPortal1 is Nothing Then
     Set iPortal1 = iPortals.Add
     iPortal1.Caption = "Advansys Home"
     iPortal1.TabCaption = "Advansys"
     iPortal1.ID = "PORTAL1"
     iPortal1.NavigationControlsEnabled = True
     iPortal1.URLInputEnabled = True
     iPortal1.Url = "www.advansyscorp.com"
   else
     MsgBox "Found it - try to print it"
     const IDM_PRINT = 6
     call iPortal1.NativeInterface.ExecWB(IDM_PRINT, -1)
   End If

End Sub

This is somewhat incomplete, because the printer selection dialog still appears. I understand it should be possible to turn this off by using flags. See the Microsoft Documentation on the IWebBrowser2.ExecWB() method, and the IDM_PRINT command. More information is available at http://msdn.microsoft.com/workshop/browser/mshtml/reference/constants/idm_print.asp.

I hope this helps.

Advansys Support

[Support 1a]

Great news. Feel free to post any questions you have.

Advansys Support

[Support 1a]

The components on the GroupWise tabs of the component palette are Novell’s ‘GroupWise Controls for ActiveX’. Legal restrictions preclude us from re-distributing documentation for these controls. You can find documentation at:

http://developer.novell.com/ndk/gwactive.htm

Regards,

Advansys Support

[Support 1a]

This function does not let you save the files using different names. You would have to rename the files afterwards (or use the native Attachments collection, which would let you provide the name to save each file as).

Use the RenameFile() function to rename a file. It returns a boolean if the rename works. Use it like this:

if RenameFile("c:transferoldname.htm", "C:transfernewname.htm") then
     MsgBox "File was renamed"
   end if

I hope this helps.

Advansys Support

[Support 1a]

quote:

---

Is there a way then to remove specific addresses from the TO field without having to use the problematic ItemSetText() to re-insert or replace names into the field?
Maybe there is a way to cross out these addresses deliberately so that message aren’t sent there?

---

Unfortunately not. When you are composing a message, the ItemSetText() style tokens are all that is available.

It might be possible to solve your problem by delaying the point at which you add the system addresses. Other customers do a similar thing, except they add the system addresses in the ‘OnSend’ event. This way the users don’t get the opportunity to manually remove the system addresses.

Regards,

Advansys Support

[Support 1a]

Hello Patric,

Thank you for your posting above. You can download a version of the Today View source code as part of the Examples Pack. See http://www.advansyscorp.com/formativ_example_applets.htm for more information.

Regards,

Advansys Support

[Support 1a]

We agree these resoures should be installed by default, and we will possibly do this in the version of Formativ that will support GroupWise 7. Your offer of a translation is kind, but we should be able to extract the translations ourselves once we are able to obtain a full set of multilingual clients.

Regards,

Advansys Support

[Support 1a]

We don’t have a specific example, but you would use the XML DOM to access the elements in the XML. Formativ exposes the native Microsoft XML DOM, which means you can access all the members of the IXMLDOMDocument2 interface. See the following URL for more details:

http://msdn.microsoft.com/library/default.asp?url=/library/en-us/xmlsdk/html/2dfe145d-c9a5-47d9-8ae3-7722befedd90.asp

In a nutshell, you would call Utilities.XMLDom in your applet to create an instance of the XML DOM wrapper. You would then load the XML from the body string of the message with a call like this:

set oDOM = Utilities.XMLDom

oDOM.LoadFromString(iMsg.BodyText.PlainText)

You would then be able to access the XML via the standard XML DOM interface. You should be able to find examples of this on the microsoft Web site mentioned above. You can also use XPath to locate specific nodes. Again, this is documented at the site mentioned above.

Regards,

Advansys Support

[Support 1a]

Thank you for your posting. You have two general options when you need to store many custom field values. Both involve the creation of a custom message type as you state.

The first approach is to create custom fields in the message, and store the values in the fields. This is purely a native GroupWise Object API technique, and is beyond the scope of what I can describe here. Nonetheless, have a look at: http://developer.novell.com/ndk/doc/gwobjapi/gwobjenu/data/hrgfssmm.html, specifically the Fields property of the message object. In a nutshell, you need to create a field definition associated with an account if it doesn’t exist, then create one or more fields associated with the message via the Fields property. Your applet reads and writes values to these fields.

The second approach, and probably the one I would recommend, is to use XML to store the field values, then store the XML in the body text of the custom message. This has the advantage of not having to define potentially large numbers of field in your GroupWise system, and is more easily extensible. When the message is opened by the recipient, your applet parses the XML contained in the body of the message and populates the custom form. You can find an example of creating a message containing XML data in the example applet called ‘TUT333 – MIIRalert.vbf’.

I hope this information is sufficient to get you started. Feel free to post any specific questions you may have.

Regards,

Advansys Support

[Support 1a]

This sound like you are using the GroupWise Admin API(?), which is not actually implemented by Formativ. I suspect you may need to ask this question in a Novell support forum.

Perhaps you could post some sample code to help us determine where the best place would be to obtain support.

Regards,

Advansys Support

[Author]

Replies