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

Ignoring 'no modified files'

System

Anyone know how I can submit a file to staging even when there have been no changes in that file?
Currently when the user 'Submits' the presubmit.cgi intervenes with that 'no modified files' message before my workflows even get a look in.
much thanks in advance as always,
/nick

Find more posts tagged with

Comments

iwovGraduate

Do you actually intend to "submit" these files with no changes or just make them part of some workflow and possibly submit it subsequently ? In the later case, invoke the workflow on a different event - e.g.: "new_job" or "assign" instead of "submit".

What version of TeamSite are you using ?
Hope that helps.

Migrateduser

TS 5.5.2 W2K
Yes, I'd like the users to just have to Submit if possible. You see the DCR's are actually submitted first in a global branch before being iwupdated to a local branch for a specific 'site', submitted there and then DDandODed to that site. But the user should just think its a normal submit.

Edited by nichporter on 05/03/04 08:35 AM (server time).

iwovGraduate

If you do a "iwupdate" from one area to another, the file will appear as modified or new in the destination area. So when you try to "submit" the updated file, you will not run into the situation what you are suggesting.

The "submit" in the local branch is done automatically or by users ?

Migrateduser

Everyting is done automatically, in a workflow, initiated from the submit. So I have no chance to do anything before presubmit.cgi intervenes.

Edited by nichporter on 05/04/04 04:55 AM (server time).

Migrateduser

Not sure if you're saying that the presubmit.cgi kicks off, but the submit won't. If that's the case, you should be able to put a "touch" command in the presubmit.cgi to touch all attached files (which just modifies the date). Then you should be able to submit the file with no difficulties.

- Jason

Adam Stoller

We created a custom menu item 'Touch Files' to get around this issue - so that when you need to submit a file through a workflow process, even if the file you are selecting to initiate the workflow wasn't modified, you can "touch" it and then you can do the Submit.

Yes - it's a low-technology work-around - but it works...

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

iwovGraduate

Ok, so the way I understand is:

- You have a branch called global and another branch called local.
- Some user or some process modifies a DCR in global branch and submits (to the STAGING area of global branch) using a workflow.
- As a part of the workflow, you have an externaltask that copies/iwupdates the DCR to local branch. Also it does a submit (to the STAGING area of local branch), and runs a deployment (OD/DD). (or you maybe kicking off a separate workflow for the local branch)
- So now, a user wants to submit the DCR in local branch without modifying it ? I think I am missing something.

Can you explain what is "normal submit" in your statement: "But the user should just think its a normal submit." ?
I think a normal submit would be when a user modifies a file, and then submits.

You can touch the file(s) to get around presubmit.cgi. See suggestions by ghoti and jmeyer503. Note that you will be creating extra versions.

Adam Stoller

Not sure about the original case behind this thread, but for us, the tricky part, and why we created the touch-files custom menu item - was because our users created DCRs via a workflow process - but when they navigate through the system they do so through the generated files part of the branch rather than the templatedata part. If they select a generated page and click Edit - they'll edit the DCR but the generated page (which they still have selected) will not be modified (all page generation is taken care of through the workflow process too) - and thus if they click the Submit button with the un-modified generated page selected the workflow complains about there not being any modified pages - because it doesn't know to figure out that the DCR source of the generated page *is* modified.

We resolved this in two ways: (1) the aforementioned custom menu item, (2) our home-grown "Preview" functionality (generates to a temporary location and deploys to a preview server) also looks for existing generated files and touches them.

Thus, as long as our users Preview their changes - the file they originally selected will work just fine.
If they don't Preview it, then they have to do the "Touch Files" menu item, or navigate through the templatedata tree (which they don't want to do)

--fish
Senior Consultant, Quotient Inc.
http://www.quotient-inc.com

Migrateduser

The reason that I may want to submit again is that I have several local branches. One day a file may be ready for submitting and deploying to one local branch and eventual location. At another time the same, unmodified, file may now be ok to be submitted and deployed to another local branch and eventual location. My problem is that I do a submit in the global branch before iwupdating to the local branch, submitting and the OD/DD to my final location. The way I see it I can 'solve' the problem by one of ´two' ways - 1. Remove my initial submit (but then I lose editions on my global branch) or 2. Touching somehow the original file in the Global branch at the end of my workflow. I've used option 2, the only downside being that all files have the edited icon always. Thanks to everyone for all the intrest and help BTW :-)

Edited by nichporter on 05/05/04 05:12 AM (server time).