Support 1a

[Support 1a]

You cannot unflexalock an applet. It is a security feature.

We have a large number of sample applets available in the Developer Examples pack and the BrainShare examples pack. Have you looked at these?

Please feel free to post any ‘how do I’ questions and we’ll see if we can come up with an example.

Regards,

Advansys Support

[Support 1a]

Thank you for your posting. If you mean the drop down proxy access list available from the ‘From’ button on a composing message, no, I don’t believe it is possible to remove these entries. GroupWise does not provide any API to remove/disable this feature.

A large percentage of the information on this control comes from the proxy rights a user has granted to another user. You could remove/restrict this information using something like our Enterprise Proxy solution.

I hope this helps.

Regards,

Advansys Support

[Support 1a]

This sounds like a problem with the GroupWise command that reports if you are in plain text or HTML mode. I recall some issues with this token with some earlier GroupWise clients.

I need to know the exact release of the GroupWise client you have. Start GroupWise, then from the main menu select Help | About Formativ. When the about box appears select the configuration tab. Press the ‘copy to clipboard’ button, then paste the contents of the clipboar into a message addressed to support@advansyscorp.com and we’ll take it from there.

Regards,

Advansys Support

[Support 1a]

We may be able to assist if you send a working (as a far as possible) sample applet to support@advansyscorp.com.

As you are using the native Object API here, you could also ask over in Novell’s Object Usenet forum.

Regards,

Advansys Support

[Support 1a]

It sounds like a problem with the technique you are using to show and dismiss the forms. It is normally best to show a form using the .ShowModal() method, and dismiss them via the modalresult property of each button (i.e. set the modalResult property of the Cancel button to MRCancel).

We would be happy to take a look at your applet if you send it to support@advansyscorp.com.

Regards,

Advansys Support

[Support 1a]

This sounds peculiar. When logged in as one of the secondary users, can you see the ‘About Formativ’ menu item on the GroupWise Help menu?

Could you please send me the Formativ configuration information from a machine when logged in as a secondary user. Assuming you can see the ‘About Formativ’ menu item, select it. When the about box appears, select the configuration tab. Press the ‘copy to clipboard’ button, then paste the content of the clipboard into a message back to support@advansyscorp.com.

Thank you.

Regards,

Advansys Support

[Support 1a]

I suspect you have come across a somewhat obscure bug in GroupWise another user reported recently. It appears that a particular sequence of HTML involving the Marquee tag can cause the GroupWise spell checker to throw an access violation. It does depend on the layout of the HTML. This is nothing to do with Formativ. You could test this by composing a new HTML message, then pressing F11 and retrieve the HTML signature file into the message. Once retrieved, spell checking the message should cause the AV to occur.

Novell were able to duplicate it and allocated it defect no: 414866 against the GroupWise 6.5.5 client. They reportedly fixed it in GroupWise 7.

The only workaround is to remove the marquee tag from the HTML (which is a shame, because that’s what causes the night scrolling effect), or spend the time playing with the HTML to try to find a combination that doesn’t cause the problem.

Regards,

Advansys Support

[Support 1a]

Thank you for your posting. The only known issue that may a factor here related to versions of Formativ Runtime prior to build 2.0.0.14. With earlier builds, an access violation could occur on shutdown due to an interaction with the Microsoft Script host debugger. The fix was to install a version 2.0.0.14 or newer.

If this does not solve your issue, I would suggest you uninstall Formativ, manually delete any files left over in the ‘C:Program FilesAdvansysFormativ’ folder, then re-install.

Regards,

Advansys Support

[Support 1a]

Dear Brian,

You should be able to upgrade the client from 6.0 to 6.5 without harming the Formativ client installation. We have received feedback from users indicating this upgrade worked without any problems. (This, of course, depends on the technique you use. A ‘vanilla’ upgrade using the standard GroupWise installer should be fine. Performing an upgrade via a Zen snapshot may be a different story).

I would suggest you try a single upgrade using your preferred approach before upgrading your entire installation.

Regards,

Advansys Support

[Support 1a]

You need to use Formativ Creator or Studio to change the values of the text constants in order to change the language of the user interface.

I’m not sure which files you are referring to. Out of the office builds a rule in GroupWise that autoresponds when new items appear.

Regards,

Advansys Support

[Support 1a]

You can add buttons to the GroupWise toolbars using the Integration tab of Formativ Studio or Creator. Consult the Users Guide for full details.

Advansys Support

[Support 1a]

This has been answered in the email sent directly to support.

Advansys Support

[Support 1a]

Let us know how you proceed.

Advansys Support

[Support 1a]

You need to use the Object API to create a new entry – the API does not let you copy existing items. See:
http://developer.novell.com/ndk/doc/gwobjapi/gwobjenu/data/h3r0rhi6.html

as a starting point. The Object API is available in Formativ via the GroupWise.Account() object.

Regards,

Advansys Support

[Support 1a]

You cannot perform a query/find operation by using ThrowToken(). ThrowToken() is designed to accept a string representing a GroupWise token (such as ‘AboutDlg()’. You cannot pass it a query/find string and have it do anything.

To perform a find, you need to pass the query string to one of the Find/Query methods, part of the Object API, which are exposed in Formativ via the GroupWise.Account() object.

For example, the Messages() collection has a Find() method. This method accepts a query string. See the following for more information:

http://developer.novell.com/ndk/doc/gwobjapi/gwobjenu/data/huyzfn9z.html#huyzfn9z

I hope this helps clarify the issue.

Advansys Support

[Author]

Replies