When procedures triggered from screens fail you 😯

Carlos Eduardo Meneses Maran · 2024-11-13T08:53:04+00:00

There was an error rendering this rich post.

We are looking at all cases where a procedure executed from a screen can fail and stop. We have found what I relate below.

⚠️ Could you, please, point to additional cases? This way they are registered for future consultation by other members of the Community. ⚠️

When a procedure is launched from a screen, it can be with a button, a data entry trigger or a screen trigger, if the screen is closed, refreshed or the connection is lost, then the procedure is completely stopped in the following steps:

1️⃣ Refresh data.
2️⃣ Refresh screen.
3️⃣ Interactive selection.
4️⃣ Restore to current screen.
5️⃣ In general, any procedure step related to a screen.

When execution stops within a procedure invoked by a call procedure step, execution does not continue in the initial procedure either 📝.

Conversely, for our peace of mind, the data reader, wait, and call procedure steps do not result in the execution stop when the screen is closed, refreshed, or connection is lost.

Find more posts tagged with

Capsules

Data Modeling

Procedures

Usage

Data Model Maintenance

Accepted answers

Helmut Heimann

Hi @Carlos Eduardo Meneses Maran ,

I think, you've put it right "in general, any procedure step related to a screen".
Because in those cases the procedure needs a connection to the screen, you could say that it communicates with the screen. Any conversation will stop when one of the partners is not available anymore (Imagine a conversation with your wife when she's leaving the room in the middle of your conversation—just joking).

Best,
Helmut

Carlos Eduardo Meneses Maran

Thank you, @Helmut Heimann ,

The concept of screen-procedure communication is made clear by the illustration. Personally, though, I hope never to speak nonsense that would cause such a reaction 😉.