I am looking for how to display pop-up message on ViewX depending on internal Variable digital bit being set ON. i am
The ClearSCADA / ViewX architecture is not designed to accommodate this.
There are ways of emulating this, by using visibility animations on every overview page that would become visible on the top when the expression results in the desired value (having visibility on a special layer is probably the best way to do it). However I don't recommend this, it starts to make for messy overview mimics.
You should go back to what the actual use case is for this. If it is alarming, then having an always visible alarm banner of an appropriate size which would show the alarm condition that you desire is the more appropriate way to do this.
Having custom popup alarms deviates from ASM guidelines as they are too difficult to handle in a consistent manner without obstructing other information on the underlying mimic.
The main functionality is if operator enters a value (x) and depending on it, the process send out a number (y). If y is less than a particular threshold - a warning message to displayed stating that value (x) entered is not correct.
The ideal situation here is if you could just limit the controllable value (x). This would then be configured via the Control tab Min/Max settings for an Analog Point (or the Hand Control Min/Max settings for an Internal Analog Point).
If the (x) -> (y) mapping is really not known until the value has been entered then this isn't possible.
You could have a VBS/JS form which accepts the initial user input and passes it to the device, then waits for indication from the device that (y) has been assessed (from the (x) provided), and whether it is valid or not. If it's not valid you display a prompt as part of your form saying that it's not valid and getting the user to try again, or you just close the form (if everything was good).
You would want to have a way for the user to cancel the process also (since you would essentially have the UI spin locking waiting for the device to say whether (y) is valid or not).
What happens to the value of (x) in the device if it is invalid? Does it stay as the operator set value?
What happens to the value of (y) in the device if it is invalid? Does it just stay as per the previous (y) [based on the previous (x)]?
Is there a third status point which advises that the current (x) is invalid (and hence (y) has not been updated)?
I will limit the input using Min and Max settings the variable and depending on the final result of Y will make the value blink red.
If my answer has adequately solved your question, then please mark it as the solution.