> For the complete documentation index, see [llms.txt](https://activiti.gitbook.io/activiti-7-developers-guide/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://activiti.gitbook.io/activiti-7-developers-guide/overview/comformance/set-1-basic-service-tasks.md).

# BPMN Comformance Set 1

These scenarios cover the use of BPMN Service tasks and the events generated by processes including these kind of tasks. In order to cover the side effects that can be caused by an external (third party integration), these scenarios cover and validate the changes in process variables. The [source code of these tests can be found here](https://github.com/Activiti/Activiti/tree/develop/activiti-spring-conformance-tests/activiti-spring-conformance-set1).

![](/files/-Lgkw2xseWslgqpv1Uxm)

* [Service Task with Implementation](https://github.com/salaboy/bpmn-scenarios/blob/master/processes/ServiceTask%20with%20Implementation.bpmn20.xml)
  * Check that the process start and the status after start is COMPLETED, due the Connector is a sync operation
  * Check that the connector logic is executed
  * Check that the following Events are emitted
  * **Start Process Operation**
    * PROCESS\_CREATED
    * PROCESS\_STARTED,
    * ACTIVITY\_STARTED,
    * ACTIVITY\_COMPLETED,
    * SEQUENCE\_FLOW\_TAKEN,
    * ACTIVITY\_STARTED,
    * ACTIVITY\_COMPLETED,
    * SEQUENCE\_FLOW\_TAKEN,
    * ACTIVITY\_STARTED,
    * ACTIVITY\_COMPLETED,
    * PROCESS\_COMPLETED
* [Service Task with Implementation and Variables](https://github.com/salaboy/bpmn-scenarios/blob/master/processes/ServiceTask%20with%20Implementation.bpmn20.xml)
  * Check that the process start and the status after start is COMPLETED, due the Connector is a sync operation
  * Check that the connector logic is executed and the variable modified
  * Check that the following Events are emitted
  * **Start Process Operation**
    * PROCESS\_CREATED
    * VARIABLE\_CREATED
    * PROCESS\_STARTED,
    * ACTIVITY\_STARTED,
    * ACTIVITY\_COMPLETED,
    * SEQUENCE\_FLOW\_TAKEN,
    * ACTIVITY\_STARTED,
    * VARIABLE\_UPDATED
    * ACTIVITY\_COMPLETED,
    * SEQUENCE\_FLOW\_TAKEN,
    * ACTIVITY\_STARTED,
    * ACTIVITY\_COMPLETED,
    * PROCESS\_COMPLETED
  * Check that the VARIABLE\_UPDATED event contains the modified value
* [Service Task without Implementation](https://github.com/salaboy/bpmn-scenarios/blob/master/processes/ServiceTask%20without%20Implementation.bpmn20.xml)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://activiti.gitbook.io/activiti-7-developers-guide/overview/comformance/set-1-basic-service-tasks.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.