Testing the Event with XML Payload
As mentioned in previous article, we will attempt to extract the value of Bank Account Number from the Payload. The extracted value will then be assigned to the WF Attribute.
Lets see this working, in steps. You must implement previous article [ Link here for Workflow with Payload ] before trying this exercise.
Step 1. Run the below update
update ap_bank_accounts_all t set t.bank_account_num = '101010' where rownum < 2 ;
commit;
This step will build the XML Payload and initiate the event.
Step 2. Lets go to WF Status Monitor and check to see if Workflow Process has been launched.
Step 3. Click on Workflow details to see if Bank Account Number has been extracted and assigned to desired WF Attribute.
BANK_ACC_CHANGED_PAYLOAD Click on this link ro view the XML Payload generated by Trigger on bank account table
BANK ACCOUNT NUMBER FROM PAYLOAD 101010 (The bank account number extracted from XML Payload of the event)
This concludes the testing of XML Payload with Oracle Workflows Business Event.
Note:- You may also decide to use the "Test Functionality" by clicking on Test button in Workflow Event screen. However I preferred testing via a methodology that encapsulates end-to-end approach.
Comments
For subscriptions, we have to select our system and attach our workflow.
I am able to launch workflow but I can not see bank account number.
XML data is only like this:
-
xx.ap.bank.acco untupdate
19486
Anil,
afte r updating records in ap_bank_account s_all table. not able to see the status monitor for this process..
.
.
Hi Ram
I am impressed, you were quick in trying this out.
May be your subscription is in the deferred queue.
Is the phase of subscription between 1 and 99?
If so, email me your screenshots of your event/subscript ion definitions.
Thanks
Anil Passi
For subscriptions, we have to select our system and attach our workflow.
I am able to launch workflow but I can not see bank account number.
XML data is only like this:
-
xx.ap.bank.acco untupdate
19486
Anil,
afte r updating records in ap_bank_account s_all table. not able to see the status monitor for this process..
.
.
Hi Ram
I am impressed, you were quick in trying this out.
May be your subscription is in the deferred queue.
Is the phase of subscription between 1 and 99?
If so, email me your screenshots of your event/subscript ion definitions.
Thanks
Anil Passi
Goo d to see that you are able to initiat Workflow.
So the hard work has been done.
In order to debug your issue, I need your XML Message. Please can you email me that.
Go to Workflow Status Monitor, and click on Workflow Details, and then click on Event Attribute hyperlink to see XML message.
Ema il me that XML message
Than ks,
Anil Passi
Goo d to see that you are able to initiat Workflow.
So the hard work has been done.
In order to debug your issue, I need your XML Message. Please can you email me that.
Go to Workflow Status Monitor, and click on Workflow Details, and then click on Event Attribute hyperlink to see XML message.
Ema il me that XML message
Than ks,
Anil Passi
how ru this bhaskar i have one query i have instel oracle 11.5.10.vertion in this datbase is 9i ,now i want instel workflow builder witch vertion it works , i dowenloeded 10 g server but its is asking again oracle home/ path ,
Simply install the 10g client on your PC. That should come bundled with WF Builder version 2.6.x
This will work with 11.5.10 instance.
Than ks,
Anil Passi
Though Event is raised , the bank_acc_change d_payload is not getting populated with userid , bank number .
it seems as though the l_event_data is getting only event name and event key
MR
I have followed all the steps implementing payload. when i try to update the bank_account table the trigger fires and raises the event but after that nothing and also when i try to search for my workflow in status monitor screen i can not see anything under that.
I have doubt in the procedure, can please explain the procedure you have created by the name of (xx_get_bank_ac count_number).
Thanks & Regards,
khan
The solution to this is we need to pass a dummy parameter like this..
l_param eter_list := WF_PARAMETER_LI ST_T := WF_PARAMETER_LI ST_T();
-- Then add a dummy parameter
wf_e vent.addparamet ertolist ( p_name => 'FIRST_PARAMETE R'
,p_value => 'FIRST PARAMETER VALUE'
,p_parameterlis t => l_parameter_lis t
);
-- Pass this parameter list while raising the event along with xmlpayload
wf_ event.RAISE ( p_event_name => l_event_name
,p_event_key => l_event_key
,p_event_data => l_event_data
,p_parameters => l_parameter_lis t --- This point has been missing from the above exampl
Thanks,
Mahesh.K
);
Thank you very much for your great work on workflow events and its use. I've to say I am enjoying it a lot. I've a question regarding the use of workflow events to pass XML data, what's the benefit of using workflow events compared with using a document attribute to pass the XML data? I hope you are still answering the questions received on your forum. Have a great day
RSS feed for comments to this post