With the enable tool you can enable or disable process definitions.

 usage:  cm enable -u <user> [other options] [-n <name1> <name2> ... | -i
    <name1> <name2> ...]

 available options:

                 Options                              Description
 -d, --domain <domain name>                  domain for login
                                              (default=<builtin>)
 -g, --grpc-endpoint <gRPC endpoint>         gRPC endpoint to connect to
 --grpc-wfs-endpoint <WFS gRPC endpoint>     gRPC endpoint of Workflow
                                              Server to connect to
 --http-base-uri <HTTP base URI>             HTTP base URI of Content
                                              Server where HTTP servlets
                                              are provided (e.g. blob
                                              servlet)
 -i, --disable <disable>                     names of workflows to disable
 -n, --enable <enable>                       names of workflows to enable
 -p, --password <password>                   password for login; you will
                                              be prompted for password if
                                              not given
 -u, --user <user name>                      user for login (required)
 --url <ior url>                             url to connect to
 -v, --verbose                               enables verbose output

The options have the following meaning:

Editors cannot start new workflows from disabled process definitions. Initially uploaded process definitions are enabled.