Skip to main content
Version: ACE 5

Setup ACE environment

Accessing the application​

ACE Designer is available in Web and Desktop versions.

Web environment​

Using one of the following

  • Open Designer Web application installed in your environment
  • Open Designer Web application running in local docker instance
note

Environments set up to require authorization will ask for login. Make sure you have been granted the necessary credentials to access ACE.

Desktop environment​

  1. Download and run installer here
  2. Open the ACE Designer client
  3. Get access to euadigportalcoredev02acr.azurecr.io/ace-runtime-server image

macOS: allowing the first launch​

The macOS build is code signed but not notarized by Apple, so the first launch after each download is blocked with "Apple could not verify "ACE Designer.app" is free of malware that may harm your Mac or compromise your privacy." This is expected. To clear it:

  1. Open the downloaded .dmg and drag ACE Designer.app into Applications. Approving the app while it is still on the mounted disk image does not persist.
  2. Double-click the app in Applications, then press Done on the warning.
  3. Open System Settings → Privacy & Security and scroll down to Security. Press Open Anyway on the "ACE Designer.app" was blocked row and authenticate.
  4. Press Open Anyway once more on the final prompt. Every later launch starts without a prompt.

The approval is stored per download, so each new version needs it once. If you prefer the terminal, this clears the block with no dialogs at all:

xattr -dr com.apple.quarantine "/Applications/ACE Designer.app"
note

If macOS instead reports that the app "is damaged and can't be opened", you are running a build older than the switch to .dmg packaging — those were distributed as a .zip and were unsigned. Download a current build, or use the xattr command above.

note

ACE Desktop uses external ACE runtime (http://localhost:5050) for API and flow testing. This endpoint can be used for developing applications locally.

ACE runtime must be started manually for flow and API testing to work.