Page History

...

The next screenshot shows these configurations:

Image RemovedImage Added

If the feature is available for your organization, you can:

...

button[data-id='SignOnPhone'] {
    visibility: hidden;
}

#sopProtocolLink{
visibility:hidden;
}

.inSigningProgress{
visibility:hidden;
}

#qrcodeImage > canvas{
  visibility:hidden;
  display: none;
}

If you removed both Mouse and SignOnPhone, the device selection looks like:

Image Removed

Without those configuration the following settings will be visible:

Image Removed

<variable name="DisableSignOnPhone"/>
<variable name="DisableMouseForBiometricSignature"/> 

If you removed both Mouse and SignOnPhone and no other device for signing was found, the device selection looks like:

Image Added

Without those configuration (Mouse and SignOnPhone enabled) the following settings will be visible:

Image Added

For an instance-wide custom.css (For an instance-wide custom.css (not within Customization.zip) you could change the descriptive text above/instead the QR code image with following CSS definition:

...

<variable name="lighterGrayColorprimaryColor" value="#{[color:#d3d0d0#00A69D]}#" comment="
	default: #d3d0d0
	used as thumbnail background, page navigation background, disabled form fields, menu button hover effects#00A69D Primary color of the SAW Viewer affecting several major elements and referenced in different shades like 'primaryLightestColor' or 'primaryLighterColor' (see 'ADVANCED' section)
" category="Basic" />

With this one:

<variable name="lighterGrayColorprimaryColor" value="#{[color:#8b8989#000088]}#" comment="
	default: #d3d0d0
	used as thumbnail background, page navigation background, disabled form fields, menu button hover effects#000088  Primary color of the SAW Viewer affecting several major elements and referenced in different shades like 'primaryLightestColor' or 'primaryLighterColor' (see 'ADVANCED' section)
" category="Basic" />

After the page navigation background color we are now changing the document background color. Therefor, search for the following line and change it to the lines below:

Replace the following line:

Replace the following line:

<variable name="lightestGrayColorsecondaryColor" value="#{[color:#ebeaea#35364A]}#" comment="
	default: #ebeaea
	mainly used for the document background and menu backgrounds #35364A Secondary color of the SAW Viewer affecting most icons, some buttons and used as counterpart of 'primaryColor'
" category="Basic" />
  

With this one:

<variable name="lightestGrayColorsecondaryColor" value="#{[color:#EEE9E9#000088]}#" comment="
	default: #ebeaea
	mainly used for the document background and menu backgrounds#000088  Secondary color of the SAW Viewer affecting most icons, some buttons and used as counterpart of 'primaryColor'
" category="Basic" />

...

Replace the following linelines:

<variable name="defaultColorguidanceButtonNextColor" value="#{[colorcolorvar:#661864secondaryColor]}#" comment="
	default: #661864
	affects the cancel button border, active page navigation bar items, top small bar, focused element in the document, upload progress bars, finished message background color, active page border, active thumbnail border, icons and headers in dialogs, batch signing progressbar foreground, SignOnPhone background color
" category="" />

With this one:

" category="Expert" />
<variable name="guidanceButtonPreviousColor" value="#{[colorvar:secondaryColor]}#" comment="" category="Expert" />
<variable name="menuOverlayButtonColor" value="#{[colorvar:secondaryColor]}#" comment="" category="Expert" />

With this one:

<variable name="guidanceButtonNextColor" value="#{[colorvar:whiteColor]}#" comment="" category="Expert" />
<variable name="guidanceButtonPreviousColor" value="#{[colorvar:whiteColor]}#" comment="" category="Expert" />
<variable name="menuOverlayButtonColor" value="#{[colorvar:whiteColor]}#" comment="" category="Expert

<variable name="defaultColor" value="#{[color:#000088]}#" comment="
	default: #661864
	affects the cancel button border, active page navigation bar items, top small bar, focused element in the document, upload progress bars, finished message background color, active page border, active thumbnail border, icons and headers in dialogs, batch signing progressbar foreground, SignOnPhone background color
" category="" />

After this configurations the viewer should look like the following:

Image RemovedImage Added

 For changing the Logo you have to put your Logo in the subfolder /files. Then you have to change the variables.xml to set the new files (e.g. my-logo-large.png and my-logo-small.png).

...

• For the loading screen
• and for the top bar

Loading screen	Top bar
Image RemovedImage Added	Image RemovedImage Added

Viewer Preferences

...

Document Policies

These policies, also called "Global Policies" sometimes, define which of the features of a client are allowed on a signer activity - in case the client application supports this feature. Please note that the SignAnyWhere Viewer does not support all of these.

Name	Description	Values	SAW-Viewer
AllowSaveDocument	Is the client allowed to save the workstep document	Possible values: 0 (default), 1
AllowSaveAuditTrail	Is the client allowed to save the audittrail document	Possible values: 0 (default), 1
AllowRotatingPages	Is the client allowed to rotate the pages of the document	Possible values: 0 , 1 (default)
AllowAppendFileToWorkstep	Is the client allowed to append a file to the workstep	Possible values: 0 (default), 1
AllowAppendTasksToWorkstep	Is the client allowed to add append tasks to the workstep	Possible values: 0 (default), 1
AllowEmailDocument	Is the client allowed to email the workstep document	Possible values: 0 (default), 1
AllowPrintDocument	Is the client allowed to print the workstep document	Possible values: 0 (default), 1

...

AllowFinishWorkstep	Is the client allowed to finish the workstep	Possible values: 0 , 1 (default)
AllowRejectWorkstep	Is the client allowed to reject the workstep	Possible values: 0 (default), 1
AllowRejectWorkstepDelegation	Is the client allowed to reject the workstep with reject type ‘Delegation’	Possible values: 0 , 1 (default)
AllowUndoLastAction	Is the client allowed to undo actions	Possible values: 0 (default), 1
AllowColorizePdfForms	Is the client allowed to colorize pdf forms	Possible values: 0 (default), 1
AllowReloadOfFinishedWorkstep	Is the client allowed to view/download the document after finishing	Possible values: 0 , 1 (default)
AllowAdhocPdfAttachments	Is the client allowed to add adhoc attachments	Possible values: 0 (default), 1

...

AllowAdhocSignatures	Is the client allowed to add signatures which are not defined in the tasks	Possible values: 0 (default), 1
AllowAdhocStampings	Is the client allowed to add stampings which are not defined in the tasks	Possible values: 0 (default), 1
AllowAdhocFreeHandAnnotations	Is the client allowed to add adhoc freehand annotations	Possible values: 0 (default), 1
AllowAdhocTypewriterAnnotations	Is the client allowed to add adhoc typewriter annotations	Possible values: 0 (default), 1
AllowAdhocPictureAnnotations	Is the client allowed to add adhoc picture annotations	Possible values: 0 , 1 (default)
AllowAdhocPdfPageAppending	Is the client allowed to append adhoc documents	Possible values: 0 (default), 1

...

Configurations

Configurations for API integrations, where you directly configure the workstep per recipient.

WorkstepIdStampConfiguration

In the configuration of the workstep you can define the stamp imprint:

<workstepIdStampConfiguration>
    <referenceCorner>Upper_Left</referenceCorner>
    <color>White</color>
    <location width="340" height="15" marginLeft="3" marginTop="3" />
</workstepIdStampConfiguration>

NotificationConfiguration

Also the notification configuration is possible via the workstep configuration.

<NotificationConfiguration>
    <NotificationEventsNotToSend>
        <NotificationEvent>ActionCalledEvent</NotificationEvent>
        <NotificationEvent>WorkstepCreated</NotificationEvent>
        <NotificationEvent>SignWorkstepDocument</NotificationEvent>
    </NotificationEventsNotToSend>
    <NotificationUrl>http://localhost:52094/ReceiverSample.aspx?WorkstepId=##WorkstepId##&EventType=##EventType##&Source=##Source##&Time=##Time##&Description=##Description</NotificationUrl>
</NotificationConfiguration>

StampImprintConfiguration

You also can define the stamp imprint for signature fields configuration.

  <AllowedSignatureTypes>
                <sigType id="..." type="Picture">
                  <allowedCapturingMethods>Click2Sign</allowedCapturingMethods>
                  <StampImprintConfiguration>
                               <DisplayExtraInformation>1</DisplayExtraInformation>
                               <DisplayEmail>1</DisplayEmail>
                               <DisplayIp>0</DisplayIp>
                               <DisplayName>1</DisplayName>
                               <DisplaySignatureDate>1</DisplaySignatureDate>
                               <FontFamily>Times New Roman</FontFamily>
                               <FontSize>11</FontSize>
                  </StampImprintConfiguration>
                </sigType>
  </AllowedSignatureTypes>
</sig>

SignAnyWhere Viewer – Opening Link

Opening a workstep with the SAW Viewer is quite easy. Just reference to the SAW Viewer endpoint and use a workstepid parameter.

<http|https>://<server>/<virtualDirectory>/SignAnywhere.html?WorkstepId=<WorkstepId>

Parameters

...

...

SignAnyWhere Viewer Client Finish Action

You can configure a client finish action to be redirected to an predefined URL for the signer.

...

  <FinishAction>
    ...
    <ClientAction CallClientActionOnlyAfterSuccessfulSync="1" clientName="SIGNificant SignAnywhere">http://myurl.com</ClientAction>
    ...
  </FinishAction>