Running an External task as soon as a DCR is saved

Hi our requirement is such that as soon as the User saves a DCR , An external task (Program) would start.

Presently we are able to run the external task (Perl program) while the DCR is Saving . Because of this an DCR can take upto 20 Mins to Save.

So we want some changes so that the User saves the DCR , and continue with other work , but in the background the Perl program would be running.

Prem pratick.

Find more posts tagged with

Comments

gzevin

Hi our requirement is such that as soon as the User saves a DCR , An external task (Program) would start.

Presently we are able to run the external task (Perl program) while the DCR is Saving . Because of this an DCR can take upto 20 Mins to Save.

So we want some changes so that the User saves the DCR , and continue with other work , but in the background the Perl program would be running.

Prem pratick.

with callServer you can probably spawn a process and return to the form. However, this is very unsafe, one should wait for another process is done, otherwise what would you do should the external process fail?

nipper

Hi our requirement is such that as soon as the User saves a DCR , An external task (Program) would start.

Presently we are able to run the external task (Perl program) while the DCR is Saving . Because of this an DCR can take upto 20 Mins to Save.

So we want some changes so that the User saves the DCR , and continue with other work , but in the background the Perl program would be running.

Prem pratick.

Call server (as Greg said) works exactly how you want it to. However I must ask, what the heck are you doing that takes 20 minutes ? If you have more than 3 DCR edits per hour, you are going to have some serious issues. & ob, by the way, what happens if I edit this DCR and save while Greg's save is still in process ? Something ugly ?

You should consider doing this task in workflow rather than on the save event.

Andy

Valentine

Another possibility is to use triggers

prem_pratick

In our Design, We have some Option Values in dataCapture.cfg file, These Option values comes from ADMIN DCRs ,

For eg.

If a User Creates a ADMIN DCR and saves it . Then the /title field of the ADMIN DCR should come as an option value in the Rest of the Templates.

So we have to either manually edit the datacapture.cfg or Use an Inline callout. Using InLine callout would Increase the CPU Utilization.

So we want that as soon as an ADMIN DCR is Created and saved , a Script would envoke that would update all the datacaptur.cfg files for that BRANCH.

Hope I am clear.

Prem

nipper

In our Design, We have some Option Values in dataCapture.cfg file, These Option values comes from ADMIN DCRs ,

For eg.

If a User Creates a ADMIN DCR and saves it . Then the /title field of the ADMIN DCR should come as an option value in the Rest of the Templates.

So we have to either manually edit the datacapture.cfg or Use an Inline callout. Using InLine callout would Increase the CPU Utilization.

So we want that as soon as an ADMIN DCR is Created and saved , a Script would envoke that would update all the datacaptur.cfg files for that BRANCH.

Hope I am clear.

Prem

Inline callout will have minimal affect on the CPU. Write it to a file and have the DCT run a inline perl process that reads that file.

Much better approach.

ISCBorisB

In our Design, We have some Option Values in dataCapture.cfg file, These Option values comes from ADMIN DCRs ,

For eg.

If a User Creates a ADMIN DCR and saves it . Then the /title field of the ADMIN DCR should come as an option value in the Rest of the Templates.

So we have to either manually edit the datacapture.cfg or Use an Inline callout. Using InLine callout would Increase the CPU Utilization.

So we want that as soon as an ADMIN DCR is Created and saved , a Script would envoke that would update all the datacaptur.cfg files for that BRANCH.

Hope I am clear.

Prem

You are clear. Your idea is not. Using Inline callout is much better solution.

If parsing Admin DCR on the fly has such a big performance hit, then parse it once onSave and create a flat
file somewhere for your inline to return instanteneously.

gzevin

In our Design, We have some Option Values in dataCapture.cfg file, These Option values comes from ADMIN DCRs ,

For eg.

If a User Creates a ADMIN DCR and saves it . Then the /title field of the ADMIN DCR should come as an option value in the Rest of the Templates.

So we have to either manually edit the datacapture.cfg or Use an Inline callout. Using InLine callout would Increase the CPU Utilization.

So we want that as soon as an ADMIN DCR is Created and saved , a Script would envoke that would update all the datacaptur.cfg files for that BRANCH.

Hope I am clear.

Prem

it's clear that your architectural solution needs to be refined. If all the values come from ONE admin DCR, an inline callout in other DCTs could parse it and produce an option list. If You need to parse a number of them, then, as it was suggested already, build a flat file (or XML, as you like) that will contain those options.