Details
-
Type:
Improvement Request
-
Status:
Resolved
-
Priority:
Major
-
Resolution: Fixed
-
Affects Version/s: 1.1.0
-
Fix Version/s: 1.2.0
-
Component/s: Monitoring (Business)
-
Security Level: Public
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|
|
||
Activity
| Transition | Status Change Time | Execution Times | Last Executer | Last Execution Date | |||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
|||||||||
|
|
|
|
|
| Description |
The Petals SE Flowable must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if defined in the incoming exchange creating new process instance, the flow tracing activation should be propagated to all service providers invoked during the process instance execution according to the flow tracing activation propagation defined in the service consumer definition or at component configuration. |
The Petals SE Mapping must support the MONIT trace filtering (see PETALSDISTRIB-395).
Moreover, if defined in the incoming exchange, the flow tracing activation should be propagated from the service provider side to the service consumer side according to the flow tracing activation propagation defined in the service consumer definition or at component configuration. |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Resolution | Fixed [ 1 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | Resolved [ 10004 ] | Open [ 10002 ] |
| Resolution | Fixed [ 1 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 1.1.1 [ 10871 ] | |
| Resolution | Fixed [ 1 ] |
| Link | This issue blocks PETALSDISTRIB-395 [ PETALSDISTRIB-395 ] |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Field | Original Value | New Value |
|---|---|---|
| Status | New [ 10000 ] | Open [ 10002 ] |
| Priority | Major [ 3 ] | |
| Component/s | Monitoring (Business) [ 10465 ] |
User documentation updated