0 Replies Latest reply on Aug 18, 2014 4:44 PM by Piyush Chauhan-Oracle

    Use of custom primary key using OSM Activation Tasks

    Piyush Chauhan-Oracle


      We are using OSM Activations Task to interact with ASAP. By default it uses OSM_ORDER_ID.HIST_ID as the corelation key and same as primary key while sending the request to ASAP. Is there a way we can customize this logic so as to send a custom value as the primary key to ASAP.