topic Re: is it possbile to listen to the UpdateFileLifecycleStateEvents in standalone in Vault Customization Forum

is it possbile to listen to the UpdateFileLifecycleStateEvents in standalone exe

chenghongjieRP3JG — Wed, 19 Jun 2019 16:26:30 GMT

Hi Experts,

I want to run a standalone exe on the vault server, in the exe i want to listen to the DocumentServiceExtensions.UpdateFileLifecycleStateEvents when user start that exe application,

but when i change a file lifecyle state, the event is not fired.

and if i put similar code to an explorer extension, which is an extension of Vault Profession 2018,

when a file lifecyle state changed, the event will fired.

so my quesiton is how i can monitor any file lifecyle state events in a standalone exe application?

thanks,

Richard

Re: is it possbile to listen to the UpdateFileLifecycleStateEvents in standalone

chenghongjieRP3JG — Wed, 19 Jun 2019 16:33:47 GMT

related code as below, private void ConnectToVaultServer() { VDF.Vault.Forms.Settings.LoginSettings settings = new VDF.Vault.Forms.Settings.LoginSettings(); _VaultConnection = VDF.Vault.Forms.Library.Login(settings); if (_VaultConnection == null) { MessageBox.Show("Failed to connect to Vault Server"); return; } DocumentServiceExtensions.UpdateFileLifecycleStateEvents.Post += new EventHandler(UpdateFileLifecycleStateEvents_Post); ItemService.UpdateItemLifecycleStateEvents.Post += new EventHandler(UpdateItemLifecycleStateEvents_Post); }

the event is not fired when i run the standalone exe and change a file lifecyle state in Vault Professional 2018. but if i

run the code an extention of Vault profession 2018 explorer, the event can be fired.

Re: is it possbile to listen to the UpdateFileLifecycleStateEvents in standalone

Anonymous — Sat, 13 Jul 2019 10:24:26 GMT

Hi,

In my opinion there is no such a possibility. These events are fired when You use IWebServiceExtension implementation. I would do that like that:

1) Implement IWebServiceExtension for desired event,

2) In that event I would execute code to make a simple request to WCF service,

3) WCF service hosted on IIS or as Windows Service would execute desired bussines logic (that one You implemented in standalone app).

Of course I would make such an architecture only if IWebServiceExtension extension can't for some reason execute bussines logic directly.

Re: is it possbile to listen to the UpdateFileLifecycleStateEvents in standalone

chenghongjieRP3JG — Tue, 16 Jul 2019 09:22:00 GMT

thanks for the reply, I am out of town for the past server days.

and your input did helps, given me another ideal on how to handle the business logic.

but the key point i want like to resolve is that I want to Monitor the LifeCycleChange events on the Server side,

if i can not monitor the change, i have to deploy my Vault extention to all the Client machines(which run Vault Professional 2018..) , thus will lead to a big effor to installation. so i just want to be able to be notified when a file/item lifecyle changed on every Client mache, a ID is enough, and with that i can do my business logic only on a specific server(machine), no need to install on all the client.

do u have any ideal on that?

thanks,

Richard

Re: is it possbile to listen to the UpdateFileLifecycleStateEvents in standalone

Anonymous — Tue, 16 Jul 2019 09:40:20 GMT

Three solutions:

1) That one I described. IWebServiceExtension implementation, simple one that calls WEB API on one of your servers, sending only MasterIds and StateIds indicating state change and then do your bussiness logic on server side - this is the solution You want to ommit, bcause You will have to install this simple extension on every Vault Client You have in your company (there is no server extension unfortunatelly),

2) Hack: on Vault server side listen TCP connections and filter WebService calls regarding state change then fire You bussines logic,

3) Add trigger on Vault DB tables regarding state change then call RPC from such trigger to call Your bussiness logic on Your Windows Service hosting WCF (dirty one I know:) )

That's all that comes to my mind at the moment.

Re: is it possbile to listen to the UpdateFileLifecycleStateEvents in standalone

chenghongjieRP3JG — Wed, 17 Jul 2019 15:50:21 GMT

thanks for the reply, seems i have to take a hack way to resolve my problem.

so for the solution 2, is it doable? i did not do this kind of hack before.

another question, is it posssible to create a custom job,and withtin that job, we start the pdf publish job, then when the customer job is done its execution, the pdf publish job is also done. or can i trigger two jobs one by one, one is publish pdf, the other custom job is following that pdf publish job, and i need to make sure the first job is executed before the second one.

thanks,

Richard

Re: is it possbile to listen to the UpdateFileLifecycleStateEvents in standalone

Anonymous — Thu, 18 Jul 2019 07:44:52 GMT

Hi Richard,

1) Yes, it's doable, but I must warn You it's not simple task. If I were You I would take a look at IIS ISAPI Filters to write your own "extension" for IIS Server in order to intercept incomming requests and then analyze them to trigger sending messages to yours, for example, WEB API or WCF service.

2) About staring job in a job - please make another topic regading this use case, because title of that topic has nothing in common with Job Processor and we want to keep an order and information for other community users whiele they'll be searching for solutions.

Re: is it possbile to listen to the UpdateFileLifecycleStateEvents in standalone

chenghongjieRP3JG — Thu, 18 Jul 2019 08:50:22 GMT

thanks for the reply, and i will try your ideal.

also i have post my other question at

https://forums.autodesk.com/t5/vault-customization/is-it-possible-to-run-a-job-within-a-cusmomized-job/td-p/8916425

thanks for all your input.

Re: is it possbile to listen to the UpdateFileLifecycleStateEvents in standalone

Anonymous — Mon, 05 Aug 2019 12:53:58 GMT

Yes, it's possible, though I'd have to get with one of the developers on my team to see how he did it. We have a "tray application" - which is a standalone app, that listens for life cycle changes and does things accordingly. If I remember correctly, what actually happens is there is a vault plugin that is loaded when the client app loads, and it uses an interface to dispatch event notifications to a web service written by us, that then sends the notifications to 'listeners', which is the tray application. It sounds complicated because quite frankly it IS complicated, but you can certainly do it.