Forms Builder 2.x

You can use Installation Manager to install the Forms Builder application. Forms Builder is an easy-to-use, web-based application for the creation, design, publication, and management of electronic form workflows. It enables organizations to quickly customize complex processes without the need for expensive programming, custom web design, or service costs. Forms Builder enables users to create forms for every constituent at the institution: new applicants, existing students, faculty, and staff.

Prerequisites

Note: Installation Manager checks for the prerequisites to be installed. It does not install them.

For information on compatibility with operating platforms and other products, see Platform Compatibility and Product Compatibility (logon required).

Installation Manager installs the following components:

  • Forms Builder

  • Security Token Service (STS)

    alert Forms Builder version 2.3.0 or later requires the Staff STS component to be installed. Go to the Start screen and select Package Manager. Download the Staff STS package and install it. For more details, see Staff STS.

  • If you are using CampusNexus Student and Workflow with Forms Builder, the Forms Builder Contracts and Activities are required. Go to the Start screen and select Package Manager. Download the Forms Builder Contracts and Activities package and install it.

Software Prerequisites

Microsoft .NET Framework 4.5.1

Accounts, Permissions, and Other Prerequisites

  • Only Integrated Authentication for SQL can be used to install Forms Builder.

  • If a Forms Builder database does not exist, a blank Forms Builder database must be created prior to installing Forms Builder.

  • All Forms Builder web applications use ApplicationPoolIdentity for authentication. To avoid errors during the Forms Builder installation, ensure that the following permissions are set up:

    If Forms Builder and Database are on different machines, ensure that Domain\FormsBuilderMachineName$ has db_owner permission to the Forms Builder, CampusNexus Student, Portal, or CampusNexus CRM database before starting the installation.

    If Forms Builder is on same machine as the SQL server, ensure NT Authority\system and NT Authority\Network Service has db_owner permission to the Forms Builder, CampusNexus Student, Portal, or CampusNexus CRM database before starting the installation.

    Postinstallation steps when Forms Builder and Database are on the same server

    • If Forms Builder and SQL are on the same machine, then after Forms Builder is installed, the application pools for all Forms Builder web applications need to change from ApplicationPoolIdentity to built-in NetworkService account.

    • In a few instances, the Forms Builder CRM Adapter, Designer and Renderer web sites may need to be running under the service account to launch Forms Builder Designer.

    • The application pools that are installed as part of Forms Builder must be added to the database as db_owner.

      For example, the following accounts need to be added to CampusNexus Student, Portal, or CampusNexus CRM and Forms Builder databases:

      • IIS AppPool\CMCPortalSTSAppPool

      • IIS AppPool\CMCFormsBuilderAdapterAppPool

      • IIS AppPool\CMCFormsBuilderDesignerAppPool

      • IIS AppPool\CMCFormsRendererAppPool

      • IIS AppPool\CMCDataServiceAppPool

      • IIS AppPool\CRMFormsBuilderAdapterAppPool

Forms Builder License

Please contact Support to get a license script.

Forms Builder for CampusNexus CRM

  • The Forms Builder machine needs to have access db_owner permission to the CampusNexus CRM Main database.

    Domain\FormsBuilderMachine$ has to be added to SQL security with db_owner rights.

  • Forms Builder uses the Security Token Service package delivered with CampusNexus CRM Web Client. Therefore, the installation of Web Client is a prerequisite for Forms Builder when Forms Builder is intended for use with CampusNexus CRM.

  • CampusNexus CRM Application Server is a prerequisite for installing Forms Builder.

    If Forms Builder is being installed to a machine where the CampusNexus CRM Application Server is not installed, an instance of Application Server has to be installed before installing Forms Builder. Alternatively, Forms Builder can be installed on the Application Server machine.

  • CampusNexus CRM 10.1 should be installed before installing Forms Builder 2.1.

  • Forms Builder 2.0 cannot be installed on CampusNexus CRM 10.1.

Forms Builder for CampusNexus Student

  • Forms Builder uses Student API and Portal web services to log in. Therefore, the installation of CampusNexus Student and Portal is a prerequisite for Forms Builder when Forms Builder is intended for use with CampusNexus Student.

  • The Forms Builder machine needs to have access db_owner permission to the CampusNexus Student database as well as the Portal database.

  • Domain\FormsBuilderMachine$ has to be added to SQL Security with db_owner rights.

  • Student Portal web services must be accessible from the server where Forms Builder is installed.

Conditional Postinstallation Step for Forms Builder

If Forms Builder is being installed on a Windows Server 2012 that has SharePoint Foundation 2013 installed, the following script must be executed to avoid errors when rendering a Form.

%windir%\system32\inetsrv\appcmd.exe set config -section:system.webServer/globalModules /[name=’SPNativeRequestModule’].preCondition:integratedMode,bitness64