Formpipe uses cookies to improve how the website works for you as a visitor. To change your settings or for more information about cookies, click on 'Settings'.
Formpipe uses cookies to improve how the website works for you as a visitor. Here you can change and see information about what cookies are used. Turn on and off categories and save your choice. To learn more click 'Cookie policy'.
These cookies are essential for the website to operate correctly and cannot be disabled without ruining the usability of the website. We delete these cookies when you leave the website, where possible.
Name | Retention period | Information about the cookie | Disclosure of information to third party |
ASP.NET_SessionId | Used to maintain an anonymised user session by the server. | 1 session | No. |
cookie-consent-settings | Used to determine if the user has accepted the cookie consent, contains consent choises | 30 days | No. |
lidc | To promote data center selection | 1 day | Yes, LinkedIn |
li_mc | Used as a temporary cache to avoid database lookups for a member's consent for use of non-essential cookies and used for having consent information on the client side to enforce consent on the client side | 2 years | Yes, LinkedIn |
BIGipServer~EPWS~EPWSWEB103_HTTP_Pool | Determine pool | 1 session | Yes, EPiServer |
These cookies are used to track our visitors across our website. They can be used to build up a profile of search and/or browsing history for every visitor, or to better understand how the user uses the website so that we can improve it. Identifiable or unique data may be collected. Anonymized data may be shared with third parties.
Name | Information about the cookie | Retention period | Disclosure of information to third party |
_fbp | Used by Facebook | 90 days | Yes, Facebook |
AnalyticsSyncHistory | Used by LinkedIn | 30 days | Yes, LinkedIn |
bcookie | browser identification | 2 years | Yes, LinkedIn |
lang | Language preference | 1 session | Yes, LinkedIn |
li_gc | Used to store guests' consent to the use of cookies for non-essential purposes | 2 Years | Yes, linkedIn |
lms_analytics | Used to identify LinkedIn Members in the Designated Countries for analytics | 30 days | Yes, LinkedIn |
_guid | Used to identify a LinkedIn Member for advertising through Google Ads | 30 days | Yes, LinkedIn |
_ga | Used by Google Analytics to identify a visit. | 2 years | Yes, Google gains access to the information collected by the cookie. |
_gid | Used by Google Analytics to identify a visit. | 24 hours | Yes, Google gains access to the information collected by the cookie. |
_gat_gtag_[Property-ID] | Used by Google Analytics to identify if a visitor (web browser) is new or recurrent. | 1 minute | Yes, Google gains access to the information collected by the cookie. |
These cookies are used by third party to track and collect data to be used in advertisment. They can be used to build up a search and/or browsing history for every visitor. Identifiable or unique data may be collected.
Name | Information about the cookie | Retention period | Disclosure of information to third party |
ajn | Used by adnxs for marketing | 90 days | Yes, adnxs |
uuid2 | Used by adnxs for marketing | 90 days | Yes, adnxs |
IDE | Used by Google doubelclick | 2 years | Yes, doubleclick |
_gcl_au | Google adsense | 30 days | Yes, Google |
msd365mkttr | Dynamics marketing | 2 years | Yes, Microsoft |
NID | Google ads optimization | 6 months | Yes, Google |
__Secure-3PAPISID | Builds a profile of website visitor interests | 2 years | Yes, Google |
__Secure-3PAPISID | Builds a profile of website visitor interests | 2 years | Yes, Google |
__Secure-3PAPISID | Builds a profile of website visitor interests | 1 year | Yes, Google |
UserMatchHistory | Sync LinkedIn Ads ID | 30 days | Yes, LinkedIn |
lms_ads | Used to identify LinkedIn Members off LinkedIn in the Designated Countries for advertising | 30 days | Yes, LinkedIn |
Support
Whether you're looking for some
assistance or further information
regarding your solution, we're here
to help. Yes, take me there!
Sweden
Headquarters, Stockholm
Formpipe Software AB
Sveavägen 168, Stockholm
Box 231 31, 104 35 Stockholm
SE – Sverige
Tel: +46 8 555 290 60
Email
Linköping
Gasverksgränd 2, 582 22 Linköping
Tel: +46 8 500 072 25
Email
Västerås
Metallverksgatan 6, 721 30 Västerås
Örebro
Engelbrektsgatan 6, 702 12 Örebro
Denmark
Lautrupvang 1
2750 Ballerup
Tel: +45 3325 6555
Email
Germany
Formpipe Lasernet GmbH
THE SQUAIRE 12
Am Flughafen
60549 Frankfurt am Main
Email
UK, Cambridge
First Floor, Block A, Harston Mill,
Cambridge – CB22 7GG
Tel: +44 1223 872747
Email
UK, Nottingham
Unit 1, Isaac Newton Centre
Nottingham Science Park
Nottingham – NG7 2RH
Tel: +44 115 924 8475
Email
USA
Formpipe, inc.
1200 US Highway 22 E Suite 2000
Bridgewater, NJ 08807
Tel : +1 908 200 7937
Email
Compliance is a constant battle for business leaders. Even small infractions can be damaging between the fines and reputational harm. In previous articles, we looked at how UI/UX can enable more effective audit trials, but there’s another side to the story.
The right Electronic Document Management Systems (EDMSs) should make it easyfor employees to manage files. However, senior leaders also need to establish document retention guidelines for employees to follow, and use an EDMS to maintain them effectively.
To find out more, we sat down with James Baxter, one of Formpipe’s Software Developers working on Autoform DM. In this interview, he discussed why document retention is so important to ensure compliance, what document retention best practices look like, and some of the recent document retention developments within Autoform DM.
So, I currently work on the development team. However, I have held various other roles in the past, including departmental management and solution architecture.
Altogether, this means I’ve been at Formpipe for something like 5 years. These days, I mostly focus on application development and build automation within Autoform DM.
Well, document retention is crucial for businesses for several reasons, including legal, financial, and operational considerations.
Like most businesses, our customers place great importance on complying with legal requirements. Depending on the industry and country, they may be obligated to retain certain types of documents and for a specific period, too. Obviously, failure to meet these requirements can result in legal and financial penalties - not to mention harm to the company's reputation!
There are also lower-stakes or more mundane areas, like simply running your business effectively. Different client contracts, SOWs, invoices or customer data can quickly become difficult to manage without the right software. So, having document retention guidelines specifying where and for how long you store documents becomes essential.
The length of time an organisation should retain a document or record depends on a few different factors. These include specific document retention laws (GDPR being one), the type of document, the industry, and the organisation's internal policies.
Regardless, when a document is no longer required, it should be securely removed. I think this is where some organisations go wrong: making this process more difficult than it should be. The process and steps to remove a document from your database should be easy to understand. That’s why things like the software’s UI/IX are critical.
Fundamentally, GDPR requires organisations to limit the amount of personal data they collect and retain. The right document retention policy can help organisations reduce the amount of personal data they process and store.
This means they only retain data that is necessary for legitimate business purposes since everything else isn’t included in the first place. From here, like I said above, anything that then expires can be properly removed.
In the EU, non-compliance with the GDPR can result in some costly fines. These can range from 2-4% of a company's global annual revenue or €10 million to €20 million (whichever is higher).
A data breach or violation of GDPR can also damage a company's reputation, which can result in a loss of customers, revenue, and investor confidence. Companies that take data privacy seriously and have robust data protection measures in place are likely to be more trusted by customers and investors.
Of course, the cost of non-compliance with other document retention laws depends on where you operate. We have customers in the US and APAC region, so we follow the strictest global standards to ensure they’re always protected.
In addition to the impact on document retention strategies and compliance mentioned earlier, remote access to files can increase the risk of non-compliance being discovered and litigated. This is because files and company data can be exposed to threat actors without the right access tools in place.
The trick is to find a cloud-native EDMS so you can benefit from the added security features that cloud computing offers. Ideally, you’d want to run everything in the same cloud architecture so you don’t have to worry about extra integrations, but a lot of SaaS software is cloud-agnostic, so there are plenty of options depending on your current and future IT environment.
We’ve introduced a new native capability to DM that enables it to recognise the expected lifetime of a document. This means that document retention periods can be applied without requiring any external components, which simplifies the entire process and reduces the risk of non-compliance.
We’ve also prioritised the user experience by allowing them to mark entire categories of documents as ‘expiring’ when a document reaches a certain age, as well as tagging specific documents with an expiration date. This means that your document retention policy can be automatically executed according to your guidelines, giving you less to worry about.
Yes and no. The move is part of a larger and ongoing strategy to enhance the "out of the box" capabilities of the software, whilst maintaining simplicity and promoting resilience.
We’re always listening to what our customers are saying and trying to think of ways to meet and exceed their needs, so it’s a combination of both, really.
The system can be configured to prevent ad-hoc deletion. This means that it ensures documents can only be removed in accordance with pre-arranged retention (or deletion) rules. So, more documents you expect to be deleted are, and files you expect to stay around do so automatically.
Like always, we look at our customers’ needs, how they fit within existing regulations and where there are or might be gaps in the future. Our aim was to design an intuitive yet powerful feature set that caters to a wide range of business scenarios, without surprising users with unexpected system functionality.
Additionally, we want to ensure the process is technically fast and robust, given the high volumes of data that are processed through these systems. We’re confident that what we’ve developed satisfies all these areas and users can easily create document retention guidelines to rely on.
I'm particularly proud of the automated CI/CD process we have in place. The update allows developers to easily push them to a central location. From here, they’re then run through a battery of automated tests before being deployed to a dynamically provisioning instance of the software for peer review.
Yes, the wait is finally over! We are excited to announce that the release is now available. Without giving away too much, we've implemented some fantastic changes that we believe our customers will love.
Looking for a digital archiving solution that offers secure file access, first-class user experience and seamless integration? Autoform DM is easy-to-use and is compliant with ISO 27001, with a customisable audit trail. Find out more here or book a demo below.