Bookshelf Home | Contents | Index | PDF |
Siebel Life Sciences Guide > Using Personalized Content Delivery > Accessing and Delivering Messaging Plans > Using Signature Control for Personalized Content DeliveryWith signature control, users can capture signatures for samples disbursement to qualified contacts. This section contains the following topics:
About Loading Signature ControlThere is a separate component for capturing signatures in Flex. This component is available in PCD as an Signature control can be loaded in PCD using three different modes:
Configuring Signature Control ModesThis section outlines the required configuration steps for different signature control modes. For additional information about the modes available, see About Loading Signature Control. Configuring Mode 1 Signature ControlThis topic contains information about configuring signature control for mode 1. When the instructions in this section are applied to a messaging plan, the specified signature message will be displayed when the representative clicks Sign. To configure mode 1 signature control
Configuring Mode 2 Signature ControlThis topic contains information about configuring signature control for mode 2. When the instructions in this section are applied to a messaging plan, the specified signature message will be embedded in the message that is being played at that moment. To configure mode 2 signature control
Signature Capable MessagesA signature capable message is an SWF file that has a space allocated in it for displaying the PCD signature control: SignatureCtrl.swf. The file communicates with both the signature control and the PCD application. To properly implement a signature capable message certain requirements are member variables must be set, and certain methods must be applied. Follow the requirements in the following sections before using signature control:
Member Variable Requirement for Signature Capable MessagesIn order to hold a pointer to the SignatureCtrl.swf embedded within the message set the following variable:
This pointer will be used to invoke methods in SignatureCtrl.swf Method Requirements for Signature Capable MessagesThe following method requirements must be met in order to properly implement signature control:
FlexApp ExamplesFlexApp is a sample signature asset created in Flex. This asset has the following minimum method requirements:
FlexApp appLoaded ExampleFlexApp.mxml has a method called appLoaded. The <mx:Application .....................applicationComplete="appLoaded();"> public function appLoaded():void Application.application.signAssetLoadComplete(this); The appLoaded method notifies the parent application -- in this case Interactive Detailer -- that the Signature Asset is loaded and ready to load SignatureCtrl.swf, using the following statement: Application.application.signAssetLoadComplete(this); Where Application.application refers to Interactive Detailer and signAssetLoadComplete refers to a method in Interactive Detailer that receives a pointer to the Signature Asset as an input parameter. This pointer will be used by the Interactive Detailer to send data to the SignatureCtrl.swf embedded in the Asset. FlexApp LoadSignCtrl ExampleFlexApp.mxml has member variable of type SystemManager. This member variable holds a pointer to the SignatureCtrl.swf embedded within the asset. The pointer is shown in the following sample: private var m_signCtrl:SystemManager; public function loadSignCtrl(strSignCtrl:String):void loader.addEventListener(Event.INIT, loadComplete); private function loadComplete (event:Event) : void m_signCtrl = SystemManager(event.target.content); The Interactive Detailer sends the path of SignatureCtrl.swf The Signature Asset method, loadSignCtrl FlexApp InvokeSignCtrlMethod ExampleFlexApp.mxml also implements a method called InvokeSignCtrlMethod. When the Interactive Detailer is required to send data to SignatureCtrl.swf, it does so by calling this method in the Asset. The following XML data is passed to the Asset: public function InvokeSignCtrlMethod(strXMLData:String):void Object(m_signCtrl.application).InvokeMethod(strXMLData); Capturing a SignatureWith signature control, users can capture signatures for samples disbursement.
Modifying Contacts in the Signature ComponentA representative can change the contact to another contact within the signature component. For example, a representative is speaking with Dr. A. A Contact Call Record has already been created for Dr. A. The representative adds sample drop records to this call by clicking the Detail button in Call view. Now consider that the signature was captured for Dr. A and saved. The status of the record has been changed to Signed. If instead of Dr. A, the representative selects a different contact: Dr. B. The signature control will then create a new contact call record in the Siebel database for Dr. B, and the sample records will be copied over to the new call. This new call will be validated, and the signature is captured and saved and the status of the call record will be set to Signed. The module will only allow the representative to change the contact if the validation process confirms that the contact is eligible. Otherwise, an error message will appear. To modify contacts in the signature component
Deleting a Sample RowA representative can delete a sample in signature component. For example, if the representative is speaking with Dr. A and discovers that the sample is not of use, the sample row can be deleted. To delete the sample row in the signature component
Cancelling a TransactionThe following topic describes how to cancel a transaction. The Cancel button will cancel but will not delete all of the data associated with the transaction. When the Cancel button is clicked, it marks the transaction as voided, but is sent back to the system as a no signature activity.
When you click the Cancel button in signature control, a cancelled transaction record will be written to the Siebel database only if the transaction was valid. A transaction is valid only when it passes all the validation checks and the signature was captured but the action was cancelled. Viewing all Captured Signature DataOnce a signature is captured, it is stored in the Siebel database for future reference. You can view all of the captured signature data in one location. |
Siebel Life Sciences Guide | Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices. | |