InCert Guided Navigation

Purpose: InCert allows an online intake interview to be embedded on a compatible web page rather than using the standard LegalServer online intake interview site format and styling. For example, an organization with InCert can embed its online intake interview within its own branded website, and allow an applicant to complete that interview without navigating away to a differently styled site.

Cost: $2500 one-time setup fee and $50 per month for up to 5 embeddable InCerts. InCert requires Online Intake and further requires that the online intake interview be written in guided navigation.

Additional support hours are available for setup beyond the included details. Non-standard configurations as described below may require additional costs.

Guided Navigation Dialogues

To use InCert, your dialogue will need to be written entirely in LegalServer's Guided Navigation. Create your interview using Guided Navigation on your LegalServer Online Intake site. Rather than making this dialogue part of a regular Online Intake process, InCert lets you call it from an external site.

Set the Dialogue Runner block on a new intake form. Set the intake form as the only form on an intake process. After you save the intake process, return to edit it. There will be a radio button field "Process should be offered in Guided Navigation API". Select "yes" and save the dynamic process' configuration. Under Permissions, please also ensure that the API User Role is set to "Full". "Default Full" won't do it here friends, it must be set to "Full".

API User

The API User Role will also need the permission for API Guided Navigation granted to it.

It is not recommended to grant the API User Role any additional permissions beyond API Guided Navigation . This should be a limited use API User.

The API User should not be used for other purposes. Keeping it to the single use and the limited permissions is recommended.

Enable CORS headers for the InCert API

Go to Admin → Process Settings and set an appropriate Access-Control-Allow-Origin header.

Because the interview dialogue comes from your LegalServer site, like abcoi.legalserver.org, but is displayed on another page, like nyhelpfinder.org, we need to set headers to tell the world that these two sites are cooperating and not nefarious. You'll need to add https://nyhelpfinder.org, https://www.nyhelpfinder.org to the list of URLs allowed to pull the dialogue.

Supported Blocks in Guided Navigation

Not all blocks will function in the InCert environment. If you attempt to use a block with InCert that isn’t yet compatible with InCert, and would like to request additional development to support a specific block, contact LegalServer with your request.

Getting Started

As of now, we encourage you to work directly with LegalServer to use InCert. We will support entirely self-service use of InCert in the future. For self-service InCert, you'll need to be familiar with basic html editing and .css concepts.

LegalServer InCert can be added to any site with just a few lines of basic HTML.

Once the Guided Navigation dialogue is complete and CORS headers are set, add the following lines to the host page where you will display InCert content. These lines should be placed in the <head> section if possible. If it’s not possible to add them to <head> (for instance if you’re using a content management system like WordPress), then just add them into the body.

The InCert application can be placed anywhere on the page by adding a <guided-nav></guided-nav> tag. It will resize to fit inside the <div> that contains it.

Adjustable InCert Attributes

Use tag attributes configure the settings of the InCert element:

url (required) - Guided Navigation API endpoint
token (required) - Authorization token
process (required) - the UUID for the Guided Navigation Process used by the
theme (required) - Styling options
language (optional) - Two-character language abbreviation of requested content
redirect (optional) - Target destination of the Cancel button in the InCert interface

The results of setting these parameters might look like this:

<guided-nav url="https://mysite.legalserver.org/api/v1/" token="k0P3X!b@djidadfi4829ZH^gk3k$EZ" theme="light color-blue font-sans" language="en" process="28d1ea12-ccfa-11ea-bf94-1866dafbcb38" redirect="http://www.legalserver.org">

Token Authentication

For authentication purposes, InCert requires use of the Personal Access Tokens. Directions for setting those up are in the LegalServer API Documentation. Your token must have a label that includes the term "InCert". This allows us to check for it expiring before your users tell you that it is no longer working.

Theming

Modify the theme attribute to customize the look of the form:

<guided-nav url="https://mysite.legalserver.org/api/v1/"    token="k0P3X!b@djidadfi4829ZH^gk3k$EZ" theme="light color-blue font-sans" language="en" process="28d1ea12-ccfa-11ea-bf94-1866dafbcb38"    redirect="http://www.legalserver.org">

For example:

theme="light color-blue font-sans"

 theme="dark color-red font-serif"

The parameters allowable are below:

Theme
- dark
- light
Accent color
- color-gray
- color-red
- color-brown
- color-green
- color-teal
- color-blue
- color-purple
- color-pink
Font
- font-sans
- font-serif

For instance, to specify a dark theme with a green accent color and serif font, the theme attribute should be set to: theme="dark color-green font-serif"which would result in an InCert style.

Troubleshooting

I get a 400 error on the site trying to access the intake.

Go to the intake process, make sure the settings "Process can be used with the Guided Navigation AP" is set to "Yes" and under Permissions the API Account User Role is set to Full.

Collecting Signatures in InCert

Using the Signature Attestation Block in Guided Navigation, you can render the block in InCert. When a user signs using this block, the signature is saved to the case. It can then be mapped into a document template using the Signature Actor.