Joget Workflow v6 Beta Released
Check out the latest Joget Workflow v6 Beta for many new features and improvements in user experience (UX), app maintainability and performance.
The following FAQs were compiled from emails we received from customers and partners.
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 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. By default, forms are open to the public (no login required) unless they are mapped to a "group", "department" or "user" under participants.
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.
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.
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 JogetWF.
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 JogetWF.
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.
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:
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.