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

Customizing iw.cfg

phenom

Would customizing iw.cfg have any impacts on TeamSite performance? Whoever did it in our current implementation essentially used it to store all sorts of configuration info.

For example, target server info (for deployments) is stored in an XML but the location of the XML is stored in iw.cfg. So everytime a workflow runs, it gets the location of the XML from iw.cfg.

Does this in anyway impact TeamSite performance?

Find more posts tagged with

Comments

Garth McMillan

How is the property accessed?

If the workflow opens iw.cfg from the file system to read the property and then opens the relevant XML file each time, then yes, you will get a performance hit, however, I doubt it would make a noticeable difference - the file isn't very large.

If you are having problems with performance, I'd probably look elsewhere first.

mart2001

You might want to look at the [iwserver] section of the iw.cfg file. If there was any TeamSite performance issue, I would look around that area. Other stuff like templating, workflow probably won't have much differences on TeamSite performance.

phenom

How is the property accessed?

If the workflow opens iw.cfg from the file system to read the property and then opens the relevant XML file each time, then yes, you will get a performance hit, however, I doubt it would make a noticeable difference - the file isn't very large.

If you are having problems with performance, I'd probably look elsewhere first.

TeamSite::IW_cfg is being used to access it.