Help and support

On this page you will find help and support information for Jorm Form automation.

Below we have included information we think you may find helpful and/or to reference should you experience any issues (we hope not). If you continue to have any issues please reach out to us via our contact page or contact our support desk and we will try to remedy your issue.

Other related pages:

• Quick Start & Administrator Integration Guide
• Jorm Form Automation Product Page
• Jorm Terms and Conditions
• Jorm Privacy Policy

Who is this intended for?

This extension is predominately aimed at professionals/IT departments where data entry via web submission using forms is common. This extension makes it possible to automate aspects of these submissions.

Data Collection

We respect your privacy and your data; we do not collect nor transmit any data parsed or autofilled by this extension. We work with a variety of clients including law firms and medical practices with strict requirements.

Supported websites and/or forms

Most HTML forms are supported but there will/maybe instances where we are unable to automatically index urls; the reasons may include:

1. The form is behind an login system; i.e. the form trying to be filled can’t be publicly viewed without an account.
2. The website has measures in-place that prevent, disrupt or discourage crawler like behaviour.*
3. URL length; Chrome limits URLs to a maximum length of 2MB for practical reasons and to avoid causing denial-of-service problems in inter-process communication.
   On most platforms, Chrome’s omnibox limits URL display to 32kB (kMaxURLDisplayChars) although a 1kB limit is used on VR platforms. Source
4. Supported browsers include:
   • Chrome and Chromium based browser (including Edge)

* In these instances; where our crawler efforts have failed we may be able to manually intervene and generate an mapping.

We are also exploring adding the option for account owners to manually submit HTML for forms behind paywalls/authentication to workaround point 1. Planned in release in 1.3.0.

Important: most forms do not support or make available form fields as query parameters unless designed to. If you try to access/post data to URL’s prepared by this extension and service without using the extension you will be posting that data to the third-party server. You may encounter:

413 Entity Too Large in response.

Where the Jorm extension would typical intercept the request and extract the query parameters.

We monitor and track the outcomes from all indexing requesting to improve our indexing service further.

Subscription requirements and usage

A subscription is required to use this extension; your subscription is used for various operations. On sign-up we email you credentials to access the Jorm Admin Portal used to manage aspects of your account including:

• Portal: Allow your organisations administrator/IT department to centrally manage origins/hosts allowed by the plugin.
  • Extension users will be prompted by a notification to approve new origins; this is important and is a requirement under Manifest v3 and ensures only origins you approve can be accessed by the extension.
  • Provisioning support for deploying the extension within your organisation.
• Request new URL indexing jobs.
  • We re-index forms ensuring that the mapping information is synced.
• Sync changes to extensions users under your account.
• Generate authentication tokens for use with the extension.
• CRM/Integration helper: Generate template URL’s with placeholder query parameter’s.

Our Jorm Administrator Portal uses WordPress to provide an admin portal; with exception to your account email no data is stored in the WordPress installation. Instead all custom components you see make use of the Jorm’s API to retrieve data from your account and make any actions. Read more in our terms and conditions.

Extension permission requirements explained

Here is a breakdown on extension permissions how we use them:

• scripting
  Enables the extension to inject a content script and stylesheet on optional_host_permissions matches from webNavigation. The injected script perform the autofill task.
• webNavigation
  Extract URI parameters from a URL, caches them so that the extension can populate form fields based on the ID’s. This permission is used to identify when a tab matches a approved origin then performs the following operations: strip the URI params, cache them and redirect to the same URL without the URI params.
  Only matches origins/domains the user has approved.
• storage
  Temporarily stores extracted URI params to local storage; once the form field have been populated by ID it is cleared.
  Other settings store include auth token and cached mappings.
• contextMenus
  Used to add two right click menu entries to extension icon; one for the main status page, the other for the settings page.
• tabs
  Used to send a message when a tab url matches an approved origin and has a cached data mapping stored locally. When it is a match it triggers the formFill functionality.
• alarms
  Used to schedule form data mapping updates for hosts present on the users account.
• notifications
  Used to indicate authorisation is required for plugin use; renders a notification for scenarios such as when there is no account configured or the subscription may have expired.
• host and/or optional_host_permissions
  This is used to allow the extension to communicate to our API servers using origin rule: https://*.oddineers.co.uk/*.
• optional_host_permissions
  This is used to allow the extension to run on domains that the users has linked to their account; these are cached locally under option userDomains.

All origins require that the user approve them through user interaction; where approval is required the extension will trigger a notification to inform the user where that user interaction is required.

Extension Badge Error codes

Under certain scenarios the extension may display small and short badge message atop the extension icon; these badges and their error message or code are intended to quickly inform the user that there is a issue.

• AUTH Indicates that there is a error with the provided authentication details. These could include:
  • Empty or missing credentials.
  • Mistyped credentials.
  • Expired credentials.
• BUSY Indicates that the API may be experiencing high loads and rate limiting is in place scenarios may include:
  • Large volumes of traffic.
  • Client rate limits.
  • Recovery: Automatically retries operations periodically.
• MAX Indicates that you have hit the device limits for the active subscription.
  • Example: you have 2 licenses; and install/activate a third device. The third device will be prevented from running.
  • Recovery: Automatically queries account status periodically; please check and ensure you have sufficient licenses available for the concurrent users utilising the Jorm extension.
• N/A Indicates that the API is not available:
  • This may be client connectivity related.
  • Review access and ensure you have adequate connectivity.
  • Review the Jorm Administration Portal for API status and notices.

Authentication, device activation and expiration

Chrome extension authentication

Administrators can generate tokens for use with the Chrome extension from the Jorm Admin Portal.

Administrators can choose to:

• Generate a single token and share that with users of the Jorm extension.
• Or (more secure) generate a separate token for each user of the Jorm extension.

Which ever option is used; you can send a provisioning URL to users to log them to the Jorm Extension (template available under admin Portal).

Device activation and expiration

Device session work by assigning unique ID’s to connecting clients. These sessions have a lifetime (currently 336 hours or 14 days): If a device ID hasn’t be seen for 336 hours it is automatically cleared freeing the token for use on another device.

Connecting clients are those coming from the Chrome extension; each authenticated instance represents a session which consumes a license.

Example scenario: you have 2 x licenses on your account; you have configured 2 x initial devices and come to install/activate a third device. The third device will require an additional license. The extension will indicate if you need additional licenses as well as session count information. The same information can be found under the admin portal.

Account resets can be requested for consideration via support. These resets are not intended to work around user/device licensing and are considered for certain situations such as internal infrastructure upgrades, etc.

What this extension does not do

• This extension does not complete ReCaptcha’s.
• This extension does not automatically submit the form. You are encouraged to review any data auto-filled (more-so on larger more complex forms).
• This extension does not handle file attachments.
  • Although possible in practice it is limited and based from real-trials; the biggest limitation is with a web browsers address bar length (URL length). Different browsers (even Chromium variants) have differing limits.
    • Hypothetically: if files were enabled; the contents of the file would have to be encoded and generally that increases the size and will quickly if not outright consume the available character length limit.
    • See note above on URL length limits

Organisations/Users migrating from the private/unlisted alpha

There are several significant changes to September’s 2024 preview release:

• Jorm now requires an account and active subscription for continued use.
• Jorm no longer exclusively matches on a single origin: https://financial-ombudsman.egressforms.com/ and now uses a dynamic host (i.e. origin’s) system that account owners manage under their account through the portal.
  • Once a domain is linked/mapped under your account; it is synced to authenticated Chrome extensions.
  • Google’s Chrome Extension Manifest v3 brings significant changes to the permission system; in the name of security Jorm’s design deliberately avoids requesting to match on every host (origin) and instead chooses to use the `optional_host_permissions` to ensure the user approves the new origin. The extension will notify the user through various means.
    • Vigilant administrators/IT departments when submitting a new url and building their URL maps internally are advised to notify users to approve the origin. Prior to going live with any workflow implementations.
• Provisioning support is now available which enables administrators to send links that allow users to authenticate the extension.

Disclaimer & Notices

Google Chrome and the Chrome Web logo are trademarks of Google LLC.

Terms & Privacy Policy

Your use of the application: Jorm Form Automation from Oddineers Ltd. is subject to the following: Terms & Conditions and Privacy Policy.