As the subject line says, I've noticed recently that default in Data Input fields in different smart service nodes, the "Save Into" fields are now disabled, and this is not how the behavior worked in the past.
I'm creating this thread here today because I finally noticed a place in our system where this is a bit of a blocker. There are nodes where this was configured in the past and is now not even changeable.
As you may be able to tell from the above screenshot, the "new process variable" control is NOT disabled here (but the output-selector dropdown arrow is, even though you can't tell visually). Clicking on New PV allows you to save that input's value into that new PV, but then that output target is stuck and not changeable again (unless perhaps by adding a redundant new PV again).
This really seems like a bug - if this was an intentional change then I certainly don't remember seeing any announcement for it, or mention in any of the recent version release notes.
Is anyone out there on an earlier version, and can confirm whether or not this issue affects your current version? My CE site is on 22.2 still (why that is, is another question for another day) and once it's done restarting I'll edit this post to add a note confirming either way.
Edit: as promised, I checked my 22.2 CE site and can confirm that the Save Into is quite enabled / openable:
To confirm, if needed: this behavior in both cases compares a Create User node placed directly into a brand new process model (plus I checked other smart service nodes with default Data Inputs and the behavior seems consistent with those as well).
Discussion posts and replies are publicly visible
That does not seem logical to me that you can create a new PV to save into, but can not use a current PV (and that the save into is disabled regardless). Assuming however you can still access the ac! value and save into on the Outputs tab (albeit more work)? Is this only a few services or most/all?
21.1 here, no issues with this service or others having disabled save into's..
Chris said:Assuming however you can still access the ac! value and save into on the Outputs tab (albeit more work)?
Yes, though that's not very helpful for cases in which the SaveInto has been configured from the Input tab and needs to be changed (since it's not editable, whether it has an output target already or not). Plus of course the issue where, if it's always worked both ways, and there's no reason for it to not continue working both ways, and the change wasn't announced (and maybe even not intended, but who knows), then it seems a big issue for it to just suddenly change.
Chris said:Is this only a few services or most/all?
I'm not clear, but I spot-checked a few arbitrary smart service nodes (some OOB and some plug-in based) and the behavior seems consistent at least among the ones I checked.
Chris said:21.1 here
Yea especially to not be able to change a previously configured save into, seems illogical.
I'm just hanging out in the 21's until y'all iron all this stuff out in the 22's