Configuring a Start Processor

The start node serves as the the start of a function flow.

Notes and Constraints

Function flows created in Data Workroom (DWR) can only be viewed on the FunctionGraph console; editing and deletion must be done within DWR.
Each function flow must start with only one Start node and end with an End node.
The start node must be followed by a node that is not stop or error handling.
Only triggers can be configured for the Start node.
- Flow triggers include APIG (dedicated) and timer triggers.
- A flow can have a maximum of 10 triggers.
- Triggers must be included in the start node.
- Triggers cannot be connected to any other node.

Timer Trigger Configuration Description

Click the Start node. On the displayed page, click Create Trigger, set Trigger Type to Timer, and set other parameters, as shown in Table 1.

Figure 1 Timer trigger
Click to enlarge

**Table 1** Timer trigger information
Parameter	Description
Trigger Type	Select Timer.
Rule	Triggering rule of the timer. Currently, only cron expressions are supported.
Cron Expression	Specifies the date and time when the flow will be scheduled. For details, see Cron Expression Rules.
Additional Info	Must be in JSON format and contain an input. The value of input will be passed to the flow.

APIG (Dedicated) Trigger Configuration Description

APIG flow triggers support only IAM authentication.
Ensure that you have created a dedicated gateway before this operation. For details, see Buying a Dedicated Gateway.

Click the Start node. On the displayed page, click Create Trigger, set Trigger Type to API Gateway (dedicated), and set other parameters, as shown in Table 2.

Figure 2 API Gateway (dedicated) trigger
Click to enlarge

**Table 2** APIG (dedicated) trigger information
Parameter	Description
Trigger Type	Select API Gateway (dedicated).
Gateway	Select a dedicated gateway. For details, see Creating a Gateway.
API Group	An API group is a collection of APIs. You can manage APIs by API group. For details, see Creating an API Group.
Environment	An API can be called in different environments, such as production, test, and development environments. APIG supports environment management, which allows you to define different request paths for an API in different environments. To ensure that the API can be called, select RELEASE.
Visibility	Options: Public: The API can be released to KooGallery. Private: The API will be excluded when the API group to which it belongs is released on KooGallery.
Path	Path for requesting the API. Format: /users/projects
Method	The API calling method. Options: GET, POST, DELETE, PUT, PATCH, HEAD, OPTIONS, and ANY. ANY indicates that the API can be called using any request method.