Creating an Anonymous Form-Based Process Using Adobe

8/3/2019 Creating an Anonymous Form-Based Process Using Adobe

1/30

Version 1.00 July 2006

SAP Composite ApplicationSAP Composite ApplicationSAP Composite ApplicationSAP Composite Application

FrameworkFrameworkFrameworkFramework

Creating an

Anonymous Form-

Based Process

(Adobe)


2/30

SAP AGSAP AGSAP AGSAP AGNeurottstrae 1669190 WalldorfGermanyT +49/18 05/34 34 24F +49/18 05/34 34 20www.sap.comwww.sap.comwww.sap.comwww.sap.com

Copyright 2005 SAP AG. All rights reserved.

No part of this publication may be reproduced or transmitted in

any form or for any purpose without the express permission of

SAP AG. The information contained herein may be changed

without prior notice.

Some software products marketed by SAP AG and its distributors

contain proprietary software components of other software

vendors.

Microsoft, Windows, Outlook, and PowerPoint are registered

trademarks of Microsoft Corporation.

IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex,

MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,

pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner,

WebSphere, Netfinity, Tivoli, and Informix are trademarks or

registered trademarks of IBM Corporation in the United States

and/or other countries.

Oracle is a registered trademark of Oracle Corporation.

UNIX, X/Open, OSF/1, and Motif are registered trademarks of

the Open Group.

Citrix, ICA, Program Neighborhood, MetaFrame, WinFrame,

VideoFrame, and MultiWin are trademarks or registered

trademarks of Citrix Systems, Inc.

HTML, XML, XHTML and W3C are trademarks or registered

trademarks of W3C, World Wide Web Consortium,

Massachusetts Institute of Technology.

Java is a registered trademark of Sun Microsystems, Inc.

JavaScript is a registered trademark of Sun Microsystems, Inc.,

used under license for technology invented and implemented by

Netscape.

MaxDB is a trademark of MySQL AB, Sweden.

SAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver,

and other SAP products and services mentioned herein as well as

their respective logos are trademarks or registered trademarks of

SAP AG in Germany and in several other countries all over the

world. All other product and service names mentioned are the

trademarks of their respective companies. Data contained in this

document serves informational purposes only. National product

specifications may vary.

These materials are subject to change without notice. These

materials are provided by SAP AG and its affiliated companies

("SAP Group") for informational purposes

only, without representation or warranty of any kind, and SAP

Group shall not be liable for errors or omissions with respect to

the materials. The only warranties for SAP Group products and

services are those that are set forth in the express warranty

statements accompanying such products and services, if any.

Nothing herein should be construed as constituting an additional

warranty.

Disclaimer

Some components of this product are based on Java. Any code

change in these components may cause unpredictable and severe

malfunctions and is therefore expressively prohibited, as is any

decompilation of these components.

Any Java Source Code delivered with this product is only to be

used by SAPs Support Services and may not be modified or

altered in any way.


3/30

T y p o g r a p h ic C o n v e n t io n s

Type Style Represents

Example Text Words or characters quoted fromthe screen. These include fieldnames, screen titles,pushbuttons labels, menunames, menu paths, and menuoptions.

Cross-references to other

documentation.

Example text Emphasized words or phrases inbody text, graphic titles, andtable titles.

EXAMPLE TEXT Technical names of systemobjects. These include reportnames, program names,transaction codes, table names,and key concepts of aprogramming language whenthey are surrounded by bodytext, for example, SELECT and

INCLUDE.

Example text Output on the screen. Thisincludes file and directory namesand their paths, messages,names of variables andparameters, source text, andnames of installation, upgradeand database tools.

Example text Exact user entry. These arewords or characters that youenter in the system exactly asthey appear in thedocumentation.

Variable user entry. Anglebrackets indicate that youreplace these words andcharacters with appropriateentries to make entries in thesystem.

EXAMPLE TEXT Keys on the keyboard, forexample, F2 or ENTER.

I c o n s

Icon Meaning

Caution

Example

Note

Recommendation

Syntax


4/30

Contents

Scenario..................................................................................................................................... 1

About This Document................................................................................................................ 1General Prerequisites......................................................................................................... 1

Applicable Releases........................................................................................................... 1

Disclaimer........................................................................................................................... 1

The Step By Step Solution ........................................................................................................ 2

How to Check the Configuration of the J2EE Engine ........................................................ 2Prerequisites ............................................................................................................. 2Description of the Scenario ....................................................................................... 2

How to Create a Standalone Interactive Form................................................................... 3Prerequisites ............................................................................................................. 3

Description of the Scenario ....................................................................................... 4How to Manage Impersonalized Interactive Forms............................................................ 9

Prerequisites ............................................................................................................. 9Description of the Scenario ....................................................................................... 9

How to Use Impersonalized Interactive Forms ................................................................ 11Prerequisites ........................................................................................................... 11Description of the Scenario..................................................................................... 11

Examples of a Standalone Adobe Document.......................................................................... 13


5/30

- -1

Scenario

Anonymous - or in other words, impersonalized - Interactive Forms can be used to start aGuided Procedures (GP) process without logging in to the SAP Enterprise Portal.

You are allowed to download the PDF file containing your impersonalized interactiveform and then you can store it in your file system or forward it to somebody else and useit later to start a given GP process.

To start the GP process you should open the downloaded PDF file, complete and submitit. If you have filled out the fields on the form, then the GP process started by the formwill be initialized according to the parameters you have specified in the form.

Additionally you can specify a timestamp after which the downloaded form expires, thatis, GP will no longer accept the form.

About This Document

General Prerequisites

To implement an Interactive Form based process using Adobe interactive forms youshould perform the configuration steps described in Error! Reference source notfound..

To use Adobe interactive forms you should install the Adobe Reader Version 7.0.7.

Applicable Releases

This tutorial is compatible with the following release SAP NetWeaver 04s SPS06.

Disclaimer

Any software coding and/or code lines / strings ("Code") included in this documentationare only examples and are not intended to be used in a productive system environment.The Code is only intended better explain and visualize the syntax and phrasing rules ofcertain coding. SAP does not warrant the correctness and completeness of the Codegiven herein, and SAP shall not be liable for errors or damages caused by the usage ofthe Code, except if such damages were caused by SAP intentionally or grosslynegligent.


6/30

- -2

The Step By Step Solution

How to Check the Configuration of the J2EE Engine

Prerequisites

For detailed discussion about the configuration of your J2EE engine see also Error!Reference source not found..

Description of the Scenario

1. Open the Visual Administrator ofyour J2EE engine.(Start -> Programs -> SAP J2EEEngine -> Visual Administrator)

Select your connection configurationand click the Connectbutton.

2. The Logindialog appears. Enteryour password and then clickConnect.


7/30

- -3

3. The main window of the VisualAdministrator opens. On the left-hand select the Clustertab ifnecessary and then expand theservers node.

4. Expand the Servicesnode.

5. Select the caf/eu/gp/modelnode.


8/30

- -4

6. Check the entries on the right-handside of the window.If you need to adjust any entries,restart the engine after changing theconfiguration values.

How to Create a Standalone Interactive Form

Prerequisites

We assume that you have already created an XDP file or you that you have saved theXDP contained in the Error! Reference source not found. of this document.


1. Launch the SAP Enterprise Portal(http://:/irj/portal)and login with your GP user.Navigate to Guided Procedures

Design Time.Choose Create Callable Object.


9/30

- -5

2. Enter the name of the callable objectand a description. Choose Englishas the original language, choose afolder in which to store the callableobject and select Interactive Form

from the Typelist.

Then click the button.3. Choose to specify an XDP

file for the interactive form.

4. Choose the Adobe Based Formfromthe Template Typedrop-down list.

Click and specify yourXDP file.You can find the source of the XDPfile used in this document in section

0 of the Error! Reference sourcenot found.. The encoding used bythe XDP document must correspondto the encoding specified in theEncodingdrop-down menu.

Choose .


10/30

- -6

5. Click .

6. The input parameters of yourinteractive form are displayed.

Here you can specify how theinteractive forms fields are pre-filled,(for more information see also Error!Reference source not found.), and

then click .


11/30

- -7

7. The output parameters of yourinteractive form are displayed.Here you can specify here thevalidation of the interactive formsfields (for more information see also

Error! Reference source notfound.), and then click .

8. If you would like to createimpersonalized interactive forms to

start a GP process for example, thenyou should specify the followingconfiguration for you callable object:

o Set Enable Use asStandalone Interactive Form

o Check the CreateImpersonalized InteractiveFormcheckbox.

o Check the Start ProcessUpon Completioncheckbox

o Choose .


12/30

- -8

9. Select the GP processto be started by theInteractive Form.

10. Click .

Please note that the GP started by the GP process must satisfy the following conditions asit is started anonymously:

o All built-in roles should be set to Initiation Defined.

o All roles defined by the GP process should be set to Initiation Defined.

o All roles including the built-in roles should have a default user assignment.

One possibility would be that you use the process defined in Error! Reference sourcenot found. and prepare default values for every role. Or you have to change the time-offprocess that is delivered as standard example. To do this you need the role GPsuperuser.

11. Click the button.


13/30

- -9

12. Specify themappingbetween thefields on theInteractive Form

and the contextvariables fromthe GP processto be started bythe form.

From theattached documentthe time-off data fromthe vacation requestprocess (built in

Error! Referencesource not found.)or the leave requestcan be mapped. Ifthe Time-Off Data isnot shown in themapping UI, pleasecheck that it ismarked as exposedin the chosenprocess.

13. Then click

.

14. Choose .


14/30

- -10

15. Click .

16. Activate your callable object.

How to Manage Impersonalized Interactive Forms

Prerequisites

In this scenario we assume that you have created an Interactive Formtype callableobject as described in 4.2.


1. Launch the SAP Enterprise Portal(http://:/irj/portal)and login with your GP user.Navigate to Guided ProceduresAdministration.Choose the Interactive Formssubmenu and then the ManageImpersonalized Formsmenu item.


15/30

- -11

2. Select the line of your callable objectfrom the Impersonalized FormTemplateslist.

Select the square before the line. Donot click the text of the line.

Select .

3. Optionally, specify an expiry date for your form

and then click the button.

4. Download the PDF file by clicking itslink.After downloading the file choose

.

5. Your form is displayedamong the currentrequests.The Return Count

column shows howmany times thedownloaded form hasbeen completed andreturned to the system.

Similarly the Total Request Countcolumn counts how many times theform has been downloaded.


16/30

- -12

How to Use Impersonalized Interactive Forms

Prerequisites

In this scenario we suppose you have created an Interactive Formtype callable object asdescribed in 0 and you have downloaded it as described in 4.3.


6. Open the impersonalized interactiveform that you have downloaded.

Fill in its fields and then click theSubmitbutton.

7. Launch the SAP Enterprise Portal(http://:/irj/portal)

and login with your GP user.Navigate to Guided ProceduresAdministration.Choose the Interactive Formssubmenu and then the ManageImpersonalized Formsmenu item.


17/30

- -13

8. Check that your formhas been received byGuided Procedures.The Return Countshould be incremented

and the Last ReturnDateshould correspondto the actual date andtime.

If you skipped the previous step because your administration GUI was already open, thenyou should refresh the list of the current requests, since it will not refreshed automatically.

9. Check that your GP process hasbeen started by your InteractiveForm.Login with the user assigned asdefault user to the process startedby the Interactive Form andnavigate to Guided ProceduresRun Time.

10. Choose Incomplete ProcessesWhere Role Assigned is Owner.


18/30

- -14

11. The process started by theInteractive Form is listed in the list ofRunning Processes.You can access your process nowby clicking its name.

12. If you specified the mapping

between the forms fields andthe GP process contextvariables in step 12 of thescenario described in section0, the GP process will bestarted with fields initializedaccording to the InteractiveForm content.

Examples of a Standalone Adobe Document

The following screenshot shows an example XDP file containing a request form for theTime-Off process.


19/30

- -15

Figure 1: createRequest.xdp in the Adobe Designer

The corresponding code example can be saved into an XDP file and then you can use itin your GP process.


20/30

- -16

Start Date

YYYYMMDD

Create Time-Off Request Form


21/30

- -17

End Date

YYYYMMDD


22/30

- -18

Absence Type

Vacation

Sickness

Unpaid Leave

Maternity Leave

Military Leave

0

1

2

3

4

5


23/30

- -19

Submit

Comments


24/30

- -20

pdf

pdf

0

1

1

1

D:\usr\sap\C11\SYS\global\AdobeDocumentServices\lib\acrobat6.xdc


25/30

- -21

uri>

D:\usr\sap\C11\JC00\j2ee\os_libs\adssap\FontManagerSe

rvice\fonts\adobe\typespt\unicode

D:\usr\sap\C11\JC00\j2ee\os_libs\adssap\FontManag

erService\fonts\adobe\reqrd\cmaps

D:\usr\sap\C11\JC00\j2ee\cluster\server0\.\pe

rsistent\com.adobe~FontManagerService\fonts\customer;D:\usr\sap\C11\JC0

0\j2ee\os_libs\adssap\FontManagerService\fonts\adobe;D:\usr\sap\C11\JC0

0\j2ee\os_libs\adssap\FontManagerService\fonts\adobe\pdfl\6.0\fonts

1

1

0

*

memory


26/30

- -22

1

preserve

January

February

March

April

May

June

July

August

September

October

November

December


27/30

- -23

Jan

Feb

Mar

Apr

May

Jun

Jul

Aug

Sep

Oct

Nov

Dec

Sunday

Monday

Tuesday

Wednesday

Thursday

Friday

Saturday

Sun

Mon

Tue

Wed

Thu

Fri

Sat

AM

PM

BC

AD


28/30

- -24

EEEE, MMMM D, YYYY

MMMM D, YYYY

MMM D, YYYY

M/D/YY

h:MM:SS A Z

h:MM:SS A Z

h:MM:SS A

h:MM A

GyMdkHmsSEDFwWahKzZ

z,zz9.zzz

$z,zz9.99|($z,zz9.99)

z,zz9%

.

,

%

-

0

$

USD

.


29/30

- -25

26T20:59:50+02:00" xap:MetadataDate="2005-07-26T20:59:50+02:00"

xapMM:DocumentID="uuid:7f7a22db-4091-4250-951d-1a8c3eee692b"

xapMM:InstanceID="uuid:4fc34b91-5e78-423e-b328-16ad68887029"

dc:format="application/pdf">

Figure 2: createRequest.xdp Source Code


30/30

www.sap.com/netweaver

Documents

Creating an Anonymous Form-Based Process Using Adobe