Issue with 22.3 - Smart Service Node default Data Inputs now have their "Save Into" targets disabled. Why??

RE: Issue with 22.3 - Smart Service Node default Data Inputs now have their "Save Into" targets disabled. Why??

Mike Schmitt — Mon, 06 Feb 2023 20:43:29 GMT

Per Appian Support, this issue has been captured in their internal ticket AN-224980, and may be addressed in an upcoming hotfix. Copying this info to this thread for future visibility.

RE: Issue with 22.3 (and maybe earlier) - Smart Service Node default Data Inputs now have their "Save Into" targets disabled. Why??

Chris — Wed, 05 Oct 2022 15:42:58 GMT

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 😀

RE: Issue with 22.3 (and maybe earlier) - Smart Service Node default Data Inputs now have their "Save Into" targets disabled. Why??

Mike Schmitt — Wed, 05 Oct 2022 15:35:53 GMT

[quote userid="2401" url="~/discussions/f/process/26137/issue-with-22-3-and-maybe-earlier---smart-service-node-default-data-inputs-now-have-their-save-into-targets-disabled-why/102447#102447"]Assuming however you can still access the ac! value and save into on the Outputs tab (albeit more work)?[/quote]

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.

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.

😖

RE: Issue with 22.3 (and maybe earlier) - Smart Service Node default Data Inputs now have their "Save Into" targets disabled. Why??

Mike Schmitt — Wed, 05 Oct 2022 15:32:50 GMT

[quote userid="59361" url="~/discussions/f/process/26137/issue-with-22-3-and-maybe-earlier---smart-service-node-default-data-inputs-now-have-their-save-into-targets-disabled-why/102446#102446"]Did you open a support case already?[/quote]

No, that was the next step I was planning, I figured I'd socialize it first here and at least solicit some initial feedback.

Plus (and this is partly me just being lazy) it's about 50x easier to post arbitrary screenshots here, versus in the support case system.

RE: Issue with 22.3 (and maybe earlier) - Smart Service Node default Data Inputs now have their "Save Into" targets disabled. Why??

Chris — Wed, 05 Oct 2022 15:30:55 GMT

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..

RE: Issue with 22.3 (and maybe earlier) - Smart Service Node default Data Inputs now have their "Save Into" targets disabled. Why??

Stefan Helzle — Wed, 05 Oct 2022 14:59:09 GMT

While this makes totally sense and removes a lot of confusion, I did not see this mentioned anywhere. Did you open a support case already?