> 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-6-basic-signals.md).

# BPMN Comformance Set 6

This scenario covers Signal events in different combinations. The [source code of these tests can be found here](https://github.com/Activiti/Activiti/tree/develop/activiti-spring-conformance-tests/activiti-spring-conformance-signals).

![](/files/-Lgm_jUcVaL_yGRTUnXD)

* [Process throwing a signal event](/activiti-7-developers-guide/overview/comformance/set-6-basic-signals.md)
  * **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

![](/files/-Lgm_jUelmkcgdnRWIkU)

* [Process with signal intermediate catch event](/activiti-7-developers-guide/overview/comformance/set-6-basic-signals.md)
  * We should have the following events after starting this process (process is waiting for matching signal):
  * **Start Process Operation**
    * PROCESS\_CREATED
    * PROCESS\_STARTED
    * ACTIVITY\_STARTED
    * ACTIVITY\_COMPLETED
    * SEQUENCE\_FLOW\_TAKEN
    * ACTIVITY\_STARTED
  * **Signal Operation**
    * We should have the following events after a matching signal is sent:
    * SIGNAL\_RECEIVED
    * ACTIVITY\_COMPLETED
    * SEQUENCE\_FLOW\_TAKEN
    * ACTIVITY\_STARTED
    * ACTIVITY\_COMPLETED
    * PROCESS\_COMPLETED

![](/files/-Lgm_jUieAhkYJpGgfng)

* [Process with signal boundary event](/activiti-7-developers-guide/overview/comformance/set-6-basic-signals.md)
  * We should have the following events after starting the process
  * **Start Process Operation**
    * PROCESS\_CREATED
    * PROCESS\_STARTED
    * ACTIVITY\_STARTED
    * ACTIVITY\_COMPLETED
    * SEQUENCE\_FLOW\_TAKEN
    * ACTIVITY\_STARTED
    * TASK\_CREATED
  * We should have the following events after sending a signal matching with boundary signal event:
  * **Signal Operation**
    * SIGNAL\_RECEIVED
    * TASK\_CANCELLED
    * ACTIVITY\_COMPLETED
    * SEQUENCE\_FLOW\_TAKEN
    * ACTIVITY\_STARTED
    * TASK\_CREATED

![](/files/-Lgm_jUm0NCT7zG3mft1)

* [Signal start event](/activiti-7-developers-guide/overview/comformance/set-6-basic-signals.md)
  * We should have the following events when a signal matching the signal start event is sent:
  * **Signal Operation**
    * SIGNAL\_RECEIVED
    * PROCESS\_CREATED
    * PROCESS\_STARTED
    * ACTIVITY\_COMPLETED
    * SEQUENCE\_FLOW\_TAKEN
    * ACTIVITY\_STARTED
    * ACTIVITY\_COMPLETED
    * PROCESS\_COMPLETED


---

# 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:

```
GET https://activiti.gitbook.io/activiti-7-developers-guide/overview/comformance/set-6-basic-signals.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.