Is anyone serving up tasks to external users via embedded Sail? What do you do a

Currently the alerts that go out can only point to the congifuration you have in custom.properties
conf.suite.SCHEME=
conf.suite.APPLICATION_CONTEXT=
conf.suite.SERVER_AND_PORT=

If you have configured your setting to your embeded URL then you need to handle the url on the other web application accordingly.
Example:
The email task link will be like this
conf.suite.SCHEME://conf.suite.SERVER_AND_PORT/conf.suite.SERVER_AND_PORT/tempo/tasks/task/14

Part of the url "tempo/tasks/task/14" should be handled accordingly.

OR

You can disable notification emails: forum.appian.com/.../Configuring_Notifications.html

Keep in mind changing, changing below to other than Appian will break direct Appian access.
conf.suite.SCHEME=
conf.suite.APPLICATION_CONTEXT=
conf.suite.SERVER_AND_PORT=

Yeah, that's not really the solution I'm looking for. Everything needs to stay as is for 99% of the tasks we assign.

If we started using embedded Sail, we'd have two tasks that will be accessed through a different UI (not Appian) and so need to not trigger a task notification. (Or trigger one that points to the custom UI).

Since it doesn't sound like that is possible, I'm thinking embedded Sail is not the right solution. Thanks!