Joget DX 8 Stable Released
The stable 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.
Table of Contents |
---|
...
An Enterprise user is someone who needs to login to Joget Workflow 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.
The Enterprise Edition comes default with "3 Users free". The "3 users" refer to users who can login to Joget Workflow. In the image below, the 3 free users will always be the first three in the user listing (username sorted alphabetically). If 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 Workflow Admin web console (http://localhost/jw/web/login), scroll to the bottom of the screen and click on "License: Joget Workflow v5 Enterprise".
The following window will appear with the system key and license activation form.
Or you can read this how-to article, "How to Activate Your Joget Workflow Enterprise License?"
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.
You can update your Joget by following these steps:
Note: If the Workflow Designer does not show the correct build number in the window title, you will need to clear the Java Web Start Cache for your client machine.
For Windows :
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-6.0.18\logs and locate the log files.
Yes. You can protect the apps you develop on Joget Workflow 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. App license and protection can be requested from our License site.
Please refer to this article: How to Activate Copy-Protected Joget Workflow Apps.
Joget Workflow runs on the Java platform, you can monitor the Java VM using tools like VisualVM.
The process image generation may have failed, please refer to Process thumbnails not showing.
...
...
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 JogetWF feature to allow submission of a form before starting a process by mapping the form to the "Run Process" activity. Also, the administrator can stop a process while it is running.
...
A user is someone who needs to login to Joget Workflow 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.
"3 users" refer to users who can login to JogetWF. In the image below, the 3 free users will always be the first three in the user listing (username sorted alphabetically). If user "cat" is deleted, then "david" will be one of the 3 free users.
...
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 automatically kick-start another process after one ends, using the JSON plugin.
This one depends on your preference. If your IT team is comfortable with Linux, then by all means run JogetWF on Linux. However, you will need to write a start-up script to auto start JogetWF. As for Windows, you can start the server as a service in order to auto start.
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 previerw image for each process can take a longer time.
<span style="color: #222222">However, if you still 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 "</span>javajava.lang.OutOfMemoryError: Java heap space" exception in the 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).
Wiki Markup
1. Stop JogetWF.
the Joget server.
2. Open and edit \ [Joget Installation Directory\]/joget-start.bat.
3. Modify <span style="color: #484848">set Modify set JAVA_OPTS=</span><span style="color: #484848"><strong>--XX:MaxPermSize=128m</strong></span> <span style="color: #484848"><strong>-Xmx512M</strong></span> <span style="color: #484848">-128m -Xmx512M -Dwflow.home=./wflow/</span> on line 13 to <span style="color: #484848">set on line 13 to set JAVA_OPTS=</span><span style="color: #484848"><strong>--XX:MaxPermSize=256m</strong></span> <span style="color: #484848"><strong>-Xmx1024M</strong></span> <span style="color: #484848">-256m -Xmx1024M -Dwflow.home=./wflow/.</span>
4. Save and start JogetWFthe Joget server.unmigrated-wiki-markup
Note: If you get a "black" preview image instead of the process preview image, you will need to delete the generated images located in \located in [Joget Installation Directory\]/wflow/app_xpdlImages/\[App Id\] and refresh your browser. A new image will be generated again.
...
In your Joget Workflow Admin web console (http://localhost/jw/web/login), scroll to the bottom of the screen and click on "License: Joget Workflow v3 Enterprise". A window will appear with the system key and license activation form.
...
...
...
You can update your Joget by following these steps:
Wiki Markup |
---|
Delete "jw" folder, "jwdesigner" folder, "jw.war" & "jwdesigner.war" in your "\[Joget Installation Directory\]/apache-tomcat-6.0.18/webapps". |
Wiki Markup |
---|
Delete "jw" folder, "jwdesigner" folder in your "\[Joget Installation Directory\]/apache-tomcat-6.0.18/work/Catalina/localhost". |
Wiki Markup |
---|
Place the downloaded "jw.war" & "jwdesigner.war" in "\[Joget Installation Directory\]/apache-tomcat-6.0.18/webapps". |
Note: If the Workflow Designer does not show the correct build number in the window title, you will need to clear the Java Web Start Cache for your client machine.
For Windows :
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.
Wiki Markup |
---|
Go to *\[Joget installation folder\]\apache-tomcat-6.0.18\logs* and locate the log files. |
Yes. You can protect the apps you develop on Joget Workflow 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. App license and protection can be requested from our License site.
Please refer to this article: How to Activate Copy-Protected Joget Workflow Apps.
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 on "Mobile View Disabled".