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

Content in Teamsite STAGING

jeffldavis2

Workflow1
----------------------
We have an overnight automated job that publishes content from teamsite STAGING to "Production webserver".

Workflow2 (New Requirement)
---------------------------------
This proposed workflow, a new requirement, should publish files only to "staging webserver". This is when the user publish content from teamsite GUI. I know I may tweak the content submission workflow but I have some doubts over this process.

In the new workflow2, I suspect, after publishing the content to "staging webserver", the content left in the teamsite STAGING area might be picked up by overnight batch job of Workflow1 and may publish to "Production webserver". I dont want this to happen. To prevent this, I want to delete content(though perl code) in teamsite STAGING area once it is deployed to "staging webserver". But I heard the content in teamsite STAGING area is read-only. Is this approach is practical or doable?

suggestions...??

Thanks
Jeff

Find more posts tagged with

Comments

Amit_LnT

Hi Jeff,
As per my understanding, your second WF should deploy the files to staging server and it should not submit the file in TS staging area. You can do that by not submitting the files in the workflow. Just deploy required files from workarea and do not use submit task.
As far as the file deletion in Staging area, it is readonly from UI. But you can definitely delete it with commands. You need to delete the workarea file first and then submit the file.

jeffldavis2

Amit,

When you said the deploy files to the staging server and not use submittask means I shouldn't use "iwsubmit" but only use OpenDeploy "iwodstart" in the content submission WF to deploy to staging server. That's what you mean?

Thanks
Jeff

Amit_LnT

Jeff,
my understanding was that, you are using submit task in the workflow.
But, if you are explicitly submitting the file with iwsubmit, then what you said is correct. You can just remove that from your code and not submit the file to staging area.

jeffldavis2

Our content submission WFs were customized and not using OOTB workflow code.

We are using combination of 'exernaltask' and 'command' directives and 'iwsubmit' in the task definition to submit content.

Thanks for quick response.

Adam Stoller

Workflow1
----------------------
We have an overnight automated job that publishes content from teamsite STAGING to "Production webserver".

Workflow2 (New Requirement)
---------------------------------
This proposed workflow, a new requirement, should publish files only to "staging webserver". This is when the user publish content from teamsite GUI. I know I may tweak the content submission workflow but I have some doubts over this process.

In the new workflow2, I suspect, after publishing the content to "staging webserver", the content left in the teamsite STAGING area might be picked up by overnight batch job of Workflow1 and may publish to "Production webserver". I dont want this to happen. To prevent this, I want to delete content(though perl code) in teamsite STAGING area once it is deployed to "staging webserver". But I heard the content in teamsite STAGING area is read-only. Is this approach is practical or doable?

suggestions...??

Thanks
Jeff

Without understand ALL the requirements of the process flow - it is difficult to determine what "should" happen. If you deploy to just the "staging webserver" - is this before, or after, the content has been fully approved? If it is before - you should probably be deploying from the workarea, if it is after approval, then having it versioned in TeamSite's staging area is probably fine. Of course this also depends on the purpose of the branch on which the workflow is running - and quite possibly dependent upon all sorts of other variables - ultimately it comes down to an issue of requirements and design before implementation.

jeffldavis2

Sorry to open this thread after a long gap. Because of the other priorities, this requirement was pushed back.

Ghoti, the requirements are plain and simple. Thanks for your reply.

- User should pick their teamsite GUI
- The workflow should deploy the content directly from TEAMSITE WORKAREA to "staging webserver".
- There is no approval or versioning process.
- This content MUST NOT be pushed through TEAMSITE STAGING.

Is this a possibility?

Teamsite 6.1
win 2003

Thanks
- Jeff

nipper

From your basic description, this is trivial. You write a WF without a submit task and it deploys the selected files from the workarea to the test/stage server.

What are you having trouble with ? A basic WF would take a day max to put together

BTW, TS 6.1 is EOL, you really need to upgrade.

Migrateduser

Sorry to open this thread after a long gap. Because of the other priorities, this requirement was pushed back.

Ghoti, the requirements are plain and simple. Thanks for your reply.

- User should pick their teamsite GUI
- The workflow should deploy the content directly from TEAMSITE WORKAREA to "staging webserver".
- There is no approval or versioning process.
- This content MUST NOT be pushed through TEAMSITE STAGING.

Is this a possibility?

Teamsite 6.1
win 2003

Thanks
- Jeff

This seems pretty simple. Just have your deployment configuration use the TS workarea as it's source area. Don't submit the files to STAGING. Is there something I'm missing? This is what has been suggested to you in the previous posts.

nipper

This seems pretty simple. Just have your deployment configuration use the TS workarea as it's source area. Don't submit the files to STAGING. Is there something I'm missing? This is what has been suggested to you in the previous posts.

wow, that is a brilliant post. Just take my previous post, and change a few words and pad you post. Smiley Very Happy

new_report.rptdesign

jeffldavis2

Thanks all for your replies.

-Jeff

CRB

- User should pick their teamsite GUI
- The workflow should deploy the content directly from TEAMSITE WORKAREA to "staging webserver".
- There is no approval or versioning process.
- This content MUST NOT be pushed through TEAMSITE STAGING.
f

Since the goal is just to get content from workarea to staging webserver, it can be done in many ways:
- with one task workflow (deploy task)
- action menu item which invokes a script(to invoke deployment job)
- if users have access to opendeploy (which is not very common), then they can just run a deployment (no need for a workflow)...

Migrateduser

wow, that is a brilliant post. Just take my previous post, and change a few words and pad you post.

Normally I would just agree with you and add yet another post count, but I honestly didn't see your reply till after I wrote mine. But I'll take the extra post count as a bonus. Smiley Wink