The service includes the following main capabilities:

• Digitalisation of forms and contracts

  • Creating, deploying and maintaining hundred of online forms

  • Automated document and contract generation

  • Signing contracts with electronic signatures

• Scaling

  • Forms management with the central customer component library

  • Best-practice forms factory operation model with roles and concepts

• ajila Form Data Management

Definitions

The following schematic diagram illustrate the service, components and roles:

Service Access Interface Point (SAIP)

The Service Access Interface Point (SAIP) is the logical point at which the service is provided to the customer.

Roles

A key element of the Forms Hub concept is the agile approach to to create, maintain and deploy forms. Our solution includes a best practice forms factory operation model for a fast and formal template management at scale.

Roles at design time:

• The form owner is the expert who knows and owns the form. This role works with the business analyst to specify and tests the form.

• The business analyst describes the requirements graphically and in writing, reflects it with the form owner until the final state (ready for development).

• The forms developer implements new functionality for front- and backend components organised in the customer component library.

• The forms designer creates and maintains forms based on the customer component library.

Roles at run time:

• The end user is a customer, employee, partner or supplier filling- and submitting a form via the website, portal or app.

• The platform operator is operating and maintaining the service.

• The incident helpdesk is receiving, qualifying and resolving issues reported by the customer.

Components

The service has the following components:

• Customer Forms Project

  • The Customer Component Library is the customer specific library which contains the front- and backend form components to encapsulate the complexity and redundancy.

  • The Customer Forms are the customer specific forms and document definitions, based on the customer component library and rendered by AEM Forms

  • Customer PDF templates to render PDF/A documents based on input data

  • Customer backend connectors ensures the data exchange between the Customer Systems and the service. This is data to refill forms, validate data or write data back after a successful form transaction.

• The Adobe AEM Forms Publish Service hosts the Customer Forms, the Customer Component Library and has the capability to render the adaptive forms and PDF templates into PDF/A format.

• The ajila Form Data Management provides fundamental functionality for secure and managed form data processing/storage.

• The ajila platform services provide fundamental infrastructure functionality like the data center (networking, computing and storage) security (Firewall, WAF, routing, etc.), Monitoring, Logging, etc.

Licences

All required licenses are maintained and included in the service.

Customer Systems

These are the customers backend systems such as ERP, CRM, workflow engines, archiving and other systems which interact with the service. to prefill data into the form and where the final form data and documents will be stored after as successful Form Transaction. The data is exchanged typically via REST APIs in JSON or XML format and will be deleted automatically on the service.

Form Transaction

A form transaction is a form process which start usually with the initial form data entry by an end user, data submission, some actions in between and ends with the successful data handover from the service to the customer.

The actions could be:

• Data payloads and validations

• Document renderings

• Electronic signatures

• Notifications via email, SMS, etc.

• Online payments

• Online identifications

• etc.

References

• Visit the ajila Forms Cloud Service on the ajila website.