All changes to the JobRouter Workflow Designer are listed here, sorted by version
Changes in JobRouter Designer version 5.2
New connection type Remote DB (only in JobRouter Cloud)
A new connection type Remote DB is available for global and process connections. These connections can be used in SQL elements in the dialog and in SQL rules. For more information about Remote DB configuration, please refer to the Administration Guide.
Changes in JobRouter Designer version 5.1
Introduction of a new additional module
Please note: Restrictions has been applied to the usage of some mobile form elements.
As of JobRouter version 5.1, an additional module JobMobile is available.
The Check Archive function of the JobArchive system activity
The Check Archive function requires the allowed file extension xml in the system-wide list of file extensions if the Check Log (XML) parameter is mapped to an attachment field.
Changes in JobRouter Designer version 5.0
New process flowchart
The flowchart designer has been redesigned to make process creation easier and faster.
Elements in the Mobile View
With the further development of the JobRouter app, additional form and subtable view elements can be used in the mobile view. For a better differentiation to the Mobile Client, relevant hints are displayed in the form Designer. Furthermore, the differences have been documented in the chapters concerning forms.
Changes in JobRouter Designer version 4.3
Maintenance mode for processes
In process properties a process can be set to maintenance mode. As long as this mode is active, only users with Process management rights and persons responsible for the process with Process editing rights can open and send steps of this process. All other users receive a message stating that this process is under maintenance.
Regular expressions for text box validation
In the element configuration of text boxes a regular expression can be stored now. This enables a specific verification of the entries, such as the invoice number format. A respective error message can also be stored. This will be displayed, if the validation of an entry fails.
SQL list as selection box
Now any text can be entered as column name. So the name is no longer limited to SQL permitted characters and one language. Process messages can also be used as column names.
Configuration extensions for result columns in SQL tables
•For result columns of the type decimal numbers a new decimal places column is available. Here it can be defined, how many decimal places of the value should be displayed. The value is set on 2 by default.
•Now the new column type HTML is available. This type can be used, if a column contains HTML which should be interpreted as such.
Behavioral change when using result columns in SQL table and SQL list as selection box
Until now the return of SQL queries was displayed completely; configured result columns were formatted accordingly. As of now - when result columns are configured - only these will be considered in the presentation.
When archiving via system action, paths relative to the uploads directory are no longer supported
Archiving and clipping documents via the JobArchive system action now only supports absolute paths if file path has been selected as the data type. The use of file paths relative to the uploads directory is no longer possible.
New system activity JobData
The new system activity JobData can be used to add data records to JobData tables or to delete them from tables.
Changes in JobRouter Designer version 4.2
JobData database connection available
If a JobData database connection has been configured, this form element can be used.
Send/open subsequent step directly
It is possible now to Display the following user step directly to the user. So several user steps can be displayed successively or PHP-sided system activities can be performed directly.
E-mail notification in user system activity
Notifications for new steps, queries/responses and assignments can be configured separately in the system activity settings. Existing system activities must not be adapted.
PDF export in JobArchive system activities
As of now the function PDF export is available in the JobArchive system activities, enabling the export of documents from the archive in the form of PDF files. Here the file can be also exported with JobViewer 2 annotations if the PDF conversion of the file type is supported.
Changes in JobRouter Designer version 4.1
Edit batch as profile setting
The option Edit batch was removed from the step properties and can now be activated for users in the user profiles. If a user activates batch processing in one step, the function is comprehensively active in all boxes and steps.
Ignore upper and lower case letters in the rule conditions
In rule conditions of the type Define query the consideration of upper and lower case letters can be deactivated now.
Wait system actions are excluded during the identification of the system steps that need to be performed.
Wait system actions are excluded during PHP system actions to avoid an unnecessary strain on the server. Thereby, the necessity for implementing the step status request in the system action configuration was eliminated.
The escalation actions from version 2.x will no longer be supported from version 4.2 and higher.
The escalation actions directly defined in the step properties and rules in version 2.x will no longer be supported from version 4.2 and higher. They will be displayed as outdated on the user interface and the admin monitor. Please replace these escalation actions with the step or process escalation actions.
The width of labels within a column is configurable
In the menu Column properties the label width of form elements can be determined within one column. You can set different widths for all available process languages.
Extension of existing form elements
SQL_TABLE
Now any translatable column text can be entered. Therefore headers are not limited to characters and languages permitted in SQL. Also process reports can be used as column headers.
It is possible to determine display properties: You can determine the width, select a data type or hide the column completely.
During configuration the additional properties Sortable, Filter and Paging has to be used. Additionally, to facilitate the migration to new properties, the property Use old structure can be used.
Process message assignment
As of version 4.1.1 the assignment of process messages to elements can be canceled.
Mobile Client
New functions in the mobile views of forms
Mobile forms can be deleted and disabled in the mobile view of forms. In both cases this form will no longer be displayed on mobile devices.
Link for mobile view
If the Mobile Client is selected, a mobile view link is available on the Login page.
Viewer in Mobile Client
For FILE elements in the mobile view it is now possible to determine how the files should be displayed on the device.
LIST AND SQL_LIST elements
You can now integrate list elements in the mobile view of the forms to enable the user to chose between predefined values. Additionally, by using SQL_LIST elements, database queries can be integrated in the form.
JobArchiveShowDocument element
In the mobile view of the form the element JobArchiveShowDocument is available now, which can be used to activate archived documents.
Changes in JobRouter Designer version 4.0
Embed external scripts with full URL
External scripts can be embedded via a full URL. Also the JobRouter URL can be used by using the new jr_jobrouter_url variable.
Change the form element type
It is now possible to change the type of an already existing form element. The values of all properties that are still existing (e.g. name, required field etc.) are not changed.
No longer supported form section properties
The property Folded? and the associated actions onOpen and onClose have been removed. Therefore, it is no longer possible to open or close sections by mouse click and thereby execute JavaScript actions.
Show Manual
All available manuals can now be listed and displayed in the Show Manual menu.
Compact display of forms
As of version 4.0.3 the display of compact forms can be activated in the Process properties. Thereby font size, panel height, symbol size etc. will be reduced.
Export process chart
In version 4.0.3 the process designer is also able to Export the process chart created for the process.
Changes in JobRouter Designer version 3.9
Result of PHP condition functions reversible
It can now be selected in Rules for which return value of a PHP condition function the rule is to be executed. Possible values are true and false. By default, the value true is used.
Process messages expanded
Until now, translations in multilingual processes were always stored directly in the form or sub-table element that was to be translated. Now, translations can also be stored as process messages, which allows their reuse in all elements that are to be translated. In which way the translations are stored can be decided for each process.
Furthermore, process messages can be used in the E-mail text of process and step escalations as well as in step notifications.
Parameter for PHP functions
Parameters can be defined in the configuration of a PHP function. These parameters can be used additionally in rule conditions and action rules when selecting the PHP function.
Storage location and names of the PHP function files changed
The cache directory of the PHP functions was changed from phpfunctions to processes. In this new directory the functions will be stored in {Process name}/{Process version}/phpfunctions/{Function name}.php.
Temporary Job Functions
The Job Function system activity can be used to create a new temporary Job Function and to add users to this Job Function. This Job Function will only be available during the instance.
Changes in JobRouter Designer version 3.8
Mobile view for user forms
Next to the previous desktop view, a mobile view can now be defined for individual user forms. The mobile view is intended for mobile devices with small displays. To be able to use mobile forms, the JobRouter Mobile Client has to be installed additionally. However, it is not yet available.
When creating a mobile view for a user form, only a part of the form element types available in the desktop view can be used. Not available are e.g. sub-table views, SQL tables, IFrames and all module specific form element types. Furthermore, only one column forms with one page are possible for mobile views.
Verify the archive integrity
The integrity of documents archived in JobRouter can now be verified. The new Check archive function of the JobArchive system activity provides a list of all missing and manipulated files of the archive.
Cancel steps
Steps can now be aborted via an action button in the form. Steps can also be aborted via the JavaScript API function jr_execute. A JavaScript event OnAbortConfirm is available.
User specific placeholders for E-mail system activities
In the Send e-mail to JobRouter user function of the E-mail system activity, JobRouter variables can no be used in the subject and E-mail text field. They will be resolved in the context of the user when sent.
Expand process messages
In previous versions, only the languages activated in a process were recognized. Now, the messages can be edited in all languages available for the process.
Until now, translations in multilingual processes were always stored directly in the form or sub-table element that was to be translated. Now, translations can also be stored as process messages, which allows their reuse in all elements that are to be translated. Which way the translations are stored can be decided for each process.
Furthermore, process messages can be exported and imported in the process messages overview.
New PHP function types
The following new PHP function types are available:
•Inbox action functions
•Step initialization functions
Inbox action functions can be linked to the actions of process inboxes. They enable the performance of specific cross-step operations, which facilitate a special kind of batch processing for the selected steps.
Step initialization functions are executed during the loading of the step and can, for example, be used to initialize the process table or sub-tables with up-to-date data from external sources. This is especially important for start steps.
Changes in JobRouter Designer version 3.7
Support of archive profiles
In JobArchive form elements and the JobArchive form integration, optional archive profiles can be used to control user access to documents and result list according to globally defined restrictions. If no archive profiles are used, the user processing a step can access all documents and result lists attached to the step without restrictions. If archive profiles are used, the user's permissions will be checked when opening documents to see if the user has access to these documents via an archive profile. When opening result lists, only the hits complying with the filter set in the archive profile are shown.
Default values and maximum amount of hits added to SQL lists
For SQL_LIST elements, it is now possible to define a default value that will be used if no value is stored in the linked process table field or in the form variables, yet. The new option is called Default value and is available for all three list types: Dropdown List, Autocomplete List and Select Box.
The maximum amount of hits (between 1 and 100) can now be defined for the list type Autocomplete. If no value is entered, the global default value of 10 is used.
Support of annotations added to JobArchive form elements
The setting Allow annotations in JobViewer was added to the JobArchive form and sub-table elements. The user can add annotations to the opened document, if this setting was enabled and JobViewer selected.
Support JobRouter variables [jr_row] and [jr_row_id]
In the SQL_LIST elements of the sub-tables it is now possible to use the row number or the ID of the sub-table row for the SQL query, via the JobRouter variables [jr_row] and [jr_row_id].
Changes in JobRouter Designer version 3.6
New Edit Steps option in process inboxes
A new Edit Steps option is available in the process inbox settings. This option is only available, if the option Show All Instances is active. If Edit Steps is active, all not processed steps can be processed by every user who is allowed to see the process inbox.
JobArchive system activity can now create cache files
It is now possible for the JobArchive system activity to instantly create the cache files for JobViewer when a document gets archived.
Display of subtables in the simulation
The content of subtable fields can now be displayed in the simulator. Furthermore, stored files can be downloaded directly using a link.
Postpone status selectable for inboxes
When editing inboxes, Postpone can now be selected as a new status. This box will only display steps of the process that the user postponed himself.
Status selection can be activated in the inbox filter
When editing inboxes, Status Selection can be activated. Activating it displays the corresponding step status entries in the filter of the inbox.
Returning the number of affected rows in action rules
In the Database tab of action rules, a new option Return number of affected rows is available. It can only be activated, if the option Execute in Transaction is activated. If it is enabled, the number of affected data sets will be returned for SQL queries of the INSERT, UPDATE or DELETE types (not for SELECT queries).
Changes in JobRouter Designer version 3.5
New date field for process tables
JobRouter Version 3.5 offers a new date field for process tables. The new date field will not be saved as UNIX timestamp like the old one, but as true DATETIME field. This allows entering dates later than the year 2038 without problems.
For further information on how to use this function, see this manual.
Please note: We recommend to only use this kind of date field for new processes.
Improved clipboard
The form clipboard was completely reworked and now allows to easily copy single or multiple elements from a form into the clipboard. A comfortable menu allows naming every entry in the clipboard. You can copy form elements, columns, rows, sections and entire sites to the clipboard, allowing you to create forms in JobRouter considerably easier.
For further information on how to use this function, see this manual.
Introduction of rule groups
To simplify the display of rules, rule groups were introduced with JobRouter 3.5. rule groups allow to combine single rules. This clears up the display of the rule groups, as connected rules are easily recognizable (i.e. an allocation and a forwarding rule for the approval of a process). Furthermore conditions can be centrally defined in the rule group and do not have to be repeated in every rule. This eases the modification of rule conditions significantly. Naturally conditions expanding the rule conditions can still be set for single rules.
For further information on how to use this function, see this manual.
Length of process messages adjusted
Until now, process messages could only contain 50 characters. From Version 3.5 on up to 4000 characters can be used. Furthermore, the input field now has multiple lines.
New system step: ShellExecute
The ShellExecute system step is a new function in the process designer to call programs. This system step allows to store the program call and the parameters fixed or create them dynamically from process data. The program is run in the JobServer service, making it significantly more save and stable compared to running it using PHP.
New system action: CSV
This new system step allows to read and write CSV files. This action aids in connecting any CSV file easily to the process and subtables using a configuration interface. It is possible to choose the structure of the file freely (separator, text qualifier, etc.).
New system step: Data-Management
Data-Management allows executing databank actions on tables without the need to write SQL commands. You can add, modify, read or write entries. The tables themselves can be in any database that is connected over JobRouter database connections to the process. Using this step not only spares you from writing the SQL commands, it also masks special characters automatically sparing you from treating them yourself.
Direct execution of PHP functions in a form
The JobRouter JavaScript API offers the possibility to directly execute PHP functions from a form via AJAX using the function jr_execute_form_function. Parameter can be transferred from the form to the function and also from the function back to the form. This allows you to easily implement server side actions in the form.
Changes in JobRouter Designer version 3.4
Renaming of JobArchive to JobShift
The module JobArchive, which shifts old instance data into a separate database, has been renamed to JobShift. From version 3.4 the name JobArchive is used for the new integrated JobRouter archive.
Improved clipboard
It is now possible to also store not only form elements, but also columns, rows, sections and complete pages in the clipboard of the process designer. This allows for comfortable storing and reusing of form parts. A popup window lists all the entries when pasting from the clipboard.
New form events
New events have been added to the form editor to execute scripts when one of the following actions is executed: Assign, Request, Answer, Jump To Step or Postponed. These scripts are called up when the action is executed and can therefore be used to e.g. deactivate elements before sending so they can be submitted to the server. Further information on these events can be found in the JobRouter JavaScript API manual.
Multi-language support (Enterprise Edition)
JobRouter list entries can now be translated into all process languages. For process inbox actions translation can also be added. The only requirement is the allocation of more than one language to the process.
Time zones (Enterprise Edition)
In version 3.4 JobRouter now offers individual time zone settings for the users (for more information see the JobRouter admin manual). Form fields of the DATE type can optionally be converted into the user's time zone.
Escalation notifications to substitute
Escalation messages will now also be sent to the substitute of a JobRouter user in order to guarantee the processing of an instance during an employee's absence. The chapters Process escalation behavior when substitute is active and Step escalation behavior when substitute is active contain a detailed list about the behavior when the substitute rules are active.
Lists and SQL-lists are case-insensitive
When displaying SQL_LIST or LIST elements that are linked to a database field and where a value is predefined, the check of the value will no longer be executed case-sensitively. This means even if the process table contains the value e.g. testvalue and the list entry contains the value TESTVALUE, it will be marked as chosen in future.
Improved displaying of SQL_LIST elements in completed and read-only mode
In JobRouter 3.4 the displaying of SQL_LIST elements was improved so that next to the chosen value the label is also stored. This makes it possible to show data in completed or read-only mode even though they cannot be determined using an SQL statement. Also the SQL statement has no longer to be executed in view mode.
Performance Optimizing when forms are displayed
When trying to display forms with several elements and a high rate of parallel access, the performance in JobRouter was occasionally affected. To counteract this, in JobRouter 3.4 changes have been made to the logic, so the forms are displayed quicker.
Improved auto-complete in SQL_LIST
JobRouter 3.4 now offers an improved auto-complete function for SQL_LIST elements. The new element is based on the JavaScript framework jQuery and is therefore considerably faster and more comfortable to use than the previous element.
Additionally the form element now offers the event OnSelect. This means the event OnChange is only executed if the user leaves the field with his cursor. The event OnSelect is executed when the user chooses an entry from the suggested list.
Changes in JobRouter Designer version 3.3
SQL quote functions
To use SQL form elements and SQL queries securely in the JobRouter designer, special new functions for checking and converting values of variables are available. These functions help increasing the security of applications and offer protection against attacks carried out by dangerous SQL queries.
Changes in JobRouter Designer version 3.2
JavaScript-API
The JobRouter form designer was expanded by a JavaScript API, which fundamentally simplifies working with forms. The API offers default functions for accessing and working with form elements. For more information see the new JobRouter JavaScript API manual.
Extended escalations
Step escalation actions in JobRouter can now also generate allocations to other steps. Additionally it is possible to send e-mail messages to the supervisor of the user the step was allocated to.
Changes in JobRouter Designer version 3.1
Automated saving
When a step is saved, the behavior of the button can be set identically to version 3.0 with the new option Automatic reservation in the step properties.
Changes in JobRouter Designer version 3.0
Process flowchart
•Display of step properties in a properties form window
•Continuous storage of individual elements' position
•Direct redefinition of the individual steps is now possible
•Steps can be inserted at any position in the process map
•Rules
Rules are divided into different rules types to give a better overview. The following rule types are available during process creation:
•Routing rule
Activation of further steps in the process flow
•Termination rule
Definition of the process end
•Assignment rule
Change any number of values in the process table and subtables
•Action rule
Execution of JobRouter rule actions (SQL, Shell, …)
•DocuWare rule
Execution of DocuWare functions
System Activities
Automatic system steps can be bound to a process, for example, to execute DocuWare actions or other actions on the server. These automatic steps wait for the execution of the respective action (for example, archiving a document in an archival system. In this way, data can be easily passed as return parameters to the JobRouter process (for example, the unique ID of an archived document).
For every automatic step, you can define how JobRouter should react to errors. It is even possible to flag the step in an error status and then to read the error message and handle the error in the process.
Rule steps
This new rule step type can be bound to any place in the process. It does not contain a form, and it automatically performs the defined rules. You can easily implement decision trees using this new step type.
Parallelization start and end
The new step type Parallelization Start can be used to parallelize the process. Using it along with the step type Parallelization End, the process flow can be brought together again and the process data of individual paths will be coalesced. By using Parallelization Start and Parallelization End, you can much more easily model parallel processes in JobRouter compared to step groups.
E-mail notifications
You can define E-mail notifications for any step. These notifications can contain global process data as well local process data (for example an invoice number). The E-mail notifications can be defined in every defined system language.
Form editor
The following changes were made to the form editor:
•Use of several tabs in forms
•Elements can be placed next to one another
•A form will no longer be reloaded when uploading or deleting attachments nor when adding, copying, or deleting subtable lines
•New PASSWORD form element for entering passwords
•New IFRAME form element to display IFRAMES in forms
•AJAX-based Designer
•An automatically recorded form history permits changes to be rolled back at any time.
Form integrations
Integrations such as a DocuWare web client element can be inserted at many locations in the form. These integrations remain at the defined location and are not changed even when scrolling the form.
Process analysis
Process analysis permits you to check for logic errors or gaps in the documentation and so makes it possible to eliminate errors before the simulation and the test phases.
Documentation
The process documentation can be generated in PDF format.
Logging
All changes to a process will be automatically logged, so it can always be shown who altered a process and when it was done. The change log is open to inspection by every process designer.
Comment
During process design, the process can be documented with comments by any person making revisions. This feature is especially recommended for commenting process changes to facilitate code maintenance in a shared work environment.
Process messages
Messages used in JobRouter forms, rules or PHP functions can be defined in a central location for all processes. With JobRouter Enterprise Version, these messages can be entered in several languages, so that even JavaScript functions can include multi-lingual messages.
Database connections
In a process you can use local database connections that apply only to that process or global database connections that apply to all JobRouter process incidents. So you won't have to maintain frequently used connections in multiple places.
Process configuration
For every process, you can set up configuration preferences, so important process parameters can be defined in a single place. That way you can establish, for example, certain paths or certain limits as configuration preferences and access them in forms, in rules, in scripts, or in PHP functions. This simplifies process maintenance significantly, since you won't have to search out the parameters in multiple locations of the process.
In addition to the process-level configurations, global configuration preferences can be employed by every process in the respective JobRouter installation.
Escalations
Escalation messages can now be defined in multiple languages, so they can always be displayed in the user's language.
PHP functions
PHP functions represent the further development of the previously used export functions. Of course those export functions will still be supported, but we recommend using the PHP functions for new processes. These are saved in the database relative to a process version. This way, they will be moved with the process during process import or export, and PHP functions can be changed in individual versions without influencing other process versions.
The PHP functions offer various methods to access process data, configuration preferences, and database links, etc. In addition, the PHP functions can be checked for syntax errors. PHP functions are incorporated into rules, where they can be integrated into the conditions or into the rule's execution. PHP functions are incorporated into rules, where they can be integrated into the conditions or into the rule's execution.
