smcnabb
My feedback
-
64 votessmcnabb
supported this idea
·
-
7 votessmcnabb
supported this idea
·
-
87 votes
At this time, this item is not currently scheduled for a release of PI Vision. If this changes, this item will be updated to reflect the current status.
An error occurred while saving the comment smcnabb
supported this idea
·
-
3 votessmcnabb
supported this idea
·
-
8 votes
An error occurred while saving the comment smcnabb
commented
would like to know the use case and design decision for this change. Why does the interface override a system setting for the folder? And why is this listed as an enhancement request if the "enhancement" is restoring previously defined behavior?
The behavior is now significantly different, it doesn't appear to follow standard conventions and there doesn't appear to be any documentation explaining the new behavior or reason(s) for the change.
It definitely is causing problems for our system and use cases because if the file is ever accidentally deleted or needs to be temporarily or permanently moved, manual intervention will now be needed to create the files, with the correct names, and with the correct (previously inherited) permissions. It no longer is automated and managed (as expected) by the interface. With more than a couple interfaces (we have over 50 easily), management of this is now a nightmare.
smcnabb
supported this idea
·
-
171 votes
We understand and acknowledge the importance of this request. We are evaluating how to provide a homogeneous and unified experience for health information across all our connectors.
smcnabb
supported this idea
·
-
13 votessmcnabb
supported this idea
·
-
65 votes
I agree with Bryan1. It seem it should be a standard built in symbol or control. It's a historian so being able to view archived values in multiple ways seems an obvious use case.