Security first

Regardless if you are using Cellosign builtin login or your organization Single Sign On application, keep your password safe:

1. Do not use passwords or tokens that were not granted to you. This is strictly prohibited
2. Do not leave notes with password on your desk
3. Keep your password easy to remember and hard to guess
4. If you have a slight suspicious that something is wrong, logout immediately, report your manager and Cellosign support for immediate response

Testing new business processes

It is recommended that new or changes to existing business processes will be carried out at pre-production environment rather than production. This will help you to develop the process in a secured and controlled environment with no client access and no disruption to production environment.

Every type of business process and it’s related meta data can be easily exported from pre-production and uploaded to production when testes are completed.

New releases are distributed every other month in according to yearly plan that takes into account holidays and peek times such as end of Quarters and end of year.

On Cellosign cloud application typically new releases are distributed to production occurs at Thursday night. There are also reserved time slots for distribution for on premise clients.

Please make sure to read full cycle practice, schedule and change logs in this documentation branch.

Cellosign customers have the option to contact Cellosign support by submitting a ticket using our web form.

Important: in case of critical production issues open a ticket and contact your account manager / support by phone.

What kind of issues can be submitted:

1. General Support issues.
2. Reporting a bug.
3. New request or CR.

Note: in our FAQs section you can find detailed information about common issues.

There are several options to submit a ticket.

In case you can login to Cellosign application the options are:

1. From “Processes” screen (recommended).
2. From main application menu.

In case you cannot login, contact Cellosign support from the web site.

See below a detailed explanation of each option.

Contact Cellosign support from “Processes” window

1. Login the Cellosign application.
2. Navigate to the “Processes” window.
3. Select the transaction from the list and press “Show Transaction Details” (+).
4. Click “Service call” button. You will be redirected to “Request for support and reporting service” form.
5. Add the details and send the form. Please describe a complete scenario and add as much information as possible.
6. The ticket will be opened automatically with all the attached to the form information.
7. You will receive an email with the ticket number and all the details to the email address filled in the form.
8. To update the ticket or add an additional information click the link in the received email.
9. You will be redirected to the ticket details in the support site.
10. If, for any reason, you have lost access to your Cellosign account, you can still submit a support ticket from the web site (see below).

For more information about “Processes” window read here.

Contact Cellosign support from the application

1. Login the Cellosign application.
2. Click “Service call” button at the left bottom corner.
3. You will be redirected to “Request for support and reporting service” form.
4. Add the details and send the form. Please describe a complete scenario and add as much information as possible.
5. The ticket will be opened automatically with all the attached to the form information.
6. You will receive an email with the ticket number and all the details to the email address filled in the form.
7. To update the ticket or add an additional information click the link in the received email.
8. You will be redirected to the ticket details in the support site.
9. If, for any reason, you have lost access to your Cellosign account, you can still submit a support ticket from the web site (see below).

Contact Cellosign support from the web site

1. Navigate to Cellosign site.
2. Click “Support” button at the top menu at the right.
3. You will be redirected to “Request for support and reporting service” form.
4. Add the details and send the form. Please describe a complete scenario and add as much information as possible.
5. The ticket will be opened automatically with all the attached to the form information.
6. You will receive an email with the ticket number and all the details to the email address filled in the form.
7. To update the ticket or add an additional information click the link in the received email.
8. You will be redirected to the ticket details in the support site.

For detailed information about “Privacy statement” read here.

1. Connect to the representative interface page using the URL provided to you by Cellosign:

2. Enter your user name and password and click the ‘Sign In’ button.

If its the first time you are logging in , you will need to set a new password:

Enter a new password on the ‘New password’ field and again on the ‘Confirm password’ field.

Click the ‘Change Password’.

After the successful login in the header of the interface you can see the user name, where under it you can find Profile details and Logout option.

To send a form to the client from the agent’s interface, press the “Show Agent” button.

For a detailed explanation about user application read here.

To send a form to the client from the agent’s interface, press the “Show Agent” button at the top of the screen and select a form prepared for you from the list. For more information about forms templates read here.

Enter the client’s email address or mobile phone number at the top of the screen and press “Connect” button.

At this point, when the client opens the link from the phone message or the email, you can both work together on the form.

Visit Screen sharing section for more information about the screen sharing option.

When the client sends the form (after all the mandatory fields have been filled in) you will receive the signed form by email.

For additional information about how to send a form in Cellosign application read here.

Cellosign system allows sending a template to the client and creating a common interface (client and agent) for filling out a common template. The interface allows the agent to view the values ​​entered by the client and the client to view the values ​​entered by the agent in real time. Each of them (agent, client) can add values according to the editing and viewing permissions given in the template.

The screen sharing option can be implemented in two ways, through the Show Agent interface or Processes interface.

In the Show Agent interface, the option exists by default and under the following conditions:

• Agent has sent the template (a timer indicator will appear next to the target box for sending the template).

• Client opened the link sent to him (a green indicator will appear at the bottom of the screen at the agent side in real time).

If both conditions are met, you can use the screen sharing option.

For more information about Show Agent interface read here.

In Processes interface the option exists in the actions screen under the specific transaction.

Press “+” next to the transaction that need to share:

After it press “Show Agent” button to open the transaction from the agent side:

Note: In Processes interface users with organization manager or project manager privileges can also open a client screen by pressing “Show Client” button and view or edit the template with client permissions.

For more information about Processes window read here.

Under each section it is possible to perform search, filter by user and see the details of each transaction.

From this window Agent can run already existing template or create Ad-Hoc form with PDF file with or without recipients.

After uploading PDF file the form will be opened. Press “Add Fields” button to add controllers.

The following controllers can be added to the Ad-Hoc form:

For additional information about controllers read here.

For each controller it will ask to select who is allowed to fill the field, whether it is required or not, background color [for signature, text and signature & seal] or display name [for file and image].

Example of image controller settings:

When the form creation is completed add phone number or email address of the client and press Connect. Timer will be started.

Once the client opens the form the green indicator will appear at the bottom of the screen at the agent side for a short time.

At the end of the process after the client completed and submitted the form the green indicator will appear at the bottom of the screen at the agent side for a short time.

Recipients

When the “Recipients sequence” check box is selected the following fields will be shown:

When adding controllers it will ask to select which recipient is allowed to show or edit the field.

For more information about recipients read here.

It is possible to add new dashboards by clicking Add -> Create new dashboard.

Add the name of the dashboard and select the users’ permissions radio button.

Note: Shared dashboards feature requires activation. Please contact your CS contact for activation. Without the activation only dashboards for personal use can be created.

Click the “Add Widget” and select the widget from the list.

Selected widget will be automatically added to the dashboard.

Each widget has it’s own settings that can be edited by clicking the gear icon.

The widget can be removed from the dashboard by clicking the trash icon.

Press Save button to save the dashboard and Delete button to delete the dashboard.

The owner of the dashboard can edit it by clicking Edit button or clone the dashboard by clicking Clone button.

Users that are not owners, but have permissions to use the dashboard can add it by selecting from the list and hide or clone the dashboard by clicking proper buttons.

This section allows you to see all the transactions to be expired.

Search options

It is possible to perform search or filter by expiration time. Default: 48 hours.

At the end of each line there is a menu with additional options.

Extend validity

Press “Extend validity” to extend the expiration time of the form.

Reminder

In order to send reminders to the client select “Reminder” in the additional options menu. Add new destination or select an existing destination, add the message and press “Confirm” button.

Show Agent

Press “Show Agent” to open the transaction from the agent side.

For more information about “Show Agent” read here.

Show workflow

This option will appear only for the workflow and for the template with recipients.

Select “Show workflow” from the list to see the workflow status.

Delete

In order to delete the transaction from the list press “Delete” in the additional options menu.

The confirmation message will appear for approval.

This section allows to see all the transactions that are waiting for the user that is logged in to the system.

At the end of each line there is a menu with additional options.

Show Client

Press “Show Client” to open the transaction from the client side.

Show workflow

This option will appear only for the workflow and for the template with recipients.

Select “Show workflow” from the list to see the workflow status.

Delete

In order to delete the transaction from the list press “Delete” in the additional options menu.

The confirmation message will appear for approval.

This option allows you to run existing published templates from the dashboard.

Select a template from the list and press Send.

The template will be opened at the Agent screen.

Add phone number of the client or email address where the client will be able to open the form and add the relevant details. Press “Connect” button to send the form to the client.

For more information see “Show Agent” section.

This option allows you to initiate Ad-Hoc process from the dashboard.

Drag PDF file to the field or upload it by pressing “click here to upload” and selecting PDF file location.

It is possible to delete the uploaded file by pressing “Delete” button and add description if needed.

By pressing “Send” button the file will be opened at the Agent screen.

Press “Add Fields” button to add controllers.

For more information see “Show Agent” section.

Add phone number of the client or email address where the client will be able to open the form and press “Connect” button to send the form to the client.

What is a process on Cellosign?

A process in Cellosign is running a template to its destination and includes the filling of the form and its sending by the customer.
Running a template can be done in 5 ways:

1. Running a template by an operating system (integration)
2. Running a template by a system user
3. Running a template via an external link – from a website or portal (public)
4. With a multi-recipient process – a new process is created for each recipient in the process
5. With a multi-templates process – a new process is created on each template in the process

For every action in Cellosign there is an information line in the “processes tab”.

This screen shows all the processes performed in your projects according to a section of time, with the default when entering the screen being actions created “today”.

At the top of the screen:

• Panel for selecting a date range
• Free text search to find processes that contain certain text such as: phone number, email address or template
• A list of projects to select from in case you have more than one project
• If you have selected a project, you can also select a specific template
• An “Export” button that allows downloading all the processes selected by the searching criteria’s to an excel document

Below is an explanation of the data appearing in the processes panel:

• At the table header, the column names where the first column # can be used for arranging the table by ascending or descending order.
• At the bottom of the table, the number of columns in the selected section appears, as well as a navigator that moves to the following processes.
  

Process details

Clicking on the green plus to the left of the process opens the process details screen and displays the process update actions:

This action will appear as long as the operation has not been deleted from the system. The buttons allow:

• Manual deletion of the process
• Open the form as client
• Open the form as agent
• Open a service call for support

Bellow them, we have five panels contains the process data, detailed below:

Document

Displays the process IDs and form processing information.

Archive

If there is a connection [integration] between Cellosign and the CRM system in the customer organization, this panel will show the details of the process archive, after the form has been sent and processed.

Mail to Agent & Mail to Client

If copies of signed forms are sent to the email boxes of the organization or the client, their details will appear in these panels.

Cellosign is a multi-tenant application, so it knows how to handle multiple clients (projects) in a way that produces complete separation between the various projects.

The advantage of a project is complete separation between users, templates, logs, interfaces, tokens and a separate repository for custom code.

The disadvantage of multiple projects for the client is mainly when using functionality that is not out-of-the-box because then in fact each project manages a separate code repository. Let’s take for example a case where requests from Cellosign to SMTP or SMS server must go through PROXY. In such a case, a specific code should be written for the proxy and be duplicated and maintained for each environment separately.

Moreover, the API for our interfaces include the project code in the URL, which means that the client will have to maintain several different repositories in order to communicate with the Cellosign servers.

If the main purpose of the separation is for access to templates and performed actions, you can use the functionality of teams because it allows you to associate users, templates and actions to a team.

Press “Save” button to save the changes.

Note: for users with multiple projects the restricts of security policy will apply according to the highest security measures.

Logo appearance

In HTML and Hybrid templates the logo will appear in the show agent screen when starting the template along with the template name and the Start button.

From the client side it will be shown when opening the form link and in the form header.

In the HTML template only it also will be added to the header of the final PDF.

For all the types of templates it will appear in the invitation email along with an invitation text and “Click to Fill Form” button.

After the form submission the logo will be shown at the final screen with the transaction token.

Why would I want to use this?

Because user/password is sometimes just not enough. Simply put, apart from hacking methods, the weakest chain in protecting our resources is …us.

We tend to leave notes with our user and password on desk, push it through emails and text apps and we keep passwords to our most valuable resources easy to guess????‍♂️.

Case your organization deploying on Cellosign sensitive clients, employees and company data and typically it is, we strongly advise to use this feature.

Case your organization is bound to GDPR, ISO/SOC or other methodologies for security regulations such as ISO-27001, you would need to incorporate this feature into your operation nonetheless.

Cellosign offers 2FA as a security module that can be plugged into your tool set with a click of a button.

Please consult your success contact for activation of 2FA module or post a mail to service@cellosign.com.

How does it work?

Once 2FA module is enabled:

1. login to Cellosign application and click on “project settings” (you will need Administrative permissions)
2. Click “Activate MFA” on “MFA settings” pane
3. That’s it!

Once 2FA is activated, each user associated with the project, will be compelled to go through a process of selecting default Authentication method.

Pane below is used to select and configure 2FA delivery method.

• Select delivery method
• Enter corresponding email/mobile number
• And click “Send code”

Once you received code to your email/mobile device, enter the code to complete the authentication coupling.

Case 2FA method and activation needs to be changed.

1. Login to “Profile” tab, scroll MFA section
2. Click on “MFA configuration”
3. Follow activation process on-screen

Aside from API integrations, connector is a method in Cellosign to interact with your core apps and database with no additional code. Once Cellosign and your data source are coupled, an implementation of business processes can be carried out my mapping your data source objects (or tables) using drags and drop and clicks by, hence no code.

With an integration using database connectors Cellosign is able to provide one way CRUD operations (Create, Read, Update and Delete operations) seamlessly.

With an integration using an application connector, such as for Salesforce, you would be able to do the above plus the ability to trigger actions directly from your application.

Cellosign includes comprehensive set of RESTful API for both inbound and outbound traffic. The underlying concept is that the client core applications (such as CRM/ERP applications) are the system-of-proof. Meaning it is well informed by Cellosign regards business process activities.

Let’s take for example an on boarding process that involves clients, back office and specialists that are attached to the process given the right conditions. Cellosign is perfectly able to report a status of each station as the process progress both by pull (querying) or by pushing it into your core app at the time of event.

How does it happen?

When a core application starts new business process (any) with an API call, it receives in response process keys specific to the process. Based on that set of keys, you will be able to pull data from Cellosign regards the process status. Also, if configured, our outbound API (aka webhooks) can post the data to the CRM

Cellosign includes the ability to post emails to users and clients for purpose of invitations, reminders, alerts etc. On cloud installations we use 3rd party providers to post and manage email traffic.

Using our integrations you are able to integrate and deploy SMTP service of your organization.

Why do I need this?

There are number of reasons to integrate with your organization SMTP:

1. Emails from cellosign are posted with cellosign’s sender such as “invite@cellosign.com”. Using custom SMTP will control the sender and better service to your clients
2. Have tighter control on outbound email traffic and content

You can add as many SMTP as you need to serve as fallback. For example, assume there are SMTP1 and SMTP2 integrations. In case SMTP1 fail to respond, Cellosign will automatically try to send it with SMTP2 integration. Also see below fallback option to trigger Cellosign SMTP service in case of failure.

Setting up SMTP

Follow these steps to add SMTP integration:

1. At the dashboard click integrations
2. locate SMTP integration pane
3. click “Add”

Save the integration and test it by entering email address under “Recipient” and click “Test”.

Authentication types

“Simple” use the standard SMTP protocol for Authentication and require user and pasword”Simple use the standard SMTP protocol for Authentication and require user and pasword

“SASL XAUTH2” option is a secured way to Authenticate mainly SMTP requests with services such as GMAIL, Office exchange etc.

To use SAL XAUTH2 option, first you will need to define the Authentication method through secret integration and then connect your SMTP resource with the authentication. Note that regardless of Authentication method, the service is integrated over SMTP protocol to post emails.

“No Auth” method does not require authentication at all. Be advised that this is not a recommended approach. In case your SMTP relay has no other way to connect with authentication please make sure to whiten relevant Cellosign IPs.

NOTE: “SASL XAUTH2” IS DEPRECATING. DO NOT USE THIS OPTION

SMS are typically used when posting invitations to clients, reminders and also as an evidence for processing at the end of client engagement.

Cellosign is typically bundled with SMS out of the box service, however, in case your organization requires to explicitly integrate with your own provider you are able to easily configure top SMS providers such as: inforu, bezeq, 019 and unicell with configuration only.

Case you require additional provider, let us know.

Why do I need this?

In case your organization requires to have tight control on outbound SMS for any reason such as regulatory, you may add your provider as plugged in SMS integration. Once done, all SMS traffic for your project will consume your integration.

Note that SMS integration is deployed per project and not organization. Case you need custom integration for all your organization projects, this has to be done one by one. Also you may add as many SMS integration as you need for purpose of fallback. For example assume you have configured SMS1 and SMS2 with different providers, in case SMS1 will not respond, Cellosign will automatically fire off SMS2 integration.

Note: SMS failure means that an error response received from the SMS provider. It doesnt mean if message was arrived to recipient or not.

Setting up SMS integration

To add SMS integration, follow these steps:

1. At the dashboard click integrations
2. locate SMS integration pane
3. click “Add”

Save the integration and test it by entering phone number under “Recipient” and click “Test”.

A secret facilitates an Bearer token authentication method (i.e. OAuth2) that is consumed in builtin web-hooks and with application connectors such as Salesforce.

While Secrets for application connectors are created automatically, secrets for Web-hooks are required to be created manually. This is a guide for manually creating and testing your secret integration.

OAuth2 Conventions

With Cellosign Secrets are managed in two standard conventions that are slightly defer in implementation.

• Username/password [General username and password]
• Client ID/Client secret [Microsoft Graph Rest API]

General username and password

Request example

With the example above this is how the request from Cellosign looks like

{
	"username": "Myusername",
	"password": "Mypassword",
	"grant_type": "password",
	"scope": "('read,write',)"
}

Expected response

Cellosign expects at least two parameters in response:

{
	"expires_in": 300,
	"access_token": "BULvsea4JtiGRiSDSJSI%3DEUifiRBkKG5E2XzMDjRfl76ZC9Ub0wnz4XsNiRVBChTYbJcE3F"
}

• “access_token” that will be used in web hook request header for Authorization
• “expires_in” is a lapse time, in seconds, that the access token can be used before it is expired

Microsoft Graph Rest API

Request example

{
	"client_id": "8e17edb9-0f05-46cc-8741-a937e351e631",
	"client_secret": "Mysecret",
	"scope": "read,write",
	"grant_type": "password"
}

Expected response

Cellosign expects at least two parameters in response:

{
	"expires_in": 300,
	"access_token": "BULvsea4JtiGRiSDSJSI%3DEUifiRBkKG5E2XzMDjRfl76ZC9Ub0wnz4XsNiRVBChTYbJcE3F"
}

• “access_token” that will be used in web hook request header for Authorization
• “expires_in” is a lapse time, in seconds, that the access token can be used before it is expired

Notes and gotchas

1. Note the difference in SCOPE parameter value between the two methods.
2. Cellosign will use token until the time of expiration provided for token request. When token is expired, Cellosign will initiate a request for a new token.

At the end a business process Cellosign produces number of files that can be shipped via email, API or directly to your storage.

Currently we support out of the box integrations for FTP/FTPs and Google drive.

Storage service can be deployed with “callback”, which means an API request will be executed from Cellosign to let you know that a storage call has been made. If you have decided to use storage integration, it is recommended to couple it with a callback webhook so you can close the gap between completion on Cellosign to acknowledge in your application.

Why do I need this?

There are number of reasons to integrate with your organization Storage:

1. Occasionally business process ends up with huge and heavy list of attachments that it makes hard for an API to process massive requests
2. You may have more options on files transformation such as the ability to compress all in a single zip archive

Follow these steps to add Storage integration:

1. At the dashboard click integrations
2. locate Storage integration pane
3. click “Add”

Basics and storage type

1. Insert an alias for the integration
2. Set implicit or Explicit. Implicit means that whenever a business process is completed, this integration will fire off. Explicit means, don’t fire unless instructed. See below reference for setting up explicit/implicit
3. Select storage type FTP or Google drive. See below reference to each type
4. Enter relative path
5. Apply file transformations as needed. see details below
6. Setup callback webhook. See details in Webhook: Callback
7. Upload file and test

Configure Google drive integration

First step with Google drive integration is to prepare and download your service account.
1. Use Service key link to create service key at your Google Cloud Platform -> Google Drive Api -> Credentials -> Create Credentials -> Service account

2. download your JSON file with service account credentials

3. Modify default scopes case required

4. Configure path where files will be uploaded into

Configure FTP/s integration

Enter the following details to integrate with your FTP server

Explicitly/Implicitly Storage integration

Storage can be setup to fire off Implicitly that means every business processes will fire this integration. For example a storage action will be executed to your when every business process within your project is completed.

This is the recommended approach if indeed all your business process should end up in in this manner. However if there are different use cases, such as: separate endpoints or some business process does not need storage, it is recommended to couple your integration with a business process Explicitly.

To explicitly couple a Storage with business process we purpose two options:

1. Manually connect it to specific template(s), which means, templates configuration will include explicit coupling with your storage integration. See details below
2. Ad hoc integration for a business process: When the integration is set to explicit, the storage pane display the integration code that can be added to create session request. Simply add the code to your request. All ad hoc integration can be add within the integrations Array

Setting up storage connector

Follow these steps to apply the storage integration into the template:

1. Login to your template
2. Select “Integrations” on the top right and then click on “Connectors”
3. Storage can be applied to “Submit” only. Click “Add Live Connector”
4. On source, select “Storage”
5. On Type: select your integration [by alias]
6. Turn it’s status to “Active”
7. Save the connector and the template

File transformations

Initial set of files can be transformed with simple rules. Each rule selects some files and applies some action to selected set. It is possible to select files by tag, by content type or select all files.

Initial set of files in the end of session looks like this

Transformation examples

Collect all files to zip and apply unique name

1. Click “Add”, Select “All files” from left drop down and “Archive Zip” in drop down on the right. With only this option you will receive to your FTP file named “archive.zip”
2. Click “Add” Select “By tag” from the left and “set name” on the right
3. On select tag, enter “archive”.
4. In “New template path” enter this string “{% now “Y-m-d_H-m-s” as the_time %}{{ reference }}_{{ the_time }}.zip”

This parameter join the process reference id and add to it the current date time : “b7eeb82f-9aab-4dea-813c-7ba06b515867_2025-01-08_14-01-06.zip”

Why this is a good option?

1. All process product are aggregated into a single file (And not scattered)
2. Zip ensure single commit. As oppose to separate files where 1 file can go through and the other wont
3. Unique by date time.
4. Reference that always exists in our output ensure that process can be located easily on our dashboards

In the digital age, safeguarding data integrity and security is a top priority. To ensure that files uploaded by clients during data collection are free from malware and other malicious content, Cellosign has integrated advanced file cleansing technology into its platform.

This integration acts as a robust layer of security, meticulously scanning every file uploaded into forms. The process involves real-time inspection and sanitization of documents, ensuring that only clean, safe files are accepted before being archived. This proactive approach mitigates risks associated with file-based attacks, protecting both users and the system from potential vulnerabilities.

Beyond security, the integration enhances user trust, offering peace of mind that their data and interactions with Cellosign are handled securely. It also aligns with industry compliance standards, reinforcing Cellosign’s commitment to delivering a reliable and secure document management experience.

This seamless file cleansing feature empowers businesses to collect data confidently, knowing that every document meets stringent security requirements. With this integration, Cellosign continues to set a benchmark in secure, efficient, and trustworthy digital solutions.

How it works?

File cleansing integration does not work by default. You will need to activate it. See “Setting up File Cleansing integration” below.

Couple of points before explanation on how this works.

1. Files and images in Cellosign retained as base64 encrypted files. They are never stored as file objects when collected from clients and users. Also when shipped to your endpoints via API (archive) files are delivered in base64 as well.
2. Cellosign has co-browse extension, so user and an agent can sync data in between. For example client can upload a file and an agent can download it for inspection
3. Data collected in form is preserving its state. As such files and images are stored in Cellosign DB until form is submitted or expired.

Our approach for securing and validating the files is by allowing only clean filles to be uploaded into our database, while exposing as little as possible to a potential attacker.

In case a file was successfully uploaded, it will be stored in Cellosign DB and be available to sync any which way, given the appropriate permissions. In this manner we are ensuring that only validated data is stored and ready to sync and distribution.

What is not covered in file cleansing integration?

There are a few endpoints in which Cellosign accept files and images for which File cleansing integration is not covered. All the endpoints below require authenticated user

1. API. Inbound files and Images from your application API to Cellosign.
2. Management application when constructing new template
3. Agent app when uploading a PDF for ad hoc transaction

Setting up File Cleansing integration

To setup file cleansing integration, log in to application console and click projects page.Locate pane “Secured file upload”.

In addition please note the switch “Allow upload if service is not available” (Default to false). Because we are using 3rd party provider service for file cleansing, we need to be ready for events that are beyond our control. Having that we are leaving to your disposal the option to allow upload in case file cleansing service is not available. We recommend that it will remain switched off. Rest assure that we have taken our stand to monitor the service and take action as needed.

Audit log

Each file uploaded to cleansing is recorded in Audit log. Log is preserved in case of success as well as failures. Following are audit details.

Cellosign has a built-in authentication and authorization system, you can also hook-up Cellosign to your SSO/Idp (Identity provider) application to provide user authentication.

For that purpose, Cellosign is already equipped with SAML2/Idp integration. This integration works with any SAML applications, such as Okta or AzureAD.

Why do I need this?

If your organization is already coupled with Idp application then you are already managing users access to resources, in that perspective Cellosign is a service provider (SP) that can be mapped to group of users with set of permissions.

The alternative is to self-manage users within Cellosign and make sure that new employee have an account with Cellosign or account is blocked on leave. In terms of Information security you can control Access, Authentication requirements with your Idp seamlessly.

How it works?

The goal for integration is retain users credentials in a single place, with the Identity provider (IdP), and use it in Cellosign, as a Service Provider(SP) for authentication.

The way it works is that user request a resource from Cellosign application that requires authentication, such as access to template editor or initating a business process. Let’s assume this is first-time user. The process works as follow:

1. User access Cellosign resource (through browser).
2. Cellosign identify that the resource is coupled with your Idp
3. Cellosign redirects the request to your Idp for authentication
4. On a successful authentication, Cellosign will record user details such as name and email and mark user’s record as managed with Idp
5. Once user has been automatically registered he will be redirected to the required resource

Notes:

1. Cellosign keeps some data of the user since the application requires some level of engagement such as emails, alerts and other notifications.
2. Cellosign does not keep users password

For a returning user the process is pretty much similar, instead of creating user, we are validating and updating user details.

Integration strategy

Clients structure with Cellosign works as follow:

1. Organization is a top level entity
2. Within organization we have “project”(s). Some of the resources are shared on organization level, others are project specific.
3. Users are mostly coupled with projects, for example users from HR department requires exclusive rights to HR Business processes, Digital department requires exclusive rights as well
4. For some users, you would like to have access rights to more then one department or even access to the entire organization resources, for example support or implementation.

Integration with your Idp can work both on organization, project and users layer. See details in setup section.

Setting up Idp integration

To integrate Cellosign with your Idp we need to couple if both ways. Before you start, you will need to get:

1. Cellosign domain
2. Your project(s) in Cellosign
3. Choose role assignment strategy. For quick starter you may choose to assign minor permissions automatically in Cellosign

Step 1: Integrating Idp to Cellosign

In your Idp edit the Entity ID which is global unique ID of service provider.

with Cellosign the components are: https://domain/project/saml2_auth/acs/

For example assuming this is an integration with shared cloud production and your project is “digital” then your entity id would be:
https://app.cellosign.com/digital/saml2_auth/acs/

Same value also goes to ACS, that is url for callback.

The image on the right is taken from Azure AD for setting up Entity ID and ACS[Reply URL].

Make sure to get metadata data URL (aka federated data url) or download metadata XML file, you will need it for next step

Step 2: Integrating Cellosign to Idp

Follow the steps below to set up Cellosign Integration:

1. At the dashboard click integrations
2. locate SSO integration pane
3. click “Add” and continue with the table below for an explanation on setup

Role assignments

The steps above are bout Authentication. This step is about Authorization. There are couple of options here:

1. This is the most common implementation. When a new user is introduced, he will be assigned with the lowest permissions or no permissions at all. The permissions level,  if need to be upgraded or setup, will be controlled in Cellosign application by your admin user
2. Another option is that the authorization will be controlled by a claim or list of groups. list of groups is useful when our users are diverse, for example user may have lower permissions on Project A and higher permissions on Project B. (Keep in mind that this permissions can be made both manually or automatically with the proper setup)

For option one, select “Do not assign user role” for having no permissions at all, or “Assign default role” and then select the appropriate role. Select “Agent” for minimal permissions.

For option two, you are able to:

1. Select role from a claim
2. Select role from list of groups

For selecting role from a claim, insert the claim name. The value of the claim should be one of:

1. “agent”: For lower permissions
2. “manager”: for project admin
3. “company_manager”: for organization administration

For getting role from list of groups.

1. Insert claim
2. Insert the ID for project admins group. This id represents a list of projects in cellosign that the user will be associated with for agent permissions. for example: [“hr”,”it]
3. Insert the ID for agents group. This id represents a list of projects in cellosign that the user will be associated with for agent permissions

Note: Project names should be identical to those in Cellosign.

Azure AD, EntraID Specifics

Setup Azure/Entra like so:

Matadata is a url starting with https://login.microsoftonline.com/

Use the claims notation as demonstrated: name, givenName, surname,emailAddress

In case you require to use assignment policy per claim, set it up like so”

Before creating an integration with the Cellosign system, the integrity of the terminal must be checked against Credit Guard.Get the login information from Credit Guard and perform a terminal health check on the payment page.

In order to create payment integration in the Cellosign system go to “Integrations” screen and press “+Add” under “Payment” section:

Basic settings

Terminal settings

Note: the following information must be obtained from the payment service provider.

Authentication settings

Save and press “Test” button to verify connection with your payment server.

For more information about the implementation of the Payment controller click here.

How credit guard integration works?

The integration with credit guard works in 3 steps:

This integration allows to validate the company ID when user fills the form. There’s a public GOV API available that exposes data of Israeli companies, including: ID, name, status etc..

Company ID validation includes two steps: creating a WebHook integration and configuring a connector from the template side.

WebHook integration

In order to create WebHook integration in the Cellosign system go to “Integrations” screen and press “+Add” under “WebHook” section:

All the other parameters should not be changed, default values will be used.

Save and press “Test” button to verify connection with the WebHook server.

Template implementation

From the template side need to add relevant fields and change their IDs according to the table below:

Company ID field example:

Company English name field example:

Go to “Integrations tab” and press “+Add Live Connector” under Connectors section:

In the Source field select the created WebHook integration.

Set the Trigger action on “Change” of the company ID field or use “Click” action in case of button.

Map the company fields from the template. Alias will be completed automatically according to the field ID.

In the client side when entering the Company ID value all the other fields will be completed automatically with the returned values from the Registrar of Companies API.

For more information about templates options click here.

Analytics screen allows you perform the analysis of your transactions and perform filtering by date and specific templates.

In addition it is possible to save parameters and fields in the template and perform search by specific parameters and values.

For more information about saved parameters and fields read here.

Cellosign manages three types of user’s permissions:

In Cellosign, there is the option to create users and also the option to connect to Active Directory
systems, so the login process will take place as part of the corporate identification system.

In case that Cellosign is connected to the Active Directory system in your organization, the creation
of the user will be automatic, without the need to create the user in Cellosign as well.

Users panel

This panel can be used to view and locate existing users, add new users and set permissions.

To update a user, select a user from the list. Perform the needed changes and press “Update User” button.

Service user are used for an API connection with Cellosign. Service user cannot login to UI applications and can only be used for integrations. To create Service user, login to Cellosign”, click on “Users” on left pane and click “Add service”. Enter details as instructed below.

To reveal the Access token click on “Show token”. This will display the access token for integrations

At the end of registering a new user, select the “Save User” button and additional options will immediately open. For more information see “Password control” section.

In order to change user’s permissions for the same project, first remove the existing permission by clicking the “Delete Permission” button. Then select the organization from the list, the project and the desired role from the options.

Click the “Update User” button to save updated data if a change is made to the user’s details.

Email and mobile phone

The user’s email address and phone number are supported by a quick search on the form submission page.

Type a part of user’s details to locate it in the list of users and send to the relevant destination, email, or mobile phone.

The access to the list of users may therefore also be for you a kind of contact list for those without any specific role in your organization who may receive self-filling forms.

In the list of users must only be people from your organization and not from another external source.

Notes:

1. password operations on user are allowed for users with manager and organization manager permissions.
2. In case user has permissions to more then one project, the password requirements will be the strict one. for example if on project A password is limited to 5 characters and on project B to 8 characters. User will be obligated to 8 characters password.

In the Profile area user can view and edit his account details, change password, add the private signature, view and change his token, and configure MFA for login additional verification.

Note: user details cannot be changed by the third party user and should be updated by the organization.

Private signature

The signature allows to input the user’s signature into the form automatically.

The functionality is usually used for automatic signing of files, such as invoices or a certificate “authorized to sign” in the organization.

API

Show Token/Hide Token/Refresh Token will show, hide and change the token accordingly.

“Open documentation page” link will open the related API documentation.

MFA configuration

User can configure 2-Step verification for login by choosing code destination.

Templates panel displays the list of templates related to the project. The page is accessible for users with “Project manager” and “Organization manager” permissions.

In the header of the page there are buttons “+ Create New Template” and “Upload Template From File”.

You can filter templates by using “Search by template or tag” field.

A form in the Cellosign application can be created using the following types of templates:

• Responsive HTML template, automatically adapted to the client’s screen and rich of display capabilities and directing the end user. For more information see “HTML template“.

• A template based on a PDF form that is loaded when the form is created. For the most part, the form is quite limited in its functional richness by nature. For more information see “PDF template“.

• A template that combines a PDF and HTML form, when the customer fills the details in HTML form and the information is embedded to the PDF form. For more information see “Hydrid template“.

1. Add the Template Name.
2. Choose one of the options:

• If you would like to create a template based on HTML experience and you do not have a file, select the “HTML Template” option.
• If the product should be a PDF, select the “From PDF file” option. Upload PDF file by pressing “Choose file” button and selecting PDF file location.
• If the product should be a combination of PDF and HTML form, select the “From PDF file” option. Upload PDF file by pressing “Choose file” button and selecting PDF file location.

When you click “Save”, the template editor will open.

Template toolbar

To update a template, select a template from the list and click the template name.

Perform the needed changes and press “Save” button.

Disclaimer

This option is intended to transfer a template from one system to another, such as a test server to a production server.

The file can be downloaded from a template editor before.

For more information about template tools read here.

It is recommended to use the PDF format only for documents that are regulatory such as powers of attorney and insurance forms.

And in any case, even if the template is a PDF, it is recommended to use it in combination with an HTML template to provide a better customer experience.

For the explanation about the HTML integration in PDF template read here.

After loading a PDF file and saving, the application will go to the template editor screen with the template in “Draft” mode.

On the right side is a list of possible controls for a PDF template and on the left side is the PDF file uploaded for the template.

Click any controller on the right, drag and drop it to the desired position on the PDF.

For more information about controllers read here.

Clicking on the controller will move the right side to the controller editor.

For more information about controller editor read here.

Basic options

In the PDF form the label does not appear, but a value must be entered in this field for accessibility purposes. The screen readers read the value embedded in the label for the accessibility of the form. For more details about accessibility read here.

For a detailed explanation about controllers: mandatory fields, dependencies and more, read here.

Position

To reposition the input field on the PDF there are two options:

• Click on the control and drag it to the desired location on the PDF or,

• Click on the control and click on the “Position” tab on the right side of the screen. The “Top” and “Left” controls indicate the distance [in percent] from the top and left edges of the PDF page.

To decrease or increase the input field there are two options:

• Click on the control on its right or bottom side and drag to fix the height or width of the input field, or

• Click on the control and click on the “Position” tab on the right side of the screen. The “Height” and “Width” controls, specify the height and width [in percent] of the height and width of the PDF page.

Upload files and images

Under the list of controllers on the right side there is an option to upload files and images:

• Add the Display Name: instruct client what file to upload.

• Select the Type of file: Image upload or File upload.

• Select whether the file is mandatory or not.

• When finished, click “Add” [green V button].

Default attachment extensions are defined in the Session settings under Projects.

For more information read here.

Archive

Information in the archived PDF file based on PDF template is aligned to the center according to the width of the field in the form.

HTML template is responsive, automatically adapted to the client’s screen and rich of display capabilities.

After adding a template name and saving, the application will go to the template editor screen with the template in “Draft” mode.

HTML template is built from four nested components:

• Page: The template contains one or more pages. Switching between the pages in the form is possible for the user using the navigation buttons at the bottom of the page.
• Section: Each page contains one or more sections.
• Row: Each row contains at least one column and up to three columns.
• Column: A column may contain one or more controls.

At the top of the template editor is “Intro” section, that allows a Welcome message to be displayed in the form.

At the bottom of the form editor is “Outro” section, that allows the completion message to be displayed to the person filling out the form.

Below is an example of a template consisting of one page, in which one section includes four rows and three columns in each row.

Page

Template contains pages that the user can navigate through. It is recommended to use division into pages when the form is loaded with controllers, and we want to create a more pleasant experience when filling out the form. For each page in the template, you can apply a title and additional design options.

To enter the page’s options, click on the margin of the page, the page will have a light green background and a panel for the page’s options will open on the right.

Page design includes the following options:

Section

As mentioned before, page contains one or more sections.

Similar to the page options, the section also includes design options. To enter the section’s options, click on the section’s margin. The section will have a pink background and a panel for the section’s options will open on the right.

Rows and columns

The template editor allows us to create a form that will automatically adjust to the size of the user’s screen.

If we use only one column per row throughout the form the entire form, the form will be presented to the client as one column of the fields.

If we use more than one column in a row, then:

• If the client uses a large screen such as a tablet or a desktop computer, the controls will be displayed as they are displayed in the template.

• If the client uses a narrow screen, for example a mobile phone, the controls in the column will be displayed in a column one after the other.

• Display of the form on a tablet and a desktop computer.

• Display of the form on a mobile phone.

Intro

Clicking on the “Intro” button at the top of the template entry will display the panel on the right.

The “Hide Welcome screen” button will hide the rest of the parameters in the panel and will also hide the welcome screen for the client, so that the link to the form will go directly to the form itself.

Outro

The completion page displays an indication that the procedure has been completed successfully and even navigates it to another page such as your home site.

Archive

In the HTML template it is possible to hide any specific controllers from the preview and the final PDF by adding “pdf_hidden” class under the Developer tab.

In this case fields with pdf_hidden class will be shown in client’s form to add the values and complete the form.

But they will not be shown in the preview and in the final PDF after submission.

For more information about the Developer tab click here.

A template that combines a PDF and HTML form, when the customer fills the details in HTML form and the information is embedded to the PDF form.

When creating a hybrid form first the PDF template should be created.

For more information, see “PDF template“.

To create an HTML template from the controllers entered in the PDF template, click “HTML Template Editor” on the top toolbar at the right side, and then click “Create HTML template”.

Once clicked, all controls from the PDF template will be injected into the HTML template. Read about the HTML template editor here.

Archive

Information in the archived PDF file based on Hybrid template is aligned to the center according to the width of the field in the form.

A template usually consists of a collection of controllers, some of which are read-only and some of which are intended for the user to enter data, upload a file, or select one or more of the displayed options.

In “Controller editor” section we will describe common options for all controllers.

See below a detailed explanation of each controller type and additional editor options.

In this section we will describe possible options for all controllers. For additional options for a specific controller see “Controller types“.

Basic options

Values & Display

The options in the tab allow you to enter values ​​for the controller according to the type of controller. For each controller its related collection of options will be shown, like list values, etc. See “Controller types” page for detailed information.

Field clone allows copying the value to a field from another input field. It is recommended to use when the customer has already filled in his name at the beginning of the form.

Types and Validation

This tab includes options for data validation and possible input types for each controller. For example, in a signature field we can choose whether it is a signature and a company seal; in a text field we can limit the number of characters to a minimum and maximum.

Conditional permissions

This tab allows you alter user permissions given a set of conditions. For example field will be required if a client is of “Business type”.

To add a dependency, click the “Add Dependency” button. Select the behaviour of the control as result of the dependency:

To add condition[s] for the dependency, click the “Add Condition” button. Select the controller on which the condition will be applied and the values ​​on which the condition will be applied.

If two or more conditions are added, the dependency will only be activated if they are all met [AND].

You can add more than one dependency, all the dependencies are related to each other. The dependency that will be activated is the one that meets all the dependency conditions.

Note that the first condition met will trigger the permissions. This pane allow you to reorder the permissions order with drag and drop.

Conditional values

This tab enables you to carry out the following settings:

1. Clone. If assigned value as clone of another field than its value will be fetched from the field it’s pointing at. This is very useful in cases where client name needs to be collected once and paste in multiple positions. In case clone is not defined then you are able to set default value or conditional value with this pane.
2. Default value. Set up a value for the form control that will be propagated into the control whenever new session is created
3. Conditional value. Similar to above conditional permissions you may query other form controls and based on that set up a new value to form control. Conditional value supports: concatenation of strings and arithmetic calculations. For instance
   • This value “=OrderSum * 0.17” will search for a value in control “OrderSum” multiply it with “0.17” and return round up number. Arithmetic are always rounded.
   • Thus value “=textA textB 123” will concatenate values in textA, textB (given that these are form controls, if not textA and textB will be added as plain text) and append to it “ABC” given that this is not a form control.

Note that the first condition met will trigger the permissions. This pane allow you to reorder the permissions order with drag and drop.

Style

All the options in Style tab are to design the controller, such as the Background color of the field and the Font color and choosing an icon to be attached to the field.

In order for the form to comply with the accessibility standard, it is recommended not to edit and use background colors for fields and fonts and to use only the design of the template to select colors.

Developer

In this tab there are additional options for developers:

Built-in classes

In the HTML template only it is possible to hide any specific controllers from the preview and the final PDF by adding “pdf_hidden” class under the Developer tab.

In this case fields with pdf_hidden class will be shown in client’s form to add the values and complete the form.

But they will not be shown in the preview and in the final PDF after submission.

For more information about the HTML template click here.

Use this class in the section settings when need to remove irrelevant blank spaces in the final PDF.

It is possible to create a group of controllers with the same basic settings and conditional permissions.

In order to create the group, go to the Control Group tab, under the template editor, and press the “Add Group” button.

Press the Edit button and add the group name.

Click on the controllers in the template to be added to the same group. They will be marked in green, and will be shown under the group in the right pane.

Press the Settings button and add the basic settings and the conditional permissions that will be applied to all of the controllers in the same group.

In the example below the fields ID, Email, Phone and Signature will be shown to the client and will be required and editable only when the check box is selected and the Full name is not empty.

Client side before the conditions are met:

Client side after the conditions are met:

Note: the controller that belongs to the group will have only the label and the description parameters in the Basic settings tab. Also Conditional Permissions and Conditional values tabs will not appear. They should be defined as part of the group.

Example of the Text controller that belongs to the group:

Example of the Text controller that does not belong to the group:

To remove the controller from the group, click on it in the template or use the trash button. The green mark will be removed from the field and it will not be shown under the group in the right pane.

Note: the controllers that have been removed from the group would keep the definitions of the group after it has been deleted. In order to change or remove those definitions you would need to do it manually.

The Design tab is divided into two parts. It is possible to choose the design that is already ready for you or to set your own style for each component in the form. Part of the parameters are available only in HTML form or HTML combined with PDF.

Page design

Form design

Buttons design

Buttons design settings will be applied to all types of buttons in the form, including navigation buttons, radio buttons and check boxes. See below the example of controllers according to the design:

Controllers

Note: Error messages will always appear in red.

PDF form design

It is possible to select the completed design from the “Custom theme” tab.

Configuration of the template includes the following tabs:

• Basic configuration: show form before submission, text for general buttons, categories for the template, etc.

• Messages & Reminders: client messages that go out of the application, text messages and emails throughout the life cycle of the form.

• Workflow: multiple recipients workflow, definition of different roles in the form while everyone can have a different experience.  

• Templates sequence: definition of a triggering action (sending another form) when this form is sent by the client.

• Javascript & Stylesheet: options for developers [Extensions].

• Errors: definition of custom error messages.

• Custom PDF template: definition of a unique header and footer for PDF final form.

This chapter describes information security options in the template.

Also, apart from the identification options shown in this chapter, there are additional security settings under Projects.  For more information read here.

Activate OTP

Activating this option will generate a random 4-digit one-time password for entering the form by the person filling out the form. The password will be sent to the destination to which the action was sent.

In case the operation cannot be sent through Cellosign in SMS or email, it is not possible to use the OTP.

Default OTP validity is 5 minutes. Selecting the OTP option allows you to set a validity between one minute and 1440 minutes (which is a day).

eIDAS

The eIDAS standard implemented in the template generates a log of activity in the signature fields. Every event of signing or deleting a signature is saved in the system log and exported together with the results of the operation in an archive to email or to the core systems of your organization.

The sample output below is a sample of a signature deletion event:

Add browser timestamp to signature field

When set to ON the timestamp of the browser will be added to signature field:

Clone graphic signature for approval

When set to ON it will use the last signature added by the customer and insert it into the signature field for the customer’s approval.

Note: Although this is a signature that requires approval, it is recommended to consult the legal department to validate the solution of the process.

Combining input fields from the form to the signature field

In addition to a digital signature that is embedded in the product, it is also possible to embed input fields from the form into the signature field. In this way a signed document can be presented when the signature fields contain identifying details of the client.

Require password

When activated the client will be asked to fill in data that was inserted by the agent into the form, for example an ID Number. To activate this option, you must select an input field from the list of fields in the form.

The field label will also serve as a guide to the client regarding what to type.

Expiration in hours

A working assumption is that a form contains sensitive information such as personal details, photographs of sensitive documents and signatures. Each operation has a predefined lifetime, according to the following hierarchy:

• At the project level: valid for 24 hours [1 day], unless otherwise applied.

• At the template level: valid for 48 hours by default. Valid values between 1 to 960 hours. This value overrides the project default.

• At the operation level [in integration only] that overrides all defaults.

If the form is not sent by the client, the token [the unique link to the action] will be deleted automatically after the action is expired and will no longer be accessible. The message to the customer “404”.

Additional parameters

Input validation

Cellosign forms comprised of various input fields, images and datasets. Some of the inputs, such as paragraph may include rich text editor features as: html, css and javascripts.

In order to secure your forms and restrict inputs it is advised to use the proper data types where needed. For example, use “Number” controls instead of plain “Text” fields to ensure that number value will be collected. Use “Email” for the same reason.

In addition, Cellosign template studio include rich configuration to limit the allowed input values. For example Text field includes variety of configuration options to make sure that the right data is collected.

In addition, you may also use REGEX to narrow down input options even further.

Read only

When activated, client will not be able to submit the session.

BMPN engine

Drag & Drop establishment of exclusive, parallel, or dynamic business processes while integrating a round of approvals between internal and external organizational users, collecting and automatically completing data from tangential systems, creating digital forms, and driving tasks required for the business process by a representative or a core system. The process can begin from any digital point starting from the company’s portal or website of the end user (customers, suppliers, employees), web landing page, CRM, DWH, ERP systems as well as from a representative through individual or multiple sending.

Workflows panel displays the list of workflows related to the project. The page is accessible for users with “Project manager” and “Organization manager” permissions.

In the header of the page you can see buttons “+ New Workflow” and “Import From File”.

The following options are available in the workflow screen:

• Create new workflow by pressing “+ New Workflow” button.

• Import workflow from file by pressing “Import From File” button.

• Update already existing workflow by selecting it from the list and pressing the name.

Workflow window consists of the controllers list at the left side, workflow toolbar at the bottom and parameters editor at the right side.

Workflow toolbar

Controllers

Controllers allow to create the workflow with different forms, messages, dependencies and tasks.

See below the explanation of each controller.

	Activate the hand tool	Use this controller to activate the hand tool and move the whole workflow.
	Activate the lasso tool	Use this controller to activate the lasso tool in order to mark a part of the workflow and move it to another place.
	Activate the create/remove space tool	Use this controller to activate the space tool in order to add or remove the space between controllers in the workflow.
	Activate the global connect tool	Use this controller to create the connection between two controllers.
	Create start event	It is required to add the start event at the beginning of each workflow as a start point.
	Create finish event	It is required to add the finish event at the end of each workflow as the end point.
	Create form	Use this controller to add a template to the workflow, select roles, insert data to the form fields etc.
	Create message	Use this controller to create SMS or Email messages of different types with default or custom messages.
	Create parallel gateway	Use this controller to create parallel tasks in the workflow. It is recommended to add this controller at the beginning of each set of parallel tasks as open point and at the end of each set as close point, so the workflow will wait for all the parallel tasks to be completed before continue.
	Create exclusive gateway	Use this controller to create an exclusive path of the tasks and to add conditions.
	Create script task	Use this controller to add scripts to the workflow.
	Create service task	Use this controller to add services to the workflow, like Webhook, Archive etc
	Create call activity	Use this controller to create a call activity.

In addition a new controller can be added from another controller by clicking the relevant icon and they will be automatically connected to each other.

Additional options

	Remove	Press the icon the remove the controller from the workflow.
	Change color	Press the icon to change the color of the controller in the workflow.
	Change type	Press the icon to change the type.
	Append type	Press the icon to append the type.
	Append form created event	Press the icon to append the form event. For example, to send a message to the recipient.

Example of the workflow

This option is intended to transfer a workflow from one system to another, such as a test server to a production server.

The file can be downloaded from a workflow editor before.

For more information about workflow tools read here.

This controller is used as a start point of the workflow with input parameters and other configurations.

When pressing “Start” controller in the workflow the settings panel will be opened at the right side.

General settings

Upon selecting public checkbox additional parameters will be shown.

Inputs settings

This screen is used to add input parameters to the start event controller that will be displayed when the workflow starts and used in the following sessions and messages.

Public link screen example

This controller is used to create a session with a specific template and role, input parameters and other configurations.

When pressing “Session” controller in the workflow the session settings panel will be opened at the right side.

General settings

Inputs settings

This screen is used to add input parameters to the session controller from the previous controllers or from the form.

Example of the input parameter from the Start event:

Example of the input from the previous session result:

Example of the input parameter from the Form Result of the client session:

Form settings

This controller is used to create SMS or Email messages of different types with default or custom text, input parameters and other configurations.

When pressing “Message” controller in the workflow the message settings panel will be opened at the right side.

General settings

Inputs settings

This screen is used to add input parameters to the message controller from the previous controllers or from the form.

Example of the input parameter from the Start event:

Example of the input parameter from the Form Result of the client session:

Message settings

This screen is used to configure the kind of message, recipients, message text etc.

Select the kind of the message: SMS or Email. Parameters of the window will vary according to the selected kind.

Email

Email message settings

SMS

SMS message settings

This controller is used to create an exclusive gateway in the workflow with Javascript or Expression Builder conditions, input parameters and other configurations.

When pressing “Create exclusive gateway” controller in the workflow the settings panel will be opened at the right side.

General settings

Inputs settings

This screen is used to add input parameters to the exclusive gateway controller from the previous controllers or from the form.

Example of the input parameter from the Recipient1 session result:

Example of the input parameter from the Form Result of the Recipient1 session:

Condition definition

When pressing the gateway in the workflow the settings panel will be opened at the right side. Press “Condition” tab to add conditions to your exclusive gateway.

Expression language can be “Javascript Expression” or “Expression Builder”.

For detailed information about this section see “Post transactions from spreadsheet”.

This function enable you to post transactions from data you have in EXCEL spreadsheet. This is a convenient option for mass distribution in case posting from API is not available to you.

Quick brief on this function

To use this option select “Transaction file” from the left menu.

1. Select template that you would like to distribute and select template fields that you wish to inject values into’ for example client name, address etc..
2. Download Cellosign spreadsheet that includes structure to fill data into
3. Update Cellosign spreadsheet and upload it back
4. Uploaded data will be displayed and will highlight invalid data, such as incorrect email address or phone number, that needs to be fixed
5. Fix or remove rows and post transactions
6. Cellosign will post all transactions one by one. At the end of posting you should be receiving an email on posting completion

Configure

Start by selecting template from templates select box.

Note: users with “Agent” permissions will get templates in status “Publish” in the list and users with “Project manager” permissions will get both “Publish” and “Edit” templates in the list.

Select fields that you would like to inject values into.

Filtering fields to for selection includes to options:

1. Filter all required fields. This will display fields that are setup as “required” by default in the template
2. By Class. This function can be very handy if you are using this function a lot. Filter by class will enable you show only fields of some attribute that are per-configured in the template.

To configure a class for a template field.

1. Go to template studio
2. Select field you wish to apply class for and enter class name. You may enter classes as many as you wish to filter for different needs
3. Once fields are configured are setup your Class be displayed in your filter list

Upload

Once spreadsheet is ready. go back to Cellosign configuration screen, upload the file and click “Next”

Validate

On next screen your data will be displayed with the entire data set from your spreadsheet. Cells with a light-red background indicate an invalid value, such as wrong email format or date field that the value assigned has incorrect format. Hover the cell to see the details regard error.

In addition, you may check the switch “Alert on required fields with no value” to highlight and prevent submission where row has required field that has no value.

On the left most column all rows are checked, if you wish to prevent a row from being posted, simply uncheck it.

Once all errors are cleared or rows unchecked Click “Post” to send transactions file for process. Once all is done you will be receiving an email with notification on transactions submission. This email will also include an id, like this one “fd52f83a-19d4-4bce-b6f8-8dacbe90b23f”, use it to filter all the batch transactions in the transactions board.

Limitations

1. Posting transactions from file is carried out in sequence (one at a time) and may take time to complete
2. Make sure to use Spreadsheet that was downloaded from Cellosign, otherwise it might not work correctly
3. Although this function is available for your disposal, it is advised to use API or Connectors instead as these options are faster, cleaner and in general a superior alternative

This screen allows you to add a “data list” manually or from a file (An excel, csv or a json) and associate the data list with a “List of values” type control while editing the template.

Several data dictionaries can be associated with the same template and the same data dictionary can be associated with several templates.

To create a dictionary, login to application and click “data sources” and “Dictionaries”.

At the top on the right there is a button for adding a new dictionary and a button for uploading a file.

You can use the upload button for loading a file for your dictionary. You can see on the bottom the explanation on every item at the dictionary table.

Also, you can click on the Add button to create the new dictionary.

In this case, you can add data manually to the dictionary by using the green + or use the replace and append buttons to load files to the dictionary.

Here you can also export the dictionary that you are viewing/editing using the ‘Export” Button.
The exported files will be on CSV format by default and on JSON format if you choose it using the arrow on the “Export” button:

Here are the editing options on current dictionary (from left to right):

• The name of the dictionary, you can change this as needed.
• Save button, to save a new data dictionary or save changes to an existing data dictionary.
• Replace button for replacing the existing dictionary with a loaded excel or csv file
• Append button for adding the loaded file data to the existing dictionary
• Delete button for deleting the dictionary

This table will explain the dictionary table:

Notes and Gotchas

For security reasons some characters are disallowed.

Disallowed for Text column: '<', '>', ';'

Disallowed for value and group columns: '<', '>', '#', '$', '%', '^', '&', '*', '|', ';', ':', '{', '}', '[', ']', '=', '+', '-'

Think about it as a custom table hosted in Cellosign. You can customize it any way you want and connect it to template.

What it’s for?

Consider the option when you have large repository of texts and inputs that needs to be incorporated into business process either as initial value, as a condition to other selection or per user engagement. Up until now that way to handle this process would have required to configure fields and conditions inline the template.

In case texts and inputs needs to be incorporated into large amounts of fields and templates, this can be quite tedious. With this feature you will be able to configure relational table with keys and data and use it in cellosign templates using our connector editor. This is specially become handy when you have extensive conditions to handle the texts and in case you have texts such as terms/legal that are expanded over large amount of templates, so you can keep it all in one place.

Configuring data table

To configure data table login to application and click “data sources” and “Tables”.

Click add table and define: table name, columns as instructed on screen. Click to add rows.

Eventually, you will have a data table with rows and columns.

Note that “key” type columns are designated for the connector in next step so you can search matching records.

Adding data and inputs to data table

Let’s add some data and input elements to it.

In the screen capture on the right we added:

1. “House” as key for selection
2. Texts with input elements to Application
3. Additional texts for Conditions.

To add input elements, simply click the icons bordered with blue.

• The icon on the left is a “Checkbox”
• Icon in the middle is text input
• The right most icon is Dropdown(select) input.

Configure a template

Lets add a new template that includes Select element and two paragraphs.

Select will include values “Car” and “House”. What we require to occur is that when client selects “Car” or “House”, Cellosign will fetch via the connector the matching “Application” and “Conditions” for his selection.

Switch on “Display bottom border only for input” in case paragraph includes input elements that otherwise might conceal upper text lines.

Note: In order to secure your form you will be required to toggle a paragraph in order to allow parsing input elements into the form. So whenever data table data includes input for parsing, the toggle displayed on the right, must be checked.

Connector configuration

On template editor click integrations on top pane and then “Connectors”.

In this screen you will see “Preset”, “Live”, “Submit” and “Post submit” for which our connectors will be integrated into.

“Preset” is the ability to get values from the table on session initiation, requires no user intervention.

“Live” will be configured when the connector require some of interaction from the user such as selecting value or click on a button.

“Submit” and “Post submit” are for databases and apps such as salesforce or Dynamics [that are coming up in next releases].

To configure connector to data table click “add” on “Preset” or “Live” sections.

1. Select data table you have configured
2. Set status “Active”
3. Define the lookup:
   • keys from the data table [one or more]
   • Equation [for data table equal only is applicable]
   • To which entity to compare with: form field value, label [integration] or fixed value
   • Add conditions as many is needed for the lookup
4. Define what happens if query return no results, one or more than one result
5. On “Live” you will need to configure how the connector is activated
   • on “Change”: As the user types in. Select the field from the list to attach the connector with
   • on “Click”: select a button from the form that will activate the connector
6. Finally map the query result into the form fields. which value from data table goes to which field in form

Demo

For your convenience, this is a demo form already setup with the example above.

Categories are an easy way to sort our business processes into groups. We can relate any template or BPMN process to a category.

First we will see how to create categories and then we relate our templates and BPMNs to the categories.

How to create a category?

To create a new category, login to application and click “data sources” and “Category”.

Click Add category:

TBD

Support and accessibility toolbar incorporated in all forms. The toolbar receives first focus when open a form link so screen readers can read through its content.

To open the menu click the hamburger icon at the top of your frame.

Accessibility features

Activate accessibility option

Transform inputs to valid accessible collection.

• Date input transformed from a date or date-time widget to manual input
• Signature pad will require upload a signature image rather then drawing the sugnature

In addition focus on input or (Tab/Shift+TAB) between fields will draw a border on the focused input

Monochrome option

This option modifying colors to monochromatic that makes to contrast accessible. It is advised to use high contrast as a default, regardless if the Monochrome option is activated or not.

Accessibility statement

Link to our accessibility statement

Assistance

Download file for print

This option, if activated, allow client to download a PDF file based on the data already propagated into the form. please consult with our support for activation of this feature.

Privacy statement

Link to our accessibility statement

About

View display form and client data. On some cases were client has an issue we will require this data

1. Release: Cellosign release
2. Token: Session ID in view
3. Browser: Client browser

Client forms is a user interface that present to a client a list of forms that needs to be filled in an organized and secured fashion. Clients receives one link against they will need to identify and authorized for access.

The interface is highly customizable and include rich function customization and looks configuration to match your brand.

Why do I need this?

Client forms is a great way to communicate with your clients, push new forms that needs to be filled, Client can see show how much time left to complete and all in a single link and one time authentication.

Setting up client forms

Login to projects page and locate “Client forms” and follow the tabs to set it up. Before modifying default colors and backgrounds make sure to read accessibility section below.

Background settings

This setting is optional. It affect the authorization pages only. It does not propagated in transactions page.

Color settings

Button background color and button text color

All buttons on transactions view and authorization page gets there attributes from the first two color pickers. including the shading below a transaction row.

The image on the right is a result of a red background and white-gray text color as configured in the image below

Remember to make sure to pick colors that contrasts well.

Text color

Most of the texts in client forms view will pick on this color, including transactions text and hello text as can be seen in the image above.

Authentication settings

This tab includes a collection of settings to process the authentication stage and configuration of footer links

Identification header, text, error and support text

Configure texts for intro page. For accessibility compliance make sure your text are simple and direct

Suppress leading zeros

Client forms viewer collects all client’s transactions that share the same password, see require password for details. Occasionally the access password is a number, such as ID that has fluid representations to include or exclude leading zeros. As such when client insert the password it will not include leading zero and when the transaction is initiated from your core application it does include it. Essentially, we might end up with mismatch when client enters “7673899” as password and your DB inject “07673899”. These will never match.

This is where “Suppress leading zeros” become handy. It will suppress leading zeros to match. As such “000123” is equal to “123”.

Note: Be aware on what data to use for password authentication. Make sure that “0123” and “123” are not different entities. In

Activate OTP

We encourage you to use this option. OTP will guarantee that clients can access their transactions can do so only after we have doubled checked their identity. To apply OTP to transactions, at least one transaction that match the password will need to have an OTP associated. If there are more that one OTP address then the viewer will list the propagated OTP destinations.

Footer links

By default Cellosign displays links to Accessibility, Privacy and terms of use pages. Use the switch to turn off any of the links. Alternatively. You may override the defaults to include links of your own. Make sure to add valid markup and texts. i.e.:

1. Markup to open external web address: “https://yourdomain.com”
2. To pop up phone app. “tel:0500001234” (For mobile apps)
3. To display only the label please enter “#” in url

Transactions settings

Introduction text

Enter here text that will appear before the list of transactions

Show validity

When activated the date and time on which a transaction will be expired is displayed below the transaction button.

Aggregate

Enable this option if you are using business models and wish to display collections of transactions associated with business case.

In the example below we have two business case aggregations and two stand alone transactions:

1. Loan 12345-67: Has 2 transactions and is expanded
2. Loan 456778-90: Has 3 transactions and is collapsed
3. “Change of banking information” and “Direct debit consent” are stand alone transaction

Note that stand alone transactions are displayed only after business case aggregations.

Show submitted transactions and document options

These options are related with data model option which is not yet released.

Popup

Enter title and texts (or HTML markup). The popup will be displayed after each successful login. In case you are using HTML markup make sure to test the result on different browsers.

Order of appearance

Note that aggregated transactions appear prior to standalone transactions

Additional control on looks

Template configuration offers the option to control the icon and the text of the button that opens up a transaction.

Make sure to select a proper icon and a “call to action” text

Client forms security

We are investing great deal of efforts protecting your and your clients data. For some of the methods we are providing the coverage. others require your attention. Following is a list of protections we have for client forms

Rate limit

This feature is builtin and is not optional. Rate limit prevents a client from posting too many requests for access in a given time window. The conditions of lock and release can be modified from time to time o our discretion.

Captcha

This feature is builtin and is not optional. Google captcha to prevent brute force

Password

This is a preliminary condition to access client forms. We advise to use passwords that cannot be mined such as sequence numbers. Instead make sure that the password include checksum/parity and it needs to be captured as part of the password.

OTP

OTP option is at your discretion and we encourage to make use of it.

Auto logout on idle

On idle (No use of client forms view) client is automatically logged out after 5 minutes

Auto logout if no transactions left on view

When completing a transaction client is be redirected to main client form view. If there are no transaction he will be automatically logged out after 1 minute

Poplast option

When appending ?poplast=true parameter to client forms it will automatically open a form in condition that there is only one transaction in view. Note that transaction will be displayed after authentications and regardless if there is a popup message configured.

Accessibility guideline

As in any other interface builder, we are making our best efforts to bring you all the goodies for collecting data and create amazing interface for your clients that reflect your brands. However this also come with a responsibility on your side. Although we are try to protect you in whatever way we possibly can to avoid accessibility errors, there are couple of ground rules to pay attention to.

Contrasts

Make sure that colors setting has sufficient contrasts. A button with pale background and pale text is not accessible. same goes to background image. make sure to incorporate background and colors sets that has contrast. How much contrast? check out this tester.

Messages and text

Make sure your messages, errors and instructions are clear and not implied. for example “Open” is better than “Transaction” as a text on a button to open new transaction.

This page described how to move a process with all of its related elements into another project on the same environment.

We will have to download/export every element separately in order to do so.

(BPMN processes, templates and also Dictionaries and Tables – if we are using them on our templates)

Follow the bellow steps:

1.Go to all the elements that are used on your process (BPMN processes, templates, Dictionaries and Tables) and download each one of them using the download or the export option.

On a BPMN process, use this button for download:

On a template, use this button for download:

On a Dictionary, click on the arrow next to the export button, and than ‘Export JSON’:

On a table, use this export button:

2. After you are sure that you have all the files related to you process saved on the side, delete from your current project all the data you want to move. (You can’t have identical processes/templates on the same environment)

3. Open the wanted project on the app.

4. Upload the data to the wanted project on this specific order (for remaining current connections):
-Dictionaries and Tables
-Templates
-BPMN processes

5. Connect integrations if needed.

6. Run the all process for making sure its working as expected.

Over the past mobths we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed

Release rollout schedule

• Pre production [preprod.cellosign.com]: xx
• Production [app.cellosign.com]: yy

Security

Allowed browsers

We have updated our blacklisted browsers.

Rate limit

This new addition is builtin, none optional and controlled exclusively by Cellosign staff. In end-client views this feature limit a client to post too many requests for access in a given time window. The conditions of lock and release can be modified from time to time to our discretion.

Cellosign views that includes rate limit are:

1. Client forms (new addition shipped with this release)
2. OTP and Challenge with Client session

Javascript limitation

Due to security concerns we are reducing our support to Javascript extension in templates. Please make sure that your templates does not contain javascript code. If it does, find configuration alternatives in Cellosign or seek our support team assistance.

Upload file size limits

Forms already include builtin limitations to upload files. Be advises that with this release we have also applied 5Mb limit when:

1. Posting file(s) through API
2. Configuring template
3. Creating Adhoc session

Heads-up for using iframe

Over the past year browser providers were and still consistently preventing and deprecating usage of iframes. Technology wise the prevention is about blocking cookies and outbound communications from the guest. Eventually, it is widely accepted, that iframe technology will be deprecated all together sooner or later.

Although Cellosign allows to deploy views in iframes, we encourage you to adapt other methods.

Template changes

Signature field button text

Added option to change default text for signature button

Default values for select field

Added preference to pick default option for select field

Lock template

Until this release a template could be edited and changes are reflected on live sessions. With this new release we are promoting template lock per session for which a session will also hold the template properties at the time a session is initiated, which eventually result that changes in templates will have no impact on forms that have sent to clients. No clients will automatically work like so and by the end of Q1 2025 we shall enforce this change.

Font David Removed

Font David deprecated from Template configuration for the reason that it has issues with mixed char-sets and special characters, such as “@”. Be advised to replace template to other font face in case you are using it.

Autodate field

Added formats to auto date and now include breakdowns for day, month and year.

Zip and password

Depreciation notice. Zipping files in archive email has been depreciated.

Download PDF for print

We have added a new feature for client toolbar to create and download a PDF out of the data that is incorporated in a form without submitting the form.

Changes in connector integrations

Added functionality to modify integrations inline when moving template from one environment to another.

Read only

Added a read only configuration for session that disable the ability to submit a form.

Integrations

Filter archive web hook data

Added ability to exclude data and paragraph filed types in archive web hook.

Group data

Added “group_data” array to archive api for future use.

Dashboards

Expiration widget

Updated search expiry, Added 3 days and 1 week options.

Applications

BDI

Builtin BDI interface.

Electronic 101 form (טופס 101)

We have renewed our 101 certification. Please consult with your reference regards fully compliant 101 template.

All new client forms application

Refactor of client forms application. It includes many new configuration and UI settings to match your brand looks

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: xx
• Production [app.cellosign.com]: yy

New features & enhancements

Heads-up for using iframe

Over the past year browser providers were and still consistently preventing and deprecating usage of iframes. Technology wise the prevention is about blocking cookies and outbound communications from the guest. Eventually, it is widely accepted, that iframe technology will be deprecated all together sooner or later.

Although Cellosign allows to deploy views in iframes, we encourage you to adapt other methods. Sooner the better.

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: released
• Production will be released at 28/07/24

New features & enhancements

Attachments to client email

With Cellosign we have two types of recipients that may receive an email at the end of a business process: agent and client. At the end of a business process a recipient of type agent will get on email that includes: signed PDF, raw data (Typically json file), attachments that were collected during the process. Client receives only the signed PDF.

With this change. A file upload and image upload controls include option to attach the file to client email as well.

Search in list of values field

Typically a remote search in LOV fields should include some flexibility to avoid cases where spell is wrong or an hyphen is in between words. This is called a “Fuzzy” search. Cellosign search works this way and it’s good for most cases, in other cases it doesn’t. Mostly it doesn’t work well when the words are long 7 letters or more. For that purpose we have added option for select type. The default one is “Fuzzy” as it is today and the new option is “Strict”. The values Cellosign will look for are only ones which were typed.

Fort more information see List of values control.

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: released
• Production will be released at 19/06/24

New features & enhancements

Email validation

On previous releases, Cellosign validated email extensions. With this release email validation is conformed to RFC 5322 standard which is basically composed of a string given that it includes “@” and a”.” in specific places. With this change there is no limitations on domain or sub domains.

Company seal from image

Cellosign includes a signature feature that embeds company details: name, company ID altogether with a graphic signature. With this release we added a new feature for which a client will be required to upload an image that will be used as a background for graphic signature.

Email buttons recolored

With this release button colors in emails has been modified from yellow to grey that conforms with contrast requirements for accessibility.

Get sessions API enhancement

Get sessions API enhanced to include assignee filter, that is the user whom created a session or was assigned to (“puh client”). See API Documentation for further details

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: released
• Production will be announced separately

New features & enhancements

Company Registrar API

We are happy to announce that we have added an interface to Israeli companies registrar (“רשם החברות”). The interface allow you to validate that a company number actually exists. In addition the interface enable to fetch the following company details: name (Hebrew and English) and company status.

This feature is available on cloud installation. Please contact our support to check your eligibility for this feature

SMTP Authentication

Added new option to SMTP integration that requires no authentication. Please read the following documentation prior to implementation

Security enhancement: blocked login pages on iframe

In order to protect your data and your users from Click jacking and phishing vulnerabilities we have disabled the ability to carry out user login from an iframe. This security enhancement added to all pages that requires your users authentication: Login to main application, Login to Agent application and Login Tasks application.

Client authentication to open invitations, client forms and OTP remain unchanged.

Form control dependencies split

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: 17/08/23
• Production [app.cellosign.com]: 23/08/23

New features & enhancements

Default date and date time to date control

Currently date control accepts a fixed date as a default value. With this release we have added the option to configure Date control to accept the date when transaction is generated. To configure current date apply “$now” to default value.

Salesforce formula editor

We have added into Salesforce “Percent” data type and now it can be edited and converted prior to propagation into form.

Enhancements to paragraph control

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: 26/6/23
• Production [app.cellosign.com]: 06/07/23

New features & enhancements

Table footer

We have added to Table control ability to configure footer row to include textual values and SUM function that SUM column values. See here for more details

SMTP/SASL XAUTH2 Autentication

We have added SASL XAUTH2 authentication for SMTP integrations. SASL protocol is a secured way to Authenticate SMTP requests with services such as GMAIL, Office exchange etc. See here for more details

Validation errors

Ordered lists font

We have made changes to ordered lists to include formatting of bullet items. See here for more details

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

Release rollout schedule

• Pre production [preprod.cellosign.com]: 18/5/23
• Production [app.cellosign.com]: 01/06/23

New features & enhancements

Connectors filters

We have enhanced our connector functionality greatly to query and sort data from remote source based on complex conditions. Conditions can now meet any complexity of “AND/OR”, querying based on field types and compared with either fixed values or values already populated in a form. This option improves connector flexibility and to simplify connectors configuration.

More details in Integrating a connector.

Connector fields mapping

We have enhanced our data mapping for filling forms automatically. On top of building a formula for converting native datasets, we have added the ability to CONCATENATE values and into one string and also the ability to repeat those as many as records matches the query. For instance this feature will enable you configure a result that include first, last name and DOB for all account contacts. More details in Integrating a connector.

Client forms

Transaction board

We have added to Transaction board the new features to access Workflow and BPM processes:

1. Click on “See Workflow” to open Workflow or BPM diagram.
2. Click on search icon to filter list based on workflow/BPM unique key to get all related sessions
3. Click on Copy icon to copy the aggregating key to your clipboard

Bug fixes

1. On earlier releases search items on multiple selections in PDF documents was not enabled. Please see notes on configurations in List of values.
2. Fixed issue with a display of conditions in a control group after modifying control ID.

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

New features & enhancements

Enhancements to paragraph control

1. Added option for nested numbering, i.e. 1, 1.1, 1.2 etc.. with configuration
2. Added option to display text in columns (similar to news paper) using configuration

Note: this features requires activation. Submit ticket to our support to apply.

Enhancements to table control

Table control was added with:

1. Design options to control Font size and cell padding, Alignment
2. Automatically add prefix and suffix to cells
3. Improved responsive by automatically collapse rows in case table is wider then view

Connector data mapping enhancements

We have added new features for mapping of data objects from remote sources:

1. Conversion of numbers
2. Representation and format to numbers
3. Representation and format to dates

For more details see Data mapping and conversions.

Connector description

Descriptions for connectors have been improved to provide better visibility on the connector content.

1. Heading texts improved to include reference to objects in remote data source
2. Ability to add description on connector level

Data tables enhancements

1. Improved usage with format text switcher to display or hide text styling for clear view on content
2. Row editor is fixed for easier navigation
3. On paragraph connectors we added the ability to override border display. See more details in data tables

Faster SEAL document

SEAL API is used to create sealed (closed) PF documents without user intervention. We have improved this feature to response faster by 50%. This features requires activation. Submit ticket to our support to apply.

Salesforce package enhancements

We have added new methods to Salesforce package:

1. SEAL: Create signed documents
2. Delete: Revoke transaction

See more details in Salesforce guide

Apply signatures at bottom of PDF pages

Normally when using HTML template to produce signed PDF documents, signatures like any other form element are applied per relative position on the PDF result. With this release we have added the ability to create Signature controls that can be applied to the bottom of the signed PDF. See more details in Signature documentation.

This features requires activation. Submit ticket to our support to apply.

Bug fixes

1. On earlier releases landscape documents could be uploaded for which the result could have contain errors in signed documents. To prevent that, we have added an error response when landscape PDF document is uploaded with an API or agent application

Announcements

Cloud migration

As previously announced, an upgrade to our cloud infrastructure (migrate to Azure) in production is planned at 23/4.

As a result of the upgrade our IP addresses will also be changed.

This is a list of current production IP and new infrastructure IPs:

Please make sure to list the new IPs before the planned migration date 24/03/2023 to prevent service blockage.

As soon as the IP addresses have been whitewashed, please submit a service request to set up a joint inspection date.

Make sure the new IP addresses are enabled before the test. We recommend for a joint test as soon as possible.

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

New features & enhancements

Temporary account lock

Prior to this change, five consecutive failed logins were locking a user account. Only user with project admin or above can release the account. While this is remain the default option, we have also added the option for a temporary lock.

With this option, you will be able to setup a lock policy:

1. Lock policy: Lock account after X consecutive failed logins. [That is the default policy]
2. Temporary lock to prevent login for X minutes

temporary lock based on two parameter:

1. After how many consecutive failed logins the temporary lock kicks in
2. For how long (in minutes) the account will be locked

What‘s next?

We advise you to review this change together with your organization security officer and choose appropriate lock policy for you.

Adhoc form permissions

Prior to this change, when a temporary session is created, permission defaults are applied to each field. In order to prevent errors in permissions, we have removed default permissions and leave it to the agent to define explicit permissions to each field.

When field is added without permission a warning is displayed for adding permissions “Agent allowed” or “Client allowed”.

Accessibility enhancements

Over the last minor releases 4.3.1 to 4.3.5 we have released various changes and bug fixes for accessibility.

Initial focus

Prior to the following change the initial focus was applied to START button. With this modification, the focus has been moved to Hamburger icon on the Top-Left corner in left-to-right forms and Top-right corner in righ-to-left forms.

Color switcher

We have removed “Normal” color toggler from accessibility menu. With this change when “Monochrome” is activated form colors will be mokdified

Preview texts

We have added texts to screen reader in order to describe the PDF document applied to preview.

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

New features & enhancements

Salesforce integration

With this release we are very happy to introduce you with Salesforce integration to Cellosign. This feature opens up a world of new possibilities were the entire digital journey can be implementation with no APIs on the client can be carried out with APIs integration. Simply couple Cellosign and Salesforce, configure what data is connected for two ways integration.

For more information please visit Connectors and Salesforce documentation pages.

Geo location

Added ability for Geo coding client location that includes a visible map, inserting an address or location manually or automatically with Client GPS or IP when applicable. Read more

Passwords vulnerability check

In addition to the regular passwords complexities, two-factor authentication we have applied additional security layer that check passwords renewals and passwords for new users with an internal vulnerable passwords database. When a user applying new password, password will first match the complexity and length according to your organization requirements and than match the password with passwords known to be vulnerable.

Underline placeholder for empty fields

New design option added to entry fields. Checking this option will include an underline where input value is empty. This is specially helpful when you need the final PDF result will show an empty value. To set this option:

1. Click on template field
2. Click on Design tab
3. Check “Apply underline in result PDF when field has no value”

Note: This option is available for field of type: text, number, select, textarea, paragraph, date, pad, date, email, phone only.

Email on Archive errors

On previous version we have added a feature that post Email to configured recipients notifying them regards failed archive. Within this release we have incorporated meta data file that includes identical content and structure to data which was pushed through the API.

Note: We advise you not to use the meta data from email to your application from number of reasons:

1. Email servers are typically rendering files content, encoding etc
2. We can’t always be sure regards the failure reason so you may consider the meta data file as unsafe

As a result of the notes above we will not be able to support cases where meta data from email is failed to upload into your APIs.

Fixes

1. #DEV-1052: Archive error notification in email are now posted with updated archive structure
2. #BUG-1173: Signature padding on HTML to PDF when additional field on same column is now fixed
3. #BUG-1351: Redirect URL at the end of session fail to redirect
4. #BUG-1477: Client form screen fail to render data fields but instead display fields id

Over the past weeks we have been working on improvements to Cellosign platform. In this post you can see a list of what has been changed, updated, and/or what bugs have been fixed.

New features & enhancements

Updated Content Security Policy (CSP)

We have updated our security policy to prevent access from forms to unknown web resources.

Why is that important?

We are considering that any form that posted to remote client contain sensitive and valuable information (health, financials etc). By adding external resources to forms, such as image backgrounds from external URLs or PIXEL implementation such as google-tag-manager, the form is exposed to external Attack that prevent us from keeping you and your clients data safe.

What has been carried out on our side in that respective?

We have scanned your templates, checked and validated external resources and explicitly added resources that are secured to our CSP whitelist.

What should be done on your side?

1. Background images to forms using URLs must be avoided. Use base64 strings for background images. This is how to do it.
2. Case you require PIXEL support, please submit a ticket our support team. Add your PIXEL URLs to ticket for inspection.

Software upgrades

Software packages that are effecting remote client forms and agent application (co-browse) has been updated to latest release.

We have carried out comprehensive testing to make sure applications are intact. However, in case your templates includes Custom CSS and Javascript we advise to carry out tests to make sure your custom software works as expected. To see custom code, login to application console. For each template, open “Settings” and on the right pane click “Javascript” and “Stylesheet”, case the left pane is not empty, please double check your template at work.

Public page enhancement

As you probably aware, template and BPM processes can be launched using a public template. Typically public pages require an input to initiate a process. Up to this release, public page is presenting page with required input. With this upcoming release input requirements can be added to URL in a querystring format.

For example:

Open the this url. https://preprod.cellosign.com/public/02774a7724ae4211a903043bd4171c96. It display a page where you will be required to enter name, mail and phone number.

Alternatively, you can open this URL. All the required parameters are injected using a query string and the form will be opened instantly. Be advises that although this option is available use it wisely. Public pages with client data should be secured and posted to clients directly. DO NOT leave public URLs with client data out for grabs.

Apply user context to form

With this release you will be able to apply Agent context into form automatically. This can be helpful if you require Agent name,phone or email to appear on form automatically with no user intervention.

To do so, you will need to apply context as default values to field in a form. For example, you would like an agent email to appear on form automatically.

1. Add email field to form
2. On field settings add “$initiator.email” to default value.
3. Once new session is created the agent email will be displayed automatically

Note: It is advised to use this option when it’s required. Do not expose your employees data when not needed.

The following contexts are available for your disposal:

Added “Table” element

Due to multiple requests, we have added “Table” element to our form builder.

For more details see reference to table in this guide.

Data tables enhancements

We have added new feature to data tables, that is the ability for data table cell to include input elements as well as static data.

When this is useful?

Let’s assume that you have an “Insurance proposal” that needs to be implemented. Your proposal might end up with hundreds or thousands of texts and input elements that are varied as our client engaging with the form, for instance, when “Second driver” is required, we want to show legal notice and inquire regards the potential driver(s).

One way of doing this is implement the entire data set within the form as it’s normally being done, this can be tedious when there are lots of form elements…

Another way is to implement it with data tables. With this enhancement, data table cells can include input elements as well as static data, so when client selects “Second driver” in the form, the entire set of texts and input will be displayed automatically, without the need to configure them in the form itself.

More details in data tables reference.