About Key-Commit

Question

I have lots of complex validation written on Key-Commit trigger.
But whenever user tries to clear the form, its asking "Do You
Want To Save The Changes", if user says yes then Key-Commit
Trigger is not firing.
Same thing happens when user press Key-Enterqry, Key-Exit
button.
So could u suggest me where can i write my complex validation
that should fire before commit.
Note : I can not write in Pre-commit & On-Commit trigger because
i am having restricted procedure in kEY-COMMIT.
wILL NEW VERSION OF FORMS FIRES HEY-COMMIT TRIGGER.
rEPLY SOON
BHAVESH
null

Answer 1

Hi Bhavesh,
You might have solved your problem by now but if not then a
suggestion from my end.
In key-clrfrm trigger
fire an explicit alert asking if user wants to commit changes
if user chooses ok to do so then
use following built-in : do-key('commit')
which will explicitly fire the key-commit trigger
hence fulfilling your purpose.
the following is the source code :
declare
al_button number;
begin
if :system.form_status = 'CHANGED' then
al_button := show_alert('c_alert');
if al_button = ALERT_BUTTON1 then -- OK button
do_key('commit');
end if;
end if;
clear_form;
end;
Hope this solves your problem...
Regards
Rashmi
Bhavesh (guest) wrote:
: Hi
: Thanks For reply
: I can not write restricted procedure like go_item in
: When-validate-record.
: Also i have lots of complex validation, flag setting and
: updatation which should gets fire before commit.
: Because of restricted form procedure i can not write in pre-
: commit or when-validate-record, according to me keycommit is
the
: correct trigger for all complex validation.
: Also i am giving u example
: Try to create simple master-detail form.
: Make a business rule on form level that at least one child
: record should present.
: So how this business rule u will implement using simpest way,
i
: know there are lots of way like creating global or parameter
: variables. but i don't want to use that.
: My logic for above business rule is as,
: Create key-commit trigger
: navigate to detail ---- Restricted proc. go_block('detail')
: go to the first record ---- Restricted proc. first_record
: if :field is null then
: message('at least one child should present') ;
: raise form_triger_failure ;
: end if ;
: commit_form ;
: so for above validation code which is the alternative trigger
: Reply soon
: Bhavesh
: Fatih Sami KARAKAS (guest) wrote:
: : Bhavesh Gandhi (guest) wrote:
: : : I have lots of complex validation written on Key-Commit
: : trigger.
: : : But whenever user tries to clear the form, its asking "Do
: You
: : : Want To Save The Changes", if user says yes then Key-Commit
: : : Trigger is not firing.
: : : Same thing happens when user press Key-Enterqry, Key-Exit
: : : button.
: : : So could u suggest me where can i write my complex
: : validation
: : : that should fire before commit.
: : : Note : I can not write in Pre-commit & On-Commit trigger
: : because
: : : i am having restricted procedure in kEY-COMMIT.
: : : wILL NEW VERSION OF FORMS FIRES HEY-COMMIT TRIGGER.
: : : rEPLY SOON
: : : BHAVESH
: : If you write your validation code in the
: : WHEN-VALIDATE-RECORD trigger then
: : this trigger fires before KEY-COMMIT.
: : For KEY-EXIT and KEY-ENTERQRY, you must re-write this
trigger.
: : for the first one, write the code as
: : exit_form(no_commit);
: : for the second, write
: : clear_block(no_commit);
: : enter_query;
: : Fatih Sami KARAKAS
: : Turkiye
null