nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Extending UCF

ukdavo

Hi there

Can anyone point me to documentation re extending client-side UCF. I am aware that you can pre/post-process server-side but I need to fire some custom functionality on the client side (e.g. fire an ActiveX or some Java) following some WDK actions (export, checkout, etc).

Cheers

Find more posts tagged with

Comments

Francois Dauberlieu

No idea about firing client side stuff after the UCF processes but maybe if you let us know what kind of processes you need to perform, we might find a way to do it beforehand and then you can leave the client side alone. Been doing stuff like that in the past (e.g. forcing the folder to check out files depending on attribute values, or changing the file name depending of attributes values. There are actually a couple of posts in this discussions forum about that)

ukdavo

Hi Francois

I agree that server-side development would be preferable but I'm not sure that this would be adequate for what I'm looking to do. I need to synchronise object attributes with Windows.

Windows has tight integration with MS Office so you can, for example, copy attribute values to MS Office properties via ActiveX or POI then expose MS Office properties in Windows Explorer. With other file formats (e.g. crtext) you cannot save properties in the content file. You can however update the metadata for the associated NTFS entry via IPropertySetStorage.

So the idea was to extend UCF to do the following on export/checkout/view:

1. write attribute key/value pairs to the registry

2. fire an ActiveX or some Java to read from the registry

3. either update relevant MS Office properties or update NTFS with the relevant attribute key/value pairs

This should also work in the other direction (i.e. read key/value pairs from NTFS or MS Office) which would be written to the relevant object at checkin time.

I am sure that this would be possible if the client side components for UCF were documented and the source code made available.

Regards

lastnitescurry

your link was wrong, or got corupt, so reposted it

http://msdn.microsoft.com/en-us/library/aa379964(VS.85).aspx

interesting concept... not sure if I agree with the need but if I had to do it... I would not touch UCF in a million years... but I would do the following... which I just might now as its interesting and an excuse to play with DFS....

The following does not work for exports as there is no way to track back the file to the repository

write a client side file watcher to interact with registery and NTFS file system. It can chat to repository via DFS.

I've already commented on service accounts here, in this case the service user only needs browse access to all objects. Unless you plan to update them of course

https://community.emc.com/thread/5104?tstart=0

Watch UCF check out and viewed folders. When a file is added the registry is also updated... Get the ID from there and then get the details from repository with that ID.

Francois Dauberlieu

Sorry for the shameless self promotion:

Synchronizing MS-Office properties with Dctm attributes is what we do with OFCbridge, you might want to have a look on our web site (http://www.btmsoftware.eu), maybe even evaluate the product. If you need pricing info, then use the contact form (I'm a techy and don't want to know the prices, I just want the software to work well ;-)

For the rest, I agree with Brian, his way of doing it seems sound to me

ukdavo

@Brian - Thanks for the suggestion. That's certainly worth investigating. I may look into monitoring the registry as well.

@Francois - thanks for the shameless self promotion :-) I was aware of the product but I'm dealing with more than MS Office files. Just out of interest, does it just sync on checkin (e.g. via BOF) using POI?

Regards

Francois Dauberlieu

It's up to you, you can configure it to request the synch upon check in, promote/demote in the lifecycle, manually, etc... **** it uses the dm_queue facilities, you can request it anywhere you want with only a couple of lines of codes in your procedures/customizations