Hi all.. New to Appian here. I've got a general question regarding applications in Appian. What is the use of an application apart from its ability to group related design objects? Also I'm able to refer rules from a different application in current application. What are the boundaries and best practices of an application? Can there be circular references between applications and What are it's impacts?
Discussion posts and replies are publicly visible
Welcome! An Application is purely a method to group related design objects, to organize development and provide deployment package creation.
Objects can be included in multiple applications, there are no native impacts but it can create concerns with 'loose' deployment practices where say, a developer includes all objects updated this week in a patching package. If shared objects contained in this application are in a different deployment cycle (say, still in testing), they would be erroneously deployed. For this reason, I typically recommend including only objects specific to a certain solution to be included in the application bundle.
But yes, generally these applications are only for design organization.
An object can be referenced in any number of applications / packages, but applications can't refer to each other, so there's no chance of circular references per se.
An application used to have a somewhat more important feature while Tempo was the primary user-facing UI, as certain process models could be published as "actions" that would appear in the general Tempo "actions tab", however this has now been all but deprecated (and i recommend against it in general, other than toying around with it to see what we used to have to deal with).
These days, as Chris said already it's mainly an organizational tool for deployment / sprint / hotfix management (etc). I run O&M (among other things) for my org, and one trick I use is to create a monthly "hotfixes" application right away in Dev at the beginning of each month, with a catch-all "rolling ad-hoc hotfixes" package declared to add things that I need to push into the higher environments but which don't warrant their own JIRA ticket/etc.
Mike Schmitt said:An application used to have a somewhat more important feature while Tempo was the primary user-facing UI, as certain process models could be published as "actions" that would appear in the general Tempo "actions tab", however this has now been all but deprecated (and i recommend against it in general, other than toying around with it to see what we used to have to deal with).
Additionally, "Publishing" applications also makes them become listed in your Tempo dropdown below, along with your Sites - however the published application links to the OLD OLD "Apps" (Portal) environment - not to be confused with the current/new Portals functionality. If you don't know, don't ask *shudder*. I assume this will be removed when the deprecated /apps environment is completely removed.
Chris said:OLD OLD "Apps" (Portal) environment
Funny you should mention that - i was just wondering to myself last night whether /suite/apps is still accessible in modern versions. Talk about a ghost town, lol.
Mike Schmitt said:Funny you should mention that - i was just wondering to myself last night whether /suite/apps is still accessible in modern versions. Talk about a ghost town, lol.
Yep, no removal for /apps yet as of 22.4 (we are starting our upgrade). I'm sure there are some older customers on it still, we just got our last app out of there a few months ago
Thanks for clarifying Chris!
Thanks for the clarification and pointing out its relevance in older days Mike..