November Update

Tagged with: , , , , ,

We have a big release coming up this Saturday, and there is a lot to talk about.

If you’re short on time, here is a tl;dr summary:

  • API Version 2 release with new documentation
    API Version 1 will be supported until the end of 2017.
  • Two new sizes of checkboxes and new design
    Checkboxes will be updated with two new sizes and a new design.
  • Highlighting of document during signing and new top bar
    For in-person signing, there will now be a highlighting pen available to use during the contract review process.
  • Ability to see requested attachments in Sign View
    It will be possible to see uploaded attachments in sign view before signing a document.
  • Small update to email layout
    Invitation and confirmation emails will get a layout update to make the custom message clearer.

Note that all features are always available using our API. To understand how to use all new (and current) features, read the API Documentation or use our API Explorer.

API Version 2 released with new documentation

We are now releasing the new version of our API.
Version 2 contains the following improvements:

  • A new naming structure for API endpoints
  • Changes to the JSON data structures
  • Changes to parameters and their names
  • More comprehensive documentation
  • Better error messages

All of the above will make our API more intuitive to use and a lot easier to debug.

New documentation can be found at

Checkboxes – New design and sizes

Our checkboxes are getting a makeover with a new design, and two additional sizes. The size is “small” by default and will stay the same on all existing documents. For a more mobile-friendly signing experience we are now adding “Medium” and “Large.”

Apart from adding two more sizes, the checkboxes are now in SVG so they look crisp on retina displays and we are also giving them more color so they “pop” more in the document. The color is set to your branding profile so that the Mandatory checkboxes will have the same color as the arrow (main color in branding) and the optional boxes will have the secondary color in your branding profile.

After signing, the checkboxes will be black and white in the signed document.

Checkboxes on a signed document

Highlighting of documents and a new “top bar.”

Our focus on digital retail continues with the addition of our latest premium feature: highlighting.

Since Scrive is used during the process when our customer signs up their customer, the review process of the contract during signing is essential for a great customer experience. We are therefore adding a “highlighting pen” as a tool to add clarification to certain key parts of the contract before signing.

Together with this release we are also adding a bar that will hold the zoom controls and the controls for highlighting. The bar will also tell you the document name and in which state you see it.

After the document has been signed, the highlighting will remain on the sealed PDF and the events created by highlighting will be stored in the evidence log of the signed document.

Evidence log of a signed document with highlighting

Initially, this feature will only be available for in-person signing, and the highlighting is done by the author of the document, regardless of who is in the signing process.

To get access to highlighting, please contact Scrive support.

See Requested Attachments in SignView from prior signatories

It will now be possible for all parties to see the uploaded attachment by a previous signatory before they sign.

For example, let’s say party 1 must submit a copy of their driving license, and you have set yourself as party 2. Before you sign, you might want to verify that “signatory 1” uploaded a picture of their driver’s license before you sign yourself.

As you can see in this picture, “John Doe” uploaded the attachment “ID Card” during the signing process and party two (Axel Talmet) can review it before signing.

Bye bye pixels! New crisp SVG arrows for retina displays and sharper documents

We will update our beloved arrows to use SVG icons instead of PNGs to get rid of all the ugly pixels. Small but great update!

Not a pixel in sight!

We are also increasing the resolution of the documents in sign-view to make them even sharper.

Small update to email layout

To make your message clearer when inviting someone to sign over email, we have made a small but significant update to the email invitation and confirmation message.

The custom message is no longer in italic, and we will move the “instructions text” below the custom message and make it bold to be clearer.

You can add a custom message in the same place as before:

Add your custom message under “Other settings” in the design view of a document or a template.

That’s everything for this release.
The next upgrade is scheduled for the 3rd of December.


Scrive upgrade – Spain 15

Tagged with: ,


This Saturday we did an upgrade of the Scrive platform.

This release we named after the beautiful country Spain. In Spain, we have several customers using our platform to serve customers across the country for various use cases.

Before you read what the latest release includes I want to remind you of our Idea Portal. That is the place where anyone can submit and vote for new ideas that you would like to see added to Scrive. Since our release of the portal in September last year, we have shipped 12 ideas.

– Option to reject document without a reason

It is now possible to set up a workflow so that the signer may dismiss the document without having to write an essay about it.
This is valuable for anyone that may want to handle the reasons on their own inside their app or just want a smoother workflow.

To remove the reason for reject you set that under the signing page settings.

– Add event for mandatory checkbox on the verification page

We added an event on the verification page for when the mandatory checkbox has been checked.

Upcoming features

Here are some new things we are working on right now.

  • Close documents in the background when signing with Swedish BankID
  • Improved zooming of documents on small screen devices
  • New and improved API documentation for our upcoming release of our new API (v2). (API version 1 will be supported for a foreseeable future)
  • Public roadmap

We are back on the 28th of May for our next upgrade.

Let me know if you have any input or want to share your experience using Scrive.



Release Stockholm 6

Tagged with: , ,


We are back with the last upgrade for 2015.

For you coming in from the email send out, it´s not as huge as our last release.
A so-called human error snuck in and forgot to update the subject line.

This week we have named the release after the capital of Sweden, Stockholm.

Stockholm is the hometown of Scrive HQ and it is the most populous city in the Nordic region, with 917,297 people living in the municipality, approximately 1.6 million in the urban area, and 2.2 million in the metropolitan area. The city is spread across 14 islands on the coast in the southeast of Sweden at the mouth of Lake Mälaren, by the Stockholm archipelago and the Baltic Sea.

Some fun facts about Stockholm:

  • Kungens Kurva in Skärholmen is the home of the largest Ikea store in the world, covering a huge 56,301 square metres.
  • Stockholm is the home of the Ericsson Globe, which is the world’s largest spherical building.
  • On Stockholm’s shortest day the capital sees a mere six hours of sunlight, while on the longest day the sun is up for nearly 21 hours

Enough about Stockholm, here´s what´s new:

Main Features

Email issue resolved

Due to a change in the configuration of the Microsoft hosted email services incoming mail analysis system, delivery to their hosted email services was negatively affected.
We have now resolved this matter by implementing a new transactional email provider. This has resolved this specific email issue. Though, due to the nature of email, there will always be rare cases where there may be a failure to deliver.

If you wish to be certain of delivery you can always choose to send the invitation to sign via “Email and SMS”. Remember to always provide the country code of the phone number!

Introducing numbers and characters in name field

We now allow more characters in names to accommodate the need for cool company names.
You can now use numbers, dashes, ampersands and more.

Resolved mandatory attachment in combination with mass send outs

When we introduced mandatorys attachments in our last release one thing was a bit messed up.
Users doing multi sendouts in combination with a mandatory attachment were forced to sign each and every document as the author. If you send a few hundreds this, of course, takes a lot of time. This is now fixed, and you only need to sign once like before.

Next upgrade is planned for the 9th of January.

Merry Christmas and see you next year!

Release Wrocław 4

Tagged with: ,


On Saturday, we had another production upgrade.

This time, we named the release after the next European capital of culture, Wroclaw.
Wroclaw is the largest city in western Poland with a population of 634 487, also making it the fourth-largest city in Poland.

Wroclaw is also the home of Bartek, who takes care of all the nasty bugs that may appear and supports our fantastic service around the clock (almost).
Wroclaw is such a city of talent that it also houses Andrzej, who is our backend master with a fondness for optimizing database queries, which makes Scrive the fast service that it is today.

This weeks update is a minor one.

Search in “to-sign” and in the search box in the e-archive.
If you use quotes “” at the beginning and the end of the search string, you will only find contracts that contain text that matches that search string.

The next production update is on the 28th of November.

And it is a HUGE one. Stay tuned.



Release Edinburgh 3

Tagged with: , ,


We are coming to the end of October and what´s better than ending with a Scrive upgrade?

This release is named after the capital of Scotland, Edinburgh.

Edinburgh has long been known as a centre of education, particularly in the fields of medicine, Scottish law, literature, the sciences and engineering. The city is also the largest financial centre in the UK after London.

Jonathan, who is our versatile frontend/backend master, has Edinburgh as his home base when he is not working hard from his summer house in France.

Now, let´s get down to what´s new in this release.

Show owner of template

This is a request that many of our customers have been asking about and have also submitted to our idea portal.
You will now see who the owner of every shared template is. This is very useful if you and your colleagues are using the same template and a change needs to be made. Starting Saturday, you will know who to talk to in order to have it updated.

Speeding up the system

This time, we have put a lot of work into improving the speed and snappiness of Scrive. Our document searching and retrieval subsystems got a significant boost. Document access control is faster than it used to be. The more documents there are in the archive, the bigger impact this improvement has. For specific cases and larger archives the improvement in document, retrieval can be as much as 500%.

Work on APIv2 continues

Our new API version 2 is merged and work progress there in spades. Note that we are not releasing APIv2 at this point yet, as we know that “we should eat our own dog food first“. Starting now, we will migrate our own frontend to use the new API version, sorting out any issues that might come along. Stay tuned for news about the new API version.

Change behaviour of when the back button is shown

As you already may know, we are developing brand new apps for iOS and Android. To adapt our sign view to our new apps, we are introducing a method to hide the back button for in-app use.

That´s all for this week but already early next week we are back with a huge upgrade to our Salesforce application, stay tuned!

And of course, next production upgrade will be on the 14th of November.

Have a great weekend!


Release Gothenburg 2

Tagged with: ,

October 17th is coming up and that means it´s time for an update.

This time we named the release after the beautiful city of Gothenburg, on the fantastic west coast of Sweden. Gothenburg is the second largest city in Sweden and the fifth largest in the Nordics. It is called by the native Gothenburg´s “the front side of Sweden”.
We just happened to have one of them on our team, Ola, who is our frontend ninja, mastering React like no other.

Main upgrade

We have been working really hard on signature drawing modal canvas during the last couple of weeks.

We are now pleased to announce that starting Saturday, the signature drawing experience is completely rewritten in React. The code behind it is much faster and provides a smoother and better signing experience. Lines drawn as your signature follows your stylus or finger instantly.

Other improvements

Next production upgrade is on the 31st of October.



Release Warszawa 1

Tagged with: , ,


Tomorrow morning it’s time for yet another production update!

This sprint is named after the beautiful city of Warsaw, where our beloved lead developer Mariusz lives.

Main feature

You now have the possibility to change the authentication method to view the document after you have sent it for signing. It is connected to our previous release of Norwegian Bank ID.

This is done in the authors view of the document you want to change the authentication method to view on.

This new feature is very useful when you have a workflow where you, prior to sending the document, don’t know if the customer will be present or not. Now you only need to set up one template and change the workflow inside your own application.

Of course these new features are also available using our API.

You may choose between Swedish or Norwegian Bank ID.

It is also possible to change the authentication to sign in the authors view or via the API.

Here you may choose between authenticating the customer with Swedish or Norwegian Bank ID or Pin by SMS.

Minor fixes
  • The identify to view feature received a usability lift up and presents an improved identify view
  • Table of signatories now includes information about authorization status
  • Main signing page received a very important technological update. For our users it means improved signing experience and faster interaction. We used react components to achieve this result.
  • Signatory section is improved. Authors get to see more details about invited signatories when they create documents, signatories see a streamlined version of the same information.
Next production update will be on the 17th of October.

Don’t forget to submit your ideas in our new idea portal! 🙂

Have a great weekend!


Release Söderarm 0 (2015 09 19)

Tagged with: ,


We are back as always with a new production update tomorrow morning at 6 AM CET.

This release is named Söderarm 0 after the beautiful island in the outskirts of the Stockholm archipelago.

Main feature

  • Authenticate to view with Norwegian BankID

Welcome Norway! You can now use Norwegian BankID in Scrive.

Authenticate to view with Norwegian BankID
Norwegian BankID can be used as an authentication method with the “authenticate to view” feature.

When you set up a new process you can now select both Swedish and Norwegian BankID as the method to authenticate to view the document.

The recipient will not see a preview of the document as is the case when no authentication to view is set.

Here you need to authenticate with Norwegian BankID to see the document.

The author needs to provide the personal number if authentication to view with Norwegian or Swedish BankID is selected.
The view to authenticate is responsive (works well on devices with different screen sizes).

As soon as you have authenticated it works like a log in session. If you exit the document and open it again in another browser or on another device, you will need to authenticate again.

Only documents that can be signed will ask for authentication. If the document is signed already you can see the document without authentication.

Authentication to view can only be set for signing parties, not for viewers.

Two new events in the evidence log is added. We now track when someone enters the view to authenticate and when an authentication to view is done.

Minor fixes
  • Fix Evidence Log for “Change Authentication to Sign”
  • Fix copy for Evidence Log text
  • Add patch related to missing name returned from SE BankId on verification page
  • Rewrite sign section of signing page to React.
  • Remove signing page branding from to-start views
  • Last fixes to NO BankID + redirect to original domain on resolve
  • Birthday validation included when authenticating with Norwegian BankID
  • Update strings related to authentication to sign in to-start
  • Rewrite extra details section of signview into React
  • Properly handle comma and doublequote in company names

    Next production upgrade will be on the 3rd of October.