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

WFM configurable variable for timeout 731

nipper

OK, I know this works in 721 with the WFM Win32 app. However for the browser based app, it will not seem to let me save.

Anyway I am setting a delay before the deployment and plan to set the timeout in a configuration variable. When I change the timeout value, I can hardcode it and the UI lets me save the timeout. However if I edit the timeout and try change it to a configurable variable but I cannot save the change within the browser based WFM editor.

Using FF on 7.3.1. Clicking the OK button does nothing.

Find more posts tagged with

Comments

Rick Poulin

I don't have an instance to play with, but does Firebug report any JS errors? If not, maybe it works like SitePub -- open the 'net' tab before hitting the 'ok' button, and look for a POST request that might be coming back with an exception message.

Adam Stoller

Try it in IE - just to make sure it's not a browser-specific issue.
Also - I seem to recall that the new WFM UI occasionally gets "confused" and you have to re-do the entire model in order to clear up some "****" that somehow got embedded in the model (not much fun)

nipper

I don't have an instance to play with, but does Firebug report any JS errors? If not, maybe it works like SitePub -- open the 'net' tab before hitting the 'ok' button, and look for a POST request that might be coming back with an exception message.

Nope, nothing. I can assign a Script variable but not a Configurable.

Adam Stoller

Try a quick test with a fresh WFM - with just the minimum of things you need to test what you're trying to do.

If it works in the test WFM - then there's some "****" in the original WFM and, as far as I know, the only choice is to re-create it from scratch.

If it fails the same way in the test WFM - then it's either a "bug" or a "limitation" - and you'd have to check with Support on that.

Topic_38849__Footer footnote visibility.rptdesign

nipper

Yea I will do that. I am pretty certain it is a bug because it works fine in the 721 Win32 app. I was able to make a script variable which has a value of "$IW_CV(TimeoutDelay)"; and it seems to work.

Print1.png

Print2.png