Process Instance Landing

As FNZ Studio is a web application, all the interactions with the platform are done through HTTP requests.

Thanks to this, when users access FNZ Studio through a URL, the platform can direct them to a specific Process or landing page, creating a seamless entry experience.

Moreover, unauthenticated users may be guided through login and automatically redirected to the correct Process once authenticated, resulting in a smoother journey.

Custom Process Start

A first use case is when you need a custom Process (other than the default one) to start when landing on a specific website address (e.g. community.appway.com). For example, users can start an onboarding process or continue with the approval process by following the respective URLs shared with them.

To do so, you first need to set your custom Process to run as the default Process upon start:

In FNZ Studio Composition, go to System Configuration > Configuration Properties.
Click on the menu icon in the upper left corner, and click on Edit Server Configuration.
Add the following line in the config, where {PROCESS_ID} is the name of your Process such as 'Portal':
Copy
```
    nm.window.start=REDIRECT:/process/{PROCESS_ID}
```
If your instance has a context path, you need to add this to the URL of the nm.window.start property. For example, if the FNZ Studio instance is available at this URL: http://localhost:8080/mycontextpath/admin/, the configuration should be:
Copy
```
nm.window.start=REDIRECT:/mycontextpath/process/{PROCESS_ID}
```

Note: Instead of hardcoding the context path, you can use the { CONTEXT_PATH } property instead.

Unauthenticated Users' Landing

A second use case is when you have unauthenticated users first accessing a Process URL or the login page mentioned above. These users go through an error screen before landing on the login screen.

To solve this issue, you need to include /internal as part of the URL setup: this creates a new HTTP session for the user who is not logged in. For example, for the landing page, the configuration would be as follows:

nm.window.start = REDIRECT:/internal/entrypoint/Portal/Portal

With this setup, the unauthenticated user first lands on the login page and, after a successful login, they are redirected to the appropriate page. On the other hand, the authenticated user lands on the appropriate page directly.