In general, we are using configuration slicing to keep an eye on hundreds of jobs. In specific, the issue we're facing right now is that in trying to look over jobs that use different timer trigger chron values, we want to do some research into these, and then make some changes or recommendations to better accommodate scheduled down times and things like that. However, to do that we really had to copy the configuration slicing value from the web page, paste it into a text document, run some transformations on it to get it into a human-readable state, etc. I was thinking that perhaps instead of dumping the configuration all into one text box, you might split it up into more of a key/value setup on the web page. I put together a quick version that does that, and it seems to work fine. I'm sure there are some limitations I'm overlooking, etc, but I wanted to run it by you and see if it was interesting or not. I also attached a screenshot of what the patch does.