Scott.Mitchell
My feedback
-
15 votes
An error occurred while saving the comment Scott.Mitchell
supported this idea
·
-
7 votesScott.Mitchell
supported this idea
·
-
3 votesScott.Mitchell
supported this idea
·
-
18 votesScott.Mitchell
supported this idea
·
-
28 votesScott.Mitchell
supported this idea
·
-
36 votesScott.Mitchell
supported this idea
·
-
74 votesScott.Mitchell
supported this idea
·
-
80 votesScott.Mitchell
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.
Scott.Mitchell
supported this idea
·
-
3 votesScott.Mitchell
supported this idea
·
-
59 votesScott.Mitchell
supported this idea
·
-
2 votes
An error occurred while saving the comment Scott.Mitchell
commented
In response to Stephen Kwan, "Hi Scott, can I get a screen shot of wha..."
Hi Stephen. Thank you for taking a look at this. I was slightly off on my first request in that the default behavior on clicking the function expression expands the expression box with the cursor positioned at the end of the string. I work with mostly one or two line expressions. I think it would be nice that when the expression box expands for editing, the cursor would be positioned at the place I clicked.
Here are some screenshots:
Say I want to edit the attribute I am using in my EngBRunningYTD calculation. Out of habit from using other tools I click at the place I want to insert the cursor to do some editing.
…and this is the result
I think the standard for cursor placement is that it will appear at the point clicked. I actually can’t think of a tool that doesn’t do it that way. Years of time on tools that function in the way described require me to adjust the way I edit my work when using PSE. I understand this wouldn’t necessarily be a big issue for large multiple line expressions but for smaller one line editing the change in PSE would be pretty nice to see.
Again, thanks for checking in with me on this request.
-ScottScott.Mitchell
shared this idea
·
-
7 votesScott.Mitchell
supported this idea
·
-
12 votesScott.Mitchell
supported this idea
·
-
7 votesScott.Mitchell
supported this idea
·
-
1 voteScott.Mitchell
shared this idea
·
-
4 votesScott.Mitchell
supported this idea
·
-
124 votesRESEARCHING / EVALUATING · 1 comment · PI Server » Analytics & Calculations · Flag idea as inappropriate… · Admin →Scott.Mitchell
supported this idea
·
-
2 votesScott.Mitchell
shared this idea
·
-
5 votesRESEARCHING / EVALUATING · 1 comment · myOSIsoft » Customer Portal Overall · Flag idea as inappropriate… · Admin →
An error occurred while saving the comment Scott.Mitchell
commented
The keep me signed in checkbox does not work using Chrome or IE. I don't believe this is an issue with a browser GP setting as using a similar checkbox for other sites does work in both browsers.
Remembering a user sign on is a convenience for us and shouldn't be a big deal to implement on your end.
Scott.Mitchell
shared this idea
·
This idea holds true for almost every OSI product. Searching for tags in PB should be the same as DL or Builder. AF should be exposed in a similar fashion in all tools. In general the people who design the tools that allow us to expose the data we need should all get together and design interfaces that make the system work in a similar way no matter what tool you are using.