1. Home
  2. DevOps
  3. Infrastructure
  4. Installing and Configuring trellispark

Installing and Configuring trellispark

Installing trellispark published websites

The trellispark framework is implemented on the Microsoft stack using C# and Blazor. The underlying database is built on MS SQL Server. The user experience is implemented using the Telerik Blazor and Reporting controls.

The trellispark framework components can be deployed using a hybrid of Cloud IaaS/PaaS or On-Premises infrastructure.

At a minimum you will need to:

  1. Restore the trellispark-dev database on a 2019 SQL Server (either on-premises, or Azure SQL). This database contains your records and initial set of sample form definitions.
  2. Deploy the Rest-WebAPI-Core published website on an IIS website as this is required to access the trellispark DAS-RSS database and perform other secure operations.

If you want to access your application using MAUI on a client’s device, you will need to connect the UX-MAUI-SA project to your deployed Rest-WebAPI-Core API endpoints.

You can also deploy one, or more, WASM Client websites by deploying any of the following published websites:


Configuration Settings

User Experience Websites

The only hard coded application setting that a WASM Client website needs is the URL for its associated REST-WebAPI-Core website.

  "APIURL": "https://localhost:44339/" 

For the UX-MAUI-SA project this setting is in the MauiProgram.cs file.


The REST-WebAPI-Core needs a few hard code application settings:

  • Provide a valid ConnectionString to your Data at Rest trellispark database called TRELLIS.
  • The type of Database being used – at present only MSSQLServer is allowed.
  • The DatabaseCommandTime specifies the time in seconds before a database command will timeout.
  • Specify your Azure Application Insights logging target by completing the ApplicationInsights section and copying the AppInsightsKey (should you need this feature). If you don’t want to log to ApplicationInsights then set the AppInsightsKey to a zero GUID (00000000-0000-0000-0000-000000000000).
  • HTML2PDF_API_URL specifies the path to the HTML to PDF conversion Web API (should you need this feature).
  • LicenseKey – Free key is available for your user account on the Downloads page of GreatIdeaz portal
  "Logging": { 
    "LogLevel": { 
      "Default": "Information", 
      "Microsoft": "Warning", 
      "Microsoft.Hosting.Lifetime": "Information" 
  "AllowedHosts": "*", 
  "ApplicationInsights": { 
    "ConnectionString": "InstrumentationKey=000000000-0000-1111-2222-51407207361d;IngestionEndpoint=https://canadacentral-0.in.applicationinsights.azure.com/" 
  "ConnectionStrings": { 
    "TRELLIS": "Data Source=XXX.XXX.XXX.XXX;Initial Catalog=TRELLISPARK;User ID=****;Password=****;Min Pool Size=10;Connection Timeout=600;" 
  "Database": "MSSQLServer", 
  "DatabaseCommandTimeout": 400, 
  "AppInsightsKey": "00000000-0000-1111-2222-51407207361d", 
  "LicenseKey": "12341234-1234-1234-1234-123412341234",
  "HTML2PDF_API_URL": "https://yyyy.greatideaz.com/api/convert" 

trellispark Configuration Parameters

trellispark allows you to create configuration parameters within the framework that take the form of a simple key/value pair.

These parameters can be saved at one of three levels:

  • Workspace: Server Owner
  • Workspace: Custom
  • User

When a user is looking for a configuration parameter, they will start looking at the User level, then at the User’s “Custom Workspace” and finally in the “Server Owner Workspace”.

This gives you the flexibility to define the configuration parameters in a hierarchy that allows for override at the user and custom workspace level.

Server Owner Workspace

The “Server Owner Workspace” is a special workspace set aside for developers and business analysts so that they can customize the data model of the trellispark implementation.

Developers can add additional configuration parameters on the “Server Owner Workspace” to configure optional services and environment settings.

This is the best place to define any configuration that will be common for all users and all workspaces using this trellispark implementation.

Custom Workspace

The “Custom Workspace” is created to establish a security boundary around any data that needs to be secured for your organization. As a developer, you will initially create one or more “Custom Workspaces” depending upon your organizational structure and your need for securing data.

Developers can add additional configuration parameters on the “Custom Workspace” to configure optional services and environment settings.

This is the best place to define any configuration that will be common for all users within a “Custom Workspace”.


Users are created when a new user joins a Workspace.

Users are assigned configuration parameters as required whilst they interact with the trellispark implementation. For example, if they change the setting on a childlist, then those settings are stored as User Configuration Parameters.

Developers will not be creating or updating User Configuration Parameters.

Updated on October 27, 2022

Was this article helpful?

Related Articles

Need Support?
Can’t find the answer you’re looking for? Don’t worry we’re here to help!
Contact Support

Leave a Comment