Test the demo application
Last updated
Was this helpful?
Last updated
Was this helpful?
OK, ready to test! The Zentitle UI server side should be set up. You will have edited the config file and placed it in the demo app folder.
We will now start a range of tests back and forth between the desktop and the server-side Zentitle UI. Please have both open on your monitor so you can take action and then see what happens in both directions.
Now we can run our application from an IDE, e.g., Visual Studio. If you want to run an app from docker see the article about .
In the downloaded folder, once you have edited the .json config file, you will run: ZentitleSaaSDemo.sln in your IDE.
This will open up a login window. Here, you can enter the dummy username and password in the .json file - the key is that the file has a valid activation code in the Zentitle dashboard to log in.
Once you log in, you will see the dummy app emulating a server-based SaaS app with controls of the available features and usage-based controls for Consumption Tokens, Element Pools, and Floating Features.
Here, you can see the user we logged in with.
In addition, we can see the app using the attributes we set (of Company and plan) embedded in the app on the main page. This allows you to do all sorts of interesting things in your app, where you can set key-value pairs for every entitlement, which is useful for customizing your apps any way you wish.
Using Zentitle entitlement feature controls, we can turn certain menu items on and off, emulating a "good, better, best" type of offering where the user can upgrade between editions based on features allowed.
The last menu item, “License,” will open a page that contains all information about activation and entitlement.
To reload entitlement data, just click the Elevate Sass logo placed in the top left corner.
In addition, we can test the "seats" allowed per the offering controls and check the tracking of seats and associated limits.
On the first page of the demo app, you should see the words that are using your attributes under the welcome text. You can also change this and refresh the app from the top left logo to see data changes in real-time.
As we see above, the demo app uses Boeing and Standard plans on the app and on the Zentitle Dashboard.
Now, let's change the "attributes" on the Zentitle Dashboard and re-check. We changed it to Lockheed and Gold on the Zentitle Dashboard, refreshed it, and now you can see those changes in the app.
The rest of the menu items are "features" that start all enabled, and we can go back to the Zentitle dashboard to disable some of them to check that this control works.
Let's disable the Calendar and Collaboration features and re-check. Above you can see that the app now has disabled the two features we changed on the entitlement on the Zentitle Dashboard.
Click the checkout button to test this feature, then go back to the Zentitle Dashboard to check the data is passing back and forth.
As we can see, the changes on the app are reflected on the Zentitle Dashboard correctly. We can reverse the process by clicking the "return" button on the same page of the demo app.
Now, let's try the same process for floating features.
Click the checkout button and repeat the process of checking the Zentitle Dashboard. Now we can see we have set one active floating feature, and it shows both ends.
Finally, let's try using a Consumption Token.
Click the checkout button, again we see the 100 > 99 tokens, and we see one consumed on the Zentitle Dashboard.
The last menu item, “License,” will open a page that contains all information about activation and entitlement.
This page shows a lot of useful data. It illustrates areas from the API that could be useful in your app.
In particular, you can review the lease timings, so when will the app call back to the server to check the entitlement details etc.
We can also see the usage-based control test options, where we can change the values in the demo app and see those values change on the server side and also see them limit access once they hit the limits set, such as Element Pools ().
Floating Features ().
Consumption Tokens ().
Next, let's try the various . First, let's test the Element pools. We can see two are available, and we can check out one to show that interaction.
