Welcome to the NEW CHUG— your ultimate destination for cutting-edge insights and discussions at the intersection of healthcare and technology.

Our platform is dedicated to exploring the dynamic landscape of healthcare technology, empowering professionals, enthusiasts, and innovators alike with the knowledge and resources to navigate the rapidly evolving field.

From telemedicine revolutionizing patient care to the transformative potential of artificial intelligence in diagnostics, we delve into a myriad of topics shaping the future of healthcare delivery. Whether you’re a seasoned healthcare IT professional, an aspiring entrepreneur in the digital health space, or simply curious about the latest innovations, our curated content, expert interviews, and thought-provoking articles provide a comprehensive exploration of healthcare technology’s most pressing issues.

Join us as we navigate the forefront of innovation, driving forward the transformation of healthcare for a healthier, more connected world.

Have questions or suggestions? Please use the contact button below.

Notifications

Clear all

Visibility Region on Edit Field

MEL, SQL, Oracle

Last Post by Anonymous 1 second ago

5 Posts

4 Users

0 Reactions

75 Views

RSS

csimmons

(@csimmons)

Posts: 61

Estimable Member

Topic starter

Can anyone assist me in getting a visibility region to show only if there is text entered into the previous edit field?

The problem is this:

I have an edit field named "Other". I want a second edit field to show if anything is entered into the first edit field.

I came across some thoughts here on the forum while trying to post this question that indicated I may be able to accomplish this with the following:

DOCUMENT.Other == ""

That did not work. That actually has the reverse effect, I.E. the second field is visible only UNTIL something is entered into the first field.

I tried finding anything about NOT NULL, I tried just DOCUMENT.Other ==, etc.

BTW, do NOT try this line in the visibility region - it crashes Centricity:

DOCUMENT.Other <>

Good thing I was in my demo database! 🙂

Posted : August 23, 2018 9:15 am

jfitzmd

(@jfitzmd)

Posts: 419

Reputable Member

document.other<>""

Posted : August 23, 2018 9:23 am

dcarpenter

(@dcarpenter)

Posts: 323

Reputable Member

Jfitzmd has the correct answer. the "Not Equal to" symbol in MEL code is <>

Just like an equals sign, you have to have something on the right side, or else it will crash your code. Since a visibility field is looking for a true statement in order to display, your original code is telling the edit field to only show up if DOCUMENT.Other is empty.

Jfitzmd's code says, only show if DOCUMENT.Other is not empty.

Hope that helps you clarify for future use. Also, great job on using a demo database for testing! Way to use those best practices! keep it up! 🙂

Posted : August 23, 2018 11:41 am

csimmons

(@csimmons)

Posts: 61

Estimable Member

Topic starter

Thank you both. Go figure! I was working along the right path on this one, I just didn't follow it far enough! 🙂

Posted : August 24, 2018 4:16 am

Lee

(@lee-cooper)

Posts: 348

Reputable Member

One additional note:

Edit fields behave differently than other fields. To 'register' that something was entered, the user must tab or click out of the field. That means the visibility layer will not be visible until the user changes cursor focus. Because this can be confusing for users, I typically will add a fake button with a 'Record' label and no connection for these situations. It does nothing but change the cursor focus when the user clicks on it thereby permitting the visibility layer to display without breaking workflow and improves compliance with populating the item(s) in the visibility.

Posted : August 24, 2018 5:49 am

Share:

24 Forums
9,940 Topics
39.9 K Posts
0 Online
6,470 Members

Forum Icons: Forum contains no unread posts Forum contains unread posts

Topic Icons: Not Replied Replied Active Hot Sticky Unapproved Solved Private Closed

Powered by wpForo Powered by wpForo version 2.4.0