Including eSignature fragments in Mobile Apps

In order to use Esignature features inside mobile apps, some fragments within FNDDSS component should be referenced by the .projection files.

Below are the changes that you need to do to include the esignature fragments in your application development.

Changes in deploy.ini file

First you need to add FNDDSS and FNDBAS as a reference under the Connections inside the deploy.ini file. See below example.

[Connections]
<others>
Fnddss=DYNAMIC
Fndbas=STATIC

Changes in .projection files

You need to add FndEsignature and DigitalSignature fragments as dynamic component dependencies into .projection files in your application as below.

---------------------------- FRAGMENTS ----------------------------

<other fragments>

include fragment FndEsignature;
@DynamicComponentDependency FNDDSS
include fragment DigitalSignature;

After doing these changes you will be able to use eSignature functionality in your application.

Electronic signing in the mobile app client is done using the signdocument command keyword and allows a developer to render a single step assistant page as a report for signing.

Implementing the single step Assistant

The single step assistant page is defined like any other Marble assistant. The assistant page will be rendered to a pdf file after successful signing .

Marble

--- E-Signature Implementation example in a Single Step Assistant.
assistant RecordWorkAssistant using EsigRecordWorkVirtualSet {
   label = "Task Card";
   singlestep {
      group TaskDetails;
      list TaskActionList(TaskActionsArray);
      repeatingsection StepSection(Steps);
   }
   command SignCommand;
}

list TaskActionList for TaskActionLineVirtual {
   label = "Actions";
   digitalsignature for AvExeTaskAction {
      hashcontent = [SignedFlag = true];
   }
   field ActionDesc {
      label = "Action Taken";
      excludefromsignaturemapping = true;
   }
   field ActionDate {
      label = "Date(UTC)";
   }
   field ActionUser {
      label = "Signed";
      signaturemappingattribute = Completed_By;
   }
}

Supported Esignature Attributes

• digitalsignature defines the entity the signature is for and hashcontent indicates whether the row was updated and signed for. “contentHash” will only be generated for SignedFlag = TRUE rows.
• Excludefromsignaturemapping is used to exclude the field from the hash calculation.
• Signaturemappingattribute is used specify the column name of the entity if it cannot be derived from the field name.