This discussion is archived
2 Replies Latest reply: Feb 15, 2013 4:04 AM by Bhushan53 RSS

Handling AutoSave feature in Oracle Forms

user12187495 Newbie
Currently Being Moderated
Hi All,

For one of our requirement we need to invoke a custom form during save of standard order mangement form.

Working Cases:

1. When user enter line details and click save button in the menu, custom form open without any issues.
2. When user enter line details and give CTRL+S, custom form open without any issues.

Failing Cases:

1. When user creates a new line and navigate to previously created line.(Eg: creates new line 3.1 and navigates to 2.1). What happens is, the line gets auto saved. User is not using save button/CTRL+S options. During this the custom form is not getting invoked.
2. When user creates a new line and navigate to header region. (Eg: add new line 3.1 and click header tab). Now again the line gets auto saved. Custom form is not getting invoked.
3. When user changes a field and navigates to another field. Eg: Changes unit selling price and tabs out. Changes getting auto saved. User is not using save button/ctrl+s options. During this case custom form not opening.

Summary:

Custom form gets invoked if user add/modify lines and press save button/Ctrl+S.
If user do autosave as mentioned in failing cases, custom form is not getting invoked.

Request to provide pointers in handling the failing cases. In which triggers we need to handle the codes to invoke the custom form. Any pointers/Suggestions will be helpful.

Thanks in advance.

Regards,
Rajesh.
  • 1. Re: Handling AutoSave feature in Oracle Forms
    Andreas Weiden Guru
    Currently Being Moderated
    Sounds like eBusiness-suite. So without changing the original code and find all COMMIT_FORM, the only chance i see is to intercept the PRE-COMMIT.
  • 2. Re: Handling AutoSave feature in Oracle Forms
    Bhushan53 Newbie
    Currently Being Moderated
    The required functionality can be achieved by -

    1. When user created a new record and moved to an existing record w/o explicitly saving it.
    Just track a mandatory field, say USP in this case. Compare the values of that field in when-new-record-instance and when-validate-record. If there's a difference, we can invoke the custom form.

    2. While at the item level, we have to track it down with when-new-item-instance for the desired item. As, when-validate-item is not supported by PLL.

    But, for the data concerned with both these cases to be populated in the custom form that you are invoking, you need to issue a commit statement before invoking the form.

    Regards

Legend

  • Correct Answers - 10 points
  • Helpful Answers - 5 points