1 / 8

Generic Workflow API 17 April 2002

Anil Passi. Generic Workflow API 17 April 2002. Why this Generic Workflow. One workflow handles most of the notification tasks No need to design and develop a new workflow for each notification requirement Can be used by all the developers, using a simple API call

jabir
Download Presentation

Generic Workflow API 17 April 2002

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Anil Passi Generic Workflow API 17 April 2002

  2. Why this Generic Workflow One workflow handles most of the notification tasks No need to design and develop a new workflow for each notification requirement Can be used by all the developers, using a simple API call Optionally can be used for error handling

  3. Notification can be a Static Text Notification can be a Static HTML Text Notification can be an output of a query. Result of Select Statements displayed nicely in tabular format Notification can be an output of more than one Select Queries Notification can be the combination of Static HTML/Text and SELECT Statement Notification contents will be dynamically built at runtime from the parameters passed to API. Main Features

  4. How does it work?? ( Send a static message) XXDHI_NOTIFICATIONS_API_PKG.SEND_NOTIFICATION ( X_EMAIL_ADDRESS=>'anilpassi@hotmail.com' ,X_USER_NAME=>'UKEXPI' ,X_MESSAGE_TYPE=>'TEXT' ,X_PROCESS_SHORT_CODE=>'TEST' ,X_MESSAGE_SUBJECT=>’Please authorize the outstanding FX deal 403. ' ,X_MESSAGE_TEXT=>’The FX Deal 403 is outstanding. Please authorize it ASAP.' ,X_NOTIFICATION_API_ID=>n_not_id ) ;

  5. Dynamic Role Creation(If needed) How does it work?? ( Send a message static HTML) XXDHI_NOTIFICATIONS_API_PKG.SEND_NOTIFICATION ( X_EMAIL_ADDRESS=>'anil_passi@rcomext.com' ,X_USER_NAME=>'UKEXPI' ,X_MESSAGE_TYPE=>'TEXT' ,X_PROCESS_SHORT_CODE=>'TEST' ,X_MESSAGE_SUBJECT=>’ Please resolve the Receipt Number 2032402 ' ,X_MESSAGE_TEXT=> '<body> <p>Please note that you must resolve the Receipt Number 2032402.<br> This receipt is worth USD 32,434,000/-<br> This receipt has been unallocated in INBOX since 23Days.<br> Please use Triage to allocate this receipt to appropriate Technical System.<br> Free text on the SWIFT message is: <br> Treaty TOW10043, paying the premium<br> </p> <p><font color="#0000FF">Thanks<br> Delphi Treasury Team<br> 22-APRIL-2002<br> </font></p> </body>' ,X_NOTIFICATION_API_ID=>n_not_id ) ;

  6. How does it work?? ( Send a message static plus dynamic) XXDHI_NOTIFICATIONS_API_PKG.SEND_NOTIFICATION ( X_EMAIL_ADDRESS =>'anilpassi@hotmail.com' ,X_USER_NAME =>'UKEXPI' ,X_MESSAGE_TYPE =>'TEXT' ,X_PROCESS_SHORT_CODE =>'TEST' ,X_MESSAGE_SUBJECT =>’Please authorize the outstanding FX deal 403. ' ,X_MESSAGE_TEXT =>’The FX Deal 403 is outstanding. Please authorize it ASAP.' ,X_NOTIFICATION_API_ID =>n_not_id ) ; XXDHI_notifications_api_pkg.add_query ( X_NOTIFICATION_API_ID => n_not_id ,X_QUERY_TITLE_TEXT => 'These are the recent deals' ,X_FROM_CLAUSE => 'xtr_deals' ,X_WHERE_CLAUSE => 'ROWNUM < 5 AND dealer_code = ''UKEXPI''' ,X_BIND_VALUES => NULL ,x_column_title_1 => 'Counter Party' ,x_column_name_1 => 'CPARTY_CODE' ,x_column_title_2 => 'Deal Number' ,x_column_name_2 => 'deal_no' ,x_column_title_3 => 'Buy Amount' ,x_column_name_3 => 'buy_amount' ) ; This API call will dynamically generate from tables the following notification

  7. Notification Subject Query Title Static Text First Query Result Second Query Result How does it work?? ( More than one queries can be used) XXDHI_notifications_api_pkg.SEND_NOTIFICATION ( X_EMAIL_ADDRESS =>'anilpassi@hotmail.com' ,X_USER_NAME =>'UKEXPI' ,X_MESSAGE_TYPE =>'TEXT_AND_QUERY' ,X_PROCESS_SHORT_CODE =>'TEST' ,X_MESSAGE_SUBJECT =>'Please authorize the outstanding FX deal 403' ,X_MESSAGE_TEXT =>'The FX Deal 403 is outstanding. Please authorize it ASAP.' || 'Please see the table for details of your recent deals. ' || 'Also listed are the payment terms' ,x_notification_api_id =>n_not_id ) ; XXDHI_notifications_api_pkg.add_query ( X_NOTIFICATION_API_ID => n_not_id ,X_QUERY_TITLE_TEXT => 'These are the recent deals' ,X_FROM_CLAUSE => 'xtr_deals' ,X_WHERE_CLAUSE => 'ROWNUM < 5 AND dealer_code = ''UKEXPI''' ,X_BIND_VALUES => NULL ,x_column_title_1 => 'Counter Party' ,x_column_width_1 => 10 ,x_column_name_1 => 'CPARTY_CODE' ,x_column_title_2 => 'Deal Number' ,x_column_width_2 => 5 ,x_column_name_2 => 'deal_no' ) ; XXDHI_notifications_api_pkg.add_query ( X_NOTIFICATION_API_ID => n_not_id ,X_QUERY_TITLE_TEXT => 'This is the data in payment terms' ,X_FROM_CLAUSE => 'ap_terms' ,X_WHERE_CLAUSE => 'ROWNUM < 5' ,X_BIND_VALUES => NULL ,x_column_title_1 => 'TERM ID' ,x_column_width_1 => 10 ,x_column_name_1 => 'TERM_ID' ,x_column_title_2 => 'Term Name' ,x_column_width_2 => 5 ,x_column_name_2 => 'name' ) ; This API call will dynamically generate from tables the following notification The query can be a complex query with various tables and joins

  8. Developer’s World Check validity of parameters Insert records in tables XXDHI_NOTIFICATIONS_API XXDHI_NOTIFICATION_QUERIES XXDHI_NOTIFICATION_COLUMNS API World Internally handled by API Database trigger initiates workflow Workflow builds the information SQL STATEMENT based documents are generated in real time from browser/email client How does it work technically? Call API (xxdhi_notifications_api_pkg)

More Related