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; } } }

iwlistmod.exe

Jangra

Hi, I've searched lots of past posts but couldn't find my answer.

With iwlistmod.exe we can find the files modified in a workarea.

But I have requirement to implement datadeploy after finding the modified files in STAGING area. Is there any way to find the files modified in Staging.

With the help of Edition based deployment through OD we can deploy the entire set of modified files to destination server but here I cann't use that because I have deploy the content of modified files to the Database.

One solution that i think is to bind the datadeployment script with workflow after each submit operation. But before starting I want to analyse all the possible ways to do it.

I would appriciate each pointer.

Thanks in advance.
-Jangra

Find more posts tagged with

Comments

ISCBorisB

Hi, I've searched lots of past posts but couldn't find my answer.

With iwlistmod.exe we can find the files modified in a workarea.

But I have requirement to implement datadeploy after finding the modified files in STAGING area. Is there any way to find the files modified in Staging.

With the help of Edition based deployment through OD we can deploy the entire set of modified files to destination server but here I cann't use that because I have deploy the content of modified files to the Database.

One solution that i think is to bind the datadeployment script with workflow after each submit operation. But before starting I want to analyse all the possible ways to do it.

I would appriciate each pointer.

Thanks in advance.
-Jangra

What does "modified files in STAGING" really mean? "Modified" comparing to what, latest Edition?

Jangra

Thanks for reply!

Modified means if somebody edited the existeing file and again submit it (that will change the version of file). Or if there is some newly submitted file after a timestamp.

nipper

Do this in a workflow or using a TS compare (use Edition/Staging) deployment. Workflow is by far the best alternative.

Jangra

Thanks Nipper,

I agree with your suggestion that we can implement it very easily with workflow by calling the DD script in workflow.

But, what if I want to schedule the DD script at a particular time. And it should run only for new or modified files in the STAGING. Is there any way to do it. I welcome your all suggestions.

ISCBorisB

Thanks Nipper,

I agree with your suggestion that we can implement it very easily with workflow by calling the DD script in workflow.

But, what if I want to schedule the DD script at a particular time. And it should run only for new or modified files in the STAGING. Is there any way to do it. I welcome your all suggestions.

There are several ways. IMO the simplest one for scheduled OD/DD deployments is to immediately publish an Edition and deploy deltas with the previous one.
One caveat with this approach is a deployment failure. I normally remove the latest (just created) Edition in such case, otherwise Deployment may *not notice* some changes next time around