| Table of Contents | ||||
|---|---|---|---|---|
|
Provide a Management Summary of your strengths in managing your business, describing your company's background, current organization, market focus and geographic locations served. In addition, please explain how you will provide a value added advantage in service and technology.
...
For more information regarding ProcessMaker translations, please review the following link: http://wiki.processmaker.com/index.php/Translating_ProcessMaker
How do roles and groups integrate with standard directory services (LDAP, Active Directory, etc.)?
Response:
The Advanced LDAP/AD Sync feature allows ProcessMaker users to login by authenticating directly in a LDAP server or Microsoft Active Directory server. Unlike the LDAP community version that only imports users, it also enables synchronization with LDAP or Active Directory to update user information. From ProcessMaker Enterprise Edition version 3.0.1 on, this plugin has become a core feature acquired with the corresponding licence. For additional information and detailed description please refer to this link: http://wiki.processmaker.com/3.0/Advanced_LDAP
Is ProcessMaker self-contained or can it run inside a third party enterprise portal?
...
Skins/themes: new themes can be created by editing CSS files and uploading them to ProcessMaker. Each user can select the theme of their choice. In addition, a system administrator can setup the default theme. For details please refer to the link below:- http://wiki.processmaker.com/index.php/ProcessMaker_skins.
- Custom case list: the user inbox fields can be customized via an enterprise plugin in terms of fields that are shown or hidden. For details, please refer to the following link:
- http://wiki.processmaker.com/index.php/Cases_List_Builder.
What team collaboration features are supported?
...
An Input Document can be a hard copy (which has been printed out and stored in a filing cabinet), a digital file which is uploaded to the case, or both. From version 3.0.1.5, an Input Document can also be related to a file object in a DynaForm.
When configuring an Input Document ProcessMaker gives the option of setting up the maximum file size which is a required field which defines in KB or MB the maximum size of the file to be attached. If set to zero, then the file size is unlimited. Nevertheless, the limit is configured inside the php.ini file by the upload_max_size setting and that limit is shown in parenthesis when creating an Input Document. After filling the fields with the necessary information click on "Save".
...
Does the tool support notifications and how are those notifications configured?
Response:
Notifications can be used to keep users apprised of new cases in their Inbox and notify them at specified times while running cases. In ProcessMaker, all notifications are sent to users via email, which is why it is important to enter a valid email address for each user and properly configure ProcessMaker to connect to an email server so notifications can be sent out.
There are three types of notifications:
Task Notifications, which are sent when a user is designated to work on a task in a case.
Message Events, which are sent at specified timings based upon when tasks (or groups of tasks) begin in a case.
Trigger Messages, which are sent out using the PMFSendMessage() function.
Confirmation that the tool is able to support document management and / or integrate with other Document Management Platforms, providing detailed information about the tools capabilities including ‘out of the box’ support for SharePoint and IBM FileNet?
...
The result is a document management system with documents organized into folders and subfolders relative to data within a process. While all documents can be viewed from within an active case, users with the correct viewing permissions can navigate the repository, also view documents associated with cases and even download or upload documents to the repository. For additional information please refer to this link: http://www.processmaker.com/workflow-document-management
On the integration side, ProcessMaker can also store documents with third party DMS systems. The integration is done by ProcessMaker's API using REST (Representational State Transfer) to allow external scripts to remotely access and control ProcessMaker. It provides a large number of endpoints so that almost any action which can be done within the ProcessMaker interface can also be done remotely using REST. ProcessMaker functionality can be reimplemented in external web pages, desktop applications and remote scripts. Using ProcessMaker's REST API, custom interfaces can be created to access ProcessMaker.
...
One of the goals of good Business Process Management (BPM) is continuous process improvement, which can only be achieved through effective measuring and monitoring. For more information, please see this page: http://wiki.processmaker.com/index.php/2.0.X/Dashboards
ProcessMaker’s Advanced Dashboards give organizations the ability to monitor large amounts of data about their processes. Whether it’s measuring the productivity of departments by process, or identifying bottlenecks in processes, the advanced dashboards provide both simple information at a glance and detailed information in a drill-down feature. It allows regular users to check the state of the processes, cases, tasks, users and tables in interactive statistics and graphics in 4 user-friendly dashlets:
After clicking on “Participated” as shown above, users can see another graph below based on each process.
...
In addition for the need to see visually your KPI’s, we also understand the need for canned reports and making sense of data at a record set level. ProcessMaker has a reporting engine that enables business users to maintain visibility into the detailed data views of each individual application of the process, complete with filters, search, groupings, sums, and counts among other aggregate functions as well as the ability to export the data as a PDF file or Excel file for your preference.
What client platforms is your solution compatible with (web, mobile, etc.)?
Is standalone client software required or is it web-based?
If web-based, which web browsers are supported?
Does it support responsive UI?
Is mobile app available and on which operating systems?
If the functionality differs by client platform, please elaborate how
Response:
ProcessMaker works with any computer operating system as long as it has a supported web browser. In addition, ProcessMaker supports both Android and Apple/iOS mobile devices. Details, according to each specific question, are provided below:
- ProcessMaker is a 100% web based solution. This means that process design, execution and monitoring can be done via industry standard web browsers.
- ProcessMaker supports the current and previous major releases of Firefox, Google Chrome and Internet Explorer on a rolling basis. Each time a new version is released, we begin testing and then supporting that version and stop supporting the third most recent version. For additional on our supported browsers, please visit the following link: http://wiki.processmaker.com/index.php/Supported_Browsers.
- Yes. ProcessMaker Dynaforms are 100% responsive, and are based on industry standard HTML5. Therefore, users can work on their assigned tasks via a mobile device. In addition, ProcessMaker's look and feel can be customized by creating custom Skins or themes. For more information about responsive form design, please refer to the following link http://wiki.processmaker.com/3.0/HTML5_Responsive_DynaForm_Designer. For additional information regarding themes or skins, please refer to http://wiki.processmaker.com/3.0/Skins.
- Yes, The ProcessMaker Mobile App, available both for Android and iOS devices, allows end users to perform work on assigned cases as well as create new cases from a mobile device. In addition to standard forms usage, the Mobile App allows the user to enter data from mobile device sensors, including GPS positioning/Geolocation, QR codes and barcodes, signatures via touchscreen display, photos, audio recordings and video capture.
- From a process execution point of view, ProcessMaker's functionality does not depend on client platform. Process design, dashboards and KPI's, however, are only available via a desktop or laptop environments, using any of the supported browsers previously mentioned.
...
What operating systems can be used for hosting your solution?
Response:
Our solution is based on a LAMP/WAMP (Linux/Windows, Apache, MySQL and PHP stack). Our currently supported stacks include both Linux (CentOS) and Windows Operating Systems. For more details on our supported stacks, please refer to http://wiki.processmaker.com/index.php/Supported_Stacks.
What other software prerequisites are needed to ensure successful provisioning and operation of your solution? (e.g. database drivers, etc.)
Response:
ProcessMaker requires the following components in order for the software to be successfully installed:
Apache Web Server with the following components enabled
Deflate
Expires
Rewrite
Vhost_alias
Filter (only if using Apache 2.4)
PHP Runtime language
Fileinfo
MySQL
Xml
Mbstring
Mcrypt
Soap
LDAP
GD
Curl
CLI
MySQL
Strict mode disabled
If connecting to external databases, such as MSSQL or Oracle, additional drivers for the respective database engines would be required.
To see a full list of the required components pre installation, please visit this link: http://wiki.processmaker.com/3.0/ProcessMaker_Installation_Requirements.
Does your solution support horizontal or vertical scaling?
ProcessMaker can support high scalable and high available implementations. We typically only do this for very large ProcessMaker implementations (tens of thousands of users).
For small size implementations (hundreds or low thousands of users), we have server sizing guidelines that are available here: http://wiki.processmaker.com/index.php/ProcessMaker_Server_Sizing
For these types of large and scalable implementations, we have tested thoroughly in the AWS environment and would therefore recommend AWS for a highly scalable requirement, however, we have also tested in the MS Azure cloud and confirm that we are able to offer the same in the MS Azure cloud.
Here is an example diagram detailing a highly scalable and available ProcessMaker implementation in the AWS environment:
...
What are the known scaling bottlenecks (e.g. CPU/memory/IO, etc.)? What are the recommended hardware requirements?
Response:
ProcessMaker has no specific scaling bottlenecks. Actual bottlenecks experienced by our customers tend to depend on many factors, including processes' complexity, number of users, number of cases, among others.
As for hardware requirements, for personal use and/or testing use, ProcessMaker can be installed on any computer with a modern CPU and 2GB of RAM. For production use, the hardware requirements also vary based on the number of concurrent users, repository size and system configuration. Larger implementations may require some tuning to perform optimally (such tuning can be provided by ProcessMaker Professional Services Team). In any case, for production use, it is recommended that ProcessMaker is installed in a dedicated server or virtual machine, with at least 4 GB RAM, 2 CPU cores and 10 GB free disk space.
For more information on hardware requirements, please refer to: http://wiki.processmaker.com/index.php/ProcessMaker_Server_Sizing.
What technical support options are provided?
Response:
Different support plans have different SLAs. All SLAs are managed based on combination of the customer support plan and the criticality of the issue.
The following table summarizes support characteristics depending on the customer subscription:
...
STANDARD
...
Corporate
...
ENTERPRISE
...
Service Window
...
Business Hours
...
Business Hours
...
24x7
...
Support SLA
...
Severity 1
...
1 day
...
2 hours
...
2 hours
...
Severity 2
...
2 days
...
8 hours
...
4 hours
...
Severity 3
...
5 days
...
2 days
...
2 days
...
Severity 4
...
15 days
...
6 days
...
6 days
...
Support
...
Unlimited
...
Unlimited
...
Unlimited
...
Support Type
...
Web
...
Web, Phone
...
Web, Phone
...
Included Technical Points of Contact
...
1
...
1
...
2
The support process is briefly described below:
As soon as an issue is received, it is placed in a review/assignment queue. A team of agents will perform the initial review and then assign the support work to be done by a support agent. Support agents will first review the information received to understand the problem. The agent will then proceed to reproduce the problem or request additional information in order to reproduce the problem.
Once the problem has been reproduced, if there is not a known solution or if the agent cannot fix it, the problem will then be escalated to an interdepartmental coordinator. The coordinator will then assign the problem to the engineering cue for resolution. If the issue will then be prioritized and fixed in a patch release if it requires immediate solution. If the reported issue is a non-critical issue then it may be fixed in the next scheduled maintenance release. Issues that make it to engineering will be put directly into the engineering backlog to be prioritized in an upcoming release sprint.
Customer communication is prioritized at all times during this process. All incident information and resolution/escalation times are visible to the client in the trouble ticket system.
Additionally, for SaaS deployments, in case there is a service outage, ProcessMaker´s recovery time objective (“RTO”) is between 4 and 8 hours.
Solution allows for different field types (date, pick-list, radio button, free form, etc.)
Response:
...
Describe the tools provided for creating user interface forms. What skills are required for user interface form design?
Response:
Form design is based on a user friendly drag and drop interface. The interface allows the designer to test how the form will look under different screen form factors, allowing for easy testing of the mobile version of the forms at design time. Knowledge of JavaScript and JQuery, though not required, will allow for a more rich and dynamic form experience.
What type of training services does your company provide for the solution?
Response:
ProcessMaker provides three options for getting proficient and taking ownership of the solution:
The pre-recorded ProcessMaker University Training Portal is a must for anyone who wishes to master ProcessMaker features and maximize the success of a ProcessMaker implementation. (http://university.processmaker.com) – Included in the enterprise license/subscription
Advanced 40-hour Training Course:
The advanced training will provide technical resources with the knowledge to onboard any high level and high complexity requirements of the ProcessMaker solution, this training is detailed as follows:
a. Part I: Certified Architect Training (24 hours of training delivered as public on site course or private course)
b. Part II: Plug-in Training for Developers (16 hours of training delivered as public on site course or private course)
c. Customized Course can be laid-out/designed per customer specific requirements as well. This alternative would be priced at the same hour/total cost fee.
Do you have an active community around your software?
Do you have a Professional Services organization that supports product and if so, can you please describe your services methodology?
ProcessMaker offers professional services to customers and partners to be sure that their BPM projects are completed on time, under budget, and functioning correctly. Our dedicated consultants will work with you to implement your workflow requirements.
Our professional services implementation methodology has been developed and refined during these many years to incorporate better communication strategies, better development strategies, and better test and implementation strategies. Whether we or the customer is automating the process, we advocate the following 5 steps:
● Choose a project or process that will have significant impact in the organization
● Clearly identify what success looks like in order to manage expectations
● Ensure that the correct stakeholders are on the process implementation team for both the vendor and client
● Design the process
● Implement iteratively using a SCRUM methodology to ensure timely feedback and adjustments.
This service is available to Enterprise Subscription customers and can be quoted upon request.
Services can be delivered on site, remotely or combined.
There are three ways that customers can engage with ProcessMaker Professional Services:
Turn Key – We will quote an implementation fee based on the specific workflow or workflows to be automated. For provision of such quotation, we may require very specific/particular documentation of the targeted process.
A Statement of Work (SOW / See Annex I) will be created and agreed upon before any work is carried out and this document will become part of the professional services contract between our consultants and the customer. This can all be carried out either on-site or remotely.
Project Based –Hire specific project roles (Project Manager, Architect, and Programmer) to complement your existing team. Choose which parts of your workflow you require assistance with or which team roles you require us to fulfill for your project. This can be carried out either on-site or remotely.
Blended Rate Hours Packs – Quoted via a blended rate via hours purchased or hours consumed (Remote Consulting)
1) Professional Services Methodology
AGILE Project Management and SOW Methodology
The ProcessMaker Consulting team has developed an easy to follow procedure for implementing custom processes in ProcessMaker. The following table presents the methodology used to implement ProcessMaker. It shows the major activities that a project team should follow when implementing a new project or process in ProcessMaker. Whether the ProcessMaker team, client team, or external consultants are implementing the project, we have found that this methodology offers the highest rate of success. Please note that steps 4-7 are performed using an AGILE methodology. We recommend that these steps be based on 2 week sprints, daily SCRUMs, and weekly or bi-weekly verifications and checks with the client. Steps 1-3 are more directional in nature to ensure that everyone understands the ultimate direction of the project/process implementation.
A ProcessMaker implementation project has the following activities: ● Create a Project Charter Document ● Development of The Statement of Work for each process (SOW) ● Model processes in ProcessMaker ● Implementation of standard & advanced features ● Functional Validation ● Testing & Documentation ● Production |
Activity 1: Project Charter Document The first activity in deploying any process in an organization is creating a Project Charter which outlines the goals of the business process to be implemented, names the key people involved and provides a basic understanding of the project at a high level. Most of the time the companies implementing BPM systems have their processes well defined. If that is the case the effort in this activity is minimal. If the processes are not well identified and defined, the client must fully define the process before proceeding to the next activity. The ProcessMaker team will aid the client in defining the processes in compliance with ProcessMaker. |
Activity 2: Statement of Work (SOW) The Statement of Work (SOW) is the document that describes in detail how the clients’ process(es) are to be automated with ProcessMaker. Some characteristics of the SOW content are: ● Describes in detail the all process elements (Flow diagram, tasks, decision points, forms, documents, alerts, rules) ● Specifies special requirements for triggers and plug ins. ● Specifies Integration requirements with other systems and databases used by the client and other systems ● Provides technical requirements and resource requirements ● Defines the detail project plan and the work required. A Project Manager (or Project coordinator) is responsible for components 1 and 2. Elaborating a typical SOW will take between 40 to 60 Hrs. depending on the complexity of the process. Subsequent related projects may require less effort to develop the SOW. The client stakeholders MUST APPROVE THE SOW before the project goes further. It represents the technical guide that the project must follow, and it will be available to everyone. If the stakeholders decide not to continue with the project after receiving the SOW, they should be able to discontinue the project at this point. The client is responsible for all expenses up until that point, and the client is then the owner of the SOW, and may go forward with the project at a later date. |
Activity 3: Process Model When finished, the SOW is passed to a Project Technical Manager who: assigns work to the architect(s) and defines specifications for development (if needed). Whenever possible, process modeling tasks should be implemented jointly with the client/stakeholder team. This activity also includes development and implementation of advanced ProcessMaker features such as custom plug-ins, web services and custom report configuration. |
Activity 4: Standard and Custom Programming If the project has specific custom programming requirements, the ProcessMaker technical team will gather specifications for the development work. |
Activity 5: Functional Validation During the stage of functional validation, the consulting team will make adjustments and production are executed by the client, and ProcessMaker. This component includes training and documentation |
Activity 6: Testing and Documentation Validation, adjustments and production are executed by the client, and ProcessMaker. This component includes training and documentation |
Activity 7: Production The final activity is putting the process into production. This step will iterate back to 5-7 with minor adjustments during the initial period of use by the client. |
Hours Package | Blended Rate for Remote Consulting |
|---|---|
0 - 100 Hours | $160 per hour |
Above 150 Hours | $120 per hour |
What client platforms is your solution compatible with (web, mobile, etc.)?
Is standalone client software required or is it web-based?
If web-based, which web browsers are supported?
Does it support responsive UI?
Is mobile app available and on which operating systems?
If the functionality differs by client platform, please elaborate how
Response:
ProcessMaker works with any computer operating system as long as it has a supported web browser. In addition, ProcessMaker supports both Android and Apple/iOS mobile devices. Details, according to each specific question, are provided below:
- ProcessMaker is a 100% web based solution. This means that process design, execution and monitoring can be done via industry standard web browsers.
- ProcessMaker supports the current and previous major releases of Firefox, Google Chrome and Internet Explorer on a rolling basis. Each time a new version is released, we begin testing and then supporting that version and stop supporting the third most recent version. For additional on our supported browsers, please visit the following link: http://wiki.processmaker.com/index.php/Supported_Browsers.
- Yes. ProcessMaker Dynaforms are 100% responsive, and are based on industry standard HTML5. Therefore, users can work on their assigned tasks via a mobile device. In addition, ProcessMaker's look and feel can be customized by creating custom Skins or themes. For more information about responsive form design, please refer to the following link http://wiki.processmaker.com/3.0/HTML5_Responsive_DynaForm_Designer. For additional information regarding themes or skins, please refer to http://wiki.processmaker.com/3.0/Skins.
- Yes, The ProcessMaker Mobile App, available both for Android and iOS devices, allows end users to perform work on assigned cases as well as create new cases from a mobile device. In addition to standard forms usage, the Mobile App allows the user to enter data from mobile device sensors, including GPS positioning/Geolocation, QR codes and barcodes, signatures via touchscreen display, photos, audio recordings and video capture.
- From a process execution point of view, ProcessMaker's functionality does not depend on client platform. Process design, dashboards and KPI's, however, are only available via a desktop or laptop environments, using any of the supported browsers previously mentioned.
In addition, support for other platforms can be easily added by writing a client application that communicates with the ProcessMaker server via our REST API (described further below). ProcessMaker Professional Services Team can create such client applications if required for a specific project.
What operating systems can be used for hosting your solution?
Response:
Our solution is based on a LAMP/WAMP (Linux/Windows, Apache, MySQL and PHP stack). Our currently supported stacks include both Linux (CentOS) and Windows Operating Systems. For more details on our supported stacks, please refer to http://wiki.processmaker.com/index.php/Supported_Stacks.
What other software prerequisites are needed to ensure successful provisioning and operation of your solution? (e.g. database drivers, etc.)
Response:
ProcessMaker requires the following components in order for the software to be successfully installed:
Apache Web Server with the following components enabled
Deflate
Expires
Rewrite
Vhost_alias
Filter (only if using Apache 2.4)
PHP Runtime language
Fileinfo
MySQL
Xml
Mbstring
Mcrypt
Soap
LDAP
GD
Curl
CLI
MySQL
Strict mode disabled
If connecting to external databases, such as MSSQL or Oracle, additional drivers for the respective database engines would be required.
To see a full list of the required components pre installation, please visit this link: http://wiki.processmaker.com/3.0/ProcessMaker_Installation_Requirements.
Does your solution support horizontal or vertical scaling?
ProcessMaker can support high scalable and high available implementations. We typically only do this for very large ProcessMaker implementations (tens of thousands of users).
For small size implementations (hundreds or low thousands of users), we have server sizing guidelines that are available here: http://wiki.processmaker.com/index.php/ProcessMaker_Server_Sizing
For these types of large and scalable implementations, we have tested thoroughly in the AWS environment and would therefore recommend AWS for a highly scalable requirement, however, we have also tested in the MS Azure cloud and confirm that we are able to offer the same in the MS Azure cloud.
Here is an example diagram detailing a highly scalable and available ProcessMaker implementation in the AWS environment:
What are the known scaling bottlenecks (e.g. CPU/memory/IO, etc.)? What are the recommended hardware requirements?
Response:
ProcessMaker has no specific scaling bottlenecks. Actual bottlenecks experienced by our customers tend to depend on many factors, including processes' complexity, number of users, number of cases, among others.
As for hardware requirements, for personal use and/or testing use, ProcessMaker can be installed on any computer with a modern CPU and 2GB of RAM. For production use, the hardware requirements also vary based on the number of concurrent users, repository size and system configuration. Larger implementations may require some tuning to perform optimally (such tuning can be provided by ProcessMaker Professional Services Team). In any case, for production use, it is recommended that ProcessMaker is installed in a dedicated server or virtual machine, with at least 4 GB RAM, 2 CPU cores and 10 GB free disk space.
For more information on hardware requirements, please refer to: http://wiki.processmaker.com/index.php/ProcessMaker_Server_Sizing.
What technical support options are provided?
Response:
Different support plans have different SLAs. All SLAs are managed based on combination of the customer support plan and the criticality of the issue.
The following table summarizes support characteristics depending on the customer subscription:
STANDARD | Corporate | ENTERPRISE | |
Service Window | Business Hours | Business Hours | 24x7 |
Support SLA | |||
Severity 1 | 1 day | 2 hours | 2 hours |
Severity 2 | 2 days | 8 hours | 4 hours |
Severity 3 | 5 days | 2 days | 2 days |
Severity 4 | 15 days | 6 days | 6 days |
Support | Unlimited | Unlimited | Unlimited |
Support Type | Web | Web, Phone | Web, Phone |
Included Technical Points of Contact | 1 | 1 | 2 |
The support process is briefly described below:
As soon as an issue is received, it is placed in a review/assignment queue. A team of agents will perform the initial review and then assign the support work to be done by a support agent. Support agents will first review the information received to understand the problem. The agent will then proceed to reproduce the problem or request additional information in order to reproduce the problem.
Once the problem has been reproduced, if there is not a known solution or if the agent cannot fix it, the problem will then be escalated to an interdepartmental coordinator. The coordinator will then assign the problem to the engineering cue for resolution. If the issue will then be prioritized and fixed in a patch release if it requires immediate solution. If the reported issue is a non-critical issue then it may be fixed in the next scheduled maintenance release. Issues that make it to engineering will be put directly into the engineering backlog to be prioritized in an upcoming release sprint.
Customer communication is prioritized at all times during this process. All incident information and resolution/escalation times are visible to the client in the trouble ticket system.
Additionally, for SaaS deployments, in case there is a service outage, ProcessMaker´s recovery time objective (“RTO”) is between 4 and 8 hours.
Solution allows for different field types (date, pick-list, radio button, free form, etc.)
Response:
ProcessMaker supports the following variable types: String, integer, float, boolean, datetime, grid, array and file. Variables can be bound to different form controls, including textbox, text area, dropdown, checkbox, checkgroup, radio, datetime, suggest, hidden, files, grid, among others. In addition, Forms designed to be used via the mobile ProcessMaker application can make use of additional input types such as geolocation, QR/bar codes, finger signature via touchscreen, pictures, audio and video.
Can data submitted be modified after it's submission by different users?
In ProcessMaker, supervisors have the ability to edit data based on the pre defined scope by a process architect. So therefore, a supervisor can make data changes at any point in the workflow, as long as he/she has the right access rights to do so for each individual process.
Does the workflow solution have the ability to execute sub processes and how does it work?
ProcessMaker is able to execute processes and sub processes. In ProcessMaker, sub processes retain the same exact level of functionality that a normal process would have. The only thing that is different about a sub process is that they may be invoked from within another process. When invoked, sub processes can be executed synchronously or asynchronously. This means that the parent process can be made to wait until the sub process is finished or continue immediately. If the parent process waits, data can be transfered back to the parent process. If the parent process does not wait, data can only be sent to the sub process.
Is it possible for only developers/administrators to create processes?
Yes, it is possible to permission it so that only developers/administrators can delete the process. In fact, this is the default and recommended setting.
Is it possible for only developers/administrators to delete processes?
Yes, it is possible to permission it so that only developers/administrators can delete the processes. In fact, this is the default and recommended setting.
Can the proposed solution generate MS Word and PDF documents?
ProcessMaker has the ability generate both MS Word and PDF documents. These documents are known as Output Documents in ProcessMaker. Output Documents can be generated through a What You See Is What You Get (WYSIWYG) editor and contain embedded process data so that the output of the document can be dynamic, based upon the workflow that is generating it.
For more information on Output Documents, please see this page: http://wiki.processmaker.com/3.0/Output_Documents