Support 1a

[Support 1a]

I don’t believe so. Attachments are accessed via the native GroupWise Object API Attachment Object. The attachment object doesn’t expose any methods that provide this information for file attachments.

You could possible save out the physical file using the Save method and check the creation date of the resulting file, but I couldn’t tell you if the date returned would be the original creation date, or the date the newly saved out file was created.

I hope this helps.

Advansys Support

[Support 1a]

From the main GroupWise menu, select Help | Formativ Registration Utility. When the registration utility starts, select Formativ Runtime, then enter the registration key you were supplied into the appropriate area at the bottom of the dialog. Repeat the process for the Message Saver pack. You may need to restart GroupWise after this process.

Please let me know if you continue to experience a problem.

Advansys Support

[Support 1a]

The Distribution Kit contains the information you’ll need. Download a copy from http://www.advansyscorp.com/formativ_distribution_kit.htm.

You can install Formativ silently via the installer. We also provide sample Zen AXT files to make distribution via ZEN easier.

Advansys Support

[Support 1a]

Client.ClientState.SelectedMessages is documented at http://developer.novell.com/ndk/doc/gwc3po/gwc3penu/data/hye3ji8g.html

The line set iMessage = iMessages.item(cMsg) sets iMessage to a native GroupWise Object API Message object. A native GroupWise Message object is a different thing to a ComposingItem object. The ComposingItem object has a property called .To_. The native Object API Message object does not. By accessing the Client.ClientState.SelectedMessages collection, you are working with native Object API message types.

The native Object API Message object is documented at http://developer.novell.com/ndk/doc/gwobjapi/gwobjenu/data/hrgfssmm.html. Please see this link for the properties you can use. Note that you will need to work with the Recipients property of the message object in order to access the ‘To’ information.

I hope this clarifies the situation.

Regards,

Advansys Support

[Support 1a]

This message appears when a new integration has been registered, but may not actually take affect until GW has been restarted. The message will appear only once.

There is no Formativ setting you can use to suppress this message. However, you could probably suppress it by ensuring the following key and values are in the Windows registry (this key is specific to the email ‘OnSend’ event):

HKEY_LOCAL_MACHINESOFTWARENovellGroupWise5.0C3PODataTypesGW.MESSAGE.MAILAdvansys.formativEvents

Empty string values:

GW#C#COMPOSE
GW#C#FORWARD
GW#C#OPEN
GW#C#REPLY
GW#C#RESEND

This message has been removed in Formativ 2.0.

Advansys Support

[Support 1a]

Thank you.

Advansys Support

[Support 1a]

Thank you for your posting above. Could you please elaborate as to what you mean by ‘unable to make applets in the Formativ Central Admin’? Do you mean you are unable to create new applets at all, or you are unable to add applets to an applet library you defined in ConsoleOne?

It would also assist if you could email the Formativ Configuration information from the machine you are trying to use to create/publish the applets. Start GroupWise, then from the main GroupWise menu select Help | About Formativ. When the About box appears, select the configuration page. Press the ‘Copy to Clipboard’ button on this page to copy the config information to the clipboard. Finally, paste the info into an email message to:

support@advansyscorp.com

Kind regards,

Advansys Support

[Support 1a]

It sounds like you might be confusing the CurrentItem object with the native GroupWise Message object. The CurrentItem.To_ and CurrentItem.Sender properties are properties of the CurrentItem object. The CurrentItem property is accessed via:

Set iMessage = GroupWise.ComposingItem

This is only valid if the currently selected item is being composed.

On the other hand, the native GroupWise Message object, which is used to access messages that already exist in the message store (99% of messages you deal with) is different. It doesn’t have a .To_ property, for example. This would explain the error about an unsupported property.

The properties available to you when using a Message object are documented here. Don’t forget to look at any message type specific subclass on the same site for message specific properties and methods.

I hope this helps.

Advansys Support

[Support 1a]

Formativ doesn’t expose the ability to change the association via switches. You would need to re-assign the association by writing the appropriate entries in the registry. You’ll find details by searching http://www.msdn.microsoft.com/

Advansys Support

[Support 1a]

This has been addressed via email.

[Support 1a]

Create a new applet. On the editor toolbar in Formativ, press the ‘Forms’ button. Create a new form from the dialog shown. The visual forms designer appears. Drag and drop components from the palette onto the form.

A brief introduction to the forms designer can be found in the readme.txt installed with the beta.

I hope this helps.

Advansys Support

[Support 1a]

We just use the WISE Installation System to build applet installers. You could use any installation system you feel comfortable with.

Your installer will need to determine the local applets location. We do this by first chacking the registry to see if the following key/value exists:

HKEY_CURRENT_USERSoftwareAdvansys Corporationformativ1.0Settings

Value: Local Scripts

If this value exists, copy the applet to that location.

If this value doesn’t exist, you need to dynamically determine this location. Use the facilities available in your installer to determine the location of the users ‘My Documents’ location. Then append “AdvansysFormativApplets” to the end of this location.

I hope this helps.

Advansys Support

[Support 1a]

I’ve not looked at the White Pages example for some time. What happens when you display contacts that don’t have name, phone, etc. fields?

Advansys Support

[Support 1a]

I’ve seen this type of thing happen when the focus shifts to another control or window. Try calling GroupWise.FocusSet(fcsMessage, “”) to ensure the focus is in the message body prior to calling the position functions.

I hope this helps.

Advansys Support

[Support 1a]

Thank you for your question. I can’t duplicate this exactly without having all your code, but I suspect the problem may lie in the line:

 exportPath = Utilities.AddBackSlashToPath(getExportDir) 

The function getExportDir returns an empty string if the user cancels the directory select dialog. However, the line above will at the very least set exportPath to equal “”, even if the user presses cancel. This means the test:

if exportPath = ""

is never true. You’ll need to do that test before you call AddBackSlash to path.

I hope this helps.

Advansys Support

[Author]

Replies