New version!

What is Business Process Modeling Notation?

Discover the power of process automation!
Try Qflow now and automate your business processes.

Published by

Lu Prado

Diseñador

What is BPMN?

BPMN stands for “Business Process Model and Notation,” a business process modeling standard that allows organizations to graphically represent their processes, enabling clear and effective understanding and communication.

BPMN provides a standardized graphical notation for modeling various aspects of a business process, such as activities, events, workflows, decisions, tasks, responsibilities, and roles. This facilitates the identification of potential process improvements and helps manage change.

The notation consists of graphical elements that represent different aspects of a business process, such as its start and end, intermediate events, tasks, and gateways. Let’s look at an example:

Vacation request

This process designed to manage vacation requests allows each employee to request their leave through a form, initiating the flow. The approval task is then routed to the user requester’s supervisor, branching the flow into two possible paths through an exclusive gateway: if the supervisor approves the leave, the process advances to the “subtracting vacation days” intermediate event, deducting the requested leave from the total available and assigning a substitute to cover the employee’s absence. This branching of the process culminates in approved vacations. On the other hand, if the supervisor rejects the request, the requesting user is notified, and the process ends with the vacations rejected.

A Bit of Its History

BPMN is developed by the Object Management Group (OMG), a non-profit organization dedicated to promoting and developing standards for the information technology industry. The first version of BPMN was published in 2004 and has been updated several times since then, with the current version being 2.0.

BPMN has very high practical value in business contexts. Being a standard in the field, processes designed in this notation are easily understood by business professionals, facilitating the proposal of customized solutions.

Additionally, all processes designed in BPMN can be imported into tools that use BPMN. For example, if you start using Qflow today, you can import your processes designed with BPMN into another tool, transferring your mapped processes to a new platform effortlessly.

Benefits of Using It

There are multiple benefits associated with implementing BPMN notation in managing your processes. Let’s see some!

  1. Business Agility
    BPMN is a flexible tool that facilitates the creation of an agile environment, promoting the rapid resolution of processes. By having a clear path for each vacation request, your company’s employees can schedule their leaves without inconvenience.
  2. Improves Productivity
    BPMN notation provides a framework for modeling your processes. If clear processes are established and work flows smoothly, business productivity increases. Additionally, BPMN allows for clear task assignment to specific users, avoiding workload overload.

    For example, each employee’s vacations must be approved by their direct supervisor, rather than having a single user responsible for all leave requests, thus alleviating the workload and allowing each employee to focus on their tasks.
  3. Establishes a Common Code
    As previously mentioned, BPMN represents a standardized code with symbols easily understood by technical and non-technical users.

    This facilitates the quick adaptation of new employees to the company’s usual processes, such as leave requests.
  4. Facilitates Knowledge Transfer
    Likewise, BPMN facilitates the exchange of information with other team members. By designing processes in the same notation, using the same graphical elements, collaborators assuming new functions and responsibilities within the organization can quickly receive information about the processes to be managed, adapting to their new tasks in the blink of an eye.

BPMN Elements

Let’s review the graphical elements that make up BPMN notation.

Activities

Sample BPMN Activity

These are one of the fundamental elements in the BPMN notation since they represent the tasks or actions carried out within a business process. These activities can be as simple as a single task or as complex as a sub-process involving multiple tasks.

There are two types of activities in BPMN: task activities and subprocess activities.

Task activities represent a single task that is performed within a process and does not contain sub-processes. These activities classify into several categories, some of which are below:

Ejemplo Tarea de usuario de BPMN

User task

A task only performed by a human user.

Ejemplo Tarea de servicio de BPMN

Service task

This task is performed automatically by an information system or software.

Send task

This task sends a message -such as an e-mail- to another process or process participant.

Script task

This task executes a code sequence and continues with the process. 

Asynchronous service task

Performed by an information system or external software, this task will continue the process upon completion.

On the other hand, subprocess activities are those containing more than one task and may be complete processes with their internal flow. These activities group tasks or activities repeated or used in several processes, creating more complex process structures.

Subprocess

There are two subprocess activity types:

  • Process subprocess: a subprocess represented as a complete process within the main one. This subprocess can have its flow and connect to other elements of the BPMN notation.
  • Task subprocess: this sub-process represents a task within the main one. It groups tasks and activities repeated in the main process.

It is important to note that activities do not have a defined duration and are not time-related. The activity duration should not be confused with its complexity or the number of tasks involved. Instead, the process duration is determined by the events triggered at the beginning and the end of the process.

Events

Events in BPMN indicate the beginnings, endings, and decision points within a process.

The different types of events defined by the BPMN notation are listed below:

Start event

Ejemplo Evento de inicio de BPMN

This event represents the start of the process. It can be a simple event, such as the start of a workflow or of a start event message, which is triggered when a message is received.

There are other start events types, such as timed start or start by an external signal.

Intermediate event

Ejemplo Evento intermedio de BPMN

It indicates a decision point or the need to perform some action, such as sending a message. They can be simple, temporary, or conditional events.

There are different types of intermediate events to indicate each of these behaviors. For example:

  • Timer event, which waits until a certain time condition.
Ejemplo Evento de temporización de BPMN
Ejemplo Evento de lanzar señal de BPMN
Ejemplo Evento de atrapar señal de BPMN

End event

Ejemplo Evento de fin de BPMN

This event represents the end of the process and can be a simple event, such as a workflow completion.

Ejemplo Evento de fin terminal de BPMN

There are also other types of end events, such as the terminal end event, which closes all the threads that the process may have active.

Boundary events

In addition, there are boundary events that can be associated with activities, and upon their occurrence, the execution of the process will take a specific path. These can be:

  • Timer event
  • Error event
  • Compensation event

In summary, events in BPMN are important to indicate starts, endings and decision points within a business process and are used to model workflow and automate business processes.

Gateways

Gateways allow you to define the rules and conditions for a process information flow. There are three main types of BPMN notation gateways: exclusive gateways, inclusive gateways, and parallel gateways.

Exclusive gateways

Ejemplo Compuerta exclusiva de BPMN

Exclusive gateways decide between two or more alternative process paths. Only one can be taken, the others discarded.

Inclusive gateways

Ejemplo Compuerta inclusiva de BPMN

Inclusive gateways decide whether one or more options can be selected. Several options are selected and all are carried out.

Parallel gateways

Ejemplo Compuerta paralela de BPMN

Parallel gateways divide a process into several paths that run in parallel.

Other types of gateways

There are also additional types of BPMN gateways:

Complex gateways

Complex gateways are used when more complex logic is needed to determine the process flow. For example, they can be used to perform a task based on certain conditions or to make decisions based on multiple variables, such as a combination of events or data values.

Event-based gateways

Event-based gateways model processes triggered by specific events. These gateways initiate event-based processes, make event-driven decisions, and wait for events before continuing with it.

BPMN gateways are key elements in business process modeling, allowing you to define the rules and conditions of process information flow. Each type of gate is used for a specific situation and can be customized to meet the needs of the business process.

Connection objects

Connection objects represent the relationships and information flows between different elements of a business process. Connection objects defined by the BPMN notation include the following:

Sequence flow

It represents the sequence of activities in the business process. Sequence flows connect different objects in a business process and show the direction of the workflow.

Ejemplo Flujo de secuencia de BPMN

Association

It represents the relationship between artifacts and the different objects in the process.

Ejemplo Asociación de BPMN

Message flow

Represents a message that is sent or received within the business process. Messages communicate information between different elements of a business process, such as between lanes or participants.

Messages are represented by a dotted arrow and labeled with names that describe the content of the message.                                                                                                                                                                    

Pools

A pool has one or many lanes that visually group and separate business process elements according to their function or responsibility. In BPMN notation, lanes are represented as horizontal or vertical lines divided into sections containing business process elements. Lanes model different business processes aspects, such as roles, departments, or responsibilities.

Each lane in BPMN can be labeled with a name describing the function or responsibility it represents. In addition, lanes can contain annotation elements to provide more information about the business processes. Lanes create clear, easy-to-understand BPMN diagrams that explicitly show how business process elements are related and who is responsible for which activity.

Example of an approval process with lanes
Example of an approval process with lanes

Artifacts

Artifacts are additional elements used in BPMN notation to add extra or complementary information to processes. Artifacts do not represent specific tasks or actions but provide information relevant to the process or the actors involved in it.

Ejemplo Referencia de objeto de datos de BPMN

BPMN defines four types of artifacts:

Data Object Reference: They represent information used or generated in the process.

Ejemplo Referencia de base de datos de BPMN

Database reference: represents a data store, such as a database.

Ejemplo Grupo de BPMN

Groups: Represent a set of process elements that have some logical relationship with each other. Groups organize and group process elements and are represented by a rectangle with dotted edges.

Ejemplo Asociación de BPMN

Annotations: Represent notes or comments that provide additional information about the process elements. Annotations describe the purpose or function of a task or add supplemental information not included in the main diagram. Annotations are represented by a rectangle with a folded corner.

How to Successfully Apply BPMN in an Organization?

Incorporating BPMN modeling into your organization requires time, like any new tool; but the expected results from the design of standardized processes justify the effort.

To support BPMN modeling, it is important to continue designing with process automation. For this, a BPM tool like Qflow is indispensable, which allows designing in BPMN notation, either from scratch or through our pre-designed templates; automate and monitor the success of your processes all in one tool.

By having a process management tool, you can start from the current path of the process to define the events, tasks, and actors that comprise it, transferring your organization’s needs to a design that achieves them. Once the process is drawn, its automation will further optimize the times and resources of your company, and monitoring the success of each process will allow you to make the necessary adjustments to achieve optimal results.

What Industries Is It Useful For?

The implementation of BPMN can benefit any industry. By modeling processes, organizations can automate their systematic tasks, saving time and resources and projecting the efficiency of their management. Let’s see some examples:

  1. HR
    We already discovered how BPMN notation simplifies vacation management within an organization, but this is not the only HR process that can be enhanced. Model your personnel recruitment processes, employee evaluations, and contract management with BPMN and transform your HR management.
  2. Education
    Educational institutions must manage complex and diverse processes in their daily operations, many of which can be easily simplified by modeling them with BPMN. Scholarship applications, for example, can be mapped to allow interested parties to apply through the institution’s website, initiating the flow.
  3. IT
    In the technology industry, processes requiring urgent resolution such as incident management and Help Desk ticketing will see their response times optimized by mapping with BPMN.

Conclusion

In summary, BPMN is used by many organizations worldwide to model and improve their business processes and has become an essential tool for business process management. Its standardized graphical notation facilitates communication and collaboration between different areas of an organization and allows for identifying areas for process improvement.

Start modeling your own processes in BPMN today with Qflow. Boost your company’s efficiency and take your business process management to the next level.

Discover the power of process automation!
Try Qflow now and automate your business processes.
Share this post!

Terms and Conditions

1st Background

  1. 1.1. ITX S.A.- (hereinafter “URUDATA SOFTWARE”) is a company with large experience at regional level, providing quality solutions that make its customers more competitive and efficient.
  2. 1.2. It is the exclusive and sole owner of all intellectual property rights to the software called“Qflow Cloud” (hereinafter the “Software”), as well as all material related to it.
  3. 1.3. The “Software” is a web-based BPM (Business Process Management) tool that allows modeling company’s business processes and integrating people and information systems through a workflow. The whole operation of the tool oversees the client, whether it is modeling, execution and control of its processes.
  4. 1.4. This document establishes the terms and conditions that will be applicable to all “Clients” who use the “Software” in any way, under any of their contracting options.
  5. 1.5. The use of the “Software” implies full knowledge and acceptance of these terms and conditions, as well as the decisions that “URUDATA SOFTWARE” adopts according to law on any unforeseen issue, without prejudice to specific conditions that the parties could expressly agree and write.
  6. 1.6. The “Client” must make sure to read and understand the scope of this document and have the necessary legal capacity to contract, either on their own behalf or on behalf of a legal person.
  7. 1.7. “URUDATA SOFTWARE” does not guarantee that the “Software” works without interruptions, meets the expectations or functionalities that the “Client” requires. The “Software” is licensed “as it is”, according to the terms and conditions that are established, without providing any guarantee of utility or aptitude to achieve certain purposes, being the exclusive responsibility of the “Client” to know the scope, aptitudes and functionalities of the “Software”.

1nd Definitions

For the purposes of these terms and conditions, the expressions detailed will have the following meanings:

  • “Client”: Natural or Legal Persons who have carried out the process of acquiring the “SaaS” license of the “Software”, according to the regulation of these terms and conditions.
  • “Software or Qflow Cloud”: Refers indistinctly to the computer system exclusively owned by “URUDATA SOFTWARE” that can only be used through an Internet connection.
  • “SaaS mode”: Refers to the license of use granted to the “Client” on the “Software”, together with maintenance services and data hosting in cloud services, according to what is detailed in the document and the subscription process.
  • “Host / Server / Hosting”: Refers to the web service that provides computing and database capacity on cloud servers, with a scalable size.
  • “Base Software”: Refers to the different and necessary computer programs for the “Software” to work correctly.
  • “Parties”: Refers to the appearing parties jointly named.

3rd SaaS Mode

  1. 3.1. For the price that the parties agree during the subscription process, “URUDATA SOFTWARE” will grant the “Client” the following rights and services:
  2. 3.1.1. License of Use of the modules of the “Software” that the parties agree.
  3. 3.1.2. Data Hosting Services.
  4. 3.1.3. Versions Updates.
  5. 3.2. Support and Maintenance Services, as well as Training, are not included in these Terms & Conditions, and may be contracted independently by the “Client”. The rights and services will be provided under the terms, conditions and scope determined in these terms and conditions and in accordance with the specifications established in the subscription process, according to the various options that “URUDATA SOFTWARE” establishes.

4th Use license

  1. 4.1. The license granted on the “Software” is a temporary license, conditional on the payment of the price, non-exclusive, non-transferable, limited in the benefits and specifications of the “Contracted Plan”.
  2. 4.2. The license to use the “Software” will be valid during the period that the “Client” pays in a timely manner the price established between the parties.
  3. 4.3. The “Contracted Plan” by the “Client” will determine the number of users, number of execution points, necessary storage and any other specification referring to the scope of the license of use granted, without prejudice to the provisions of this document.
  4. 4.4. “URUDATA SOFTWARE” reserves all rights not explicitly assigned or authorized. The license will be terminated by right in case of non-payment of the price.
  5. 4.5. The “Client” may not give this License in any way and must use the “Software” for its own legitimate purposes. They may not modify, copy, adapt, reproduce, disassemble, decompile, translate, or reverse engineer the Software.
  6. 4.6. The “Client” must ensure that the usernames and passwords required to access the “Software” are secure, confidential and exclusively in their possession. The “Licensor” will not be responsible for the loss or alteration of data in the system.
  7. 4.7. The “Client” is expressly prohibited from:
  8. 4.7.1. Attempt to violate the security or integrity of the “Software”, networks or services and complementary systems of third parties.
  9. 4.7.2. Use the “Software” in any way that may affect its functionalities or those of other complementary products or services; as well as those of other “Clients”.
  10. 4.7.3. Attempt to gain unauthorized access to materials, systems or resources other than those with which you have contracted.
  11. 4.7.4. Transmit or add into the “Software” files that may damage devices or that contain material that is offensive or violates regulations.

5th Maintenance and Support

    1. 5.1. During the term of the contract “URUDATA SOFTWARE” will provide the “Client” with support and maintenance according to the contracted Plan, without prejudice to not being obliged to any specific response time.
    2. 5.2. The support and maintenance service implies responding to the “incidents” notified by the “Client” regarding anomalies detected in the use of the “Software” or lack of knowledge for its use. This does not imply in any way the customization of the “Software”, the advice or necessary modifications so that the “Software” is compatible or interconnected with “Systems” or “Hardware” of the “Client” and that are different from those established in the technical specifications for the correct operation of the “Software”.
    3. 5.3. The “Client” may report incidents and request support according to the contracted Plan, always through “Users” previously registered in the system.
    4. 5.4. “URUDATA SOFTWARE” will be the one who categorizes the reported incidents and will have the power, at its sole discretion, to determine whether the reported incidents are incidents subject to support and may reject the requests. Incidents will be considered resolved upon notification that a permanent or temporary solution has been established. Support service hours will be Monday to Friday from 9 a.m. to 6 p.m., on business days in the Oriental Republic of Uruguay (UTC -3).
    5. 5.5. Requests for an explanation of the use of the “Software” will not be considered an “incident”.
    6. 5.6. Incidents will not be subject to treatment if their cause is related to elements unrelated to the “Software”, such as connectivity, network, operating systems, browsers or any other dysfunctional factor caused by a “Base System”, unrelated to the “Software”, or any other “hardware” or “connectivity” reason.
    7. 5.7. In case of technical problems, the “Client” must make all reasonable efforts to investigate and diagnose the problems before reporting them. To use the support service, the “Client” must be subscribed to it, be up to date with payments and communicate by the following means and in order of priority.

Online Support: Entering the query from the same application.
Email Support: support@urudata.com

6th Data Hosting

  1. 6.1. The “Software” provides its functionalities from the “cloud”, this implies that the “Client” will be able to access remotely from any computer with Internet access that meets the technical specifications.
  2. 6.2. All information uploaded by the “Client” to the “Software” is its exclusive property and responsibility. “URUDATA SOFTWARE” will not control, manipulate or observe in any way the information that the “Client” uploads to the “Software”, except that it is necessary for the fulfillment of its contractual obligations.
  3. 6.3. The “Client” may at any time generate reports with the information loaded in the “Software”.
  4. 6.4. “URUDATA SOFTWARE” will not be responsible for the total or partial, transitory or definitive loss of data or hosted information, except when acting with intent or gross negligence.
  5. 6.5. “URUDATA SOFTWARE” states that the cloud hosting services provided by “Microsoft Azure” are used and that it transfers its terms and conditions to the “Client”, who accepts (https://azure.microsoft.com/en-us/support/legal). Any contingency or eventuality of any nature that causes damage to the “Client” that is motivated by failures, alterations or modifications of the services provided by “Microsoft Azure” will not be the responsibility of “URUDATA SOFTWARE”, being beyond its will and impossible to control, therefore, they will not be attributable in any way.
  6. 6.6. “URUDATA SOFTWARE” may at any time change the “host” service provider to a different one, which must have -at least- similar technical, availability and security characteristics.
  7. 6.7. The “Client” has the right to upload data up to the maximum that has been contracted during the subscription process.

7th Versions Updates

During the period that the contract is in force, the “Client” will receive the new versions of the “software” that are released by “URUDATA SOFTWARE”, with the same rights as those established in the “FOURTH” Clause, being these Terms and conditions fully applicable.

8th Price, payment method and billing

  1. 8.1. When the “Client” subscribes, they will make the payment through the methods available.
  2. 8.2. “URUDATA SOFTWARE” will completely and irremediably destroy all the information that was in the “Software” within a period of 30 calendar days since the “Client” failed to pay the price.
  3. 8.3. “URUDATA SOFTWARE” will issue an invoice at the time of contracting for the agreed period and the amount corresponding to the contracted Plan, which will be sent to the “Client” within the following 15 days.
  4. 8.4. The invoices will be sent according to the contact and billing information provided by the “Client”, who will be responsible for keeping this information updated.
  5. 8.5. The invoice corresponding to the services will be sent to the “Client” according to the contracted period. If no automatic debit payment was chosen, the “Client” must make the payment for the services in advance within the first 10 days of the payment month or on the due date established in the invoice if it is later than the first one.
  6. 8.6. The non-payment of invoices in a timely manner will suspend the access to the “Software” until the debt is canceled.
  7. 8.7. The price may be adjusted by “Urudata Software” at any time, having the “Client” the option to cancel the contract from the start period of the new price.
  8. 8.8. At any time, the “client” may request to change to a higher plan than the one they have contracted. Without prejudice to this, once the “client” exceeds the hired limit, “Urudata Software” will automatically block the access to the system.
  9. 8.9. At the end of the initial recruitment period, it will be automatically renewed by other equal periods.

9th Confidential information

  1. 9.1. All the information you receive or any of the Parties has access to, under or in relation to the relationship arising from this Contract, will be naturally confidential (“Confidential Information”). Such confidential information may not be disclosed, published, disseminated or used in any way by the receiving party without the express authorization of the other party.
  2. 9.2. The receiving party must protect confidential information from the informant party, with the same degree of care and confidentiality with which it protects its own confidential information.
  3. 9.3. These Terms and Conditions do not impose any obligation to any of the Parties, in relation to the confidential information of the other Party that the recipient can establish by sufficient legal evidence, in any of the following cases:
  4. 9.3.1. It was in its possession or was legitimately known by the receiving party from the informant party before receiving it that there was no obligation to maintain its confidentiality.
  5. 9.3.2. The information was in the public domain, without violating the provisions of this contract.
  6. 9.3.3. It was obtained in good faith by the receiving part of a third party, with the right to disclose it and without the obligation of confidentiality.
  7. 9.3.4. Its disclosure is required in accordance with the applicable laws, in understanding that the receiving party notifies the informant party of said requirement before the diffusion, and provided that the receiving party makes diligent efforts to limit said diffusion.
  8. 9.3.5. Its disclosure is required in accordance with the applicable laws, in understanding that the receiving party notifies the informant party of said requirement before the diffusion, and provided that the receiving party makes diligent efforts to limit said diffusion.
  9. 9.4. The receiving party will not obtain, by virtue of this Agreement, the rights of ownership or participation of any part of the confidential information of the owner or informant party.
  10. 9.5. 9The personal information, obtained by any of the parties for the execution of the contract that links them, can only be used for the fulfillment of the object, cannot be assigned or disclosed to third parties under any title. In this respect, all personal information to which they have access or intervene at any phase of personal data processing, they must act cautiously and confidentiality about them, applying strictly professional secrecy.
  11. 9.6. When the contract is ended, each party must destroy completely the information or personal information that would have obtained from the other party during the contract. Each party will be the only responsible for safeguarding their own data.

10th Responsibilities

  1. 10.1. “URUDATA SOFTWARE” will keep the “Client” harmless for any conflict or contingency that arises as a result of intellectual property claims related to the “Software”. In this regard, “URUDATA SOFTWARE” will be responsible for claims based on intellectual property conflicts, doing its utmost to keep the “Client” unaware of these conflicts and if this is not possible, it is obliged to face all costs and costs that it must bear as a result of the claim.
  2. 10.2. “URUDATA SOFTWARE” will only be responsible for omissions, delays or errors in its “Systems” or services as long as they are entirely attributable to it and not when there are other external factors, caused or linked to the “Client” or other third parties that cause that omission, error or delay.
  3. 10.3. “URUDATA SOFTWARE” limits its own accountability, for any concept, up to the amount that it has received in the last three months of the contract. The “Client” contracts having full knowledge of this accountability limitation.
  4. 10.4. The “Client” is solely responsible for the content loaded in the “Software”, “URUDATA SOFTWARE” does not know or control the loaded content. The “Client” certifies that all the content that it loads and manages in the “Software” is of a legal nature and does not violate rights or regulations.

11th Personal information

  1. 11.1. It is stated that eventually “URUDATA SOFTWARE” may host personal data that the “Client” owns or is in charge of processing, but “URUDATA SOFTWARE” will not treat any personal data in any way or control or process any personal data that the “Clients” load.
  2. 11.2. It is the sole responsibility of the “Clients” to verify compliance with the personal data protection regulations.

12th Completion

  1. 12.1. “URUDATA SOFTWARE” may terminate this contract with prior notice to the counterparty at least 90 days in advance.
  2. 12.2. The “Client” may cancel the account at any time, by communicating it reliably to “URUDATA SOFTWARE”.
  3. 12.3. After the contract expires, the data will be kept for the maximum period of ninety (90) days, after which it will be deleted. The client can request the export of the information free of charge within the first 90 days.
  4. 12.4. “URUDATA SOFTWARE” will not refund the paid price paid for the services, except that the early termination of the contract has been arranged by “URUDATA SOFTWARE”.
  5. 12.5. Either party may terminate the contract if there are serious breaches by the other party of the main obligations arising from the contract or repeated breach of secondary obligations. Failure to pay the price is considered a serious breach and therefore the license of use will be suspended.
  6. 12.6. If the “Client” breaches any of its obligations, “URUDATA” may, at its sole discretion, terminate or suspend the contract and prevent access to the “Software” and information.
  7. 12.7. At the end of this contract, the “Client” will continue to be responsible for any debt acquired whose payment date is before or after the date of termination of the agreement.

13th Notifications and communications

  1. 13.1. The parties will consider valid the notifications made to the respective emails; in “Qflow Cloud” notification system or at the physical addresses established in the subscription process.
  2. 13.2. Any notification will also be considered valid if an acknowledgment of receipt is obtained from the other party, granted by a person with sufficient representation power for such purposes.
  3. 13.3. The “Client” agrees to use the various means of communication implemented by “URUDATA SOFTWARE” and must refrain from using them to disseminate material not related to the legitimate use of the “Software”.
  4. 13.4. “URUDATA SOFTWARE” may not receive the communications that are made to it without verifying the corresponding acknowledgment of receipt or similar proof of receipt.

14th Jurisdiction

This Agreement will be governed by the stipulations contained in this document and the applicable law will be that of the Oriental Republic of Uruguay.

15th Modifications

  1. 15.1. These Terms and Conditions may be modified by “URUDATA SOFTWARE” at any time, the modification being valid from the second business day on which the new terms have been notified in the “Qflow Cloud” notification system.
  2. 15.2. Once the modification of these Terms and Conditions of Use or the price of the service has been notified, the “Client” may, within 5 calendar days from the notification, express their willingness to terminate the contract. This termination will not give rise to any liability for the parties, nor will it give the right to any reimbursement of payments already done.

16th Use of ChatGPT Service by Our Artificial Intelligence Assistant

  1. 16. 1. The artificial intelligence assistant, available starting from version 5.3 of Qflow, uses the ChatGPT service for generating process flows. 
  2. 16.2. The user acknowledges and agrees that: 
  • a. When using the artificial intelligence assistant, they accept the terms and conditions stipulated by OpenAI for the ChatGPT service: https://openai.com/policies 
  • b. Although we have validated the accuracy and usefulness of the responses generated by ChatGPT, we cannot guarantee the accuracy, completeness, or suitability of such responses for specific purposes.   
  • c. The use of the artificial intelligence assistant, including the ChatGPT service, is the responsibility of each user. Under no circumstances shall “URUDATA SOFTWARE” be liable for any damages of any kind arising from the use or inability to use this functionality or the ChatGPT service. 

TERMS AND CONDITIONS OF LICENSE MAINTENANCE SERVICE CONTRACTING

The License Maintenance service is provided to the customer by URUDATA SOFTWARE (ITX S.A.), located at Canelones 1370, 2nd floor, Montevideo, Uruguay.

It is a condition for this service that the client has acquired original licenses of Urudata products and since then has had this service without temporary interruptions. This service is carried out so that the licensed software can be adapted to the new technical requirements and to the advances in the development of the software, for such reason it covers the totality of the licensed software, not admitting partial licenses of any type.

Framework: Within the framework of this service, Urudata provides the Client with all update patches of the licensed software for which the service is contracted that are developed by Urudata within 2 years of the release of the version of the licensed software.

To that effect, the Client shall communicate to Urudata its interest in being provided with the update patches that have been developed no less than 20 days in advance.

Urudata guarantees the existence of update patches for the licensed software up to 2 years after the release of the version to the market, being absolutely irrelevant the moment in which the respective license was granted.

Upon expiration of the 2 years after the release of the licensed software version, Urudata shall have no obligation to continue developing or providing update patches.

Option for new versions: In the event that Urudata develops new versions of the licensed software, the Client shall have the right to substitute the licensed software for the new versions, free of charge, except for any consulting fees that the Client may decide to hire. For such purposes, the Client shall request Urudata to provide the new version of the licensed software no less than 20 days in advance.

When the Client chooses to use the new version of the licensed software, Urudata shall not be obliged to provide upgrade patches for the previous versions, but shall be obliged to provide upgrade patches for the “new version of the licensed software”.

Urudata guarantees the existence of update patches of the new version of the licensed software up to 2 years after its release, being absolutely irrelevant the moment in which the licensed software was chosen to be replaced by the new version of the licensed software.

Upon expiration of the 2 years after the release of the new version of the licensed software, Urudata shall have no obligation to continue to develop or provide upgrade patches.

Use of Software: The Client may use the licensed software, plus upgrade patches or, if applicable, the new version of the licensed software and/or its upgrade patches, only under the licensed conditions, systems and number of users.

Implementation: The implementation service for the implementation of the upgrade patches of the licensed software, or as the case may be, the new version of the licensed software and/or its corresponding upgrade patches, is not included in this contract. All expenses and implementation fees that the customer decides to hire, will be charged to the Customer.

Term: This service has a duration of one year, or the term established in the commercial conditions of sale, if different from one year. The starting date is established in the agreed commercial terms.

Assessment of damages: The damages caused by breach of this contract shall never exceed the price established in the licenses granted to which this service refers.

In no case shall Urudata be liable for the malfunction of the software licensed or provided, which is caused by the misuse of the software by the Client and/or its employees or dependents and/or by the defects or impossibilities of the computer equipment available to the Client, or any infrastructure defect or conditions of the computer center that are inappropriate for the correct operation of the software.

🔗 https://qflowbpm.com/terms-and-conditions/ Copy URL
Discover Qflow
Request a demo now and get ready to boost your organization’s workflows with our BPM software.