How do you close a Form after DELETE Action?

BenHayat

Note Henrik:
Those Processes need to get executed AFTER the BO is deleted and not before. That's why I originally went the route of creating a complete process to do:
a) Before Delete Process
b) delete BO
c) After Delete Process

By using Builtin Aware "Delete Object" I loose (a) and (c).

BenHayat

All we really need is a "CLOSE" action that we can call from process and it solves everything.
I'm surprised after all these years such action doesn't exist. 🙁

BobK

When you expand the BO in the left hand window of the Config tool you should see:
Attributes
Forms
Rules (when object is created or modified)
Rules (when object is deleted)

Double click the last one to enter rules that only get executed when the object is deleted.

BobK

The above post is a little late. I did not realize there was a second page of posts.

BenHayat

BobK wrote
When you expand the BO in the left hand window of the Config tool you should see:
Attributes
Forms
Rules (when object is created or modified)
Rules (when object is deleted)

Double click the last one to enter rules that only get executed when the object is deleted.

Yes Bob, I had missed that one and Henrik pointed me to it.
But after many tests, I have to use a complete process system, where deletion is only one part of it. I have to do certain checking to even allow the deletion to take place, and "IF" the deletion did take place, then other processes will follow AFTER the BO is gone. The Delete Rule of BO happens Before the BO was deleted. So that direction using Rule is out.
Thank you again for your suggestions.

aware_support

It is generally not a good idea to invoke a process from a form of an object if this process deletes an object. The system generally cannot have intelligence to understand that it has to close the form. And even if it does the behaviour after this is undefined and not intuitive to the user. All of a sudden the form will close and the system will go somewhere else (where?)

It is much better if you call this process not from a form but from a query displaying the record of the object, for example. Or if you run it from the form you have to explicitly overwrite the form with something else - for example, show some other form, query or a visual perspective. It is also a good idea to display a message to the user.

Bottom line - you have to manage this situation yourself inside the process.

BenHayat

aware_support wrote
It is generally not a good idea to invoke a process from a form of an object if this process deletes an object. The system generally cannot have intelligence to understand that it has to close the form. And even if it does the behaviour after this is undefined and not intuitive to the user. All of a sudden the form will close and the system will go somewhere else (where?)

It is much better if you call this process not from a form but from a query displaying the record of the object, for example. Or if you run it from the form you have to explicitly overwrite the form with something else - for example, show some other form, query or a visual perspective. It is also a good idea to display a message to the user.

Bottom line - you have to manage this situation yourself inside the process.

But Using the Built in Delete Object in the Operation works perfectly and closes the form.
The user needs to see the details of the form before deciding to delete it. A line in query can't show enough data.

Secondly, This is a child data that was shown in the parent section in the list. when user clicks on EDIT, a new Tab in VP opens the detail form. So it's a natural place to delete it when they are in the object.

aware_support

"But Using the Built in Delete Object in the Operation works perfectly and closes the form."

Because the system knows exactly that this is the delete operation, the developer cannot control it and the system can do nothing else but close the form.

« Previous Page