Joget DX 8 Beta Released
The beta release for Joget DX 8 is now available, with a focus on UX and Governance.
The following FAQs were compiled from emails we received from customers and partners.
Since Joget is a builder and also a runtime, a Joget server is required to run Joget apps. But Joget apps that you built will always belong to you where you can permanently keep with you and even resell as a solution and etc.
Joget, Inc. is the principle of the Joget platform, where as apps you build on Joget will always belong to you.
Joget is capable on all 3 development angles:
Aside from the plethora of elements and templates available in the platform by default, for small/specific customizations there are places where you can insert custom back-end/front-end code into, and for highly customized functionality you can easily extend the Joget platform capabilities via our extensive plugin architecture.
Joget is agnostic on this aspect. The apps can be as simple as a customer-facing contact form, or even as complex as per your needs regardless of being an internal or external app.
There are various angles where you can add customizations to the platform, and for bigger customized functions, you can take advantage of the Joget plugin architecture which provides plenty of integration angles from the form aspect, list, process, UI, and etc.
Joget can scale vertically and horizontally via server clustering and containerization.
The specs depends on a wide number of aspects such as concurrent users, processing intensity, database usage, amount of data generated in each app, and so on.
An Enterprise user is someone who needs to login to the Joget platform to use the system.
If a form requires the person to "login" before he/she can use the form, then that person is a user and requires a user license. And the user licensing is based on named user licensing model.
The Enterprise Edition comes default with "3 Users free". The "3 users" refer to users who can login to the Joget platform.
In the image below, the 3 free users will always be the first three in the user listing (username sorted alphabetically). So for example, ff user "cat" is deleted, then "david" will be one of the 3 free users.
If you have applied a trial activation for more than 3 users, please take note that when the trial license expires, it will revert the license back to the 3 free users as define above. Before the trial license expires, it is very important to ensure that the "admin user" is one of these 3 users; or there will not be any user with administrator access to the system.
In your Joget Settings page, you can see the system information and license details with a clickable license link that opens a popup to key in your license key. You can find your system key here.
Do see Activate your Joget DX Enterprise License for more info.
This one depends on your preference.
If your IT team is comfortable with Linux, then by all means run on Linux. However, you will need to write a start-up script to auto start the server.
As for Windows, you can start the server as a service in order to auto start.
Do check out our Upgrade Guide.
When an error is thrown, a stack trace will depict a sequence of events executed in the code level which can precisely suggest the point where an exception is caught.
Stack trace can also suggest meaningful error messages to help troubleshooting. The stack trace will be logged into the logs folder of the server container, Apache Tomcat.
Go to [Joget installation folder]\apache-tomcat-x.x.xxx\logs and locate the log files.
Or alternatively, you can also directly view the system logs in Joget via the admin bar, do see Web App Log Viewer.
Yes. You can protect the apps you develop on Joget against unauthorized copying and distribution.
Protected apps will be assigned to a License Holder (owner) and will require an "app license" to activate and use.
Please refer to this article, Activate Protected App.
Joget runs on the Java platform, you can use external tools like VisualVM to monitor the Java VM.
Or, you can also easily monitor your system's performance metrics via the Application Performance Management to view overall system metrics and even as granular as per individual apps.
The process image generation may have failed, please refer to this helper guide, Process thumbnails not showing.
Yes; a datalist can be used for this. Actual columns and data will depend on how you build the datalist.
Yes; apps (processes, forms, datalists and userviews) can be deleted, imported and exported.
If your process requires users to "reject" or "cancel" a task, it can and should be designed into your process itself.
For example, in your form, include an option to "accept", "complete" or "reject". Or use a feature to allow submission of a form before starting a process by mapping the form to the "Run Process" activity.
Also, the administrator can manually stop a process while it is running. And to allow end users to withdraw their own started process instances, you can also take advantage of the Process Enhancement Plugin from the Joget Marketplace.
Yes. By default, forms are open to the public (no login required) unless they are mapped to a "group", "department" or "user" under participants. You can manage permissions for the various components in your app via Permission Control.
Yes. You can design your process to "route" to an activity ("request for more information or comments") and route back to the last approver after its completion.
Yes. Use the ID Generator Field element in Form Builder to generate a running number. The ID Generator field is a read-only field.
Yes. Form Builder allows users to add multiple rows (with support for simple calculations) of items.
Yes; you can export the whole app to backup. Do see this guide, Import and Export Apps and App Configuration Management.
You will get this only when you're viewing the process for the first time and only if your process is very complicated, with many activities. It will then require some time to generate the image.
Sometimes, it can also take very long because of multiple processes in your app. Generating the preview image for each process can take a longer time.
However, if you still can't get the image displayed correctly after a long time and even after you have refreshed your browser, you probably have a "java.lang.OutOfMemoryError: Java heap space" exception in the backend. This is due to the image being too large, thus, requiring more memory to process the image preview. In that case, you may need to increase your Tomcat memory setting by following the steps below (which will double the default memory setting).
1. Stop the Joget server.
2. Open and edit [Joget Installation Directory]/joget-start.bat.
3. Modify set JAVA_OPTS=-XX:MaxPermSize=128m -Xmx512M -Dwflow.home=./wflow/ on line 13 to set JAVA_OPTS=-XX:MaxPermSize=256m -Xmx1024M -Dwflow.home=./wflow/.
4. Save and start the Joget server.
Note: If you get a "black" preview image instead of the process preview image, you will need to delete the generated images located in [Joget Installation Directory]/wflow/app_xpdlImages/[App Id] and refresh your browser. A new image will be generated again.
Mobile view for your apps are enabled by default. An app can have multiple Userviews. To disable the mobile web view for a Userview, go to your app "Userview" and under "Settings", check the "Mobile View Disabled" property.