Support 1a

[Support 1a]

Unfortunately the Name Completion Control, TGWNcc, (supplied by Novell) does not let you set an initial value in the control.

We have worked around this to some degree in the past by using a standard text box (which you can set the initial value), coupled with an instance of the address book control. The address book control has the same limitation as the NCC in that you can’t initialize it’s initial state, but this is less of a problem given the use of a standard text box to display the selected address.

Advansys Support

[Support 1a]

The technique depends on how the message you want to attached the CSV file has been created.

If you used commands like GroupWise.NewMail() to create a visible email message, you would use GroupWise.ItemAttachmentAdd(). See the Formativ Language Guide for details.

If you used the Object API to create a message, you would use the message properties Attachments collection. See http://developer.novell.com/ndk/doc/gwobjapi/gwobjenu/data/hej0zz9f.html#hej0zz9f for details.

I hope this helps.

Advansys Support

[Support 1a]

Msg.To_ is a wrapper around the token ‘ItemGetText()’, using ‘X00’ as the message ID.

Given AddressBookResolveFullName() does not work for you, I suspect you may need to submit an enhancement request to Novell. Unfortunately third parties are unable to add this type of functionality.

Regards,

Advansys Support

[Support 1a]

Thank you for your post. The second problem may be related to the first. Could you please let me know the formatted capacity of the CD’s you are using?

Advansys Support

[Support 1a]

Thanks for the additional suggestion LP.

Advansys Support

[Support 1a]

The methods you mention are wrappers around GroupWise API functions. Unfortunately we can’t add new core functionality to the client – we can only add an abstraction layer that makes it easier to access the underlying API.

That being said, have you looked at GroupWise.AddressBookResolveFullName()? The Formativ implementation is a warpper around the following GroupWise token:

http://developer.novell.com/ndk/doc/gwtoken/gwtokens/data/h6g2rtlu.html#h6g2rtlu

Advansys Support

[Support 1a]

What is the exact problem you are having?

Advansys Support

[Support 1a]

Unfortunately drag and drop operations do not appear to trigger C3PO events in the GroupWise client. I understand this has been reported to Novell previously.

I’m sorry I couldn’t provide a more helpful response.

Advansys Support

[Support 1a]

Unfortunately no, you can distribute support files via eDirectory. You have to use another mechanism to get these files installed on your end-users machines.

One technique we have used is to embed the files into the applet itself, then have the applet recreate the files on the end users machine. This works well assuming the files aren’t too large. (which could cause your applet to bloat).

Take a look at the Utilities.FileToSource() and Utililies.SourceToFile() methods in the Language Guide. In a nutshell, Utilities.FileToSource() takes the path of an existing file and returns a string formatted in such a way you can embed it as a constant in your applet.

You then use tililies.SourceToFile() to convert the string constant value defined in your applet to create a file on disk at runtime.

I hope this information helps.

Regards,

Advansys Support

[Support 1a]

If the tokens mentioned above only resave the message, then I am not aware of any way to make this happen. It sounds like you only see the dialog the first (and only the first) time the message is saved (i.e. added to the message store).

You may wish to ask this question in one of the Novell DeveloperNet forums, as this is GroupWise API/Client feature question. Those forums are monitored by Novell engineers who may have other suggestions for you.

Advansys Support

[Support 1a]

Try

GroupWise.ItemSaveMessageDlg()

or

GroupWise.ItemSaveMessageDraft(“”)

Advansys Support

[Support 1a]

We will contact you via direct email regarding this issue.

Advansys Support

[Support 1a]

The GroupWise Object API (which is what you are using here via Formativ) tends to expose collections using ‘1’ based arrays. This means the first entry has an index of 1.

I would suspect then, that you should be able to access the entries using ‘1’ and ‘2’.

Are you sure you are using the same book, and that the addressBookEntries collection is current?

Don’t forget a ListBox uses ‘0’ based arrays, so the first item has an index of 0, the second 1, etc. You may need to take this into account.

Advansys Support

[Support 1a]

There are no API’s provided by Novell that do this. The only I can think of would be to update the message in some way (i.e. add a space to the subject, then remove it) which might cause the client to recognise the message as requiring a resave.

Regards,

Advansys Support

[Support 1a]

Thank you for the update and additional information. The problem appears to lie with the GroupWise Admin API, which is used to build the system view, and some nuance of your GroupWise system. Unfortunatly, the Admin API is the only API currently available to ennumerate a GW system.

We are looking at adding ‘system caching’ support into the tree view so that it doesn’t have to ennumerate the entire system each time the solution is used. While this won’t fix any Admin API problems, it does mean any issues would be rarely seen, as the system view would be nearly always read from the cache.

I would be interested to hear if you continue to experience any issues accessing the system tree for the remainder of the trial.

Regards,

Advansys Support

[Author]

Replies