Support 2

[Support 2]

Good news, we have just received word from GroupWise engineering that a fix for this issue has been added to GW14R2FTF.

Kind Regards,

Advansys Support

[Support 2]

We’ve run tests and replicated the symptoms you describe. While adding recipients works if you create a mail message, the same approach fails for the GW.MESSAGE.APPOINTMENT class, whether it is Account.Calendar or Account.Mailbox.

At this point we will need to wait for feedback from Micro Focus.

Kind Regards,

Advansys Support

[Support 2]

Thank you for your post and for the code detail. In case the issue turns out to be related to the GroupWise 2014 R2 API behavior, as a pre-emptive step we’ve alerted the Micro Focus GroupWise team.

We will try to replicate the issue in-house and post our results.

Kind Regards,

Advansys Support

[Support 2]

Hello Daniel,

Thank you very much for your feedback and for sharing the code. Yes, indeed, we had to adapt to the many changes we discovered in GroupWise 2014 and we have worked with Micro Focus engineering to help streamline functionality. Like every choice of technology and new implementations, there are always trade-offs and sometimes unintended consequences.

Our stationery solution uses the FileRetrieve token to load the initial HTML stationery file into a GroupWise draft message and we use the DOM to massage the HTML content it when necessary. Your implementation appears more modular and perhaps offers changes to the message layout at different stages of the process.

We look forward to learning more of your progress and will notify Micro Focus engineering of your efforts and results.

Kind Regards,

Advansys Support

[Support 2]

Hello Daniel,

Thank you for the update and that does make sense. At this stage I cannot think of a reason why you could not manipulate the HTML tag styles/attributes to suit your preview requirements.

We look forward to hearing how you progress.

Kind Regards,

Advansys Support

[Support 2]

Hello, thank you for your request and we will email you the applet source today.

Kind Regards,

Advansys Support

[Support 2]

Hello Daniel and thank you for the positive update. With respect to the EmbeddedWB, there were no Formativ code changes made to this component between version 2.6 and 2.7. As EmbeddedWB is a wrapper for the IE ActiveX, if your code has not changed then it may be the underlying IE component’s behavior has changed.

Before we can provide additional feedback we need to replicate and review the behavior you describe. Are you able to provide the source code for simple test applet which illustrates this issue?

Does the behavior change between Formativ 2.6 and 2.7 regardless of underlying Windows OS version?

You may also use Techsmith’s free Jing software to record a short video of the applet behavior with Formativ 2.6 and 2.7 and send us the links to review.

Techsmith Jing: https://www.techsmith.com/jing.html

Please send information via email to support AT advansyscorp.com.

Kind Regards,

Advansys Support

[Support 2]

Hello Daniel,

Thank you for your quick feedback and we look forward to learning how you progress.

At a convenient time for you, we are certainly interested in learning more about your solution.

Kind Regards,

Advansys Support

[Support 2]

Hello and thank you for your post and the information about your solution, which sounds great. As you have discovered, GroupWise 2014 introduced significant change in the way the GroupWise message view is rendered. More of the user interface functions are combined with the content within a complex HTML/jscript/CSS framework. Unfortunately this means you cannot use the utilities.HTMLDom with the GroupWise 2014 client in the same way as previous versions. There is an alternative approach which we are currently implementing in our Stationery and Multiple Signature applets and I will illustrate the alternative method to Utilities.HTMLDom below.

Sub Main(Client, GWEvent)

	dim gClient
	set gClient = Client

	'When you need to read/write the content of a composing message, use this approach:

	dim iDoc 'HTML DOM Document Object
	dim sHTML

        'Editing access to the IHTMLDocument interface provided by the Internet Explorer browser.
	set iDoc = gClient.ClientState.HTMLEditor 

	' Display the HTML DOM content below DOCTYPE! tag
	sHTML = iDoc.documentElement.outerHTML

	msgbox sHTML
	
End Sub

If you want to get the HTML DOM Document content from a received message, use the following:

'Viewing access to the ITHMLDocument interface provided by the Internet Explorer browser.
set iDoc = gClient.ClientState.HTMLViewer

The GroupWise Client API references for these commands are found here:

http://www.novell.com/document…o/data/hye3ji8g.html

With respect to signature prompt control in GroupWise 2014, we anticipated this requirement and upon request Novell added the IsSignatureAllowed property, which uses SignatureInsertionConstants shown below.

0 – eGWSignatureNone – disables all signature insertions
1 – eGWSignatureWithMessage – allows the signature to be inserted into the message
2 – eGWSignatureWithPrompt – allows the signature prompt at send time
1 – eGWSignatureDefault – currently defined as eGWSignatureWithMessage

A test applet example is shown below.

Sub Main(Client, GWEvent)
   set myClientState = Client.ClientState
   if myClientState.IsSignatureAllowed then
     myClientState.IsSignatureAllowed = 0
     'MsgBox("Signature disabled [" + ToStr(SigState) + "]")
     MsgBox("Signature DISABLED")
   else
     myClientState.IsSignatureAllowed = 1
     'MsgBox("Signature enabled [" + ToStr(SigState) + "]")
     MsgBox("Signature ENABLED")
   end if
End Sub

Novell have made some adjustments for our Stationery and Multiple Signatures solution. We are also implementing the adoDbStream function in our Stationery solution which enables the streaming a file to disk and also to set the character encoding when saving. This can help with preserving UTF8 and ANSI encoded files. If you want further information we can email you directly.

We are interested in learning more your Formativ solution and hope the above information enables you to move past this technical road block. If you wish to send more details via email, please email them to support AT advansyscorp.com.

Kind Regards,

Advansys Support

[Support 2]

Hi Chris,

Thank you for your post. As it is likely to be a configuration/access rights/environment related issue, it is recommended that you reply with any detailed answers to support AT advansyscorp.com.

What was the previous environment under which you ran the Classify Message solution, such as the Windows and GroupWise versions? What has changed with the latest rollout?

Do you have a standard (non-SOE) Windows workstation installation which you can use as a comparison? If so, does the solution work when installing onto this standard Windows workstation?

As the symptoms indicate, the problem is likely to be related to access or folder rights provided to a standard user.

While the applet does not appear for a standard user, do the Formativ Runtime menu entries appear under the GroupWise Help menu?

Formativ works very much like a standard GroupWise C3PO and if solutions are not appearing, it is likely that the standard GroupWise C3PO registry entries do not have sufficient rights or there are insufficient rights to the folders where the applets are stored.

While logged in as a standard Windows user, what happens if you run the GroupWise client as administrator? After you do that once, what happens if you then run GroupWise as a standard user?

For both the admin and standard Windows user login, to assist us troubleshoot the problem, please send us the Formativ configuration information by selecting the GroupWise client’s Help menu, select About Formativ, select the Configuration tab and use the Copy to Clipboard button, then paste the config info into the return email to us at support AT advansyscorp.com.

We look forward to your feedback on the questions above.

Kind Regards,

Advansys Support

[Support 2]

Hi Leon,

We are not familiar with the problem with appointments. As we need to gather further information below, we recommend replying by direct email to support AT advansyscorp.com.

As it appears from our records that you have been using Archive To Go for many years, when did you first notice this problem? If it is a recent problem and assuming the version of Archive To Go has not changed, what else may have changed within your environment?

Which version of GroupWise Client for Windows are you using?

Does this issue occur for all GroupWise accounts which you export?

In the GroupWise client (or in the default client settings at the PO), for the GroupWise account being exported, what are the Return Option settings for Opened appointments under Tools | Options | Send | Send Options | Appointments? What are the Opened notification settings for other message types, such as mail, task etc?

Are you using Local or Enterprise Mode to export the mailbox? If Local Mode, have you tried using Enterprise Mode? Local mode uses GroupWise APIs which cause a message to change from read to unread when accessed for export. To overcome this GroupWise API behaviour, Archive To Go resets the message to unread status after exporting an unread message. Enterprise Mode uses special APIs and may not trigger the item Opened notification settings.

Please send your responses to support AT advansyscorp.com.

Kind Regards,

Advansys Support

[Support 2]

Hello,

As far as licensing is concerned, the key code provided for Formativ Studio 2.7 can be used for up to 5 workstations, that is no problem at all, particularly if it is meeting your operational requirements.

Could you please let us know if Formativ 2.7 resolves your applet access problem.

Kind Regards,

Advansys Support

[Support 2]

Hi Brent, we’ve responded to your direct email. You do need to have an operational GroupWise system for Archive To Go to work, for example the POA needs to be running.

Kind Regards,

Advansys Support

[Support 2]

Thank you for your post. Is it correct that this question is being addressed to Advansys or did you intend to post it in a Novell support forum?

Kind Regards,

Advansys Support

[Support 2]

It is our pleasure. Thank you also for the use case background and the additional enhancements, which are being considered for future releases.

Kind Regards,

Advansys Support

[Author]

Replies