In domino leap it's possible to connect from one app to another app by service e.g. to read basic data from a central app. The app id of the refered app is stored within the service information.
When moving apps between servers by export/import a designer needs to be more aware of app ids in use and also needs more control over it.
Leap reassigns new app ids if there is another app with this id existing or has been existing in the past. E.g. if i import the app to the server, remove it and import it again i suddenly do have a new app id on that app.
Importing apps with a reference to another leap app by it's app id also fails if no app with that id has been found.
Be aware that from a user perspective (e.g. leap manager) this is not plausible and without administration rights and notes client not controllable or fixable.
Here are some suggestions for improvement:
a) In case the app id was modified on import, there should be at least a warning for the developer. In some apps this might be a critical information.
b) Also enforcing the app id with an import option "retain app id" should be possible, as long as this app id is not being used currently by an active app. In that case there should be an import stop with information that this app id is already in use and can't be enforced.
c) If i try to import an app that refers to another app by app id the import should not fails with a generic error message but inform the developer that the referred app can't be found. Probably an option to switch to another existing app (or basically the same app with just a different app id) might be very helpful.
d) In leap designer there should be some basic "in your face" information if the currently edited app is standalone or if it is referring to another leap app or rest service based 3rd party app/software.
