Pre-filling profile fields based on Office templates

Hello.

Is there any logical way to pre-fill Worksite profile fields based on the template that a user might have used when they created a document? I'm particularly interested in the Word 2007 integration with Worksite 8.2.

We have a collection of about 40+ Word templates that our staff use, and we'd like to be able to "encourage" them to use particular class/subclass combinations depending on the Word template they're working with. eg. If they're using one of our report templates, we'd like to pre-fill the class and subclass with values that match that kind of report when they go to save it.

We previously used pre-profiling such that the template was selected based on the subclass, and that correlation between document templates and classes existed more or less automatically because of how we made people create documents. Now that we're moving to post-profiling for various reasons, however, it's become apparent that we could end up with using choosing all kinds of classes/subclasses that don't really match the kinds of documents they're working on.

Having VBA macros in the document templates is easy from our perspective, and I was hoping there might be some way I could hook the Worksite Save-As event from within the template's VBA so as to set the class and subclass prior to the dialog popping up. I haven't been able to figure out how to do this, however. (The closest I've found is Word's BeforeSave event, which unfortunately fires after the new profile dialog has already displayed.)

Another thing I've considered is to catch the dialog open event in newprof.nrs, but I don't *think* it's possible to detect which template has been used with the document by doing this.

Thanks for any help.
Mike.

Find more posts tagged with

Comments

guido1

You'll need to create a VBA addin (e.g. for Word, a .DOT file that is placed in the Startup folder).

Within it set a reference to WorkSite Office Integration COM addin (usually C:\Program Files\Interwoven\WorkSite\iManOXP.dll) and iManExt2 Type Library (C:\Program Files\Interwoven\WorkSite\iManExt2.dll)

Your first task would be to grab a pointer to the iManageExtensibility object that is exposed by the COM addin. You can access this via the COMAddins collection in the MS Office VBA object model. Something like:

 Dim extObject as iManO2K.iManageExtensibility 
set extObject = Application.COMAddIns("oUTR02K.Connect").

Object

You then will need to sink this object in to a class module in order to expose its events. A quick way to do this is to create a class module which exposes a public iManageExtensibility object using the WithEvents keyword. Something like

Public WithEvents ExtensibilityObject as iManO2k.iManageExtensibility

You will then have access to that object's events. The event you're interested in is the OnIManFileSave event. This will give you a pointer to the EAI FileSave command, which will allow you to set up yet another event sink for the FileSave command's events.

To do this you would declare a variable like so:

Private WithEvents mFileSaveCmd As IMANEXT2Lib.IManFileSaveCmd

The command event you're after is the Initialize event.

From there you'll gain access to the FileSave dialog object, with which you can use the SetAttributeValue method to set the Class and SubClass according to the ActiveDocument.AttachedTemplate.Name property, or somesuch

This all sounds a bit involved (and it is if you're not very familiar with event handling) but it's eminently do-able..!

izogi

Hi Guido.

Thanks for the instructions. This is exactly what I was after, I think.

I've spent a couple of hours working on it I had to make some minor adjustments, but here's a simplified version of what I ended up with for anyone who happens to be reading this in the future.

In my Startup template's AutoExec() sub (which runs when Word opens):


Dim y As iManageExtensibilityObject

Sub AutoExec()
    Set y = New iManageExtensibilityObject
End Sub

In my iManageExtensibilityObject class module:


'Property to catch events on the main extensibility object.
Private WithEvents ExtensibilityObject As iManO2K.iManageExtensibility

'Property to catch events on the file-save command object.
Private WithEvents mFileSaveCmd As IMANEXT2Lib.IManFileSaveCmd

Private Sub Class_Initialize()
    Dim ca As COMAddIn
    Dim extObject As iManO2K.iManageExtensibility

    Set ca = Application.COMAddIns("oUTR02K.Connect")
    If Not (ca Is Nothing) Then
        Set extObject = ca.Object
        Set ExtensibilityObject = extObject
    End If

    Set extObject = Nothing
    Set ca = Nothing
End Sub

Private Sub Class_Terminate()
    Set ExtensibilityObject = Nothing
    Set mFileSaveCmd = Nothing
End Sub

Private Sub ExtensibilityObject_OnCreateNewProfile(ByVal objImportCmd As Object)
    'Set the event-enhanced command object property to be the incoming one.
    Set mFileSaveCmd = objImportCmd
End Sub

Private Sub mFileSaveCmd_OnInitDialog(ByVal pMyInterface As Object)
    Dim fileSaveDialog As IMANEXTLib.NewProfileDlg
    Set fileSaveDialog = pMyInterface

    'Set some dummy class/subclass values, or do whatever else to the profile dialog.
    fileSaveDialog.SetAttributeValueByID nrClass, "PERSONAL", True
    fileSaveDialog.SetAttributeValueByID nrSubClass, "OTHER", True

    Set fileSaveDialog = Nothing
End Sub

Thanks a lot for the help with this.
Mike.