You do not have permission to edit this page, for the following reasons:

This IP address has been blocked from editing Wikipedia.
This does not affect your ability to read Wikipedia pages.
Most people who see this message have done nothing wrong. Some kinds of blocks restrict editing from specific service providers or telecom companies in response to recent abuse or vandalism, and can sometimes affect other users who are unrelated to that abuse. Review the information below for assistance if you do not believe that you have done anything wrong.

The IP address or range 44.199.0.0/16 has been blocked (disabled) by ‪Blablubbs‬ for the following reason(s):

The IP address that you are currently using has been blocked because it is believed to be a web host provider or colocation provider. To prevent abuse, web hosts and colocation providers may be blocked from editing Wikipedia.
You will not be able to edit Wikipedia using a web host or colocation provider because it hides your IP address, much like a proxy or VPN.
We recommend that you attempt to use another connection to edit. For example, if you use a proxy or VPN to connect to the internet, turn it off when editing Wikipedia. If you edit using a mobile connection, try using a Wi-Fi connection, and vice versa. If you are using a corporate internet connection, switch to a different Wi-Fi network. If you have a Wikipedia account, please log in.
If you do not have any other way to edit Wikipedia, you will need to request an IP block exemption.

How to appeal if you are confident that your connection does not use a colocation provider's IP address:
If you are confident that you are not using a web host, you may appeal this block by adding the following text on your talk page: ((unblock|reason=Caught by a colocation web host block but this host or IP is not a web host. My IP address is _______. Place any further information here. ~~~~)). You must fill in the blank with your IP address for this block to be investigated. Your IP address can be determined here. Alternatively, if you wish to keep your IP address private you can use the unblock ticket request system. There are several reasons you might be editing using the IP address of a web host or colocation provider (such as if you are using VPN software or a business network); please use this method of appeal only if you think your IP address is in fact not a web host or colocation provider.

Administrators: The IP block exemption user right should only be applied to allow users to edit using web host in exceptional circumstances, and requests should usually be directed to the functionaries team via email. If you intend to give the IPBE user right, a CheckUser needs to take a look at the account. This can be requested most easily at SPI Quick Checkuser Requests. Unblocking an IP or IP range with this template is highly discouraged without at least contacting the blocking administrator.

This block will expire on 12:56, 12 May 2024.

Even when blocked, you will usually still be able to edit your user talk page, as well as email administrators and other editors.

For information on how to proceed, please read the FAQ for blocked users and the guideline on block appeals. The guide to appealing blocks may also be helpful.

Other useful links: Blocking policy · Help:I have been blocked
Your IP address is in a range that has been blocked on all Wikimedia Foundation wikis. The block was made by ‪AntiCompositeNumber‬. The reason given is Open proxy/Webhost: Visit the FAQ if you are affected .
- Start of block: 13:55, 18 August 2022
- Expiry of block: 13:55, 18 May 2025
Your current IP address is 44.199.189.47. The blocked range is 44.199.0.0/16. Please include all above details in any queries you make. If you believe you were blocked by mistake, you can find additional information and instructions in the No open proxies global policy. Otherwise, to discuss the block please post a request for review on Meta-Wiki. You could also send an email to the stewards VRT queue at stewards@wikimedia.org including all above details.

You can view and copy the source of this page:

((More citations needed|date=September 2009))

'''Enterprise forms automation''' is a company-wide computer system or set of systems for managing, distributing, [[Document processing|completing, and processing]] paper-based forms, applications, surveys, contracts, and other documents. It plays a vital role in the concept of a [[paperless office]].

[[JetForm]] Corporation first used the term "enterprise forms automation" in the mid 1990s to describe their solution to automating paperwork. This process was later acquired by [[Adobe Systems]], and is now part of the [[Adobe LiveCycle]] suite of products. In 2004, Efficient Technology Inc, became the first company to apply this term to [[software as a service]].

Enterprise forms automation refers to the automation of paper-based processes that specifically rely on documents (forms, applications, etc.) that retain a paper-based look and experience, even if not printed out for interaction. To be considered an ‘enterprise forms automation’ solution, a system must meet [[enterprise software]] requirements, and specifically focus on automating paperwork and paper-based forms.

==Impact==
Organizations implement enterprise software solutions to automate major functions and large processes, as these areas offer the greatest cost savings compared to smaller projects. Enterprise-level implementations often cost over $100,000 and therefore take many months to produce cost savings. As such, organizations ignore automating smaller functions, due to the lack of immediate financial benefit or cost savings. As functions become more automated while software costs for enterprise systems drop in price, organizations begin automating lower-level functions to become more efficient. In addition, through the advent of standards like Adobe's PDF model and service models like Quik!, companies seek to automate the filling out of forms via enterprise forms automation solutions.

Automating forms also has a positive ‘green’ impact on the environment. To reduce waste and carbon emissions, companies seek ways to eliminate paper. An enterprise forms automation system can eliminate paper entirely, or significantly reduce how much paper a company uses—also reducing shipping costs, and printing and storage costs of paper forms. In addition, automating paper-based processes greatly speeds up the time it takes to perform transactions, which results in fewer errors, rejections, and revisions—and frees up time spent by users on manual labor.

== Implementation ==
=== DMS ===
Modern implementation of the paperless office concept has two main focuses: creating documents and managing documents. Since major systems have already displaced paper altogether (e.g., [[enterprise resource planning]], [[customer relationship management]], [[accounting software]], etc.), paper that remains in use is largely generated by processes that capture data, generate reports, and distribute communications. As software and computers have evolved, the first problem addressed has been management of existing and legacy documents through [[document management system]]s.

Document management and archiving systems do offer some form automation functions. Typically, the point at which document management systems start working with a document is when the document is scanned or sent into the system. Many document management systems can read documents via [[optical character recognition]] (OCR) and use that data within the document management system. While this technology is essential to a paperless office<ref>((cite journal |url=http://www.quikforms.com/WHITEPAPERAchievingThePaperlessOffice.pdf |title=Achieving The Paperless Office |last=Walker |first=Richard |authorlink=Richard D. Walker |journal=Efficient Technology Inc |date=2009-08-07 |access-date=2009-09-11 |archive-url=https://web.archive.org/web/20110715135834/http://www.quikforms.com/WHITEPAPERAchievingThePaperlessOffice.pdf |archive-date=2011-07-15 |url-status=dead ))</ref> it does not address the processes that generate paper in the first place.

The ultimate step towards eliminating paper is to change the way that documents are created. In 1993 Adobe Systems introduced the [[Portable Document Format]] (PDF) to facilitate the exchange of documents in a universal manner across most computer platforms. This format has laid the foundation for creating, transporting, working on, and archiving electronic documents—and in 2008 became an ISO standard.<ref>((cite web  | title = ISO 32000-1:2008  | publisher = International Organization For Standardization  | date = July 1, 2008  | url = http://www.iso.org/iso/catalogue_detail?csnumber=51502))</ref> In addition, the PDF model established a method for automating forms that can be pre-filled with existing data and manually entered on a PC screen—which can reduce or eliminate printed forms.

=== Implementation tools ===
A typical enterprise forms automation implementation typically combines:
* A library of electronic versions of paper-based documents (PDF format or comparable format)
* Data store of existing data or web pages that collect data to fill onto forms
* Software that pre-fills existing data from databases and data stores onto electronic forms
* Software that saves forms in process or partially completed
* Software that captures and translates electronic form data
* Workflow systems that manage interaction with forms and data
* Two-way messaging between forms and systems during submission and validation
* Barcode software that matches images of forms with electronic form data
* Digital signature solutions that capture signatures electronically

=== Implementation challenges ===
The primary challenge to using these technologies is resource planning and implementation costs. However, all necessary technologies have existed since at least 2000. Furthermore, the U.S. Congress signed the [[Electronic Signatures in Global and National Commerce Act]] (ESIGN Act) into law, which lets companies accept digital signatures as valid signatures. Even with the law in effect, companies have been slow to adopt such solutions due to the cost and skills required to design, build, and maintain them at reasonable cost.

A secondary challenge is integrating electronic forms into an existing process, whereby existing data stores can be accessed and supplied to and from the forms. While tools to assist with integration exist, most implementations require custom programming for specific forms and data sources.

Many of these challenges are addressed by middleware solutions, technology platforms, and services that tie the pieces together. Known as [[Enterprise Application Integration]] (“EAI”), developers of EAI solutions are continually introducing new cost-effective methods to take advantage of web-based and centrally-managed capabilities and leverage legacy systems.<ref>((cite book
  | last1 = Ruh
  | first1 = William A.
  | last2 = Maginnis
  | first2 = Francis X.
  | last3 = Brown
  | first3 = William
  | title = Enterprise application integration: a Wiley tech brief
  | publisher = John Wiley & Sons, Inc
  | year = 2001
  | pages = [https://archive.org/details/enterpriseapplic00ruhw/page/1 1–11]
  | isbn = 0-471-37641-8
  | url-access = registration
  | url = https://archive.org/details/enterpriseapplic00ruhw/page/1
  ))</ref> With each advancement in EAI technologies enterprise forms automation becomes easier to implement and manage.

== See also ==
*[[Document automation]]
*[[Form (document)]]

== References ==
((reflist))

((DEFAULTSORT:enterprise forms automation))
[[Category:Adobe Inc.]]
[[Category:Documents]]
[[Category:Office work]]
[[Category:Open formats]]
[[Category:Paper products]]
[[Category:Business software]]

Pages transcluded onto the current version of this page (help):

Enterprise forms automation (edit)
Template:Ambox (view source) (template editor protected)
Template:Cite book (view source) (protected)
Template:Cite journal (view source) (protected)
Template:Cite web (view source) (protected)
Template:Find sources mainspace (view source) (template editor protected)
Template:Main other (view source) (protected)
Template:More citations needed (view source) (template editor protected)
Template:Reflist (view source) (protected)
Template:Reflist/styles.css (view source) (protected)
Module:Arguments (view source) (protected)
Module:Category handler (view source) (protected)
Module:Category handler/blacklist (view source) (protected)
Module:Category handler/config (view source) (protected)
Module:Category handler/data (view source) (protected)
Module:Category handler/shared (view source) (protected)
Module:Check for unknown parameters (view source) (protected)
Module:Citation/CS1 (view source) (protected)
Module:Citation/CS1/COinS (view source) (protected)
Module:Citation/CS1/Configuration (view source) (protected)
Module:Citation/CS1/Date validation (view source) (protected)
Module:Citation/CS1/Identifiers (view source) (protected)
Module:Citation/CS1/Utilities (view source) (protected)
Module:Citation/CS1/Whitelist (view source) (protected)
Module:Citation/CS1/styles.css (view source) (protected)
Module:Find sources (view source) (template editor protected)
Module:Find sources/config (view source) (template editor protected)
Module:Find sources/links (view source) (template editor protected)
Module:Find sources/templates/Find sources mainspace (view source) (template editor protected)
Module:Message box (view source) (protected)
Module:Message box/ambox.css (view source) (protected)
Module:Message box/configuration (view source) (protected)
Module:Namespace detect/config (view source) (protected)
Module:Namespace detect/data (view source) (protected)
Module:Unsubst (view source) (protected)
Module:Yesno (view source) (protected)

Return to Enterprise forms automation.

Retrieved from "https://en.wikipedia.org/wiki/Enterprise_forms_automation"