Support 1a

[Support 1a]

Thanks for the feedback – I’ll enter that into our enhancement database.

Advansys Support

[Support 1a]

Thanks for the update. Good luck with working around this issue. Your details are in our enhancement database, so we’ll let you know when this feature becomes available.

Advansys Support

[Support 1a]

The applet focus version of the applet you described did indeed contain a problem which has been fixed. Please download the applet from the same location off the web site and try again.

Advansys Support

[Support 1a]

Formativ doesn’t currently expose the IE Security Manager interface. As you have summized, Formativ uses the Windows system security settings for the IE sessions it uses.

I have added an entry to our enhancement database requesting this API be exposed to the Formativ language. We’ll consider this request at our next feature review. I expect this request will stand a reasonable chance of being introduced during a forthcoming maintenance release.

Advansys Support

[Support 1a]

If you obtain a message with a message ID something other than ‘X00’, the message already exists in the message store. This will be the case with a message that has been saved to the work in progress folder. The ‘X00’ message ID is used for messages that are still being composed and do no yet exist in the message store.

I would probably need to see you applet to provide a definitive answer (you could email it to support@advansyscorp.com). As a general rule, if you get a message ID other than ‘X00’, you can call GroupWise.Account.Refresh to ensure the API returns the most current version of your message. The message object also has a refresh method you can call to re-read the current values from the database.

Advansys Support

[Support 1a]

Thank you for the additional information. The version of the signatures applet you downloaded from the applet focus page is really only an example of various applet techniques, and has not been updated in a long time.

We’ll take a look at the version you are using to see if it contains a problem, but I would recommend you use the commercial Multiple Signatures applet that ships with the Business Solutions Pack instead. It is a commercial product, but it is fully supported. We can’t ensure that example applets will receive the same level of support, nor be of a commercial grade.

Advansys Support

[Support 1a]

Thanks for the update. I have made an entry in our enhancement database regarding this issue. It will be considered for inclusion in the next service pack.

Advansys Support

[Support 1a]

The 1.6 Admin installation installs the GroupWise trusted application DLL ‘GWTApp.dll’ to the client location.

Currently, there is no switch available in the Admin installation that stops the installer from attempting to install this file. (This is the first report we have received of this being a problem).

Accordingly, the only way to work around this problem at the moment would be to temporarily grant yourself write access to the shared client folder, install Admin, then remove write access. Alternatively, you might be able to manually copy the trusted application DLL to the shared location, then try installing. The installer will probably not attempt to update the file in this scenario. I could organize to send a copy of the file is you wanted to try this.

Advansys Support

[Support 1a]

Thank you for your post. The problem described by bertil_p on the 19th was due to a problem in the Business Solutions Pack applet that has since been rectified.

I am not sure which applet your client is using – ‘multiple signatures_encoded.vbf’ is not the current Business Solutions Pack signatures applet. The shipping, supported applet is called ‘Multiple Signatures_bsp_Flexalock.vbf’, and is available as part of the Business Solutions Pack. I would suggest you ask your client to remove whatever version of the applet they are currently running and install the Business Solutions Pack and try again. If you still have a problem, please email a copy of the applet being used, along with the signatures files, to support@advansyscorp.com.

Advansys Support

[Support 1a]

Formativ 1.6 works better under WTS/Citrix, but is not 100% compatible for two reasons:

a) The existing security system used by Formativ can be difficult to install in a WTS system. This can be worked around, but is tedious in certain situations. This will be addressed in the next major version. No release dates are currently available.

b) The GroupWise C3PO architecture (used by Formativ and many other third party GroupWise applications) does not strictly comply with WTS standards, in that it requires user-specific entries to be made in the HKEY_LOCAL_MACHINE hive of the Windows Registry. Novell are aware of this, but I cannot say when they will address this. Unfortunately, this is out of our control, and for this reason we cannot ‘offically’ support Formativ in a WTS environment. Again, this can be worked around, but it does mean Formativ may not operate as documented ‘out of the box’ in a WTS environment.

In this regard, my comment above that Formativ 1.6 is designed to be compatible with WTS should probably read ‘designed to be more compatible with WTS’.

I hope this clarifies the issue somewhat.

Advansys Support

[Support 1a]

In Formativ 1.5.x, the location of the mirror directory was hard coded to be under the formativ programs folder. This cannot be overridden.

In Formativ 1.6, this was changed to be dynamically created in the users personal application data. While not user configurable as such, the directory used is determined by Windows to be unique to the current user.

As Formativ 1.6 is a free upgrade to 1.5.x users, I would suggest you install 1.6 to determine if this scheme, designed to be compatible with Windows Terminal Services, meets your requirements.

Advansys Support

[Support 1a]

No problems. Don’t hesitate to post if you have any other questions.

Advansys Support

[Support 1a]

As will most access to the GroupWise message store, you need to use the GroupWise Object API, which is exposed in Formativ via the GroupWise.Account object.

To save a DMS document to disk, you need to locate the appropriate DocumentReference object, access it’s Document property, then locate the appropriate DocumentVersion you wish to save. You then check out the document to phsically save it to disk, then check it back in again. (If you don’t check it back in the document will be unavailable to other users).

Here is some sample code that shows how this can be done given a DocumentReference object:

  private function GetDocument(aMsg)
    
    GetDocument = ""
    
    if aMsg is nothing then
      exit function
    end if
  
    on error resume next
    
    ' Exit, if the document is checked out.
    if aMsg.Document.CurrentVersion.CheckedOut then
      exit function
    end if
    
    ' Exit, if the document is inuse by another application.
    if aMsg.Document.CurrentVersion.InUse then
      exit function
    end if  
    
    dim iDocPath
    dim iDocumentName
    
    
    iDocumentName = replace(trim(aMsg.subject), ".", "")
    if iDocumentName = "" then
      iDocumentName = "Document"
    else
      iDocumentName = GetLegalFileName(iDocumentName)
    end if
    
    iDocumentName = iDocumentName & "." & replace(aMsg.Document.CurrentVersion.OriginalFileType, ".", "")
    
    iDocPath = iWorkFolderName & iDocumentName
    
    aMsg.Document.CurrentVersion.CheckOut(iDocPath)
    call aMsg.Document.CurrentVersion.CheckIn(iDocPath, 0)
    
    GetDocument = iDocPath
      
  end function

Advansys Support

[Support 1a]

The various properties you can access in a native GroupWise task object are documented by Novell in the Object API. I don’t think they actually expose the completed date – just the completion status.

The new GroupWise 6.5 categories can also be accessed via the Object API. Note on the link above the Task object (as well as Mail, Notes, Appointments etc) all have a Categories() property. The Categories property provides a Categories collection. You use this collection to access the categories a message has been assigned to.

For example, given a task object, you coulds access the first category name by doing something like (untested code follows):

Msg.Categories.Item(1).Name

I hope this helps.

Advansys Support

[Support 1a]

Generally speaking, we have found Microsoft Word creates HTML that will not be loaded by the GroupWise client into message views. Word inserts large quantities of style and other HTML extensions that can cause the GroupWise HTML load APIs to fail.

While a generalization, GroupWise tends to only accept HTML that adheres to the fundamental HTML standard. It also performs some processing of HTML before it is inserted. This process may fail if the supplied HTML contains verbose HTML extensions.

I would suggest you create signatures and stationery using a dedictated HTML editor, or manually remove much of the extraneous code Word inserts (this assumes you are able to identify the extraneous code).

If you would like to email your Word signature to support@advansyscorp.com, I would be happy to take a look and advise what needs to be changed to get it to work.

Advansys Support

[Author]

Replies