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

Removing Metadata step from workflow wizard

Bomberoo

We have two TS servers, a development server and a production server, both running TS 6.5. On the development server, the metadata step in the workflow wizard is shut off which is how we would like it. Unfortunately, we can't seem to figure out how we did this, so if anyone has any answers they would be greatly appreciated because looking for how to do this is becoming increasingly frustrating.

Thanks

Find more posts tagged with

Comments

nipper

what workflow are you using ? There are config files associated with
many of these.

get some training, this should be a simple task

BTW, if your dev server and your prod server behave differently, this is a bad thing.
You are not testing what is in production.

ccprofessional

look for "skip-tag-step" in your UI documentation

Adam Stoller

The answer is not within the wft.
I don't recall the actual answer (I don't use CCStd currently and so don't have the problem) - but I believe it's something controlled via the UITK.
If you search the manuals and/or forums you should be able to find information about how to do this - because this question has been asked and answered several times.

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

ccprofessional

ok, another hint: application_custom.xml

nipper

THat is why I asked which WF, some of the solutions WFs have a config file where it is defined (i.e. author assignment)

Adam Stoller

He *did* clearly say he was talking about the workflow wizard ....

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

Bomberoo

We tried application_custom allready. It didn't work. The work flow was custom designed and dosen't mention anything about metadata anywhere in it.

Phil

Make sure you are using the right customization. Search the UI Customization Guide. It's in there. Post your application_custom.xml file and it will be easy to verify.

Also, did you run make_toolkit.ipl after you updated application_custom.xml?

Phil

Bomberoo

We did use the right customization in the correct way I believe. This is what was in our application_custom.xml, it was the only entry:

<applications>
<application id="ccstd">
<param id="skip-tag-step" value="true">
</param>
</application>
</applications>

However, we never ran make_toolkit.ipl (I am positive we never ran this, we were specifically avoiding doing this because we did not want to run into problems and have it slow us up) and yet it still turned off the metadata step on development. The idea was that we would try this without running make_toolkit to see if it would work and if not we'd come back to it later after we had the site we were developing up and running. We copied application_custom.xml from development to production into the same directory when we migrated everything and expected it to work exactly as it did before without running any scripts. I removed this entry from development without running make_toolkit to see if the metadata step came back and it didn't.

Phil

I'm not clear on the problems you were hoping to avoid by not running make_toolkit. Regardless, changes to application_custom.xml or any other part of the UITK will not show up unless you run make_toolkit. Running make_toolkit will bring down CC Standard for a few minutes so make sure you schedule some downtime.

One other thing to check... are you updating application_custom.xml under <iw-home>/customer_src/etc/conf/customer? There are a few copies of this file under iw-home and it's possible you're updating the wrong one.

Phil