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

Schedule Deployment

Konidala

Can anyone here suggest me which method is appropriate to do the Schedule Deployment? Basically I want to deploy the content from TeamSite on Scheduled date & time. I am using File List deployment. In submit workflow, after submitting files to the STAGING area system will display CGI task where users are allowed to deploy the files immediately or to schedule the deployment. If users select to schedule the deployment then system will move to a delay task with timeout and deployment is done at the scheduled time from the STAGING area.

Now the problem is in-between if someone try to submit the entire content, the system will deploy all the files including scheduled content. I don’t want to create editions and publish from the EDITION instead of from STAGING area. I need to know got any better ways of handling this. Thanks.

Find more posts tagged with

Comments

JonathonG

You could adjust your workflow and deployment scripts for the case of submitting the entire area. In that case, create a file list deployment that includes all files not already attached to another workflow. You should be able to use the iwgetfilejobs clt to figure this out.

gzevin

You could adjust your workflow and deployment scripts for the case of submitting the entire area. In that case, create a file list deployment that includes all files not already attached to another workflow. You should be able to use the iwgetfilejobs clt to figure this out.

what if sombeody does submit direct?

it's not that trivial. I have seen this issue before.. frankly, it's not an easy one. A few solutions are possible.. one is to have a 'scheduled' workarea, where the approved files will go.. something like 'pre-staging' area... Some business process changes could also be done With one of my clients, I simply convinced them that their nightly scheduled job is unnecessary as everything else is deployed using filelist.:cool: