The most direct way of enacting a process is by identifying a location in the application from which a process instance must be started. Code must then be inserted at that point to call the enactment service API. This API allows the developer to specify the name of the process to start and to supply the enactment data required by the process.
While enacting a process in this way is simple and intuitive, it does have the draw back of being hard coded in the application logic. This being the case, alterations such as removing the enactment, changing the process to start or indeed even minor changes to the required enactment data will require code changes and redeployment of the application.
Further details on enacting processes from code may be found in the Process Enactment chapter of the Cúram Workflow Reference Guide.