Support 1a

[Support 1a]

Thank you for your feedback. Unfortunately, the GroupWise client does not allow third party developers to modify the smaller icons (such as the attachment icon) used in the message list.

If you upgrade to GroupWise 6.5 it might be possible to use the new categories feature in conjunction with the notes to make identification of such items easier.

Advansys Support

[Support 1a]

Formativ 1.5 cannot be used to selectively block commands other than the Send event. However, Formativ 1.6 will have the ability to selectively block events, including the delete message event. This means it will be trivial to write an applet that stops users from deleting items from there account.

Formativ 1.6 will be available prior to BrainShare (April 13-18) and it will be a free upgrade for Formativ 1.5 users.

Please watch the web site for updates.

Advansys Support

[Support 1a]

I don’t think it’s going to be in the 6.5 API – we’ve had the details of that for some time.

Unless I’m missing something, I suspect it’s something that will need to be added by Novell.

Advansys Support

[Support 1a]

I notice you have already asked this question in Novell’s support forums. As I was going to ask in the same forum, lets wait and see what responses are forthcoming.

Advansys Support

[Support 1a]

I’ve checked the GroupWise API, and cannot locate any calls that would allow for the automatic creation of IMAP or NNTP folders. Subsequently, Formativ won’t be able to create them either.

I’ll ask Novell about this and post a reply back in this thread.

Advansys Support

[Support 1a]

A standard ‘template’ applet does exist that performs this task. It has been provided by direct email.

Advansys Support

[Support 1a]

Possible but not easy. GroupWise messages don’t have a message ID before they are sent that can be used with the print method. You can’t use the composing item ID “X00” either. Basically you would need to locate the message you just sent from the sent items folder, obtain it’s real message ID, then print it.

Advansys Support

[Support 1a]

Not without editing the applet source code. The Cool Solutions applets are not generally fully featured in terms of customization features, such as adding new fields.

If you have any development experience available to you, you should be able to change the fields displayed fairly easily. If not, Advansys or another third party developer with Formativ experience could make these changes for you.

Regards,

Advansys Support

[Support 1a]

We have recently updated the applet to use the field you mention. It will be made available from the support pages in the very near future.

If you would like a copy of the updated before it is officially posted to the web site, please send an email to support@advansyscorp.com.

Advansys Support

[Support 1a]

We discovered an example config.ini installed with the Distribution Kit contains a reference to an obsolete value name. The documentation in the Kit is correct.

One of the examples in the Distribution Kit contains the following line:

Install Local Macros and Data=0

This should read:

Install Local Applets and Data=0

The first version is not recognised by the installer, resulting in the BSP applets being installed. The second (correct) version works.

Advansys Support

[Support 1a]

We discovered an example config.ini installed with the Distribution Kit contains a reference to an obsolete value name. The documentation in the Kit is correct.

One of the examples in the Distribution Kit contains the following line:

Install Local Macros and Data=0

This should read:

Install Local Applets and Data=0

The first version is not recognised by the installer, resulting in the BSP applets being installed. The second (correct) version works.

Advansys Support

[Support 1a]

Please see my response to this in the new thread you started.

Thanks,

Advansys Support

[Support 1a]

Thank you for your posting. I have tried to duplicate this without success. I am able to exclude installation of the BSP applets via a config.ini file.

There must be some other variable not present when I attempt to duplicate this. Could you please email a copy of the config file you are using to support@advansyscorp.com and I’ll try again using your file.

Regards,

Advansys Support

[Support 1a]

Unfortunately there is currently no means to extract a list of defined rules. This is an ommision in the GroupWise API’s, and is something we have requested Novell add.

Depending on what you need to do, there are other commands available that allow you to work with rules.

For example, to check if a rule with a given name exists, you can use:

GroupWise.RuleExists()

To delete a rule when you know it’s name, use:

GroupWise.RuleDelete()

To execute a rule when you know it’s name, use:

GroupWise.RuleExecute()

These are all documented in the Formativ Language Guide.

I hope this helps.

Advansys Support

[Support 1a]

No problems – glad to be of assistance.

Advansys Support

[Author]

Replies