ProcessMaker version 4.1 Release Notes for ProcessMaker build 4.1.16.
Release Date: March 11, 2021
ProcessMaker is proud to announce the immediate availability of ProcessMaker version 4.1. This update addresses multiple new features, improvements, and bug fixes.
ProcessMaker 4.1 is build 4.1.16. Release notes after this release are listed as ProcessMaker 4.1.17.
The ProcessMaker 4 platform makes it easy to create business processes that have the power of applications with our low-code approach using our BPMN 2.0-compliant suite of services so that you can design and deploy automated workflows that deliver true digital agility to your organization.
Non-core packages: ProcessMaker version 4.x packages extend core-product functionality. Packages are not available in the ProcessMaker open-source edition, but are available to customers that purchase or subscribe to ProcessMaker version 4.x. Release Notes that affect package functionality are documented in separate sections.
Release notes are cumulative with all previous ProcessMaker 4.x releases, and document new features, improvements, bug fixes, and/or known issues associated with this release unless otherwise noted.
Screen Builder version 2 is built with the latest core components.
Design Modern Chat Style Forms with the New Conversation Forms Package
Design functional rule-based chat style forms using ProcessMaker Screens with the new Conversational Screen type available with the Conversation Forms package. Learn more.
Manage BPMN 2.0 Signals and ProcessMaker Collection Signals
Manage your organization's BPMN 2.0 signals and ProcessMaker Collection signals from the new Signals page accessible from the Designer top menu. Managing your organization's signals from outside of the Process model design and ProcessMaker Collection promotes greater reusability and transparency to which ProcessMaker assets subscribe to each signal. Collectively, all signals are referred to as ProcessMaker Signals. Learn more.
Configure how records in one ProcessMaker Collection relate to the records in another Collection. Learn more.
Each ProcessMaker Collection has its own signals that can be configured with webhooks when particular events in that Collection occur. A ProcessMaker Collection event occurs when a record in that Collection is created, edited, and/or deleted. A webhook automates the sending or receiving of data to or from another application or third-party service when an event occurs. The data is sent or received via a unique URL that ProcessMaker and that application or service can parse. Learn more.
Data Connector Package
Configure webhooks for your BPMN 2.0 signals. That signal triggers when either a signal-type BPMN 2.0 element in a Process's Request calls it or an event in a subscribing ProcessMaker Collection occurs. A webhook automates the sending or receiving of data to or from another application or third-party service when an event occurs. The data is sent or received via a unique URL that ProcessMaker and that application or service can parse. Learn more.
Configure ProcessMaker Data Connector connectors in your Process models how to receive a third-party service callback and then store that response in Request data. Learn more.