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

Auto add used images to be submitted with html

wah

Just wondering if there is a solution that will allow the system to automatically add all images that are used in a html to be submitted by just submitting that html file?

Find more posts tagged with

Comments

kaalraa

Just wondering if there is a solution that will allow the system to automatically add all images that are used in a html to be submitted by just submitting that html file?

On inititiating a submit workflow, you can include an external task... which can parse the file to find all img tags and value of its src attribute.

I hope you can go ahead.

Adam Stoller

Just wondering if there is a solution that will allow the system to automatically add all images that are used in a html to be submitted by just submitting that html file?

Out-of-the-box - no.

As Kaalraa indicated, you can write a script for doing this - however the script may not be quite as simplistic as was indicated, since you may have to account for the different ways the src attribute might be specified (perhaps filtering out any URLs that begin with "http(|s)://") and you also may need to account for mapping URLs to your TS directory structure.

If you have a simple, well laid out, directory structure where the top of your workarea is mapped directly to the top of your doc root and you can thus easily map a URL of "/images/foo.jpg" to the same path relative to your workarea root - great.

If, instead, you have a sub-directory (e.g.: "/htdocs") at the top-level of your workarea that is mapped to your doc root - you would need to account for that when parsing the information so that you mapped a URL of "/images/foo.jpg" to "/htodcs/images/foo.jpg" in order to attach the file to your workflow process.

If, instead, you have your images in a different branch - you won't be able to attach them to the same workflow as the referencing HTML page (or at least not trivially) but instead you might be able to invoke a secondary workflow, based within that other branch, with those files attached. (The non-trivial comment is with regards to having a single workflow with two parallel task transition paths such that you can have each path associated with a distinct areavpath and explicitly add/remove files to/from each path -- definitely not a solution for the faint-of-heart, and not something you'd enjoy taking over maintenance for if someone else dumped it on you ;-)

I've seen other situations which are more like the second situation I mentioned - but much worse - in which there are image directories in various places throughout the TS directory structure that are all referenced as "/images/****" within the HTML code and that require all sorts of specialized proxies to make things render correctly when viewing the page content (at least within TeamSite) - in such a case you'd either have to simulate the proxy or search the entire directory tree to find a match for the URL specified within the HTML code -- and what do you do if you find more than one match? [ugh].