Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Current »

Space Index

0-9 ... 0 A ... 0 B ... 2 C ... 2 D ... 1 E ... 1
F ... 2 G ... 8 H ... 2 I ... 11 J ... 0 K ... 0
L ... 1 M ... 1 N ... 0 O ... 1 P ... 8 Q ... 0
R ... 3 S ... 11 T ... 2 U ... 3 V ... 0 W ... 2
X ... 0 Y ... 0 Z ... 0 !@#$ ... 0    




Page: Branding
Branding file editor allows to customize text and images of eSignatureOffice, driver windows and registration window. Start Branding.exe. The left pane displays possible elements that can be customized. In the bottom of the right pane a small text descr
Page: Browser Check
Info We added a Registry Entry to detect if eSO is already installed with the Browser (IE). The Standard and the Addon Setup have a unique value, which contain the Versionnumber, which can be helpful in case it´s also important to know which version the u


Page: Change List
If you want to customize your installation, where the settings will not override the settings from a default installation, you can place a text file with the name "" inside the installation folder of eSignatureOffice. Inside the file you need


Page: Device IDs and display resolutions
This page shall be used as a resource to find information about your signature device, for example when using the <SignPos> tag in XML files to exactly determine the signable area on your device display. Product names are the same as on the StepOver websi


Home page: eSignatureOffice


Page: FFF file structure
FFF file structure FFF file is used to fill in PDF form fields automatically when opening PDF document(s). FFF-file name must be passed in command line together with PDF file name(s). Example: SOSigOffice.exe document1.pdf document2.pdf Values.fff B
Page: Firefox / Chrome
Because the WebSign is an ActiveX Element you can only use it with the InternetExplorer. By default no other Browser is supporting ActiveX Elements, but there is a way to run the WebSign also under FireFox and Chrome.There is a OpenSource Project "ff-acti


Page: getExecutionState
Declaration getExecutionState: Integer; safecall; Description Function returns eSignatureOffice state in overlapped mode. After eSignatureOffice is terminated, calling application may call getXmlResult function. It is recommended to call terminate to free
Page: GetSigResult
Declaration GetSigResult() Description This fuctions returns the XML, that XML is bassicly the same as the ImputXML, but it contains the Signed PDF and other status informations about the signing process. More details about this in the XML-Docu. Return Va
Page: GetSigStatus
Declaration GetSigStatus() Description This fuctions returns the current status of the websign Return Values Value Info -1 Not initialized 0 Unknown 1 Document not loaded 2 Document loaded 3 Signed 4 Sealed 5 Cancelled 6 Sealing error 7 Document closed
Page: getSigStatus()
Declaration function getSigStatus(out Status: Integer) Description Function returns the current Status of the Signing Process Value Status -1 Not Initialized 0 Unknown State 1 Document not loaded 2 Document loaded 3 Signed 4 Sealed 5 Cancelled 6 SealErr
Page: getVersion()
Declaration procedure getVersion(var VersionText:widestring, const LongVersion:BOOLEAN); Description Returns the full Version number of the SOSecureSign.ocx, the long Version includes also the creation date Sample string textVersion; bool longVersion =
Page: GetWorkMode
Declaration GetWorkMode() Description This fuctions returns the current workmode of the websign Return Values Value Info 0 Unknown 3 Viewmode 4 Editmode 6 Signingmode 7 Signing transitional 8 Drawing signature
Page: getWorkMode()
Declaration function getWorkMode(out Status: Integer) Description Function returns the internal Workmode of SecureSign, which can be use to check the current status of the workflow. Value Status 0 None 1 No Document 2 Transitional 3 Viewing 4 Edit 5 Che
Page: getXmlResult
Declaration getXmlResult(out Xml: WideString); safecall; Description Function returns Xml data passed to sigFileXml updated after eSignatureOffice execution. Should be used in overlapped mode after eSignatureOffice is terminated.


Page: handleMessages
Declaration handleMessages: WordBool; safecall Description Host application must call handleMessages periodically if eSignatureOffice was started in overlapped mode using sigFileXml function. This function activates thread synchronization, if it is not ca
Page: HighlightFields
Declaration HighlightFields(string Fielsnames, ) Description This functions Highlights (red rectange around the fields) formfields Arguments Fielsnames List of all Formfields which should be highlighted. They should be separeted with a comma


Page: Input / Output
eSignatureOffice has different typs of INPUT and OUTPUT files which can be used to define the workflow and to analyse the signature process. Input1.PNG The different Input files can also be combined into a XML file. Input2.PNG For more details check the s
Page: Input-XML
General information SOSecureSign.ocx SOWebSign.ocx SOSigOffice.exe All 3 eSignatureOffice Versions can accept input data in XML format. XML text should be passed in a single Unicode string. The definitions of the XML tags can be found inside the following
Page: Input-XML - 1.Window placement and visual Options
Window placement (SecureSign only) Name Description <Window> OR <Fenster> Specifies parent window of eSignatureOffice control. Nested tags described below. <Handle> Defines window handle for eSignatureOffice parent. Hexadecimal values may be passed with 0
Page: Input-XML - 2.Signature fields Definition and Text on LCD
depends on settings in webSignatureOffice Signature fields Definition There are 3 ways to find the Signature Positions inside the document. You can use static coordinates (<Static/>), the alternative is the intelligent search (<Signature>), where we find
Page: Input-XML - 3.Filling PDF form fields
Filling PDF form fields Name Description <FillInfo> Defines name-value pairs for pre-filling of PDF form fields. FillInfo may appear more than once and have an optional attribute File. If File is not specified, then data from FillInfo tag is applied to
Page: Input-XML - 4.Additional Tags
Additional tags Name Description <CorpCode> Allows to pass license code inside XML file. The code must be either a Base64-encoded content of corpcode.lic file or a path to such a file. <GUIMode> Switches between different UI modes. Currently there are mo
Page: Input-XML - 5.Device Options
Options related to the Signature Device Name Description <DeviceKind> or <PADART> Restricts valid signature devices to naturaSignPad-Series only. <BlindPadSearch/> Suppresses device configuration Dialog, if pad was changed. Normally when signature is star
Page: Input-XML - 6.Ouput Tags
Output XML Parameters By default the Output XML is based on the Input-XML, this means it also contains the configuration information. The following Options allow you to reduce this to specific information. Name DescriptionDescription <Output> Tag specifi
Page: Input-XML - 7.Sample
1.) Sample XML with intelligent field: Download: Placeholder.xml (for eSignatureOffice and webSignatureOffice use) This means, the signature placement is based on a keyword inside the document. In addition to the keyword, also the size, placement and the
Page: Install/Deinstall
eSignatureOffice - Setup Parameter Parameter Function -overwrite Overwrites a previously installed program so that the old one does not have to be uninstalled. -lang= This parameter allows you to select the language in which the program is to be installe
Page: Intelligent-Placement
eSignatureOffice can place a signature field based on a keyword inside the document. If the placement is based on 1 keyword, there are additional information like size, placement to the keyword and offset required. The size is based on the width and heigh




Page: Link Handler
Mine Type The eSO Setup sets a Mine Type (Link Handler) to the SOSigOffice.exe to start eSO with a Link. The URL is eso:// and it can also contain all the StartParameter of the SOSigOffice.exe. To seperate the Parameter a | must be used. This is working i


Page: Manual
Manual (English) Anleitung (German)



Page: OpenDocWeb
Declaration OpenDocWeb(string inputxml) Description This fuctions returns the current workmode of the websign Arguments inputxml Input XML with all informations about workflow and other settings. Return Values Value Info 1 Another instance is running


Page: Parameter in <object> tag inside a HTML-Page
The Active X Control could use parameters which are defined inside the HTML-Page. following parameters are possible as <param> Name Type Description ZoomLCD Integer defines the Zoom level of the document viewing when dislpayed on pad "0" = Fit to Width
Page: PrepareExit
Declaration PrepareExit() Description This function is to Prepare the termination of the ActiveX Element.
Page: PrepareExit()
Declaration procedure PrepareExit; safecall; Description Cancel Sign Info Dialog, Hash Dialog and Signing session as preparation of Document closing and ocx removal. Normally the closing of ocx is not done when sign mode is active. Use getWorkMode to dist
Page: pressMacroButton
Declaration pressMacroButton(ButtonIndex: Integer); safecall; Description Function simulates mouse click on a macro button. Zero-based ButtonIndex specifies which macro button action should be executed.
Page: Program.ini
Notes The Program.ini is created by eSignatureOffice and it contains all the settings and the activation. Usually the Program.ini is saved individual for each User in the User Folder: XP: C:\Dokumente und Einstellungen\<user>\Lokale Ein
Page: Program.ini for WebSign
Program.ini location It is possible to use own Program.ini settings file for WebSign. Path to the file can be set in the following registry entry: [HKEY_LOCAL_MACHINE\SOFTWARE\StepOver\WebSign] "IniDir"=<ini_file_location> "ZoomLCD"="1" The value should c
Page: Program.ini of SecureSign
Program.ini location It is possible to use own Program.ini settings file for SecureSign. Path to the file can be set in the following registry entry: [HKEY_LOCAL_MACHINE\SOFTWARE\StepOver\SecureSign] "IniDir"=<ini_file_location> The value should contai
Page: PushButton
Declaration PushButton(string ButtonNumber) Description Function to trigger a MacroButton in WebSign Arguments ButtonNumber Number of the MacroButton which should be triggered



Page: Registry
HKEY_CURRENT_USER HKEY_CURRENT_USER \ Software \ Stepover \ <AppName><MajorVersion>.<MinorVersion><CustomerName> Default installation: HKEY_CURRENT_USER \ Software \ Stepover \ eSignatureOffice 5.4 Customer installation: HKEY_CURRENT_USER \ Software \ Ste
Page: requriedFiles
If you plan not to use the Setup, you can see which Files are nessecary and which are only Optional. Registy Entrys are not nessecary. Name Info Nessecary changelog.txt Someinfos about the last updates no CibDataCsv.dll PDF Library yes CibPdf32.dll PDF Li
Page: RET file structure
RET file structure General information RET file is created by eSignatureOffice when user signs a document with a signature set. RET-file name must be passed in command line together with signature set file name (*.sss). RET file doesn't contain informatio


Page: SCS File
SCS File The SCS (StepOver Configuration Set) File contains Configuration Settings from eSignatureOffice. To be exactly all the Settings, which you can set in the eSignatureOffice Administration or the Startmanager.exe (including the MacroButtons). This a
Page: secFile
Declaration function secFile(const sPubKey1, sPrivKey2, sFileName: WideString): WordBool; safecall; Description This function allows to seal a file and encrypt biodata with asymmetric encryption algorithm. It works the same way as pressing "Seal" button i
Page: SecureSign
Installation The SecureSign requires the full version of eSignatureOffice, you can either use the eSignatureOffice Addon setup which will install the SecureSign automatically or you can install it manually: Copy SOSecureSign.ocx into the eSignatureOffic
Page: SecureSign functions
Page: SetActiveField
Declaration SetActiveField(string fieldname) Description This function sets the focus to a formfield Arguments fieldname Name of the field which should be set to focus.
Page: SetMode
Declaration SetMode(string mode) Description Function to Swtich the Workmode of the WebSign. Arguments mode Number of the mode. Possible combinations of key and value Value Info 3 Viewmode 4 Edit/Form Mode 6 Signature Mode
Page: sigDevSetup
Declaration function sigDevSetup(var sSigSettings: WideString): WordBool; safecall; Description This function invokes signature device configuration dialog from StepOver Signature Device Driver. It uses ActiveX interface to access the driver, so StepOverS
Page: sigFile
Declaration function sigFile(iLeft, iTop, iRight, iBottom: Integer; const sSigSet, sFileName, sCmdLine: WideString; var sErrorText, sSigResult: WideString; hParentWin: OLE_HANDLE): WordBool; safecall; Description This function executes eSignatureOffice
Page: sigFileXml
Declaration sigFileXml(var Xml: WideString; out Error: Integer); safecall; Description This function executes eSignatureOffice with parameters defined by XML file. XML file structure is defined in additional HTML file. If overlapped mode is requested in
Page: SSS file structure
SSS file structure There are 2 possible types of signature sets: sets with explicitly (manually) defined fields and intelligent signature sets. Signature sets with explicitly defined fields. Below is a sample of signature set file: [Main] SignatureFields=
Page: Start-Parameter
To start eSignatureOffice from another application you must call up the file "SOSigOffice.exe". You can transfer different parameters to this file when calling it up, the order of the Parameter doesn´t matter. If you don’t know in which directory eSigna


Page: terminate
Declaration terminate(hParent: OLE_HANDLE); safecall; Description Function terminates eSignatureOffice that was started in overlapped mode using sigFileXml function. hParent - handle to parent window. Can be null if there's no parent window.
Page: Tips and Tricks
Open with eSignatureOffice options for PDFs By default the Setup of eSignatureOffice adds the "open with" which allows to open a PDF with right mouse click inside eSignatureOffice. It´s possible to extend the "open with" start with additional Start-Parame


Page: using automatic DigSig fields
Starting with eSignatureOffice V 5.1 a PDF File with DigSig fields could be loaded and with the start of signing, all digsig fields are possible to sign, without the use of a predefined SSS File. The default behavior (prior to V5.1) when pressing the Si
Page: using automatic SSS-File selection
Sometimes the user could not change the PDF/XML - File nor the command-line or configuration of the application, but whishing to use a specific SSS-File together with the PDF. Starting with eSignatureOffice Version 5.1, the software could try to find and
Page: Using variables
Description You can use some kind of Variables in eSignatureOffice, there are 2 Kinds of variables: External-Variables, which must be set as Startparameter or in the Input-XML Document-Variables, are Values which will be read from the PDF-Document while



Page: WebSign
General information SOWebSign.ocx is an ActiveX control that allows to embed eSignatureOffice in HTML pages. It accepts input data in the same XML format as SOSecureSign.ocx (see Input-XML). Installation The WebSign requires the full version of eSignature
Page: WebSign Functions






  • No labels