Support 3

[Support 3]

Thanks, this enquiry has been handled by direct email.

Regards,
Advansys Support

[Support 3]

Sorry, the “FML Extractor” is in beta phase. Our engineers are doing the final testing and documentation update for the “PST Creator”. Once the “PST Creator” is released then we will look into releasing the other utility.

Regards,
Advansys Support

[Support 3]

Thank you for the enquiry. We have sent you an email about the beta download link.

Regards,
Advansys Support

[Support 3]

Thank you for your enquiry.

We are certainly continuing support and develop Formativ. In fact, behind the scenes, we working continuously with the GroupWise engineering team directly to ensure compatibility with interim releases of 7.0.x and the next version of GroupWise, Bonsai.

The main challenge we face is that Formativ is a highly integrated framework which knits tightly with the GroupWise APIs. This means there is significant work in testing and evaluation of GroupWise API or client changes, either included through our request or otherwise, even when it relates to an interim client release (not just a major release). We are also working in some other areas to extend the Formativ Framework for .NET, which will expose the GroupWise server SOAP API, a key focus for Novell, to the Formativ Language (i.e. you will be able to make SOAP calls from Formativ applets). Even if you use Formativ for off-the-shelf solutions, these pending changes will enable an even wider range of solutions development.

This level of integrated third party framework development needs to be coordinated with Novell’s technology roadmap. While we may release an interim version of Formativ prior to the Bonsai release, any major developments must be tied to what is released in Bonsai. This of course can change right up to or even just after, the Bonsai release date.

I hope this helps explain some of the reasons behind our modus operandi. Please do not hesitate to contact us if you have any further questions.

Regards,
Advansys Support

[Support 3]

Unfortunately, engineers are not sure that you can use the OLEContainer with Microsoft Graph. We also unable to find any reference in the web about it.

Here are some suggestions:
– Create your own COM enabled application which display the chart then call it from the Applet.
– Create the chart in other programs (i.e. Excel, word, etc), save to html/image then show it in Formativ Form using the Image or EmbeddedWB control.

Hope this helps.

Regards,
Advansys Support

[Support 3]

We sent an updated version (2.0.30) to you by email. The updated version will make sure the message view is HTML.

Regards,
Advansys Support

[Support 3]

We will let you know when the engineers update the solution.

Regards,
Advansys Support

[Support 3]

ChainApplet method lets you to call another applet (i.e. “Applet2”) once the calling applet (i.e “Applet1”) has finished running.

You cannot call a specific function in one applet using this method. For example, you can not call a function in “Applet2”. Formativ will execute the applet, if the chainapplet method used in the source then Formativ will execute the chained applet. You can pass data between applet using the TransferData property.

Not sure whether it will help, you can also use the ChainApplet method to return to the calling applet.

For example:
– Applet1 use the ChainApplet to call Applet2. You can write your exit code after the ChainApplet method so the Applet1 stop immediately after it calling the ChainApplet.
– Applet2 will execute, you can add ChainApplet in Applet2 to call Applet1.

See below an example:

– Create a Applet called “Applet1” and paste the source code below.

  
'-------------------------------------------------------------------------------
' Applet1
'-------------------------------------------------------------------------------

Sub Main(Client, GWEvent)

  if (utilities.ExecutionSource = esApplet) then
    msgbox "Applet1 running now. It was executed by the Applet2"
  else
    msgbox "Applet1 running. Now it will call Applet2"
    CallChainApplet("Applet2")
    exit sub
  end if

End Sub


function CallChainApplet(appletName)
  Utilities.ChainApplet = appletName
end function

– Create a Applet called “Applet2” and paste the source code below.

  
'-------------------------------------------------------------------------------
' Applet2
'-------------------------------------------------------------------------------

Sub Main(Client, GWEvent)

  msgbox "Applet2 rinnung. Now it will call Applet1"
  CallChainApplet("Applet1")

End Sub


function CallChainApplet(appletName)
  Utilities.ChainApplet = appletName
end function

Regards,
Advansys Support

[Support 3]

We will strongly recommend to update the GroupWise client to the latest point release (7.0.3, build date: 8/03/2008).

If the problem persists, please try the solution in another machine to confirm the issue is not environmental.

If you have any questions, please do not hesitate to contact us.

Regards,
Advansys Suuport

[Support 3]

Thanks for the feedback.

Unfortunately, recurring appointment not supported in this version. I have forwarded your request to engineering for consideration in a future release. Please note, Applets supplied to the Novell Cool Solutions area are not supported by Advansys. However, our engineers try to update the solutions when the resources becomes available.

If you require this feature sooner, Advansys offers a custom development service; contact support@advansyscorp.com to discuss this option.

Regards,
Advansys Support

[Support 3]

Yes, you can call another Applet using the ChainApplet() method. See the Formativ language guide for more information. See below the comments from the language guide.

quote:

---

utilities.ChainApplet: String

Example:
Utilities.ChainApplet = “Message Notes_flexalock”

Applet Chaining makes it possible to build interaction solutions based on two or more discrete Applets. Specify the applet you wish to chain by providing it’s name to the Utilities.ChainApplet property. Only the applet name needs to be supplied, though the full path may optionally be supplied. When the applet containing this line finishes executing, the applet indicated by Utilities.ChainApplet will be automatically executed (assuming the applet is available).

You can only specify one Chain Applet at a time. If your Applets makes two calls to ChainApplet, only the most recent call will take affect. The applet you specify in the Utilities.ChainApplet property does not get executed until the current applet finishes.

Formativ 2.0 also introduces the concept of Applet Data Exchange, which makes it easy for one applet to pass data to another via a global ‘scratch pad’. This feature can be used to pass data between Applets during chaining. See the TransferData property for more information.

---

On a separate note, you can also use the Formativ API (COM/XML based API) to interact with Formativ from processes external to GroupWise. See the URL below for more information.
http://www.advansyscorp.com/forums/topic/4131090521/

Regards,
Advansys Support

[Support 3]

Our engineers recently made some changes to the solution (version 1.0.15) which could solve the day-light issue. We have sent the updated version to you by email.

Regards,
Advansys Support

[Support 3]

We can reproduce the behaviour here. The example applet was written for the 2005 BrainShare session. We will report this issue to Novell and post any update here.

Regards,
Advansys Support

[Support 3]

We have seen this error in some early beta version of the GroupWise 7 client where the Mime.822 file was not available. Later version of the GroupWise client has fixed this issue.

Which version of the GroupWise client you are running (See Help – About GroupWise)? Which version of the solution you are running (See the About option from the Main dialog)? If you are not running the latest point release of the GroupWise client then you may need to upgrade the client.

Hope this helps. We look foward to hearing from you.

Regards,
Advansys Support

[Support 3]

It appear, by default the registry entries for the HTML font size not availbale. However, the entries created if you specify the GroupWise default font size (Tools – Options – Environment – Views – HTML font name & Size). Once you specify the font size, following registry entries created where you can change the value to modify the HTML message font size.

HKCUSoftwareNovellGroupWiseClientSetupUSER_ID_DETAILS@DOMAIN.DefaultHTMLFontSize

Please take care when you update the registry entries.

Regards,
Advansys Support

[Author]

Replies