Is it possible to change trigger firing sequence by program?

Hi,
I would like to know if there is a command like set_item_property or set_block_property or set_lov_property which can allow to change by program a trigger firing sequence. I do not find any, so i think i have to do it manually in property palette of the trigger. Thanks for your answer.

Thx
To change Execution Hierarchy of a trigger, we go into Property palette of that trigger to change this property, i want to know if it is possible to change this property by program without need to go into Property palette of that trigger, EXECUTE_TRIGGER executes an indicated trigger but how to change Execution Hierarchy (for example set_lov_property sets the given LOV property for the given LOV, we use set_lov_property in the program and do not need to go into property palette of this lov), hope you understand what i would like to do. thanks for your help.
Edited by: Tabit7 on Mar 20, 2011 4:40 AM

Similar Messages

  • Forms trigger Firing Sequence

    Does anyone know where I can find details on firing sequence of each type of triggers on Item, Block and Form levels?
    Can I set the Debugger to trace the actual sequence of firing of triggers at run-time?
    Message was edited by:
    wyfwong

    i hope that the document may help!
    (V45) Trigger Execution Sequence in Forms 4.5
    =============================================
    Introduction
    This document lists the order in which triggers fire in Oracle Forms 4.5:
    o The first column, Action, describes the function to be performed
    (e.g. deleting a record).
    o The second column, Trigger Firing Order, describes the order
    in which triggers fire after a function is performed.
    o The third column, Level, describes the level (form, block, item)
    at which the trigger fires. This was accomplished by creating a form
    with all the triggers invoked. If a trigger could fire at all levels,
    it was included at all levels. Such a trigger fires at the lowest level
    at which it is defined.
    Key triggers and triggers which fire via buttons or check boxes are
    not included.
    This bulletin does not cover every contingency and covers only the
    most commonly used actions.
    Action Trigger Firing Order Level
    Runform 1. Pre-Logon Form
    2. On-Logon Form
    3. Post-Logon Form
    4. Pre-Form Form
    5. When-Create-Record Block
    6. Pre-Block Block
    7. Pre-Record Block
    8. Pre-Text-Item Item
    9. When-New-Form-Instance Form
    10. When-New-Block-Instance Block
    11. When-New-Record-Instance Block
    12. When-New-Item-Instance Item
    Enter Query 1. Post-Text-Item Item
    2. Post-Record Block
    3. When-Clear-Block Block
    4. When-New-Record-Instance Block
    5. When-New-Item-Instance Item
    Note: If you define the Key-ENTQRY trigger, this is the only trigger
    which fires in an Enter Query situation.
    Execute Query
    After Enter Query 1. Pre-Query Block
    2. Pre-Select Block
    3. On-Select Block
    4. When-Clear-Block Block
    5. Post-Select Block
    6. On-Fetch Block
    7. On-Close Form
    8. When-Clear-Block Block
    Note: If you define the Key-EXEQRY trigger, this is the only trigger
    which fires in an Execute Query situation.
    Execute Query
    Without Enter
    Query 1. Post-Text-Item Block
    2. Pre-Query Block
    3. Pre-Select Block
    4. On-Select Block
    5. Post-Select Block
    6. On-Fetch Block
    7. On-Close Form
    8. When_Create_Record Block
    9. Pre-Record Block
    10. Pre-Text-Item Item
    11. When-New-Record-Instance Block
    12. When-New-Item-Instance Item
    Exit 1. Post-Text-Item Item
    2. Post-Record Block
    3. Post-Block Block
    4. Post-Form Form
    5. On-Rollback Form
    6. Pre-Logout Form
    7. On-Logout Form
    8. Post-Logout Form
    Next Field and
    Previous field 1. When-New-Item-Instance Item
    Next Record and
    Previous Record 1. When-New-Record-Instance Block
    2. When-New-Item-Instance Item
    Next Block and
    Previous Block 1. Post-Text-Item Item
    2. Post-Record Block
    3. Post-Block Block
    4. When-Create-Record Block
    5. Pre-Block Block
    6. Pre-Record Block
    7. Pre-Text-Item Block
    8. When-New-Block-Instance Block
    9. When-New-Record-Instance Block
    10. When-New-Item-Instance Form
    Records Are Queried 1. Post-Query Block
    2. Post-Change Block
    3. Post-Change Item
    4. Post-Change Block
    5. Post-Change Block
    Go back to Post-Query
    NOTE: This cycle is repeated for each record retrieved.
    No Records Are Queried 1. When-New-Record-Instance Block
    2. When-New-Item-Instance Item
    NOTE: To observe this Trigger Firing Order:
    a. Enter a query.
    b. Enter a nonexistent record.
    c. Execute the query.
    The two triggers listed above, the Enter Query triggers, and
    the Execute Query triggers fire.
    Create Record 1. Post-Change Block
    2. When-Validate-Item Block
    3. Post-Text-Item Block
    4. When-Validate-Record Block
    5. Post-Record Block
    6. Post-Block Block
    7. On-Savepoint Form
    8. Pre-Commit Form
    9. Pre-Insert Block
    10. On-Insert Form
    11. Post-Insert Block
    12. Post-Forms-Commit Form
    13. On-Commit Form
    14. Post-Database-Commit Form
    15. Pre-Block Block
    16. Pre-Record Block
    17. Pre-Text-Item Block
    18. When-New-Item-Instance Form
    Update Record 1. When-Database-Record Block
    2. Post-Change Block
    3. When-Validate-Item Block
    4. Post-Text-Item Block
    5. When-Validate-Record Block
    6. Post-Record Block
    7. Post-Block Block
    8. On-Savepoint Form
    9. Pre-Commit Form
    10. Pre-Update Block
    11. On-Update Block
    12. Post-Update Block
    13. Post-Forms-Commit Form
    14. On-Commit Form
    Here the transaction is complete and one record added.
    15. Post-Database-Commit Form
    16. Pre-Text-Item Block
    17. When-New-Item-Instance Form
    NOTE: To observe this Trigger Firing Order:
    a. Execute a query.
    b. Change a value.
    c. Choose Action->Save from the menu.
    d. Record the triggers from that point.
    Delete Record 1. On-Lock Block
    2. When-Remove-Record Block
    3. Post-Change Block
    4. Post-Change Block
    5. Post-Change Block
    6. Post-Change Block
    7. Post-Change Block
    8. Post-Change Block
    9. Post-Change Item
    10. Post-Query Block
    11. Post-Text-Item Block
    12. Post-Record Block
    13. Pre-Record Block
    14. Pre-Text-Item Block
    15. When-New-Record-Instance Block
    16. When-New-Item-Instance Form
    NOTE: To observe this Trigger Firing Order, delete a detail record.

  • Trigger Firing Sequence?

    Hei Guys
    I have a form where I have a date and time field(text fields). I have a OK/SAVE button, which is subclassed, and executes do_key(commit_form), which in turn executes form level key-commit trigger. On the key-commit trigger, I have some program units, which basically validate the form, and then commit the form.
    On the time field, if I change the time(which the system calculated when I hit a button), I do some validation in the when-validate-item of the field.
    The code in the time text-fields, when-validate-item is as follows.
    fp_check_time(:BL_COMPLAINT.APPT_TIME);
    declare
         lnu_error number;
         alrt_id alert := find_alert('AL_CONFIRM');
         some_number number;
    begin
         --some_number := fpkg_error_handler.fp_message('UEM','0000','ERROR','@when-validate APPT_TIME');
         --set_item_property('bl_ok_cancel.pb_ok', enabled, property_true);     
         if :BL_COMPLAINT.APPT_time <> nvl(:parameter.APPT_TIME, '*')     then
    set_alert_property(alrt_id, alert_message_text, 'You have changed the system recommended date. This could lead to double booking. Do you want to continue ?');
    if show_alert(alrt_id) = ALERT_BUTTON1 then
    if spkg_med_schedule.sf_chk_valid_datetime
              (:BL_COMPLAINT.SICK_CALL_SERVICE_GROUP,
    '1',--check nurse
    :parameter.p_clinic,
    :BL_COMPLAINT.APPT_DATE,
    :BL_COMPLAINT.APPT_time) = 'N' THEN
         lnu_error := FPKG_ERROR_HANDLER.FP_MESSAGE('UEM','0000','ERROR','The date/time you have selected is not valid. Please change the date/time.');
         :BL_COMPLAINT.APPT_TIME := :parameter.APPT_TIME;
         --set_item_property('bl_ok_cancel.pb_ok', enabled, property_false);
          raise form_trigger_failure;
    end if;
    else
              some_number := fpkg_error_handler.fp_message('UEM','0000','ERROR','@when-vaidate APPT_TIME not ab1');          
         :BL_COMPLAINT.APPT_TIME := :parameter.APPT_TIME;
    --     :parameter.error_occur := 'TRUE';
         --set_item_property('bl_ok_cancel.pb_ok', enabled, property_false);
         raise form_trigger_failure;      end if;
    end if;     
    end;
    I have this code even in the date field. which is also a text item.
    I am hoping you might have noticed, a couple of Raise form_trigger_failure in the code. But, the processing, does not stop there and continues processing and tries to commit the form.
    [b1.]Why does that happen?

    > continues processing and tries to commit the form
    It would help if you would describe what you mean by "tries to commit". What does the form do?
    The first thing you need to do in your commit processing sequence is:
      Validate(form_scope);
      If not form_success then
        Raise form_trigger_failure;
      End if;The above code will stop the commit if an edit error occurs. If you don't validate and check for success, commit processing continues, and you will probably get multiple error messages popping up before the commit process finally stops.

  • Possible to change the variables in the program permanently?

    Is it possible to change the content of the variable in the MIDlet application??

    Hello,
    As there is no beans mechanism in J2ME, here is what you can do. You can save values into RMS and then fetch them from there when you load the MIDlet.
    Regards,
    Petteri
    Nokia Corp.

  • Prevent of trigger firing because of program process

    Consider we have a combobox and a datagridview all in vs2013, with the following triggers :
     combobox.SelectedIndexChanged : when the event fires, the datagridview is filed up with the appropriate data, according to the new selection.
    datagridview.SelectionChanged : when this event fires, the detailed information for the current row-data is displayed.
    In the process of the combobox.SelectedIndexChanged event, I use a datagridview.rows.clear() statement to clear the datagridview, before the new data stored on it.
    In this case when the  datagridview.rows.clear() statement is executed, the datagridview.SelectionChanged event fires, with unpredictable results.
    Any idea on how to prevent of firing datagridview.SelectionChanged event ?
    Thanks in advance
    George 

    you can add and drop the handler when needed (remove the handles from the event if you use below method),
    AddHandler datagridview1.SelectedIndexChanged, AddressOf datagridview1_SelectedIndexChanged
    RemoveHandler datagridview1.SelectedIndexChanged, AddressOf datagridview1_SelectedIndexChanged
    OR
    keep track of some boolean value you set to true or false depending if you want to execute the code in the event, so something like
    Private gridupdate as boolean = false
    Private Sub ComboBox1_SelectedIndexChanged_1(sender As Object, e As EventArgs) Handles ComboBox1.SelectedIndexChanged
    gridupdate = false
    datagridview.rows.clear
    End Sub
    Private Sub datagrid_SelectionChanged(sender As Object, e As EventArgs) Handles datagrid.SelectionChanged
    if grdupdate = true then
    'do your thing
    end if
    End Sub

  • Triggers Firing Sequence Of Forms 10g after commit_form trigger.

    hi all,
    please tell me Triggers Firing Sequence Of Forms 10g after commit_form trigger.
    thanks,
    Regards,
    Ambarish

    Hi,
    I have a doubt regarding the sequence of events when COMMIT_FORM is fired.
    Using the following to trigger the event.
    DO_KEY('COMMIT'_FORM');
    Added debug messages in my form triggers and found that after the ON-INSERT trigger is fired, the WHEN-VALIDATE-RECORD is fired and then the PRE-RECORD.
    However this sequence is not specified in the lists of firing sequences mentioned here.
    Is it possible to change the sequence programmatically.
    In my ON-INSERT trigger, calling a DB procedure to insert row in the table.
    Thanks
    Asfa

  • Sequence of trigger firing in forms 6i

    hai,
    please reply soon ..
    i need full details about sequence of trigger firing when form initiate,
    query mode,modify mode,delete mode and insert mode in forms 6i .
    regards,
    B.prakash

    please look into the forms 6i online help manuals. There are the trigger flows of all events

  • Sequence of trigger firing in Forms

    hi all,
    can any one tell me sequence of trigger firing in forms
    regards,
    Ajay

    Sorry boss,
    the actual link is:-
    Forms trigger Firing Sequence

  • Firing sequence of Oracle forms 6.0 triggers

    Hi All,
    Pls tell anyone what is the sequence of trigger firing in oracle 6.0 (oracle apps).
    Thanks in advance

    Hi,
    Please see if these links/docs help.
    Note: 61675.1 - Trigger Execution Sequence in Oracle Forms
    firing sequence of triggers in oracle forms
    http://tinyurl.com/2wyffj6
    Thanks,
    Hussein

  • Is it possible to change the frame rate of a motion template?

    Motion has some very useful templates, but the majority are only offered in NTSC, not PAL. (including all in 3D TEXT PROJECTS).
    Is it possible to change the frame rate to 25fps before I start adding my own stuff, so that I can easily get the timing right for a PAL sequence in FCP.
    If not in Motion, how else could this been changed?

    Try dragging all the groups from one project into another instead - you'll need to open both project and rearrange the windows so you can see the layers tab for both of them.

  • How to realize WHEN-RADIO-CHANGED- Trigger in ADF

    Hy@ all,
    I try to redevelop the Summit Forms Demo in ADF.
    One of the existing modules is called "ORDER" and contains, among other things, radio buttons based on a database column(VARCHAR2) named PAYMENT_TYPE which contains the values CASH and CREDIT.
    Based on this Item a WHEN-RADIO-CHANGED- Trigger is called which shows an alert and reset the changes to a default value when the payment type is changed but the credit rating(database column from another table) is not equal to an according value.
    The code of the trigger is the following one:
    DECLARE
         n NUMBER;
         v_credit S_CUSTOMER.CREDIT_RATING%TYPE;
    BEGIN
         IF :S_ORD.payment_type = 'CREDIT' THEN
              SELECT credit_rating
              INTO v_credit
              FROM S_CUSTOMER
              WHERE :S_ORD.CUSTOMER_ID = ID;
         IF v_credit NOT IN ('GOOD', 'EXCELLENT') THEN
              :S_ORD.payment_type := 'CASH';
              n := SHOW_ALERT('PAYMENT_TYPE_ALERT');
         END IF;
         END IF;
    END;
    Now my questions are where to place the equivalent code(EO, VO, etc.?) and how to realize this.
    Further, is it possible to roll out the trigger code to the database and then call this stored unit from "the right place"?
    I´m using JDeveloper v10.1.3.1.0 and I´m pleased about any reply or solution.
    Best regards
    Chris

    The answer will depend on how you are storing the parameter in your ADF application and when do you actually need it to be set and based on what.
    This can be for example a property of a managed bean in your JSF application and you can initialize it either in the bean itself or in the faces-config.xml file as a managed property.
    http://www.oracle.com/technology/tech/java/newsletter/articles/jsf_pojo/index.html

  • In Premiere Pro, is it possible to change the project aspect ratio once started?

    In Premiere Pro, is it possible to change the project aspect ratio once started?

    On a side note, 'projects' do not have as aspect ratio, sequences and footage do.  And a project can contain any number of sequences or footage.

  • Possible to change date format when importing files into Aperture 3

    Just wondering if it is possible to change the format of the date from YYYY-MM-DD to YYYYMMDD when you rename files as they are imported into Aperture 3? I typically rename my files and insert my initials, date the photo was taken, sequence number, camera used and original file name. When I do this in Aperture 3, the date format used includes dashes. I would like to have the file renamed without the dashes in the date. Is this possible?

    You should be able to edit the format in the import presets. I have done this for folder stucture of imports, I believe you can do the same for the file renaming. At the bottom of the drop down box for file naming at improt should be an edit option which brings up the import naming presets, select the "YYYY-MM-DD" and remove the dashes.
    Matt

  • Post-change trigger problem

    I have problem with post-change trigger, i'm using Forms 10g
    I have two block, one is database block and the other is non-database block for example A is Nondatabase block and B is Database block, I have written commit_form built-in in Key-Next-Item of a item in B(database) block. When it is getting executed commit_form built-in firing the post-change trigger of a item in A(Non-database) block. I dont know why it is firing and I dont want the post-change trigger to fire (we are not assigning any value to that item in A block during commit_form).
    Can anybody help me on this..
    Regards
    Radha

    when you issue a commit_form, forms will validate all items in all blocks which re not valid at that moment. This also occurs for non-database-block.
    The question is why is the item not valid ? Are you putting something in it in some other trigger? If so, you could explicitly set the itemstate to valid with a
    SET_ITEM_PROPERTY('BLOCK.ITEM', ITEM_IS_VALID, PROPETY_TRUE);btw.. you should not use the POST-CHANGE-trigger for validations etc. its better to use the WHEN-VALIDATE-ITEM-trigger.

  • SOAP RECEIVER: Possible to change the soap header request

    Hi
    Is it possible to change what is included in the soap header like namespaces (.. xmlns:ns="http://what.com"
    Specifically I need to have the "http://Strange.org/thisis.xsd" (see below) included in the header and the <ns:pi-create> included in SOAP-ENV
    <SOAP-ENV:Envelope xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"
    xmlns:SOAP-ENC="http://schemas.xmlsoap.org/soap/encoding/"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:xsd="http://www.w3.org/2001/XMLSchema"
    xmlns:ns="http://Strange.org/thisis.xsd">
    <SOAP-ENV:Body>
    <ns:pi-create>
    <request>
    <request-data>...
    </request-data>
    </request>
    </ns:pi-create>
    </SOAP-ENV:Body>
    </SOAP-ENV:Envelope>
    Hope somebody can help
    Cheers

    Hi Bowie,
    1.You can change the Namespace. condition is no obj's under the namesapce then only it's possible otherwise u can't.
    2.create a new namesapce what ever u want and copy all the obj's under that namesapce.finally delete the previous one.
    XMLAnonymizerBean
    Use
    You use this module to anonymize XML elements and attributes by removing namespaces or namespace prefixes from the XML document of the main payload.
    You can define a particular namespace prefix for each namespace. You can also change the encoding attribute of the XML declaration.
    Integration
    You can use the module in adapters that can be extended in the module processor.
    Activities
    Entries in the Processing Sequence
    ●      Insert the module before the adapter module.
    If the adapter comprises multiple modules, for information about the position of the module, see: Extending the Module Chain in the Module Processor
    ●      Enter the module name AF_Modules/XMLAnonymizerBean.
    ●      Select the Module Type Local Enterprise Bean.
    ●      The system proposes a module key.
    Entries in the Module Configuration
    ●      anonymizer.acceptNamespaces
    Enter a list of namespaces and their prefixes that are to be kept in the XML document as follows: namespace1 n1 namespace2 n2 u2026
    To enter a namespace without a prefix, enter '' (two single quotation marks).
    Any namespaces you do not specify are removed from the XML document.
    ●      anonymizer.quote
    Specify the character to be used to enclose the attribute values.
    The default value is '. The parameter is optional.
    ●      anonymizer.encoding
    To use a code page other than UTF-8, enter it.  The parameter is optional.
    For example, enter ISO-8859-1.
    Example
    The anonymizer.acceptNamespaces parameter has the following value:
    urn:sap-com:document:sap:rfc:functions rfc urn:sap-com:document:sap:soap:functions:mc-style rfc
    ●      Payload before using the XMLAnonymizerBean:
    <Z_PAYMITEM_GET_LIST
      xmlns="urn:sap-com:document:sap:rfc:functions"
      xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"
      xmlns:xsd="http://www.w3.org/2001/XMLSchema"
      xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
      xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
      <I_ACCOUNTIDENT xmlns="">
        <ACCOUNT_NUMBER>0080000094</ACCOUNT_NUMBER>
        <BANK_COUNTRY>DE</BANK_COUNTRY>
        <BANK_COUNTRY_ISO>DE</BANK_COUNTRY_ISO>
      </I_ACCOUNTIDENT>
    </Z_PAYMITEM_GET_LIST>
    ●      Payload after using the XMLAnonymizerBean:
    <?xml version='1.0' encoding='utf-8'?>
    <rfc:Z_PAYMITEM_GET_LIST
      xmlns:rfc='urn:sap-com:document:sap:rfc:functions'>
      <I_ACCOUNTIDENT>
        <ACCOUNT_NUMBER>0080000094</ACCOUNT_NUMBER>
        <BANK_COUNTRY>DE</BANK_COUNTRY>
        <BANK_COUNTRY_ISO>DE</BANK_COUNTRY_ISO>
      </I_ACCOUNTIDENT>
    </rfc:Z_PAYMITEM_GET_LIST>
    with rgds,
    MFH

Maybe you are looking for