Use the @add-package comment to manually add a dependency to your process. To specify a version, use the syntax: @add-package <package-name>=<version>. See the documentation for details. For example:

To prevent breaking active schedules, webhooks, or forms that trigger a process execution, modules referenced in any process can no longer be renamed or deleted. Attempting to do so will display an error message:

Or if you are using Rest Api:

YepCode modules, now support aliases like processes do, so you have more flexibility to face source code evolutions and deployments to production environments. See aliases details on our docs.

All our executions allow you to add a comment, which you can provide when starting a process through our UI, via our API, or now even when initiating an execution using a webhook!

Simply include the header "Yep-Comment," and your comment will be stored.

Don’t forget, you can search for executions by their comments, making it easy to track status, results, or logs.

Run any business logic when a new message is received from the queue.

Check the docs for more details.

With the v3.0.0 version of YepCode CLI, we allow to install the dependencies that your team has configured in its workspace (see yepcode.io/docs/dependencies for docs).

We start to use ~/.yepcode folder to store both the login credentials and the installed dependencies.

This allows to add (and then push) a local created variable as sensitive.

Each YepCode process may have some input parameters that are defined with a JSON Schema. In our UI, form validation is always done, and now, with this new feature, you could also perform validations on webhooks or API invocations:

This is an infrastructure improvement that would fix some issues we are having with on-prem installations where the executor layers are killed by autoscaling cluster configurations.

This comes to improve the performance that the keywords search had.