Installation - FORMCYCLE Wiki

Download the plugin {{code language="none"}}xima-fc-otwsm{{/code}} and extract the files to the plugin directory where you installed OpenText, eg. {{code language="none"}}C:\OpenText\WS\MS\ASP\PlugIns\{{/code}}. You will need the URL to this directory later.

16

17

== Connecting {{formcycle/}} the OTSWMS project ==

Download the content classes {{code language="none"}}FORMCYCLE Integrator{{/code}} and {{code language="none"}}FORMCYCLE Configuration{{/code}} and extract them to a directory of your choice.

24

25

For each OTWSMS project you would like to connect to {{formcycle/}}, import both content classes into your OTWSMS project, or import it into your master project and inherit from it later.

26

27

Create a new content class with a template and select one of the content classes {{code language="none"}}FORMCYCLE Integrator{{/code}} or {{code language="none"}}FORMCYCLE Configuration{{/code}} as the template file. You can given them any name you like, but for clarity, we recommend you name them {{code language="none"}}FORMCYCLE Integrator{{/code}} or {{code language="none"}}FORMCYCLE Configuration{{/code}}, respectively.

28

29

== Configuring the content classes ==

30

31

{{figure image="config-1.PNG" group="konfigCont" clear="h2"}}Click on the red circles to use the default settings.{{/figure}}

Create a new instance of the content class {{code language="none"}}FORMCYCLE Configuration{{/code}} and open it with //Smart Edit//.

38

39

Enter the URL to {{formcycle/}} plugin, as well as your username and password.

40

41

42

Use the default settings by clicking on the red circles at the left hand side. Changing these settings manually does not affect the integration with {{formcycle/}}.

Take note of the //GUID// shown on the configuration page, you will need it shortly.

47

48

49

Open the content elements of the content class {{code language="none"}}FORMCYCLE Integrator{{/code}} and select the element {{code language="none"}}std_KonfigseiteGUID{{/code}}. Open the actions menu, click on //edit element//, and enter the //GUID// from the configuration page.

50

51

52

You can change the default settings for new pages of option list element of the content class {{code language="none"}}FORMCYCLE Integrator{{/code}} as required by your project.

53

54

55

Open the structure elements of the content class {{code language="none"}}FORMCYCLE Integrator{{/code}} and edit the default content class for the elements {{code language="none"}}lnk_urlErfolg{{/code}} and {{code language="none"}}lnk_urlFehler{{/code}}. These values are used as the redirect URL for forms that have been submitted successfully and unsuccessfully, respectively. Commonly you would select a different page from the navigation menu.

Wiki source code of Installation

Navigation

version	line-number	content
1.1	1	{{content/}}
	2
	3	Follow these three steps to install the OpenText plugin for {{formcycle/}}.
	4
	5	1. Install the administration interface on the CMS server.
	6	1. Connect the OTWSMS project to {{formcycle/}}.
	7	1. Configure the content classes of the OTWSMS project
	8
	9	== Requirments ==
	10
	11	* OpenText website management system, version 11 or higher
	12
	13	== Installing the administration interface ==
	14
	15	Download the plugin {{code language="none"}}xima-fc-otwsm{{/code}} and extract the files to the plugin directory where you installed OpenText, eg. {{code language="none"}}C:\OpenText\WS\MS\ASP\PlugIns\{{/code}}. You will need the URL to this directory later.
	16
	17	== Connecting {{formcycle/}} the OTSWMS project ==
	18
	19	{{figure image="ck-import-2.PNG" clear="h2"}}{{/figure}}
	20
	21	{{figure image="ck-import-1.PNG" clear="h2"}}{{/figure}}
	22
	23	Download the content classes {{code language="none"}}FORMCYCLE Integrator{{/code}} and {{code language="none"}}FORMCYCLE Configuration{{/code}} and extract them to a directory of your choice.
	24
	25	For each OTWSMS project you would like to connect to {{formcycle/}}, import both content classes into your OTWSMS project, or import it into your master project and inherit from it later.
	26
	27	Create a new content class with a template and select one of the content classes {{code language="none"}}FORMCYCLE Integrator{{/code}} or {{code language="none"}}FORMCYCLE Configuration{{/code}} as the template file. You can given them any name you like, but for clarity, we recommend you name them {{code language="none"}}FORMCYCLE Integrator{{/code}} or {{code language="none"}}FORMCYCLE Configuration{{/code}}, respectively.
	28
	29	== Configuring the content classes ==
	30
	31	{{figure image="config-1.PNG" group="konfigCont" clear="h2"}}Click on the red circles to use the default settings.{{/figure}}
	32
	33	{{figure image="configGUID-fuellen-1.PNG" group="konfigCont"}}{{/figure}}
	34
	35	{{figure image="configGUID-fuellen-2.PNG" group="konfigCont"}}{{/figure}}
	36
	37	Create a new instance of the content class {{code language="none"}}FORMCYCLE Configuration{{/code}} and open it with //Smart Edit//.
	38
	39	Enter the URL to {{formcycle/}} plugin, as well as your username and password.
	40
	41	{{warning}}
	42	Use the default settings by clicking on the red circles at the left hand side. Changing these settings manually does not affect the integration with {{formcycle/}}.
	43	{{/warning}}
	44
	45	{{info}}
	46	Take note of the //GUID// shown on the configuration page, you will need it shortly.
	47	{{/info}}
	48
	49	Open the content elements of the content class {{code language="none"}}FORMCYCLE Integrator{{/code}} and select the element {{code language="none"}}std_KonfigseiteGUID{{/code}}. Open the actions menu, click on //edit element//, and enter the //GUID// from the configuration page.
	50
	51	{{info}}
	52	You can change the default settings for new pages of option list element of the content class {{code language="none"}}FORMCYCLE Integrator{{/code}} as required by your project.
	53	{{/info}}
	54
	55	Open the structure elements of the content class {{code language="none"}}FORMCYCLE Integrator{{/code}} and edit the default content class for the elements {{code language="none"}}lnk_urlErfolg{{/code}} and {{code language="none"}}lnk_urlFehler{{/code}}. These values are used as the redirect URL for forms that have been submitted successfully and unsuccessfully, respectively. Commonly you would select a different page from the navigation menu.