RE: Display

Robert Shankin — Fri, 22 Jun 2018 17:04:16 GMT

Hi again Jorge -

Think of an application as a logical container (a list, really) for objects.
An application is the easiest way to organize a set of related Appian objects that provide some valuable functionality when used together.
Among the most critical functionality of applications is security and effective transportation of features from one server to another.

Objects can be shared between applications.
Unless objects in ABC application are explicitly secured in a way prevents a designer from accessing them, then that designer can reference an object from ABC application in DEF application.

One object can exists in two or more applications, and this is very common.
As your development practice grows, you'll periodically face the decision of "do I split, or do I share?" There's no one size fits all answer to this question.

Have you seen the Appian Playbook?

RE: Display

jonathan.guillen — Fri, 22 Jun 2018 16:59:01 GMT

Hello Jorge,

We normally use "Quick apps" for jumpstarting demos/initial workshops on new projects. it's a good tool for visualization of how the system can look and how you can interact with the system.

You can find useful information about quick apps within Appian documentation. QUICK APPS DESIGNER and QUICK APPS LIFECYCLE CONSIDERATIONS

I would recommend using a standard Appian application, based on the information provided.

Hope it helps.

Regards.