|
|
@@ -3,7 +3,7 @@
|
|
|
Mock Activity Endpoint.
|
|
|
Automated activity enactments must be HTTP calls where users must specify the endpoint in the FTG's Transformation, and the timeout in the PM's Activity.
|
|
|
As an activity gets triggered it requires knowledge of the control and artefact flow.
|
|
|
-This endpoint expects this context in the form a json body following a highly specific format.
|
|
|
+This endpoint expects this context in the form of a json body following a highly specific format.
|
|
|
|
|
|
{
|
|
|
"ctrl": "<name of control port going into the activity>",
|
