Add an Image or Signature from Standard Attachments to Adobe Forms in SAP Sales & Service Cloud

Share
Share on facebook
Share on twitter
Share on linkedin
Share on pocket

Apart from the standard signature process on a sales order in SAP Sales and Service Cloud, customers sometimes need to have a signature in an Adobe Form.

In our blog, you can find step-by-step instructions on how to add images and signatures to Adobe Forms outside of the standard process.

We know that the signatures are kept in the standard attachment table. So, we’ll first show you how to add an image to an Adobe Form from the Application table, then how to add a signature to a custom Adobe Form.

First, we need to create a Custom Adobe Form;

1. Create Custom Business Object

2. Create Adobe Form (Print Form)

We need to create a Form Template group to use while creating embedded components.

Next, select the required fields and as we want to use the Attachment node and its contents, we need to select as shown below.

Select Attachment node for use signatures and attachments. Complete the steps to finish the Create Print Form wizard.

3. Edit Adobe Form

Adobe Form has many objects in its library. We use “Subform”, ”Table”,  “Image Field” and “Text Field” in this case.

3.1. More than one Image Attachment binding
Table Row Data Binding: $.[BOName].Attachment.DocumentList[*]

We need to change column type to “Image Field” for Images.

Field Data Binding: $.FileContent.BinaryObject
3.2. Single Image Attachment or Signature Attachment binding
Field Data Binding: $.[BOName].Attachment.DocumentList[*].FileContent.BinaryObject

4. Create Embedded Component for preview

The embedded component is used to add the Business Object (BO) and PDF we made, to the standard. For this, the following steps need to be carried out.

4.1. Create Inport & Inport Event Handler

Created AutoFire event and binding OnFire.

Event is reading own Business Object and if Business Object has not this object, event is creating this object for us in below.

Condition
First operation in condition
Second operation in condition
4.2. Outport Process
4.2.1. Add boolean field in the data model and find the template group code
find .ftgd file for your PDF in SDK
4.2.2. Create Outport and Binding
4.2.3. Create Preview Event Handler
4.3. Create Modal Dialog

Make sure ‘Lazy Load’ is set to false.

5. Data Filling in Action

5.1. Basic Attachment (Image) Code

The function of the below code is to copy attachments from the Standard attachment tab (in the Service Request) to your custom Business Object attachment node. This code is executed in the show basic image process.

5.2. Signature Code

If we want to show a signature in the Sales Order, then the code must be changed. In the Standard Process signatures the type codes are “10088” & “10087”, so we cannot copy this type of code. We must change type codes to “10001” and copy to our own custom business object.

6. Signature Outcome

In this blog, we have described a new business object and how to create an Adobe Form using it. We also demonstrated that we can use the created Adobe Form for images and signatures in the standard attachment table, and in processes such as creating embedded components in an Adobe Form. Lastly, we’ve shown filling in data in action.

Supporting your business processes with emerging technologies is the main goal of our business.

exp head deco 3
icon our expertise

Thank you

You’ll receive an email with download link shortly.

If not, reach us on solviamarketing@solviads.com

Created by icon 54from the Noun Project

Thank you

You’ll receive an email shortly.

If not, reach us on solviamarketing@solviads.com