Publishing workspace

ACE is directly integrated with GIT, which means that data is stored in a GIT repository, and is not directly pushed to server.

API testing endpoints vs Deployed APIs

It's important to understand that APIs called from Designer (starting with https://<designer-url>/dev/api/) are not the same as APIs deployed to runtime server (starting with https://<runtime-server-url>/).

Testing APIs are used to test changes from Designer and never should be used outside of Designer (e.g. integrating with other applications). These APIs start with /dev/api/ prefix which is not present when APIs are deployed to runtime server.

In order to use APIs outside of Designer, they need to be deployed to runtime server.

Deploy workspace changes

Typically, deployment in development environment is set up using CI/CD pipeline, which is triggered by GIT push events.

For example any change to main (e.g. develop) branch triggers the pipeline, which deploys the changes to the development environment.

Changes can be direct save to the main branch or pull request merge.

However, deployment might take some time to complete, especially in file based storage, so it's recommended to avoid editing main branch directly and use feature branches for development.

See more info in deployment section.

View deployed changes

If CI/CD is set up as described above, then in development environment published changes should much workspace in main branch, but it's not guaranteed as pipeline may fail.

It is possible to see deployed APIs by navigating to https://<runtime-server-url>/api-docs (requires that ACE_API_DOCS_ENABLED is set to true).

Currently, it's not possible to see deployed flows or other entities, except APIs.