Configuration by Editing the Microsoft Windows Registry Manually
2017 R1 Update Rollup 1

Configuration by Editing the Microsoft Windows Registry ManuallyPermanent link for this heading

In the Microsoft Windows Registry of the client several values have to be set. The individual values (each string values) can be found in:

HKEY_Current_User\Software\Fabasoft\Fabasoft Components GroupWise Extension

If the Fabasoft Components GroupWise Extension key is not available it can be created manually. Open the context menu of the Fabasoft key and click “New” > “Key”. Name the key Fabasoft Components GroupWise Extension.

Create the necessary entries (each of type “String Value”) in this key. The following key values are available ([2,3,4] refers to the particular button, if several buttons are inserted):

BUTTONS

Defines the number of buttons. If this value is missing, the default value is 1.

CALLURL[2,3,4]

The CALLURL is a WebDAV URL that is called when a Novell GroupWise button is clicked.

The input parameter contains the e-mail file, attachments (depends on the setting CALLMODE) or an XML file.

If CALLFORMAT=XML is defined, the optional output parameter can hold an XML file with a node, which represents the returnurlsuffix for the return URL. Normally this is a vApp.

Example:

http://<computername>/<virtual directory>/fscdav/CALL?
ACTION=COO.1.1.1.7283

In this case the option CALLURL contains the object address of the Import message from Novell GroupWise action and so the vApp for importing is called. A connection is established to the server and the virtual directory specified in the URL. Fabasoft Folio provides several actions. See chapter “Provided Fabasoft Folio Actions” to get an overview.

Example for the content of an XML file as return value:

<returnurlsuffix>
dx=COO.1.1001.1.32490&amp;

ax=COO.....&amp;

sys_object=COO.....&amp;
sys_selobjects=COO.....&amp;
commit=
true&amp;
ru=javascript:close()
</
returnurlsuffix>

CALLMODE[2,3,4]

CALLMODE defines which files are passed to the CALLURL.

CALLMODE=Mail
The e-mail file is passed to the CALLURL (default setting, if nothing is specified).

CALLMODE=Attachments
The attachments of the e-mail are passed to the CALLURL (each is passed separately).

The schema used can be found in the description of the CALLFORMAT entry, where all nodes except “File” (which contains the body text) are filled.

CALLMODE=Both
The e-mail file is passed followed by the e-mail’s attachments.

Note: If the CALLFORMAT parameter contains the value XML, the CALLMODE=BOTH and CALLMODE=MAIL settings are leading to the same result.

CALLFORMAT[2,3,4]

CALLFORMAT=XML
If the value XML is entered, the file is transferred in an XML file based on the XML schema described in chapter “XML Schema”. Note: In the CALLURL parameter an action that is able to process a XML object should be defined.

CALLFORMAT=Binary
If the value Mail is used in the CALLMODE parameter only the body of the e-mail is transferred in an RTF file.

RETURNURLBASE[2,3,4]

RETURNURLBASE contains the front part of the URL that is called when the action of CALLURL has completed. The action returns the remaining part of the URL as an output parameter.

Example:

http://<computername>/<virtual directory>/fscasp/
content/bin/fscvext.dll?

The first button is described by the entries CALLURL, RETURNURLBASE etc. For other buttons the name of the entry is extended by the number of the button, e.g. CALLURL3 for the third button.