OfficeTalk/MSP and OfficeTalk/MS

Version 5.32

This document contains the change history of OfficeTalk. All version's changes are noted here. The changes are ordered by the creation time from bottom to top. You will find the newest changes on top. A version is named with the underlined version name. Smaller corrections are additionally named with Build MM.DD.YYYY. Parts written in red indicate in general manually changes, before the described update can be used.

History of changes

Version 5.32 Build 10.05.2019

Hints for how to write a macro in the ScriptBrowser-Dialog

The source field of the macro contains at the start, wenn writing a macro starts, the formalism of how a macro should be written for a good change management.

Version 5.32 Build 07.20.2019

Exporting processes in tasklist as HTML

Logged in as a Company, Department, Office or Team exports in the HTML of the process(es) additionaly the worker of the current step of the process. Clicking onto the underlined workers name in the column Tasklist jumps the this worker’s short content.

Logged in as worker (Worker or Machine) exports the section Takeover processlist of the process(es) in the HTML some processes of the personal tasklist too.

Version 5.32 Build 06.16.2019

Contextmenu History-Summary in the tasklist

The contextmenu History-Summary of a task in the tasklist resulted in an error message with ending of the program, sorry.

Version 5.32 Build 04.06.2019

First keyboard input after inserting an errortext in the sourcefield of the ScriptBrowser dialog

On Windows-10 plattforms the first keyboard input was ignored after an error text was inserted by compiling in the source field of the ScriptBrowser dialog.

Version 5.32 Build 02.15.2019

Startportal Dialog - Opening a worker in the tabulator Organigram

Opening a worker in the tabulator Organigram of the workerdialog with the contextmenu Open... resulted in not responding OfficeTalk and OfficeTslk had to be terminated hard.

Version 5.32 Build 01.19.2019

Menu Restart in debuggerdialog of the scriptmacro

Using the menu Restart in the Scriptmacro-Debuggerdialog resulted in an error message and OfficeTalk was ended, sorry.

Menu Services in debuggerdialog of the scriptmacro

Using the menu Services... in the Scriptmacro-Debuggerdialog resulted sometimes in an error message and OfficeTalk was ended, sorry.
The contextmenu for a variable without services (e.g. Boolean) was enabled, but no service dialog was opened.

Evaluating of Or- and And-Expressions in a Scriptmacro

In the past the right operand of a Or- and And-Expression was evaluated independent of the result of the evaluated right operand. Now the right operand of an And-Expression is evaluated if the the left operand evaluates to True only. And the right operand of an Or-Expression is evaluated, if the the left operand evaluates to False only.

Version 5.32 Build 12.02.2018

Calculating arithmetic expressions in a scriptmacro

The calculation of arithmetic expressions was performed form right to left. This leaded in wrong results possible. Now the calculation is performed from left to right.
Written brackets for userdefined precedence where removed by a formating of the macro and where not applied on the calculation.

Version 5.32 Build 11.18.2018

Formating currencies for printouts

The serrvice format(..., as: ...) of the systemvariable Stepscheduler supports now in the argument as: th type Currency. With this the currency is appended with the currency sign of the country, configured in the operating system.

Selecting more items in the Scriptdialog of the Workbench

Serlecting more items in the Scriptdialog (tabulator Scriptdialog in the Workbenchdialog) with the rubberband (dragging left mouse button) did sometimes not work.

Dragging of items in the Scriptdialog of the Workbench

When dragging selected items in the Scriptdialog (tabulator Scriptdialog in the Workbenchdialog) all selected items are dragged and not the dragged item only.

Version 5.32 Build 10.14.2018

Selecting of dialog items in Scriptdialog of the Workbench

The selection of items in the Scriptdialog of the Workbench, especially in conjunction with the keys ALT, SHIFT und STRG, behaves now conform to the Windows-Rules.

Positioning of dialog items in Scriptdialog of the Workbench

Positioning of selected dialog items in the Scriptdialog of the Workbenchdialog (tabulator Scriptdialog) with the mouse and with the cursor keys is optimizes and works more efficient.

Version 5.32 Build 10.07.2018

Handling inputfields with arrows in the Script-Workbench

In the Scriptdialog in the Script-Workbench (tabulator Scriptdialog) input fields with arrows could not be worked with their contextmenu (e.g. Open, Remove). Input fields with arrows could be worked only with the contextmenu of the Statements listfield in the Workbench-Dialog.

Selecting dialog items in Scriptdialog in the Script-Workbench

The Statements listfield in the Workbench-Dialog did not reflect the deselection of all dialog items in the Scriptdialog. The last selected iterm remains selected there.

Contextmenu of disabled input fields in a Scriptdialog

The modifying items of the contextmenu (Paste, Cut, etc.) for disabled input fields (service disable) where not disabled.

Contextmenü of input fields without border in a Scriptdialog

Input fields without border support now a contextmenu like input fields with border.

Version 5.32 Build 09.30.2018

Ending OfficeTalk with a modified macro in the Scriptbrowserdialog

Ending OfficeTalk when a macro was modified in the Scriptbrowserdialog the messagedialog „Macro is changed – compile or abandom changes“. Answering with compile ended OfficeTalk with an error message.

Version 5.32 Build 08.25.2018

Removing error notifications of the Scipt-Compilers in textfield of the macro with keyboard

Removing of an error notification of the script compiler in the textfield of the macro (e.g. Variable not declared) after compiling (contextmenu Compile) with the keyboard (ALT+X) did not work. On Windows-plattforms you had to press the DEL key twice.

Version 5.32 Build 08.12.2018

Uising Public variables in Statements within Workbench

Using a Public variable in a statementblock (tabulator Startstatements, tabulator Openstatements, Actionbutton, etc.) within the workbench resulted on accepting the input in the errortext Variable not defined.

Version 5.32 Build 05.13.2018

Error in a macro on service ScriptDialog.help(…, with: …)

The service ScriptDialog.help(…, with: …) for a readonly table field, used in a macro, was not executed and resulted in an error dialog.

Version 5.32 Build 04.28.2018

Wrong indicators of columnsorting in table listfields

In dialogs containing a table listfield the sorting indicator in the column label was missing after the dialog was opened.

Version 5.32 Build 03.30.2018

Sending processtemplate faiiled

Sending a processtemplate in the dialog Graph of process <name> with the File – Send was rejected with the message „The processtemplate could not be send“. The reason was the reject of some mailservers because of incompatible mailformats.

Version 5.32 Build 12.31.2017

Logging of failed sending of mails

In the logging file a failed send of a mail (e.g. sending a processtemplate) was logged with to many lines.

Testing of the mail serttings

Testing the mail settings with the button Test in the tabulator Mail of the settings dialog resulted in an error message with ending of OfficeTalk, sorry.

Using worker toolbar of Organigram list dialog in startportal Dialog

Selecting a template worker in the worker’s toolbar of the organigram list (startportal Dialog) with the mouse resulted in an error message with ending of OfficeTalk, sorry.

Working portrait of a worker in the tabulator Adress

Assigning, removing and opening a portrait of a worker is slightly modified. For details please read documentation OfficeTalk Business-Process-Management, chapter Portrait.

Exporting tasklists as HTML

For a better readability the columns in the processtables of the HTML-Export are now prefixed with their corresponding pictogram.

Exporting resposibilities of a worker as HTML

Exporting the responsibilities of a worker (context menu Responsibilities for a worker in the OrganigramBrowser) as HTML resulted in an error message with ending of OfficeTalk, sorry.

Starting OfficeTalk with the commandline

Some inaccuracy starting OfficeTalk with the commandline where removed. For details please read documentation OfficeTalk Generals, chapter Commandline options.

Version 5.32

HTML-Export of script macros

The statements in the HTML export of script macros, performed by the export with the menu File - Save as HTML in the dialog Graph for process … and in the dialog Callgraph starting at…, contains now for easier reading the same coloring as in the source view of a selected macro in the Tabulator Scripts.

HTML-Exporte with hyperlink to extern dokuments

All HTML-Exports (Organigram, Processtemplate, Processdata) shows now links to extern documents with a Hyperlink (e.g. webadresses, files, etc.).

Changing the view settings of an active process

The view settings of the execution path of an active process, opened with the context menu Previuos executions in all tasklistes, can with the menu View – Settings now be changed. These settingsd are lost on a restart of OfficeTalk.

Path of a process in HTML-Export

The first step in the list of executed steps in section The executed steps of path was missing.

Naming of the executor of a step in all dialogs of steps and tasklists

The naming of an executor of the step in the dialogs of steps and tasklists is changed from Schedule/Scheduling to Executor/Executing. This matched the used semantic in a better way.

Settings for exporting an organigram as HTML

The dialog for the export options (Optionds for HTML export) supports now the new option With all sections. Selecting this option selects all other section options. Deselecting this option selects all default sections.

HTML-Export of processtemplate in the export of the organigram and processtemplate

In the HTML-Export of a processtemplate the names of the start scripts in the action are navigable now for a better navigation. The titles of the step sections are now for a easier reading better formatted.

Section for navigation within a worker in export of organigram

The sequence of the sections for navigating within a worker did not all match to the sequence of the hyperlinks within the navigation section.

Defining a substitute for a process or a step

In the substitutes dialog (tabulator Substitute) with the combox Subtitute no worker could be selected. Because of this defining a substitute was not possible.

Export a single worker as HTML

The HTML-Result of a single exported worker with menu File – Save as HTML... (deselected option Subordinated workers in export dialog Option for HTML creation) contains now optimized informations. The section Navigation for sub- and superordinated workers contains in this case the super- and subordinated workers striked out (not navigable) and the title indicates with Organigram with: <workername> a single exported worker.

Klickbereiche in exportierten HTML-Dateien

The diagramitems in a HTML-File (worker in organigramdiagram, step in process, etc.) had shifted clickareas. This means: For some diagramitems you had to click in the browser beside the item for following the link.
A macro in the HTML-Export of a control flow diagram supports now clickareas in the browser.

Settings for all HTML-Exports

With all menus Save as HTML OfficeTalk ended with an error notifyer, when the option Pictures inside the HTML-File was not selected, sorry.
Selecting the option Pictures inside the HTML-File leaved in the temporary userfolder and in the destination of the created HTML-File the temporary working files of the creation process. But OfficeTalk will must not waste disk space!

HTML-Exports with vovels on Linux-Platforms

On Linux-Platforms the Browser displayed special character like vovels in an HTML-Export in a wrong way.

Viewing histories of ended processes

Selecting histories of ended processes you can view the viceversa of given selection aspects with the menu View - Revert selection in the histories dialog.

Changing the setting Database in the Settings

Changing the setting Database in the tabulator General of the settings dialog, you get a important notification after saving the settings.

Exporting delegated tasks as HTML

With the new menu File – Save As HTML… , opened with the menu Work - Delegated tasks… in the personal tasklist, you can now export a complete tasklist of delegated tasks or a single task within a delegated tasklist as HTML-File. For details please read OfficeTalk Workflow, chapter Save as HTML…

Exporting tasklists as HTML

With the new menu File – Save As HTML… you can now export a complete tasklist or a single task within a tasklist as HTML-File. For details please read OfficeTalk Workflow, chapter Save as HTML…

Version 5.31 Build 06.05.2017

Opening extern files on Linux platforms

Opening an extern file with a hyperling in textfields or opening a protocol- or diagnostic-file with the loupe button in the dialog Deleting protocol and diagnostic files with no defined standard application for the file extension results in a warning.

Helpdialog and dialog for starting a process in tasklist remained open

Using the startportal Function-/OrganigramBrowser the helpdialog (opened with the button Help) and the dialog for starting a new processs (opened with the menu Start process) remained open when the tasklist was leaved by changing to another category (e.g. Scripts). These dialogs where closed, when switching back to the tasklist again.

Opening diagnostic and protocol files in the settings dialog

To open on Windows-Platforms protocol files with the loupe button in the dialog Deleting protocol and diagnostic files, opened with the Trash button in the tabulator General of the settings dialog, the default program for files with the extension „.log“ had to be associated to the program Notepad in the systemcontrol. Now this association is not necessary anymore, because these files are now opened as ordinary textfiles.
On Linux-Platforms the loupe button in the dialog Deleting protocol and diagnostic files, did not open any protocol or diagnostic file.
For details please read documentation OfficeTalk Business-Process-Management, chapter General settings, section Trash for protocol and diagnostic files.

Menu Help - Versioncheck... in startportal dialog on Linux-Platforms

On Linux-platforms the menu Help – Versioncheck... in the startportal dialog resulted in an error dialog with succeeding ending of OfficeTalk, sorry.

Sorting of processes in all type of tasklists

Each type of tasklists has now its setting for storting of its own. Up to now, all type of tasklists had a common setting for sorting. e.g. The setting for sorting of the privat tasklist was used for the takeover tasklist too.
When using the Functions-/Organigrambrowser the setting for sorting was loosed, when closing a details dialog of a process, e.g. the dialog for histories.

Menu Execute statements... in SciptDebugger dialog

The button Execute in the dialog for executing statements, opened with the menu Execute statements…, leaded to an error message with ending of OfficeTalk, sorry.

Dialogs for selecting a service in the onlinehelp of the SkriptBrowser dialog with Multi-Monitor-Environment

The dialog for selecting a service (TAB-Key after point) was opened with very long servicenames in a multi monitor environment with an invisible horizontal scrollbar. Therefore scrolling within the names was not possible.

Version 5.31 Build 04.30.2017

Writing in scriptmacro a New-Statement with comment

Writing a New-Statement with a dataype containing in a Assembly- or Interface-Direcxtive with a succeeding comment resulted by compiling in a by datatyp. e.g.
x = New Office.FileDialog ’comment
resulted by compiling
x = New OffiFiOffice.FileDialog ’comment

Using different datatype in Dim- and New-Statement

Up to now it was possible to use in the Dim-Statement and in the corresponding assignement a New-Statement with different or not compatible datatype. e.g.
Dim x As Desk
...
x = New Team
This resulted in different errors when executing the macro. Now the datatype in the New- Statement must be compatible with the datatype used in the Dim- Statement. If this is not the case, the compilation is abortet with a hint.

Wtriting a macro with using directive Assembly and Interface

For acessing the methods of a class, contained in an Assemblxy and Interface-Directive, in the onlinehelp (TAB key after the point of a variable), the macro had to be compile first. Now, the methods of a class, contained in a library, defined by a directive, are available ever in the onlinehelp.

Toolbarbuttons Execute and Debug in the ScriptBrowser dialog for macro with arguments

For a macro with arguments the toolbarbuttons Execute and Debug of the source view in the ScriptBrowser dialog have now the same state as the corresponding context menu of the source view.

Executing an debugging a macro with arguments

The menu Execute in the contextmenu of the method listfield and source textfield of the ScriptBrowser is for macros with arguments not chooseable anymore. In the past executing a macro with arguments resulted in a notifyer, because executing such a macro makes no sense. For the menu Debug the same rules are valid, but it is for a macro with arguments enabled when using the usinglevel Expert. For details please read documentation OfficeTalk Business-Process-Management, chapter Executing scriptmacro and chapter Debugging scriptmacro.

Debugging the last statement of a macro in the ScriptBrowser

Stepping the last statements of a macro with the button Step or Single step may result to an error message, when the macro is debugged with the debug button in the ScriptBrowser.

Opening of a processtemplates history dialog in tasklist

When using the startportal FunctionBrowser, the history for a processtemplate in the tasklist (rightmost top listfield) is opened within the FunctionBrowser’s dialog and not as an stand alone dialog anymore. This is the default behavior for dialogs in the startportal FunctionBrowser.

Opening processtemplates history in tabulator Processtemplate and tasklist

Using the startportal Dialog, histories for different processtemplate in the tabulator Processtemplate and in the tasklist (rightmost top listfield) can be opened simultaniosly. History summaries of different processhistories in the history dialog can be opened menu History Summary simultaniosly. This is usefull for comparing different histories.

New menu History Summary for History dialog in Processtemplate tabulator

In the history dialog of a processtemplate the new menu History Summary is available. This menu opens the summary of the history of the selected process history in the history dialog.

Version 5.31 Build 02.18.2017

Changes of emphasize in opened process dialogs

Changes in opened process dialogs by the services bold(...), color(...), font(...) etc. of a macro are visualized at once.

Version 5.31

Visibility rules for execution of a macro

To make data more save, the settings dialog Scripts supports the new option Visibility rules. Setting the option to Yes, executes a macro while scheduling an action of a step of the process, when the macro is contained within a visible worker only. When the macro is contained in a worker outside the visibility area, the scheduling of the step’s action is aborted with the message The script '<skriptname>' is not found, or contains no startmacro and can not be executed. The default setting for this option is No. This means the macro can be located anywhere within the workers hirarchy up to the company,

Warnings are logged

With the new option Warnings in the settings dialog warnings while scheduling processes can be logged into the logfile OfficeTalkWarnings.log. e.g This is executing a macro located outside the visible workers. The may be a an error only..
The dialog Deleting protocol and diagnostic files contains the new item Warnings:, for deleting the warnings.

Version 5.30 Build 01.14.2017

Optimisation of times of a processtemplate when using startportal Functions-/Organigrambrowser

The dialog for optimisation of times of a processtemplate (contextmenu Time optimisation in tabulator Processtemplates of the OrganigramBrowsers) could in startportal Functions-/Organigranmbrowser be canceled.with the window close button
Additionally the button Save was enabeled without having changed any times.

Menu Save as HTML im History-,History summary-, Responsibility- and Simulationdialog

After creating the HTML-Result it can be opened with the installed browser.

Large portraits in organigram graph dialog

A large portrait of the worker is resized to a moderate size in the graph dialog of the organigram (startportal Dialog and menu Organigram as diagram).

Exporting organigram with menu Save as HTML…

Exporting the part of the organigram in the OrganigramBrowser by selecting child worker of the topmost worker leaded to an error message with ending OfficeTalkk, sorry,
Exporting a large organigram when opened as diagram (startportal Dialog and menu Organigram as diagram) leaded to missing of some left site positioned workers in the diagram.

Version 5.30 Build 06.19.2016

Drag-Drop processes in tasklist

Dragging a process onto another process in the tasklist for setting the process into waitstate waited the process and additionally scheduled the next step of the drag/drop target. Now this additionally scheduling is not done anymore.
Dragging in the browser tasklist a source process onto a target process, when the target process is waiting for the source process produced an infinite wait. Now waiting a source process for a target process while the target process is waiting for the source process allready is not possible anymore.

New service addAll(...) for Scriptvariable Array

With the new services addAll(...) all items of the given Array are added at the end of the Array.

Slow reactions in source field of the ScriptBrowser

On slow computers in the source text field in the ScriptBrowser the reaction to keyboard inputs an mouse clicks was a little bit slow.

Portrait of the imported company was loosed when importing

Importing a company with the contextmenui Import in the listfield of the OrganigrammBrowser did not adopt the portrait of the imported company to the current company.

Version 5.30

Contextmenu Indicate hierarchy in listfield Prozesstemplates

With this option the mouse became a lense on every mouse movement within the listfield.

Icons in dialog All permissions in dialog Permissions

In this dialog the portrait of the worker is displayed for the active option „Worker with portrait“.

Export and import settings

With the new menu File – Export you can export all settings of the logged in worker into a file. With the new menu File – Import you can import a previous exported settings into the logged in worker. With the menu File – Back you switch back to the main menu of the startportal.

Extended diagnostic information for errors of a macro’s execution in OfficeTalkDiagnostic.log

For hard errors in a makro’s execution the diagbostic file contains the statement, where the error is detected.

Vetical sesizer in al tasklists

Hiding and unhiding the dialogfields of processtemplates and description deactivates the vertical resizer left next beside this dialogfields.

Menu View-Processtemplates-Yes in all Tasklists

The menu did not show the processtemplates when the description part is displaying the history of a selected active process.

Contextmenu Usings... in lidtfield of macros of the SciptBrowser showed not all usings

The usings dialog displayed macros, whith are used in the statement addRegister(...) not,

Menu View - Processtemplates in the tasklists

Switching of the processtemplates with the menu View – Processtemplates - No in the tasklists and switching on again with the menu View - Processtemplates - Yes did not show the processtemplates. To make them visible, the description had to me switched off and on with the menu View – Description first.

Ending OfficeTalk in startportal Function-/Organigrambrowser without saving a new created script

The sequende in Function-/Organigrambrowser

1. Create a new script

2. Closing Function-/Organigrambrowser portal with the window exit button

3. Message „Save script“ No

4. Message „Save database“ No

resulted in aborting OfficeTalk with an error message.

Version 5.29 Build 06.11.2016

Quickview of stephistories in all tasklist dialogs

In all tasklist dialogs the bottom right most dialogfield shows for a selected task in the personal tasklist and in the takeover tasklist the history of the already scheduled steps and right down the comment of the selected stephistory.

New service shutdownOn(…) of the systemvariab stepscheduler for batch oriented tasks

With the the new service shutdownOn(…) of the systemvariable stepscheduler you can now realize batch oriented tasks. e.g.
1. Starting OfficeTalk with login in the command line
2. System process with one step is started and scheduled (the step executes a macro with stepscheduler.shutdownOn(EndOfStep).
3. OfficeTalk is automaticly ended after scheduling the only one step and ending the process.

For details please read OfficeTalk Script, chapter shutdownOn(…).

More usability for the dialog items in the right part of all tasklists

Size and position of the rigth side dialog items in all tasklists (Processtemplates and Description) use after switched off and on the last used values instead of their original values.

Scheduled process remains in the visible area of the tasklist

A process remains after scheduled in visible area of the tasklist after it is scheduled. The helps orientating within many processes containing in the tasklist.

Toolbar for filtering of tasks in all tasklist dialogs

The tooltips of the buttons in the toolbar for filtering tasks at the bottom of all taskklists displays now the possible actions of the button.

Remembering settings of columns in tasklist when using Function-/OrganigramBrowser

Opening in tasklist as tables with used Function-/OrganigramBrowser with a menu an other subordinated dialog (e.g. history of a task), the actual changed settings of the table columns where not restored on menu Back to their previous values.

Position of resizers in all tasklists when using Function-/OrganigramBrowser without resizer memory

Opening in the tasklist with used Function-/OrganigramBrowser with a menu an other subordinated dialog (e.g. history of a task), the current settings of the resizers and the contained items of the task dialog where restored to the original sizes by the menu Back in the subordinated dialog. Now, the resizers and sizes/positions of the contained items are restored to the previous sizes. This gives more usability using the tasklist dialog.

Open internal processmonitor dialog

The keybord key CTRL+b did not open the internal processmonitor dialog in every case. e.g. When not a textfield had the input focus, CTRL+b did not open the internal processmonitor dialog.

Service actionSymbol of the systemvariable Step

Some symbolnames of the service actionSymbo() of the systemvariable Step resulted in a wrong display of the symbol of the scheduled step and its action in the history dialog.

Description field in all tasklist dialogs

The description field in the tasklist dialogs shows for a selected process the history of its last scheduled step and its schedulingdate instead of the description of its associated process template,

Processdata for further using in other applications

In the processdata dialog you can copy the value of the column Content of the selected processdata item with the contextmenu Copy into the system clipboard for further using in other applications.

Filtering process histories and processes

In the dialog for filtering process histories and processes, opened with the menu View – Filter, the group and item names for processdatas in the button part of the filter dialog may contain the wildcards ? und *.

Who is logged in dialog

In the dialog Who is logged in, opened with the menu Extra – Who is logged in in the startportal, the own logging in is displayed now too. Notification with the button Send are mailed not to this address.

Menu Help – Versioncheck in the startportal dialog

The versiontext in dialog Akctuality of installed programversion showed with „The installed version is up to date, but some small modifications, possible some corrections..“ a not installed very actual program version.

Version 5.29 Build 04.03.2016

Menu Extra – Who is logged is in the startportal dialog

The menü Extra – Who is logged in in the startportal dialog, whitch shows, who is currently logged in, was not usable, because it was not visible in the menuitem list.

Version 5.29 Build 03.19.2016

Output in the protocol file is extended

For better identifying the timestamp of a single line, the line’s prefix is extended with the date and the shortcut of the worker.

First installation resulted on start in an error message because of missing table column

Because of an incomplete installation file, the OfficeTalk database was not build correct. The extension of Version 5.27 was missing, sorry.

Labeling of toolbars did not respect its setting after logged in

After logged in as an OfficeTalk user, the toolbars are not labeled as set in the settings of the logged in user’s environment tabulator for General.

Contextmenu Dialogtitle of a process dialog in Workbench

The dialog for defining the title of a process dialog (contextmenu Dialogtitle of a process dialog) in the Workbench did not accept any expression in the field From Expression. The button Accept resulted in an error insertion like Syntaxerror….

HTTP-Login in menu Help – Versioncheck

Using this menu will open the logion dialog for HTTP in case of missing values in the fields User or Password of the tabulator HTTP of the settings dialog. The button login will now be disabled as long as both values are not given.

Menu Work – Select taskarea in tasklist dialog

Choosing a taskarea with the menu while scheduling a step is now denied with a notifyer. Additionally you get now a notifyer, when you choose a not allowed menu while scheduling a step.

Version 5.29 Build 02.13.2016

Aborting a macro running in an infinite loop

If a macro is running in an infinite loop, because of bad construction, you can abort it with the keys CTRL+ALT+SHIFT. An infinite loop may be constructed with the statements
Do While TRUE = TRUE
<statements>
Loop

With these keys any execution of a macro can be aborted, so use it carefully !

Simplifying of failure processdialog in test environment

A processdialog, opened in a macro with the test environment, can now be closed with Emergency Exit without respect to the used statement disableCancel().

Version 5.29

Diagrams in a HTML-Export of processtemplates and organigrams

With hyperlinks of the items within a diagram of processtemplate and an organigram you can easily navigate to the clicked item.

Version 5.28 Build 11.17.2015

Not neccessary contextmenus are removed

In the listfields of the tabulatordialogs (Rights, Substitutes, Useraction, Stepresults, etc.) the contextmenus Open and New are removed, because these menus are grayed ever and can not be used therefore.

Version 5.28 Build 10.03.2015

Compiling an existing macros with changed declaration

If you compile a macro with a changed declaration, you get an additional confirmer for proceeding, when this macro is used by any Call-Statement of other macros, because this will break these Call- Statements.

Version 5.28 Build 09.28.2015

Contextmenu New – Stepresult… in tabulator Processtemplates

The contextmenu New – Stepresult… in the listfield Steps of the tabulator Processtemplates resulted in an error message and ending of OfficeTalk. This menu is rearly used, because managing a processtemplate is mostly done with the dialog Graph of template: <Name of template>, but ….
With the contextmenu you can now add a new steptemplate in a step. This is not so easy as in dialog Graph of template: <Name of template>, but it is possible.

Version 5.28 Build 09.26.2015

Execution of any script macro failed

The quality assurance did a bad job !!! The execution of any macro resulted in an error message. By this the complete workflow was broken. Mea culpa, mea culpa…

Version 5.28

Support for potential wrong start macros

While managing the business processes, a macro witch is not appropriate to be used as start macro, will be used as start macro, because you forgot to apply the start property a macro within the script. The new menu Extra - Potential wrong start macros in the OrganigramBrowser searches and shows all such macros within the logged in worker and its subordinated workers (Department, Office, Team), in a dialog. For details please read documentation OfficeTalk Business-Process-Management, chapter Potential wrong start macros.

Avoiding unnecessary question when compiling a macro

When compiling a macro with missing Return statement with the contextmenu Compile… in the ScriptBrowser you got the question The macro does not contain a Return-statement. Do you want to proceed. Now you get this question in case of a potential start macro only. A macro is a start macro, when it has no arguments and it is the first or only one macro in the script. This change saves an additional mouse click.

New conditions for removing a worker

The contextmenu Remove… in the OrganigramBrowser denies removing the worker in general, when its tasklist, or in case of an organisation unit (Department, Office, Team), the tasklist of a subordinated worker, contains a process. Removing an organisation unit is also denied with a notifyer, when one of its subordinated workers is currently logged in. These conditions where not all considered, an therefore a tasklist may be lost. Additionally you are informed in these cases about the affected tasklists. These new conditions complete the already existing condition, that a removing worker must not be referenced by another artefact (step, taskarea, substitute, etc.).

Version 5.27

Better responsibility for invalid removing a worker

Removing a worker and this worker is responsible for any step in any active process in any tasklist, you get a message with the owner (workers) of these tasklists, that denys removing. Starting this version the first time, you get a message and the database is adopted to this extensions. Because this may take a time, depending of the size of the tasklists, so be patient !
In this context the database table step is extended by column processid. Starting version 5.27 the first time adds the new column in the database table automaticly. Because of this you must login the version 5.27 the first time as company !

Removing a processtemplate, whitch is the source of a process

Removing a processtemplate with the contextmenu Cut… in the listfield of the tabulator Processtemplates you are notified in case of the removing processtemplate is the source of a process in any tasklist. Because removing a processtemplate will remove its histories too !

Possible problems after removing a worker

Rrmoving a worker with the contextmenu Cut… in the worker’s listfield of the Organigrambrowser may lead in special circumstances to an unschedulable process. An example:

1. A new process is started on base of a processtemplate, with a step assigned to the worker.

2. The processtemplate is removed. This is really acceptable.

3. The worker is removed. This is really acceptable too. The using of the worker in the started process is not detected here.

This process can not be scheduled as soon as the scheduling reaches the step with the removed worker. In the worst case you get an error message in the tasklist and OficeTalk is ended. Now you get a message, when this worker should be removed and the worker is not removed.

Wizard for changing the responsible worker of steps in a processtemplate

The new menu Change step responsibilities… of the contextmenu of the processtemplates in tabulator Processtemplates and in menu Work - Change step responsibilities… of the graph dialog of a processtemplate opens the wizard for changing the responsible worker in steps. With this wizard a responsible worker in all or in a single step can be substituted in an easy way with an another worker, whitch has the required process permissions.

Version 5.26 Build 08.19.2015

HTML-Export of a processtemplate is extended

The section Paths od a HTML-Export of a processtemplate is extended. For a better overview the title of the section Paths contains now the overall number of paths and each path is titled with its number.
In the section Start-/User-/End-Action of a step of the processtemplate the line Script: is extended with the name of the owner of the macro. When the owner, a worker, is in case of an Organigram-Export contained in the HTML-Export, this workername is a Hyperlink.

HTML-Export of a macro’s call graph extended

In the HTML-Export of a call graph of a macro (contextmenu Call graph… in the macro’s listfield of the SkriptBrowser) each macro is extended with the name of its owner.

Version 5.26 Build 08.05.2015

Support for not allowed canceling of processdialog

Canceling a processdialog with the window close button or with an action button performing the service cancel, whitch is configured not cancelable was not responsive in the past. The processdialog remains open. Now you are notified with a messagedialog about the forbidden cancel action.

Dialog icon in tabulator Processtemplates

The icon on the right top in the tabulator Processtemplates is corresponding with the contextmenu Indicate hirarchy. When the contextmenu is selected, the hirarchy icon is displayed instead of the processtemple’s icon.

Version 5.26 Build 07.28.2015

Contextmenu Indicate hirarchy in tabulator Processtemplates

The setting of the contextmenu Indicate hirarchy in the list of process templates is managed now by the personal settings and therefore is valid for all tabulators Processtemplates and not only for the current one. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings without userinterface.

Contextmenu Responsibilities for a worker in all OrganigrammManager-Dialogs

The result dialog of the contextmenu Responsibilities opens with a double click on one of its step, not only the step’s dialog, but all dialogs of the path to this step. These are the worker’s dialog (only portal Dialog), its tabulator Processtemplates/Common Processtemplates and the step’s dialog with its tabulator Options With this extension you get more information about the related context.

Under specific circumstances building a processtemplate was not possible

When logged in as an organisation unit and creating a processtemplate in a subordinated worker, building steps in this processtemplate was not possible, because permissions where created in the subordinated worker and the logged in worker was missing permissions for this processtemplate. Therefore all functionality in the working dialogs (menus, buttons, fields) where handled as read only. To insert steps in this processtemplate, the permission for this processtemplate had first to be inserted in the logged in organisation unit. Now inserting steps in this template is possible without inserting a permission for this processtemplate in the logged in organisation unit.

Missing and wrong tooltip in Group-Tasklist

In the dialog of the Group-Tasklist, opened by login as a organisation unit, the tooltip of the button for ending OfficeTalk was missing, and the tooltip for the Help-Button displayed a wrong text. This does not affect the handling, but everything should be right !

Onlinehelp for funktion Start in source textfield of a macro

Typing in the function Start at the end of text of a macro’s source textfield (SkriptBrowser-Dialog) and subsequent typing in the Tab-Key, did not open the onlinehelp for the Start function.

Optimization of the evaluation version for the contextmenu Usings in tabulator Resources

Using the contextmenu Usings in an evaluation version for a resource in tabulator Resources, resulted in a complete save, when OfficeTalk was ended.

Extension for HTML-Export of a processtemplate and organigram

The options dialog for a HTML-Export of a processtemplate and an organigram/organigrampart contains now the new option Paths with steps. Choosing the option appends each path with the appropriated sequence of steps. Not choosing this option exports the paths without the sequences of steps. For details please read documentation OfficeTalk Business-Process-Management, chapter Logged in worker– Menu – Process – Save as HTML and chapter Organigram – Menu - Organigram – Save as HTML.

The HTML-Export of an organigram is extended with some navigations:
The hyperlink of the category item Processtemplates of a worker is succeeded with the hyperlinks of the processtemplates of the worker. With this hyperlinks you can navigate to a specific processtemplate fast.
The title of the process permissions is succeeded with the hyperlink of the related processtemplate. With this hyperlink you can navigate to the related processtemplate. In case of the processtemplate is not contained in the HTML-Export, because its owner is not exported, or no processtemplates are exported, the hyperlink is striked through. Global process permissions (referencing processtemplate by category only) do not have this hyperlink.

Version 5.26

Contextmenu Open document in all textfields

The contextmenu Open document in all textfields for opening the hyperlink was enabled independent of the selected string. Selecting a simple string instead off a hyperlink enabled the contextmenu. Now the contextmenu is enable for selected hyperlinks only.

Service value(…) of the systemvariable ScriptDialog for hyperlink enabled textfields

The service value(…) answered for a textfied, whitch as enabled with hyperlink(…) for hyperlinks, a contained hyperlink without the surrounding identifiers ({{ and }}).

Extension of result dialog of searching workers by any criteria

The result dialog of a workers search (the result contains more workers) contains now at the right side a text field with the used search criterias. Each category is preceeded with its blue headerline. The criterias can be hided and unhided with the menu View - Search/Hide search criterias. The search criterias are most helpfull, if more searchings are parallel in action.

Mouseclick on a hyperlink in all textfields

Clicking on a hyperlink in a textfield and then moving the mouse inside this textfield resulted in a selection of the content regarding to the mouseposition. This obscure selection mode ended with a additional mouseclick inside the textfield.

Searching for workers with specific Labelgroup

Searching for workers (menu Work – Search in OrganigramBrowser-Dialog) with a specific Labelgroup was not possible. Withal selection a Labelgroup in tabulator Address in the Search-Wizzard the button Search remained grayed.

Extension in tabulator Processtemplates and startportal Function-/OrganigramBrowser

Using the startportal Function-/OrganigramBrowser reselects after closing an opened step of a processtemplate in the tabulator Processtemplates the previous selected step. This optimizes the working with the processtemplate.

Menu Work - Delegated Processes… in the tasklist

After opening the delegated processes with the menu Work - Delegated Processes… in the tasklist was the menu File – Back grayed, when the startportal Functions-/Organigrambrowser was used. Going back to the tasklist was possible only with the button Close.

Menu Work - History in all kind of tasklists

The Menu Work – History in all kind of tasklists opens now, depending of the current selection, the history of the selected process in the personal or takeover list or the history of selected process template in the list of process templates.

Tabulator Organigram of the worker dialog with used startportal Dialog

When using the startportal Dialog, selecting the tabulator Organigram in the worker dialog resulted in an error message with ending of OfficeTalk, sorry.

Visual feedback of the toolbar button Door for ending OfficeTalk

The toolbar button Door in the startportal dialog is animated only, when OfficeTalk will be ended without of first saving possible changes. With this change the visual feedback of possible actions is more intuitive.

Version 5.25 Build 06.09.2015

Result of macro function Shell

The string result of the macro function Shell is trimmed by leading and trailing spaces, CR and LF, to get a more compact result. If one of your macros assumes a trailing CR in the result, you must change these macros.

Array-accessing in a script macro failed in combination of Try-Catch and Shell

Accessing the Description of the system variable Error in a Try-Catch-Block failed in case of using the function Shell with a program returning an array. e.g.
Dim theError As Array
…
Try
Shell ”md5.exe” ”nonExistentFile”
End Try
Catch
theError = Error.Description
MsgBox( "Shellerror " & theError( 0 ) & ": " & theError( 1 ) )
End Catch
…
leaded in the statement MsgBox(…) to an error with subsequent ending of OfficeTalk because theError( 1 ) interpreted the second part of Description in a wrong way.

Version 5.25 Build 06.04.2015

Contextmenu in the source field of the ScriptBrowser-Dialog

The contextmenu Webservice contains now the webservices of all macros in the visible worker hierarchy and not the webservices of the current worked macro only.
The contextmenues Functions - Dialog – Itemcontent and Webservice are disabled for no available items (no webservies in macros in the visible worker hierarchy or no dialog items in the current macro).

Version 5.25 Build 06.01.2015

Optimized memory management on Windows 64Bit platforms

Big tasks like macros with large database activities with ADO communication library may run slower on Windows 64Bil platforms than on Windows 32Bit platforms, because the memory management is not proper adjusted for large tasks. The memory management is now adjusted for such large tasks. Additionally you can change the memory algorithm with the new button RAM… in the tabulator General of the settings dialog. The initial value is 9095MB. You can modify it from 512MB to <max memory size>. The modification gets active on the next start of OfficeTalk and should be made carefully ! For details please read documentation OfficeTalk Business-Process-Management, chapter General settings, section DefaultMemoryUpperBound.

Version 5.25 Build 05.16.2015

Displaying of System-Processtemplates in the tasklist

In the listfield of processtemplates (top right) in the tasklist, the system processtemplates (System-Start and System-Login) are not contained anymore. In general these processtemplates must not be started manually. To contain theese processtemplates in the listfield, you must set the option System-Templates in the tabulator Tasks of the setting dialog to Yes.

Version 5.25

Changes for starting system processes on login

In opposite to the documentation, the system process System-Start was executed, when you did a relogin on the started OfficeTalk. Now the system process System-Start is executed, as documented, only on the very first login when starting OfficeTalk.
If you have tasks, to be done, organized in the system process System-Start, you must move these tasks to the system process System-Login.

Toolbar-buttons Execute and Debug with selected statements in the SkriptBrowser-Dialog

Using the toolbar-buttons Execute or Debug with selected statements removed after execution the selection of the statements. A repeated using of these buttons tried to execute the previous selected statements, but no selection was visible. Now the selected statements remains visible after an execution.

Contextmenu Execute up to here in Debugger-Dialog

Using in the source field of the Debugger-Dialog the contextmenu Execute up to here at the end of the macro leaded to an errormessage with ending of OfficeTalk, sorry.

First installation installed the database uncomplete

The first installation of OfficeTalk installed the OfficeTalk-Database without the extensions of the version 5-24. As a result OfficeTalk ended with an error message, when the tasklist was opened, sorry.

Using with extended memory requirements

Using OfficeTalk with extended memory requirements resulted in a slow down. This happened on all Windows 64-Bit platform with large operations of the ADO.Communication library. To avoid this slow down, the upper limit of space of the application was enlarged.

Choosing colors for dialog items of a processdialog in the Workbench

In the Workbench background and foreground colors for a dialog item of a processdialog are choosen now by the real color and not by the name of the color. For this the comboboxes present the available colors in their lists.

Version 5.24 Buid 04.25.2015

Position of message dialogs

The message dialogs where topped over all windows on the desk and not only on top of the windows of OfficeTalk.

Inputfields for statements in the propety dialog of dialog items of the ScriptBrowser

In some inputfields for statements in the property dialog of dialog items the error text for bad inputs was positioned wrong. Now these error texts are displayed red at the correct position. Additionally in some inputfields for statements the input of a variable name only was interpreted as error.

Version 5.24 Buid 04.17.2015

Displaying a wrong cursor after executing of a macro

The execution of a macro displayed permanently a wrong cursor, when the statement MousePointer(<new cursor>) was not undone before the macro ended with the statement MousePointer(<old cursur>).

Version 5.24 Buid 03.28.2015

Grouptasklist with setting Tasklist as Browser

The Tasklist of the Company, Department, Office and Team contained in some rare situations no tasks, but was empty. This was the case, when OfficeTalk was started with the settings Tasklist at login and Tasklist as Browser in the tabulator Tasks of the settings dialog.

Selecting a modified process in the tasklist with icons

Selecting in the tasklist with icons (setting Processes in table No in tabulator Tasks of the settings dialog) a process, whitch is modified in the meantime by another worker, leaded to the well known message Process was modified by another worker and subsequent ending with an error message.

Selecting a modified process in all kind of tasklists

Selecting in the tasklist a process, whitch is modified in the meantime by another worker, leaded to the well known message Process was modified by another worker and the process stays selected now

Using menu Delegate/Change for a process in the tasklist

Using the menu/contextmenu Delegate/Change in the tasklist for a selected process with modifying date/time, priority or additional process name, but without delegating the process to another worker, did not inform the tasklist of the other logged in workers about the modified process. When another worker used this process in its tasklist with a menu/contextmenu, the process with its outdated values is used. This may lead to some suspected result.

Version 5.24 Buid 03.20.2015

Dialog for filtering of processes in the tasklist with given processdata names

In the dialog for defining the filter values for the displaying processes resulted a click on the button >> beside the processdata group/itemnames to the message No processdata for the given name template, when the tasklist was displayed as browser (Settings – tabulator Tasks) and no process was selected in the tasklist. Details see documentation OfficeTalk Workflow, chapter Filter…

Dialog for filtering of histories of a processtemplate in the tasklist with given processdata names

In the dialog for defining the filter values for the displaying histories resulted a click on the button >> beside the processdata group/itemnames to the message No processdata for the given name template, when the processtemplates are displayed with their owner. Details see documentation OfficeTalk Workflow, chapter Processtemplates – Contextmenu – Historie - Filter…

Version 5.24 Buid 02.21.2015

Extension of HTML-Export of a processtemplate

The HTML-Export of a processtemplate contains now in the section Scheduling pathes of process for each path the scheduled steps with their scheduling values.

Extension of HTML-Export of a processtemplate simulation

The HTML-Export of a simulation starts with the base of the simulation of the steps. With this the HTML-File starts with the line Schedulingmode for steps: followed by With repetitions (self-link) or Without repetitions (self-link), depending on the choosen option With repetitions in the simulation dialog.

Option Use SSL in tabulator Mail in the settings dialog

With the option Use SSL sending and receiving mails was interrupted by some notifyers, indicating a bad certificate for login at the mailserver (inputfield Host). Sending and receiving mails is done implicitly by some menuitems of the tasklist and by services of the systemvariable Mail in a macro. Details for option Use SSL you will find in the documentation OfficeTalk Business-Process-Management, chapter Settings, section Tabulator Mail.

Version 5.24

Start process in tasklist and in dialog Start new process

The entry Start in the contextmenu of the processtemplates is grayed for the selected processtemplate, when since opening of the tasklist and the dialog Start new process the option Process can not be started of the selected processtemplate is choosen. For details please read documentation OfficeTalk Workflow, chapter Tabulator Processtemplates, section Start and chapter Start new process, section Start.

Managing processtemplates in a save way

To manage a processtemplate in a save way, you can lock the processtemplate and disable it for starting a new process while you manage it. When you are finished with managing, you can unlock the processtemplate. For details please read documentation OfficeTalk Business-Process-Management, chapter Tabulator Processtemplates section Options.
In this context the database table processtemplate is extended by column notStartable. Starting version 5.24 the first time adds the new column in the database table automaticly. Because of this you must login the version 5.24 the first time as company !

Version 5.23 Build 01.31.2015

Keyboard inputs of special characters in dialog Processgraph: <name of process>

Typing in any special character like Left, Right resulted since version 5.22 Build 2014.08.03 to an error message with ending of OfficeTalk, sorry.

Keyboard inputs of special characters in the sourcefield of a macro in the SkriptBrowser

Typing in CTRL-<any character> in the sourcefield of the macro in the SkriptBrowser leaded since version 5.22 Build 2014.08.03 to an error message with ending of OfficeTalk. Similar inputs in other dialogs may have affected the working too.

Contextmenu of the macodialogfield in the dubugger dialog

Opening the contextmenu (right mousebutton in the macrodialogfield of the debugger dialog) ended OfficeTalk with an error message, sorry.
The menuitems of the contextmenu for changing the text (Cut, Paste, etc.) where not grayed in opposite to their disabled function.

Version 5.23

Extension of the simulation of a process

The process simulation dialog Simulation of process <processname>, opened with the menu Simulation - Open in the processgraph dialog, contains the new checkbox With repetitions. Deselecting this option (is initial on), does not simulate the scheduling of repetitions of steps (links to self) when scheduling is choosen. For details please read documentation OfficeTalk Business-Process-Management, chapter Simulation.

Extension on the Pathes-Dialog of a process

The process pathes dialog, , opened with the menu Statistics – Times and pathes in the processgraph dialog, contains the new checkbox Pathes with repetitions are displayed. Deselecting this option (is initial on), does not display pathes containing links to self of a step. For details please read documentation OfficeTalk Business-Process-Management, chapter Executionpathes/-times.

Search… and Replace… in contextmenu of single line inputfields

The menuitems Search… und Replace… in the contextmenu of single line inputfields are not usable anymore (are grayed), because these functions makes no sense in single line inputfields.

Extension of onlinehelp for a Call-Statement for writing a macro

When writing a macro typing in the Tab-Key after the point of the scriptname of a Call-Statement brings up the list of macros of the typed in script only.

Unneccessary request to discard the changes on closing the ScriptBrowser

Closing a property page of an item of a processdialog (tabulator Processdialog) without changed any with the buttom Accept resulted in the false question Do you want to discard the changes in the macro, when closing the ScriptBrowser.

Hints for syntaxerrors compiling a macro

Syntaxerrors in the source’s dialogfield of a macros are diaplayed now for a better recognition with color red and bold.
Syntaxerrors in a source block of the statements addActionButton, addAction, etc. where displayed at the wrong position, when statements inside the actionblock contained doublequotes (““).. e.g. addAction(”dialog.selectionIndex(””history””) dialog.abc”, …) The text for the unknown service abc was displayed at the wrong textposition.

Extension of HTML-Export of an organigram

The HTML-Export of an organigram (menu File – As HTML… in the OrganigramBrowser- and in the OrganigramGraph-Dialog) includes for exported processtemplates (option Processtemplates in the exportdialog) in the section Processtemplates of worker <workername> for each processtemplate its diagram.

Dynamic update of windows content while dragging with the mouse on Windows platforms

The setting of redrawing obscured windows while a top windows is moved or resized is by default activated now. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings without userinterface.

Hyperlink of steps in a HTML-Export of a processtemplate

Under rare conditions two steps had the same hyperlink in a HTML-Exportfile. As a result clicking on this two hyperlinks leaded to the same step.

Extended HTML-Export of a process simulation

The HTML-Export of a process simulation, created with the menu As HTML… in the simulationdialog, is extended in general. The extensions include the possibility of navigation in a browser. The chapters can be fold and unfold with the link Fold – Unfold. Additionally the layout of the HTML-Layout of the export „beautified“.

HTML-Eport of processtemplates with subprocesses

A HTML-Export of a processtemplate with subprocesses (export of a worker in OrganigramBrowser with option Processtemplates, export of a processtemplate) resulted when Fold – Unfold of then worker with the processteplates in a wrong result in the browser.

HTML-Export of a callgraph of a macro

The HTML-Export of the callgraph of a macro, created with the menu File – Export as HTML in the dialog of the callgraph (opened with the contextmen Callgraph… in the listfield of the macros in the ScriptBrowser dialog), contains now also the source of the macros, whitch are contained in the callgraph. The Call-Statements in the source of the macros provide a hyperlink to make the following of the call sequence in a browser easier.

General Extension of HTML-Exports

All chapters in a HTML.Export provide now the hyperlink Fold –Unfold. Clicking on this hyperlink folds and unfolds the chapter. This makes the work with larger exports easier in a browser.

Contextmenus Search/Replace in inputfields

The Search/Replace-Dialog, opened with the contextmenu Search/Replace in inputfields, stayed open when the dialog with the inputfield is closed or replaced. Searching/Replacing then leaded to an error message with ending of OfficeTalk, when the related dialog was closed. Now the Search/Replace-Dialog is automaticly closed, when the dialog with the inputfield is closed or replaced.

Contextmenus Cut, Copy and Paste

The contextmenus Cut, Copy and Paste are chooseable (not grayed), if any text is selected or the paste buffer is not empty.

Extension of HTML-Exports of an organigram

For a easier navigation with the browser inside the hirarchy of the organigram with base of a worker, each worker contains a chapter of hyperlinks to the superior and subordinated organisation units/workers.

Hyperlink of step in the HTML-Export of an organigram

The hyperlink of a step may lead to the wrong step, when a same named step exists in more idendical named processtemplates contained in the export.

Picture of the organigram in all HTML-Exports

The picture at the top of all HTML-Export shows now the organigram of the selected worker (Department, Office, Team) and not the organigram of the complete company anymore.
For better navigation within the exported workers the diagram is now following a hirachical linklist of the exported workers. The hirachical list contains the exported organigram and for each contained worker a link for each of its exported category.

Extension of HTML-Exports of an organigram

The HTML-Export of an organigram in the OrganigramBrowser contains now for each exported worker its responsibilities (whitch steps of processes are scheduled by the worker) in the section Responsibilities of <name of worker>. To get this section, you must select the option Responsibilities in the options dialog of the export. For details please read documentation OfficeTalk Business-Process-Management, chapter Organigram, Section Save as HTML.

Extensions of HTML-Export for a processtemplate

The HTML-Export of a processtemplate contains now for more information the chapters Responsibilities und Executionpathes.

Version 5.22 Build 2014.09.26

Extended support for changing the name of a step

Changing the name of a step in the dialog Step and in the namendialog, opened with the step’s contextmenu Workingoptions – Name in the processgraphdialog, equalizes now the same items in tabulator Substitutes of the current worker. Because these changes can not be done automaticly in the other workers of the organigram, you get a dialog as hint, whitch names the modified processnames for the changes, whitch you must change manually. For details please read documentation OfficeTalk Business-Process-Management, chapter Dialog Step, section Category/Description

Extended support for changing the name of a processtemplate

The name of a processtemplate can now be changed in the tabulator Processtemplates, if no process of this template is executed allready. In the past this was possible, when using the locale databsase only. For details please read documentation OfficeTalk Business-Process-Management, chapter Tabulator Processtemplates, section Category und Description. In the past, after modifying the name of a processtemplate, the same modifying of the name in the tabulators Permissions, Substitutes and in the Start-Statements in the macros had to be done manually. Now the modifying of the name of the processtemplate changes its names in the tabulators Permissions, Substitutes and in the Start-Statements in the macros of the current worker automaticly. Because these changes can not be done automaticly in the other workers of the organigram, you get a dialog as hint, whitch names the modified processnames for the changes, whitch you must change manually.

Version 5.22 Build 2014.08.29

Extended analyze of the contextmenu Usings of the macolistlfield in the ScriptBrowser

When the selected macro is not used by Call-Statements, and it can be a startmacro, the usings of its script are displayed like the contextmenu Usings of the scriptlistfield. For details please read documentation OfficeTalk Business-Process-Management, chapter Scriptmacrolist, section Usings.

Script- and macronames ending with Call

Using scripts and macros, where the name ends with Call, resulted in problems:
- The export of a processtemplate, whitch uses such a macro, was denied with the message The macro could not be found.
- The contextmenu Uses… in macrolistfield of the scriptbrowser offered for such a macro bad used macronames.

Version 5.22 Build 2014.08.03

Contextmenu Directive – Assembly and Directive – Interface in the textfield of a macro

Using the contextmenu Directive – Assembly and Directive – Interface in the textfield of a macro, containing in the Scriptbrowser-Dialog, resulted in an error message with ending of OfficeTalk, sorry.

Toolbarbutton Save in the Scriptbrowser-Dialog

The toolbarbttuon Save in the Scriptbrowser-Dialog indicated after using the contextmenu of the macro listfield false the requirement for saving.

Removing a worker with contextmenu Remove in Organigrambrowser

Removing a worker with the contextmenu Remove in the dialog Organigrambrowser may have been aborted with a SQL-Errormessage.

The Workflowanalysis did not detect unknown Return value

The menu Extra - Workflowanalysis… in the process graph dialog did not detect the using of an unknown step result name in a Return statement, when the Return statement was used within an actionblock (e.g. addActionButton(”Return ””xyz”” …”, …)).

Onlinehelp for directive Assembly in a scriptmacro on Windows-Platforms

In the scriptmacro the onlinehelp for the directive Assembly (Tab-Key) did not offer the installed assemblies. The list of installed assemblies was empty after an error message, notifying about problems with analyzing.

Exporting processtemplate as HTML

Exporting in the process graph a processtemplate with the menu Process – save as HTML and using the file selection dialog twice built the filename for the export false.

CTRL-b in process graph and organigram graph

CTLR-b did not open the processmonitor dialog in the process graph and in the organigram graph.

Version 5.22 Build 2014.07.12

Wrong cursor under rare conditions

Under rare conditions the current cursor may not be the arrow, but the cursor indicating a drag-dop. In this case you can reset the cursor by performing login, opening the tasklist or opening the settings.

New menu item File - Exit in tasklist of startportal Function-/Organigram-Browser

For convinience the tasklist, used in the startportal Functions-/Organigram-Browser, supports the new menu File – Exit and the same named toolbar button. With this menu, it is easier to exit OfficeTalk in the daily work.

Extended behaviour of menu item File – Login

The behaviour of the menu item File – Login of the start portal Functions-/Organigram-Browser and of the startportal Dialog opens the tasklist of the logged in worker, when the tasklist was opened before. This makes it faster to open the tasklist of another worker in the daily work.

Onlinehelp for service processdata.item(…)

The onlinehelp of the service processdata.item(…) (typing the TAB-Key after the open bracket) offers now the group- and item names used in the other macros too. These names are following the grayed line Other names…. The onlinehelp by typing the TAB-Key after the argument in: contains only the group names, where the used item name is used.

Combobox for the itemname of processdata in the property dialogs of the Workbench

The combobox Item in the property dialogs of the Workbench for the definition of the processdata to be used contains for a better overview now the item names, whitch are known by the choosen group name only.

Version 5.22

Onlinehelp for service processdata.item(…) in the statements fields of the Workbench for new processdialog items

In the statement fields of the Workbenchdialogs the onlinehelp for the service processdata.item(…) did not contain the processdata names of the newly added processdialog items.

False request to save after using contextmenu Halt

After using the contextmenu Halt in the source filed of the SkriptBrowser a Save was requested when closing the dialog.

Onlinehelp for service processdata.item(…) in the statements fields of the Workbench

In the statement fields of the Workbenchdialogs no onlinehelp (Tab-Key) for the service processdata.item(…) was available.

Tabulator Description, Startstatements, Openstatements, Termstatements in the Workbench

After changing the contents in the textfield of the tabulators the Button Create in the Workbench dialog was not enabled.

Menu File – Close/Back of the Workbench dialog

The menu of the Workbench dialog is now enabled after modifications in the Workbench too. When changes are done, you are asked wether to close the Workbench.

Tooltip in the property dialogs of items of the processdialog in the Workbench

In the property dialogs of items of the process dialog (tabulator Processdialog) the tooltips are now available when touching the fields with the mouse.
The tooltip of the button Create of the Workbench dialog tells now detailed, wether the button is disabled.

Onlinehelp for the services doubleClick and notTabable of the systemvariable ScriptDialog

For the services doubleClick and notTabable of the systemvariable ScriptDialog the onlinehelp is available now in the statement fields of the Workbench dialogs and in the source field of the ScriptBrowser.

Using of a SQLString-Variable in Macro

Using a SQLString-Variable in an Array-Statement (e.g. Array(<SQLString-Variablename>, …) did not use the content of the referenced variable, but the name of the SQLString-Variable (e.g. $xxx).
Using in a Return-Statement a SQLString-Variable (e.g. Return <SQLString-Variablename>), did not return the content of the referenced variable, but the name of the SQLString-Variable (e.g. $xxx).

Contextmenu Rename in the macrolistfield of the ScriptBrowsers dialog

Changing the case of the macroname only did change nothing. Changing the case was recognized as no modification.
In the macros, where the renamed macro was used within another statement or within an expression, the renaming was done incorrect. The part of the statement or expression following the Call of the renamed macro was cut off. And because of this, a macro with incorrect syntax was leaved.

Contextmenu Halt in ScriptBrowser dialog and in Debugger dialog

The contextmenu Halt is now enabled only, if the cursor is at a statement, whitch is haltable. In the past the contextmeu was enabled ever. This leaded to some irritations, when the macro was not halted at this statement. Additionally the contextmenu is enabled at each Case- and Case Else-Statement of a Select-Statement.

Extensions of the Debugger dialog for debugging a scriptmacro

The debugger dialog contains the new button Single Step. The button works like the button Step, but for a Call-Statement the debugger switches the called macro, where you can Step and Single Step the called macro. The button Step executes the called macro, but does not switch to the called macro as before.
The new contextmenu Proceed up to here of the textfield with the statements executes the next statements and halts at the statement under the cursor. With this you can execute more statements and halt at succeeding statement to proceed with stepping. For details please read documentation OfficeTalk Business-Process-Management, chapter Debugging script macro.

Last statement and button Step in Debugger dialog

Clicking at the last statement of a macro the button Step in the Debugger dialog, ended the macro, but not the Debugger. As the result OfficeTalk was not usable anymore and had to be ended hard.

Version 5.21

Extension of variablelistfield in the skriptdebugger dialog

The listfield of the variable listfield in the debugger dialog supports now a contextmenu. With this you can open the dialog of the variables content and copy the variables content into the pastebuffer.

Service value(…, put: …) of the systemvariable ScriptDialog for an item in a processdialog with date-/datetime-column from a MS-SQL-Server Select

Putting the result column of a Select statement in a MS-SQL-Servers with the service value(…, put: …) into an item of a processdialog was denied with the message Invalid argument <Argument>, when the column was defined as date or datetime.

Sorting of the statements in tabulator Processdialog of the Workbench

Opening the tabulator Processdialog in the Workbench did not sort the statements. Now the statements are sorted by the column X/Y.

Contextmenu in OrganigrammBrowser for a locked worker

The contextmenu for a locked, but not selected worker, did not reflect the this worker. e.g. To unlock a worker, it has to be selected first and second had to be unlocked with the contextmenu Unlock.

Dynamic update of windows content while dragging with the mouse on Windows platforms

As a basic setting when dragging windows with the mouse, obscured parts of windows are not redrawed. The obscured parts leaved gray until the dragging was ended. To enable dynamic redrawing, use the environment setting DynamicRedraw. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings without userinterface.

New service selectItems of the systemvariable ScriptDialog

The new service selectItems gets the name of the processdialog items, in whitch items can be selected. e.g. comboboxfields, listfields, etc. The service inputItems gets now only the name of the processdialog items, in whitch any input can be done. e.g. inputfields, radiobutton fields, checkbox fields, etc.

OfficeTalk did not react sporaticly

Under rare conditions (fast mouse activities over different windows) OfficeTalk did not react to mouseclick anymore. In such situations OfficeTalk must be terminated hard.

Removing items of a processdialog in the Workbench

The contextmenu Remove... of the processdialog in the Workbench removed on more selected items the clicked item only. Removing more selected items was possible with the key Del only.

Version 5.20 Build 2014.05.22

Property dialogs for dialog items of a process dialog in the Workbench

The property dialogs for items of the process dialog in the Workbench are opened non modal now. With this you can work, while a property dialog is opened, with the other tabulators of the Workbench for retrieving informations e.g.

New service asAssociations for the variable Array in macro

The variable Array supports the new service asAssociations. The service converts the Array into a new Array with Associations for each contained Array. An Association contains a key and its value. As a condition for conversion the Array must contain Arrays with each two items. The first item is the key. The second item is its value. This Association-Array can be used in the processdialog’s items combobox and listbox. With the service value(…) of the systemvariable ScriptDialog you get not the selected value, but its corresponding key. For details please read OfficeTalk Skript, chapter Services of the datatype Array and OfficeTalk Skript, chapter value(…). and chapter value(…, put: …).

Version 5.20 Build 2014.05.10

Emergency exit for an infinite execution of a macro

Executing a macro in test mode, the debugger can be opened with the key ESC. With this you can interrupt and terminate an infinite execution of a macro. A simple example for an infinited execution is:
Dim i as Integer
i = 1
While true = true
i = i + 1
Wend
The condition true = true would result in an infinite execution and can be interrupted by execution of OfficeTalk only. Now you can open the debugger with the key ESC and terminate the execution of the macro. This emergency exit is available in testmode (Execution with the macro with contextmenu Execute in SkriptBrowser) only.

Defining in the Workbench action statements with an empty second line

Defining in the Workbench action statements for an Action or Actionbutton item containing an empty second textline resulted in an error notification with ending of OfficeTalk when building with the button Build.

Login with a language different to German

Logging in with a language different to German provides now the processing of currency and date fields with the rules of the selected language.

Login with a different language using the next program generation

Defining in the login dialog a different language, when used the next program generation, resulted in a failure behaviour of the application. The correction is for the next generation of OfficeTalk and not for the current one. But because of technical reasons, some changes had to be adopted in the current version.

Version 5.20 Build 2014.04.17

Behaviour of the Workbench dialog on selection of a script or a macro in the Scriptbrowser dialog

Selecting a script or a macro in the dialog of the Scriptbrowser with opened Workbench dialog will close the dialog of the Workbench. When the macro is changed in the dialog of the Workbench, you get a question dialog. If you answer No, the selection of the script or macro is not accepted and then dialog of the Workbench stays open. If you answer Yes, the changes in the dialog of the Workbench are abandoned and the dialog of the Workbench is closed and the selection of the script or macro is accepted.

Inserting incompatible data into an dialogitem with the service yalue(…, put: …) of the systemvariable ScriptDialog

When providing in a macro a dialogitem with the Service value(…, put: …) an incompatible data, a special error message will be used, instead of the general error message (e.g. Array instead of String for an input field).

Contextmenu Workbench in listfield Macros in the dialog of the SkriptBrowser

After compiling a macro the contextmenu Workbench was disabled and had to be enabled by selecting another macro in the listfield.

Messagedialog „An error occurred withing a cain of macro call…“ and setting OfficeTalk for messageboxes

The messagebox „An error occurred withing a cain of macro call …“ the setting OfficeTalk for messageboxes was ignored. This message was used ever with the setting Plattform for messageboxes.

Button Create in the dialog of the Workbench

The button Create in the dialog of the Workbench does not only create the macro anymore, but does it compile too. Using the Startportal Function-/Organigrambrowser closes the dialog of the Workbench. Using the Startportal Dialog brings the dialog of the ScripBrowser to the front and lets the dialog of the Workbench opened.

New onlinehelp for item- and groupnames in the services of the systemvariable processdata

In the services of the systemvariable processdata typing at the place of item- or groupname the TAB-Key opens a selection dialog with the available item- or groupnames. For details please read documentation Business-Process-Management, chapter Onlinehelp for names of processdata.

Version 5.20 Build 2014.04.04

Saving with opened SciptBrower-/Workbench-Dialog using startportal Function-/Organigrambrowser

Opening the ScriptBrowser-Dialog in the tabulator Start- User- or Endaction with the button >>, closed the Scriptbrowser-Dialog with its opened Workbench when the changes are saved (Toolbarbutton of the ScriptBrowser-Dialog or Toolbarbutton of the startportal). Because of, proceeding with working in the workbench was not possible.

OfficeTalk used after relogin without new start outdated data

After a relogin without new starting of OfficeTalk, it used outdated data, if in the meantime on another workstation changes where made. E.g: Desk logged in and macro X.Y was executed by a process. Company logged in and modified macro X.Y. The same desk relogged in without new starting OfficeTalk and executed process again. The outdated macro X.Y was executed.

Extended settings for Source of item an Target of item in the Workbench

These setting dialog supports the buttons As Source and As Target for using the settings of vice versa setting part. For details please read documentation Business-Process-Management, chapter Source of itemvalue and chapter Target of itemvalue.

Comboboxes for processdata (Group und Item) in all propertydialogs of the Workbench for source and target

The comboboxes Item and Group in the setting dialogs e.g. Source of item and Target of item.of a dialog item in the Workbench contains now the processdata names used in the other macros of the script, because these names may be used in the macro too. For details please read documentation Business-Process-Management, chapter Source of itemvalue and chapter Target of itemvalue.

Opening processdialog in the Workbench on computers with multiple screens

On computers with multiple screens configured vertically the tabulator Processdialog opened the processdialog in such a way, that the opened processdialog could not be moved with the titlebar, when the workbench’s dialog was positioned on top of the lower screen.

Version 5.20 Build 2014.03.20

Notification when ending OfficeTalk on all Windows platforms

Ending OfficeTalk on a Windows platform resulted under special conditions in the notification COM resource registries were not emptied by release logic (what to do?!). The message appeared when a special macro in a processflow, whitch was using a communication library, has executed. The ending was proceeded normally after answering the message, but the additionally message was disturbing !

Version 5.20 Build 2014.03.09

Exporting processtemplate MacroBuilder – FilloutPrintSave

Exporting the processtemplate MacroBuilder – FilloutPrintSave was aborted with the message The macro Text.CheckMark(…) is not found within the workers hirarchy, because the process uses macros, whitch are not handled correctly for export. The processtemplate MacroBuilder – FilloutPrintSave is not contained in the standard delivery, but can be ordered separate.

Enhances of onlinehelp for wrinting a Scriptmacro

Opening the onlinehilfe for all kind of statements, when writing a macro, is done now by typing the TAB-Key at the responsible position and not the Space-Key anymore. Additionally the way, of how the onlinehelp is opened, is made more consistent. For details please read documentation Business-Process-Management, chapter Onlinehelp for input of sourcecode.

Version 5.20 Build 2014.02.28

Scriptmakro for dialog with action with the option Accept changes immediatly

The option Accept changes immediatly in the property dialog of an action resulted, when opening the dialog, in an error message. Answering the error message proceeded the macro, but the specified action was not executed.

Version 5.20

Online help when writing a macro did not work

In the Workbench and in the macro dialog, the online help did not work since version 5.10. e.g. Typing a space after the statement Return did not open the available step results.

Documentation for step results

For a complete documentation of a process the step results can be described. With this description the reason of a branch of the processflow can be documented. This documentation is written with the button Decscription… in the tabulator Stepresult.

Version 5.10 Build 01.05.2014

Extension for technical diagnostic

For technical diagnostic a process monitor dialog can be opened with the keyboard key CTRL+B for others than using level Beginner. This dialog is opened on Windows platforms always on top of all other opened dialogs. Because of this, if opened from a modal dialog, like processdialog, you must end the processdialog first, before you can work the process monitor dialog. The process monitor dialog shows all internal leightweight processes of OfficeTalk. For working internal processes in this dialog, very familiar knowledge of the internal processes (threads) is required ! For details please read documentation OfficeTalk Generals, chapter Processmonitor – Internal Processe.

Menu Export… and Save as HTML… for history of process, process graph, process and worker

Menu item Export… and Save as HTML… (workers listfield in the OrganigramBrowser, listfield of processes in the tabulator Processtemplates, process graph dialog, history dialog of process in the tasklist) leads to an error message with ending of program when the name of the item to export (process, worker) contains a character, whitch is not supported by the filesystem of platform (e.g. “Your IT: Mara (Ad-Hoc)” contains a double point in the name of process in the tasklist, whitch is not supported on the Windows platform).

Toolbar of a dialogs, opened in the tasklist in startportal Function-/Organigrambrowser

When using the startportal Function-/Organigrambrowser dialogs,opened from the tasklist (e.g. State of the task), does not contain anymore unusable buttons like Login, Exit, etc. Such buttons are accessible in the toolbar of the tasklist only.

Wrong picture of toolbarbutton Term process in tasklist using startportal Function-/Organigrambrowser

When using the startportal Function-/Organigrambrowser, switching back in the tasklist from the history of a process to the processlist displayed in the toolbar the button for exiting the program instead of the button for terminating a process. Using the button performed the right action, but the image was wrong.

Resizing/moving windows and dialogs on all Windows-Platforms

OfficeTalk is based now on VisualWorks Version 7.8.1. Resizing and moving windows does not leave overlapping windows grayed, but displays these windows and dialogs with their current content, if the system setting of Windows „System control – Dialogs – Window color and Appearance– Effects – Display contend on sizing“ is set on.

Resizing an inputfield of a process dialog in the workbench with the mouse

For resizing an inputfield of a processdialog in the workbench the cursor had to be positioned exact in the middle of the left or right border. If not positioned exact, the cursor became a hand and the field could be moved only. Now the right and left border of an inputfield is ever active for resizing.

Receiving eMails with attachments with the service receiveAndRemove(…) of the systemvariable Mail

Receiving eMails with attachments with the service receiveAndRemove(…) of the systemvariablen Mail ignored the attachments of a eMail without any text in its body.

Unfolding/unfolding worker hirarchy in Organigrambrowser

Unfolding/folding an oganisationunit (Office, Department, Team) in the organigamlistfield of the Organigrambrowser and the Function-/Organigrambrowser can be done with double clicking the organisationunit and with Arrow-Left/-Right key of a selected organisationunit.

Version 5.10 Build 11.17.2013

Service executePost und executeGet of the systemvariable HTTPClient

The services executePost(…) und executeGet(…) of the systemvariable HTTPClient may be aborted in a macro with the message „Invalid certificate…”.

Defining in the Workbench for a label a shortcut

Defining in the property dialog of a label a shortcut with the combobox Shortcut for: aborted OfficeTalk when pressing the button Create, sorry.

Setting Single-Sign-On und Using level

The values of the settings Single-Sign-On and Using level where used from the not logged in state ever. Changing these settings after logging in did not alter the behaviour at the next program start.

Version 5.10 Build 11.08.2013

Fetching eMail with attachment with the systemvariable Mail

The service receiveAndRemove(…) of the systemvariable Mail did not receive any attachment of an eMail.

Function-/Organigrambrowser and menü Filter processes – Filter of the tasklist

Using the startportal Function-/Organigrambrowser and closing the filterdialog of the menu Filter processes – Filter of the tasklist left for a short moment a gray background at the place of the closed filterdialog. This was not an important fact, but neverless…

Version 5.10

Giving settings in the commandline

In the commandline only simple and no qualified settings (e.g. ProcessLayout\Margin) could be given.

Starting with a Hyperlink from a Hyperlink enabled application

OfficeTalk can now be started by any application whitch in enabled to use hyperlinks. For details please read documentation OfficeTalk Generals, chapter Start with Hyperlink.

New command line option for scheduling a process

The new command line option –Schedule can be used to start a specified process first. For details please read documentation OfficeTalk Generals, chapter Command line options.

Menu View – Select processes - By in Tasklist

The start- and enddate in the Settings of the tasklist (menu View – Select processes - By) could not be cleared, when you had used these settings before the update to version 5. Clearing these settings by choosing option All used the prior setting ever.

Opening Help with toolbar and menu Help

On the platforms Windows-7 and Windows-8 the documents for help could not be opened with the toolbar button for help and the menu Help.

Version 5.01 Build 09.06.2013

Selecting an Assembly- or Interface-Service in the selection dialog of the macro dialog

In the selection dialog for a service of a DotNET- (Directive Assmbly) or a COM-Component (Directive Interface) in the source dialog of a macro the OK-Button for accepting a selected service was grayed ever. To accept, the selected service had to be double clicked.

Receiving eMail with attachment

Reveiving an eMail with attachment with the services receiveAndRemove(…) and receiveFrom(…) stored the attachment with wrong format in the attachments directory. As a result an attachment could not be opened with its associated application.

Version 5.01 Build 08.24.2013

Using in an actionblock a Call-Statement with a global variable as argument

Using in a macro a processdialog with an actionblock (addAktion(…), addDoubleAction(…)) containing a Call-Statement (Call <Script>.<Macro>(…)) with a global variable (Public Dim) as argument, ended the execution of the actionblock with the message The Scriptmacro <Script>.<Macro> (…)) could not be found….

Sending and receiving eMails

Sending and receiving eMails with the protocol setting IMAP in the mail settings was not possible. As the result sending an eMail with the services of the systemvariable Mail and asking with the menu Ask in the tasklist, did not work correctly.
With the setting Use SSL in the mail settings sending an eMail with the services of the systemvariable Mail and asking with the menu Ask in the tasklist was not possible.

Macros for using variable columns width in tableitems of a processdialog

For easies using variable columns width of a tableitem in a processdialog the setup contains the script TableTools. This script contains the macro TableTools.CustomizeColumns(...) for setting the columns width of a tableitem and the macro TableTools.ArchiveColumns(...)for remembering the actual columns width of a tableitem for the next TableTools.ArchiveColumns(...) at open time. With these macros each worker has its private columns width for a tableitem in a processdialog. The script TableTools.bos can be imported from the folder Library. For details about importing a script please read documentation Business-Process-Management, chapter Scriptlist.

New services für reusable columns width of a table in a processdialog

For reusing of the columnswidth of a table in a processdialog the systemvariable ScriptDialog supports the new services columns(…, width: …). and columns(…). With help of the new services the columns width of a table in a processdialog can be requested at closetime and be reused for the next open of the processdialog.

New services useIMAP and usePOP3 of the systemvariable Mail

With the new services useIMAP(…) and usePOP3(…) you can overwrite the type of mailserver of the general settings while working with the systemvariable Mail. For details please read documentation OfficeTalk Skript, chapter useIMAP(…) and usePOP3(…).

Contextmenu Execute with selected source in Scriptbrowserdialog

With the contextmenu Execute the selection of a Return-Statement and a binary expression (e.g. 1+1) could be executed only. All other types of statements resulted in the message Error while compiling….

Action of a step executed the wrong startmacro

Because of a programming error (shame on me) the action of a step executed under some circumstance not the startmacro, but a wrong macro. This resulted in the message Select the result für the next step.

Version 5.01

Processdialog with not displaying columns in a table

Providing the table of a processdialog with rows containing more columns as the table defined, these not displaying columns where tried to prepeare. If one of these columns contained unusable data, the opening of the processdialog was aborted with an error message.

New contextmenu Uses in the sourcefield of a scriptmacro

The contextmenu of the dialogfield of the macro source supports for faster working the same item Uses as the listfield of the makros. For details please read documentation OfficeTalk Business-Process-Management, chapter Source.

New option Hyperlink in propertydialog of items Inputfield and Textfield of the Workbench

The new option Hyperlink in the propertydialog of the items Inputfield and Textfield of the Workbench displays the textfields marked with {{ and }} as hyperlink. Clicking with the mouse on such a marked textfield opens the file or URL. For details please read documentation OfficeTalk Business-Process-Management, chapter Propertydialog Inputfield and Textfield. Additional the systemvariable ScriptDialog is added with the service hyperlink(…). For details about hyperlink(…) please read documentation OfficeTalk Script, chapter hyperlink(…).

Extended mailservices to work for all mails of a mailbox in a process

To work for all eMails of a mailbox in a process, the services of systemvariable Mail are extended. The service receiveAndRemove (), and the variants of service reveiveFrom(….) return now all eMails matching the given criterias as an Array. The result Array for a single eMail contains as the first item the unique id of the eMail. With the new service detele(…) and this unique id eMail can be deleted in the mailbox. With this extension eMails can be readed in a first step and with service detele(..) be deleted in a second step depending on conditions of the processflow. For details please read OfficeTalk Skript, chapter delete(…), receiveAndRemove(…) and reveiveFrom(…).

Version 5.00 Build 04.14.2013

Using an userdefined background color for dialogs

A userdefined background color (button Setting… im groupbox Backgroundcolor of tabulator Generals) was not used in the tabulator dialogfields and in the label of groupbox dialogfields.

Version 5.00

Zero-Installation campane

For the Zero-Installation campane all settings of an OfficeTalk-Worker are managed in the database. The migration into the database for existing workers is done at login time and notified when ended. Therefore settings are not dependent on the local machine, but on the OfficeTalk-Login. So, an OfficeTalk-Worker keeps hold on his settings, when changing the client. By this new managing of settings an organisation unit (Department, Office, etc.) can additionally preset settings for its subordinated workers.
In this context the new database table setting is required. When the version 5.00 is started the very first time, OfficeTalk will create this table in the schema of the OfficeTalk’s database. So you must login this time as company !

Processdialog supports menubar

A processdialog can be configured to support a menubar and useraction can be activated not only by an action button, but by a menu too. For details please read documentation OfficeTalk Business-Process-Management, chapter Workbench, Tabulator Processdialog – With menubar.

Extended labelkey selection in Workbench

The dialog for selecting a labelkey for a labeled dialogitem in the workbench is extended. With Display label for labelkeys the used labels for the labelkeys are displayed. And with the button New labelkey you can create a new labelkey with its assigned labeltext. For details please read documentation OfficeTalk Business-Process-Management, chapter Propertydialog Label and Label Courier.

Tabulator Generals of settingdialog is extended

In tabulator Generals of the settingdialog you can affect the memory of dialogs. With these settings the extends of dialogs and positions of the resizers in dialogs are used from the previous open. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings – Tabulator Generals.

Tooltip was missing for some dialogitems

Some dialogitems did not show its tooltip when touching with the mouse. This is not bad, but tooltips are helpful and each because of, dialogitem should support its tooltip.

Dynamicly defining the sequence of steps scheduling for a process

To define the sequence for the steps of scheduling dynamicly, a worker can select with the statement Return stepscheduler.userChoose in a startmacro the next step for scheduling. Ending a startmacro with this statement, enables the worker to select in the step end dialog any step within the process as the next step, its worker and its startdate as the next step of work. With this you can define your own flow of control within the process.

Searching for a Systemmacro with menu Work – Search

Searching for a Systemmacro with the tabulator Scripts resulted in an entry with the found script instead of the found macro. Because of, clicking the entry opened the script instead of the found macro.

Exporting organigram with using startportal Function-/Organigrambrowser as HTML

With the menu File – Save as HTML of the startportal Function-/Organigrambrowser the organigram or parts of the organigram can be exported as HTML, like in startportal Dialog. For details please read documentation OfficeTalk Generals, chapter Startportal as Function- and Organigrambrowser - Menü.

Version 4.91 Build 12.15.2012

Opening the tasklist as an organisation unit

Opening the tasklist as an organisation unit (Company, Department, Office, Team) could result in a diagnostic with ending OfficeTalk. This could happen, when in the meantime a worker within the organisation unit has ended a process.

Extended diagnostic for the service processByIdentity(..)

For better diagnosting problems of the service processByIdentity(‚…) its logging is extended. Additionally the database query is made more save. Accessing processes of other worker should be more stable by this change.

Simpler using of a HTML-Export (Menu Save as HTML)

The pictures for the HTML-Export are inlined in the export file with the new option Pictures inside the HTML file of the optionsdialog and not created as separate files. By this, when transporting the HTML file, no extra picture files (files with the extension .png) must be transported. The HTML-Export of organigrams, processtemplates and call graphs of macros are affected by this change. In all other HTML exports (histories, process simulations etc.) the pictures are inlined by default.

Version 4.91 Build 12.05.2012

Extensions for the HTML-Export of an organigram (Menu Save as HTML in Organigrambrowserdialog)

Using the options Resources and Skripts in the optionsdialog provides the statements stepscheduler.consumed(…) within a macro for the resourcename with a hyperlink. The hyperlink leads to the description of the used resource.
For a better orientation in the HTML all sections are prefixed with their picture.

Statement Library with communication library for the full functionality of Microsoft Word

Loading in a macro with the statement Library the communication libraries Microsoft Office, Microsoft VBIDE and Microsoft Word for the full functionality of Microsoft Word was aborted since Version 3 with the notifyer Loading of library is aborted. This error was not known, because in most cases the communication library Microsoft Word Small is used for integration of Microsoft Word into process flow.

Version 4.91 Build 11.22.2012

New buttons in Settings dialog

The settings dialog supports the new buttons Shortened Settings and Full Settings for affecting the speed of working in OfficeTalk. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings.

Taskareas are exported with the HTML-Export of an organigram (Menu Save as HTML in Organigrambrowserdialog)

The taskareas of a worker are now exported by the HTML-Export of an organigram by selecting the option Taskareas in the options dialog.
Using the options Processtemplates and Scripts in the optiondialog provides additionally hyperlinks in the HTML-Export for a better navigation:
Starting subprocesses by a processtemplate provides in the section Subprocesses of the processtemplate hyperlinks to the subprocesses. Additionally you will find in the section Subprocesses of the step, whitch starts the subprocess, hyperlinks to the processtemplate, whitch is started by the step. The Start-Statement in a macro is provided with a hyperlink to the subprocess.

Extensions for the HTML-Export of an organigram (Menu Save as HTML in Organigrambrowserdialog)

Exporting the processtemplates (option Processtemplates in the optiondialog) provides for the scheduling worker of a step a hyperlink. The hyperlink leads to the description of the worker.
Exporting the scripts (option Scripts in the optiondialog) provides for each Call statement in a macro a hyperlink. The hyperlink leads to the called macro, similar to the HTMP-Export of a processtemplate.

Optimisations for the HTML-Export of a processtemplate (Menu Save as HTML in dialog Graph for process: <name of processtemplate>

Using the option Scripts in the optiondialog did not provide the hyperlink for a Call statement as argument within a Call statement.
Using in a startmacro a Call statement with the same startmacro resulted in an infinite loop when the option Scripts in the optiondialog was used. This Call statement makes no sense and is wrong in general, but the HTML-Export must be immune against such mistakes !

Version 4.91 Build 11.2.2012

Improvement of the service processByIdentity(…) of the systemvariable process in a macro

Under some rare conditions the service processByIdentity(…) in a macro did not find the process with the given identity. This was a sporadic effect on long usage of OfficeTalk and comprehensive work with different logins.

Macro was missing in the HTML of an exported processhirarchy

Using the export with option Each macro only once did not contain the macro in the export of the main processtemplate, when the same macro was used in a subprocess too.

Macros may not be where exported with HTML-Export

The exported process or processhirarchy (menu File – Save as HTML in dialog Graph for process <templatename> and in hirarchydialog Hirarchygraph for <templatename>) may not contain under some conditions the used macros, but the option All Macros was used. These macros where flagged with a red note in the HTML-Export.

Wrong links in HTML-Export of a processtemplates and a hirarchy of processtemplates

In an exported process and processhirarchy (menu File – Save as HTML in dialog Graph for process <templatename> and in hirarchydialog Hirarchygraph for <templatename>) the links in description fields of the process and its steps and the links to its subprocesses did not work in the browser. Clicking such a link in the browser resulted in an error message and the link was not opened in the browser.

New navigations in browser for a HTML-Export of a processtemplate and hierarchy of processtemplates

Exporting a processtemplate with the menu File – Save as HTML in dialog Graph for process <templatename> and in hirarchydialog Hirarchygraph for <templatename>) as HTML-Export with the options Scriptmacro and Submacros provides for the macroname on each position, where a macro is used (startmacro of an action and Call-Statement in a macro) a hyperlink. Not accessible macros in Call-Statements are noted at the end of the macro with a red note. The hyperlinks of these macros are displayed striked out.
Using the exportoptions Scriptmacro or Submacros, the Start-Statements are emphasized with a hyperlink. With this link you can navigate the subprocesses. Not accessible subprocesses are emphasized with a striked out Hyperlink.
The export part of a step contains under The succeeding steps: the hyperlinks to the possible next steps. With these links you can easy navigate forward the execution path of a processtemplate.
The export part of a step contains under The preceeding steps: the hyperlinks to the possible previous steps. With these links you can easy navigate back the execution path of a processtemplate.
Using the exportoption Scriptmacro, the Return-Statements of start macros are emphasized with a hyperlink. With this link you can easy navigate to this next step.

Run a makro in ScriptBrowser with the contextmenu Debug

Running a macro with the contextmenu Debug in the SkriptBrowser dialog, and executing the last statement with the button Step of the debuggerdialog, ended the macro and the ScriptBrowser dialog was frozen and could not be used anymore, sorry.

VB-Statement Select Case is supported by Scriptmacro

In a macro the statement Select Case can be used now. This may avoid long If-The-Else constructs. For details please read OfficeTalk Script, chapter Statements - Select Case.

Compiling a macro with similar arguments of an existing macro in script was not accepted

Compiling in ScriptBrowser a macro was rejected, when a similar macro in the script was existing allready. e.g. When the macro GetParameterValues ( LogicalName As String, ParameterType As String, A As Array ) was existing in the script, compiling in the same script the macro GetParameterValues ( LogicalName As String, ParameterType As String, ReadOnly As Boolean ) was rejected with the notification The scriptmacro can not be accepted, because a same name scriptmacro with the same signature (name and arguments) does exist allready.

Version 4.91

Labels of register pages in dialogs with register

For a better visualisation each label of a registger page in most dialogs with a register is preceeded by its icon.

New services for registers in a processdialog

With the new services page(…, register: …, indication: …) and label(…, register: …, with: …) of ScriptDialog you can use in a processdialog for the label of a page in a registeritem an additional icon.

Dialog Wizzard for finding a worker and dialog Analyzing graph for process

Because of the count of the tabulators in these two dialogs is increased in the meantime, the names of the relevant tabulators are indicated for faster recognizing with a preceeding arrow. In the dialog Wizzard for finding a worker the tabulators containing search values are affected. In the dialog Analyzing graph for process the tabulators containing detected problems are affected.

n diesen beiden Dialogen mittlerweile stark angewachsen ist, werden die Namen der relevanten Registerseiten in den Laschen für einen schnelleren Überblick fett dargestellt. Im Dialog Assistent für Bearbeitersuche betrifft dies die Register, in denen Suchwerte eingetragen sind. Im Dialog sind Ablaufanalyse des Vorgangs betrifft dies die Register, in denen Unstimmigkeiten bei der Ablaufanalyse erkannt wurden.

Exporting a processtemplate in tabulator Processtemplates

Cancelling the file selection dialog for naming the filename of the to be exported processtemplate with the button Cancel, when using the contextmenu Export in the listfield of the templates, did not export the processtemplate, but opened the dialog of the export results. This could get to little confusion.

Using with Workbench foreground and background colors for dialogitems in processdialog

In the workbench (tabulator Scriptdialog) for some dialog items a given background and foreground color could not be reverted with option Default to the default color.

Dialogitems Label Courier and Listfield Courier in the Workbench

Inserting in a processdialog with the Workbench (tabulator Scriptdialog) the item Label Courier or Listfield Courier resulted in a diagnostic. These items are obsolete since the availability of fonts for labels and the item Table, but if they are present, they should work !

Contextmenu Cancel in renamed to All Undo

The contextmenu Cancel in all input fields of type text is renamed to All Undo, because it undoes all inputs and in reverts the content of the input field to the previous state.

Some services for systemvariables results in a script diagnostic

Introducing the extended services for an Array (version 4.90 Build 07.26.2012), some services (e.g. remove(…) for systemvariable ProcessData) are not executed, but resulted in a script diagnostic, sorry.

Executing selected statements in text field of the macro

With the contextmenü Execute some selected statements can be executed for tests. When the selected statements contained a Library-, Interface-, or Assembly-directive, the execution was since version 4.86 aborted with a notification.

Column Delay in the tasklist as table

Since version 4.86 Build 05.31.2012 the column Delay (the coloured point) was displayed false, when the column was arranged with the contextmenu Columns after the column Worker, Process or Step, and the setting Indicate red delay in tabulator Tasks of the settings dialog was activated.

Contextmenues Cancel and Accept in input fields

The contextmenues of all input fields offered the items Cancel and Accept, but reverting to the previous content or accepting the input was not possible in all input fields. Now the menu items are available only in input fields, where reverting and accepting is supported.

Extended wizard for searching

The tabulator Scripts of the search dialog Wizard for finding a worker in: <workername>, opened with the menu Work – Search, supports the new option Empty macro. Using this option, you can search for empty macros within the searched worker hirarchy. An empty macro results in an error message, when the empty macro is used within the execution of a process.

Importing a worker in the organigramdialog

Importing a worker with the contextmenu Import... in the listfield of the organigramdialog from a local database, whitch contains a script with a to big macro, ended OfficeTalk with a diagnostic notification. This was possible, because using a local database did not limit the macro. Now, you get a notification for this to large macro and the source of the macro is not imported.

Version 4.90 Build 07.26.2012

Missing initiator of delegation of a process in the history

In the history dialog the initiator of a delegation was missing in the field from: of the entry for the delegation. In this field the initiator in posted, when he is not the owner of the process at time of delegation.

Missing statement Close for an opened file (Variable File) in a macro

Omitting the statement Close, for a file opened with the statement Open (Variable File), leaved the file locked until the program is ended. The file could not be deleted in the file management of the OS, until the program was ended. Now the file is unlocked at the end of the macro automatic.

Special services for variable of type Array-in macro

For easier working with an Array, a few basic services, like finding, adding and removing items, are supported by Array. The onlinehelp for a ScriptVariable of type Array offers the available services. For details of the services please read OfficeTalk Script, chapter Services for Array.

Version 4.90

Updating installations of version <= 4.70

When an installation of version 4.70 or lower should be updated with a newer version, and the database must be actualised too, the first start was aborted with the message The update of the database is aborted, OfficeTalk can not be used, when the login of the company was not synchronized already.

Importing processes form AENEIS and MO²GO

The notification, when importing a faulty process from AENEIS and MO²GO, is now more detailed, to enable a better diagnostic.

Importing a process and a script with the contextmenu Import… in the listfield for processtemplates and for scripts

When a process or a script is imported with it contextmenu Import… of its listfield, all macros a requested to import since version 4.86, no matter whether the import version is modified or not.

Writing a processdata item with different types of value in macro

When writing in a macro with the service item(…, with: …, in: …) of the systemvariable processdata an item and actualising this item with the service item(…, with: …, in: …), using a value of different type, a succeeding service item(…, in: …) may not get the actualised value, but value of the first write.

Contextmenus Uses... and Graph… of macrolistfield in ScriptBrowser

The contextmenues did not recognize the Call-Macro-Statement, used in and actionblock of a dialog macro, when the Call-Statement was following immediately after the starting quote of the actionblock. (e.g. dialog.addActionButton(“Call Script.Macro …”). As a result, the contextmenu Uses... did not contain Script.Macro and the diagram of the contextmenu Graph… did not contain the macro Script.Macro.

For the macro specialists: Assigning a variable with a multi dimensional Array

Wenn eine Variable mit einem mehrdimensionalen Array belegt wurde, konnten die Variablen der 1+n-ten Dimension nicht mehr richtig verwaltet werden. Dies machte sich in der Regel durch eine Diagnosemeldung beim Zugriff auf eine Variable der 1-n-ten Dimension bemerkbar. Die Erzeugung eines derartiges Array ist innerhalb eines Makroablaufes nur durch den Dienst einer Kommunikationsbibliothek möglich (z.B.. Der Dienst getRows(…) der Systemvariablen SmallCOM.ADODB.Recordset in der ADO-Kommunikationsbibliothek).

Invalid using of service processByIdentity(…) of the systemvariable process

Using the service processByIdentity(…) of the systemvariable process with an argument other than a number resulted in a diagnostic with improper text. Now, the diagnostic for invalid arguments is used. Additionally the output in the diagnostic file is extended, for a better diagnosting.

Working with multidimensionally Array in a macro for the macro specialists

Working with a multidimensionally Array is made easier. In the past accessing an Array, in a multidimensionally Array, (e.g. anArray = aMultiDimArray(1)) answered a copy of the Array and not the original. So creating an Array in a multidimensionally Array had to be done in two steps. First build the inner Array, then put the Array into the containing Array. (e.g. aMultiDimArray(1) = anArray).
Please verify the macros, whitch are based on this old behaviour, and modify the accessors, if needed.

Importing a script containing a to large macro from a local database

Importing a script, containing a macro with to large source (> 16.000 characters), leaded to a system diagostic and OfficeTalk ended. To run into this diagnostic, a script from a local database must be imported, because using a local database did not limit the size of source for a macro. Now, you get a notification for this to large macro and this macro is not imported.

Extended semantic of the operator & for Array in a macro

Using the operator & with a left hand Array answers an Array with the content of the left hand Array and the right hand operand. For the right hand operand as Array, the result is the concatenation of the content of both Arrays. For the right hand operand is not an Array, the result is the left hand Array with the added right hand operand. For details please read OfficeTalk Script, chapter Operator &.

Writing the content of a fixedpoint item in a macro of a processdialog into processdata

Formating an item fixedpoint did not write with processdata.item(…, with: …, in: …) its content into the processdata, when for the argument with: the items content is used with dialog.value(…). The content had to be assiged first into a Double variable and this variable had to be used for the argument with:.

Extended diagnostic on problems with database access

When a problen is recognized while accessing the database other than running a script macro, you get an information about. For diagnosting this problem easier, extended informations are put into the diagnostic file OfficeTalkDiagnostic.log. This file is found in the temporary systemfolder or in the settings dialog with the button Trash. With these informations the Support is enabled to diagnostic the problem easier.

New systemvariable SystemData to manage processdata optimized

With the new systemvariable SystemData processdata can be managed process independent. For details please read OfficeTalk Script, chapter SystemData.

No dimension of variable with type StartAction, UserAction und EndAction possible

Using in a macro the Dim statement with the variable types StartAction, UserAction or EndAction resulted in the message Unknown classname…. But the onlinehelp for the Dim statement offered these classnames. Now StartAction, UserAction and EndAction can be used in Dim statements.

Makros die Meldung Unbekannter Klassenname…, obwohl die Onlinehilfe der Dim-Anweisung diese Klassen anbot.

Wrong using of an arguments in macro

Assigning in a macro an argument to a local variable leaded in releasing at the end of the macro the resources referenced by the argument. This may lead to different problems. e.g. The macro
doAnything (dialog as ScriptDialog)
Dim dlg As ScriptDialog
dlg = dialog
…
released at its end the resources referenced by the argument dialog, and the owner macro of the variable dialog was not able to access services of dialog anymore.

Script diagnostic Unknown item… for using a service with an item of a tabulator in a processdialog

Getting in a separate macro a tabulator of a processdialog with the statement dlg = page(…, register: …) into a variable and not setting the variable with Null at the end of the macro, leads to the script diagnostic Unknown item…, when a service for an item of this tabulator is used. OfficeTalk is ended with a system diagnostic when the processdialog is closed in this case.

New service isContaining (…) of the systemvariable ScriptDialog

Since Version 4.86 Build 06.13.2012 services in a processdialog for an unknown dialogitem leads to a script diagnostic. For avoiding such diagnostics and when you are not shure wether the processdialog is containing the item, you can test the containment with the new service isContaining(…) of the systemvariable ScriptDialog.

Menu View – Sort by – Step in the tasklist as Browser

Sorting the tasklist in browserformat with the menu View – Sort by – Step by steps leaded to a systemdiagnostic, sorry.

Menu Creating database user with using Microsoft-SQL-Servers

Because the logindialog of the menu Creating database user is opened only once, giving a wrong login, OfficeTalk had to be restarted to perform the menu with the right login. Now the logindialog of the menu Creating database user is opened after using a wrong login in any case.

Assigning an Integer variable with a Character variable in macro

The integrated convert facility of the macro did not support assigning an Integer variable with a Character variable. The statements
Dim str As String
Dim i As Integer
str = "abc"
i = str(0)
resulted in the scriptdiagostic Variable <xxx> can not be converted to <yyy>. In the past the assigning had to be done with i = str(0).asInteger.

Defining in the Workbench for an dialogitem of a processdialog the formattype Text without formatrule

Defining in the Workbench for an dialogitem of a processdialog in its properties the formattype Text without formatrule (service format(…, as: ”string”)) askes you for really omitting the formatrule. Omitting the formatrule for formattype Text may result in an unexpected behaviour of the dialogitem. Omitting the formatrule for all other formattypes leads in using the system rule for the choosen formattype. For details please read documentation OfficeTalk Business-Process-Management, chapter Propertydialog Inputfield.
Please correct with the Workbench the using of the formattype Text without formatrule for to not disturb the user with by this scriptdiagnostic.

Using the service value(…, put: …) in a macro for a Combobox or a Listfield of a processdialog

Using in a macro the service value(…, put: Array(…)) for a Combobox or a Listfield, resulted in the scriptdiagnostic not understood isEmpty…., when the dialogitem is formatted with the service format(…, as: ”string”) or in the Workbench the formattype Text is given without a formatrule for the dialogitem. For details please read documentation OfficeTalk Business-Process-Management, chapter Propertydialog Combobox.

Using environment setting at start time

To get more flexibility for special purpose you can set environment values on the commandline. These settings are used instead of the settings in the registry (on Windows platforms) and in the configuration file (on Linux plafforms). For details please read OfficeTalk Generals, chapter Commandline options.

Version 4.86 Build 06.26.2012

Contextmenu New and Change im listfield Scripts of the ScriptBrowser

Typing in the scriptname in the namedialog, opened with the contextmenu New and Change, resulted since Version 4.86 Build 06.13.2012 in a diagnostic with ending of OfficeTalk, sorry.

Contextmenu Execute for a selected source in the macro of the ScriptBrowser

Using the contextmenu Execute for a selected binary expression (e.g.: CurDir & “..\Vorlagen\Datei.txt“) in the source of the macro resulted in the message Severe error while compiling.

Contextmenu New – Fast Step… of the step in dialog Graph for process: <name of processtemplate>

To close the dialog The next step with the button Accept, the input in the fields Schedulingtime had to be leaved with the RETURN key. Now the button Accept is immediatly enabled after typing in a schedulingtime. This makes the using of the dialog faster.

Simulating a process with menu Simulation - Open… in dialog Graph for process: <name of processtemplate>

The dialog Simulation of the flow: <processname>, opened with the menu Simulation – Open…, contained in the listfield Stepresults results without next step too. The simulation could not be proceeded with selecting such a result. The buttons >>| <and >> did not react. To avoid confusions, results without a next step are not listed in the listfield Stepresults anymore.

Version 4.86 Build 06.20.2012

Diagnostic on opening the tasklist

Opening the tasklist resulted in a diagnostic with ending of OfficeTalk, when a processtemplate in the right top listfield for processtemplates has the same identity as a process in the personal or in the takeover tasklist.

Contextmenu Reorder succeeding steps… of the step in dialog Graph for process: <name of processtemplate>

Choosing the contextmenu for a step with a stepresult without next step resulted in a diagnostic with ending of OfficeTalk. A stepresult of a step has no next step when a step is removed and the question Shall the associated result be removed too is answered with No.
In this context the dialog Sequence of succeeding steps, opened with the contextmenu Reorder succeeding steps…, shows for each step its associated stepresult. The numbers in [] displays the sequence of the step within its direct successors. For details please read OfficeTalk Business-Process-Management, chapter Reorder succeeding steps.

Truncated menulabel of contextmenu Schedulingoptions - Worker of the step in dialog Graph for process: <name of processtemplate>

Menuitems with larger labels of the step’s contextmenu Schedulingoptions – Worker (the names of the available workers) in dialog Graph for process: <name of processtemplate> where truncated.

Extended menu Statistic - Executiontimes/-paths... in dialog Graph for process: <name of processtemplate>

For an easier calculation of the ROI of a process the dialog Pathes of the process: <processname, opened with the menu Statistic - Executiontimes/-paths... in dialog Graph for process: <name of processtemplate>, displays additionally the minimum and maximum workingtime and the used resources for each path. With these informations the calculation of the KPI (Key Performance Indicator) of the process becomes easier. For details please read OfficeTalk Business-Process-Management, chapter Executiontimes/-paths.

Invalid delegation of the current process by a service in macro

Delegating the current process (the systemvariable process) with its service goTo(…), or with the service go(…, to:…) of the systemvariable stepscheduler, moved the process to the destination, but ending the step retracted the delegation. To avoid confusion, you get in this case of delegation a diagnostic message, whitch points to the invalid delegation.

Version 4.86 Build 06.13.2012

Deleting a single processdata item

Deleting an existing processdata item with the service item(…, with: Null, in: …) in a macro did not really delete the item. The previous value remained stored.

In the past a string, stored in a macro with the service item(…, with: …, in: …) of the systemvariable processdata in processdata, was limited to 2000 characters. This limit is extended to 4000 characters.
To support this extension by the database, you must change manually with the database administration the maximum lenght of the column valuestring in the tables historyprocessdataitem and processdataitem to 4000.

Semantical and syntactical errors while executing a macro

Execution of a macro differs between syntactical and semantical errors. Examples of a semantical error:

· A process can not be started with Start

· A service with an unknown dialogitemname is used

Examples of a syntactical error:

· Call executes an unknown macro

· A service with wrong arguments is used

In the diagnostic message for a semantical error the button Abort for aborting the execution of the macro is missing in opposite to the diagnostic message for a syntatical error. e.g. A Start should be enclosed in a Try-Catch-block. For details please read OfficeTalk Business-Process-Management, chapter E xecute scriptmacro.

Notifying semantical errors in macro of a processdialog

Using in a macro of a processdialog in the past a service with an unknown itemname was ignored. Because this may result in an unwanted behaviour of the processdialog (e.g. the service value(list, select: item) does not select the item in the list), you get now a diagnostic message in this case, whitch informs you about the use of an unknown itemname. The answer Yes opens the debuggerdialog and the answer No proceeds the execution.
When editing a macro of a processdialog manually, and not building it with the Workbench, more dialogitems with the same name could be added with the add-services. But when adding items with the same name, the first item is added in the processdialog only. In the past, the second item was ignored without any consequences. Now you get a diagnostic message in this case, whitch informs you about the duplicate named item.
When you are not shure, wether the macros for processdialogs is affected by such cases, check these macros before going live for not to irritate the worker when executing the processes.

Better usability for keys Ctrl+F, Ctrl+R und Ctrl+V for input fields

For the keys Ctrl+F, Ctrl+R and Ctrl+V in input fields the dialogs of the corresponding contextmenus are used. Up to now simplier dialogs with minor usability where used.

Key combinations in dialog Logged in workers

Some key combinations (e.g. Ctrl+Left) in dialog Logged in workers, opened with the menu Extras – Logged in workers, resulted in a diagnostic message with ending of OfficeTalk.
Additionally the selection of the workers in the listfield is undone not anymore with the key CTRL+R, but with the key CTRL+U.

Missing result in tabulator Unknown Returns of Workflowanalysis

Using in the execution’s flow of a step with the statement Return “<a name>” in one ore more macros, used by the actions, two or more unknown stepresults, the results in tabulator Unknown Returns of the Workflowanalysis did contain the first unknown stepresult only, and not all unknown stepresults.

No validation of the Return-Statement of a startmacro in the Workflowanalysis of a processtemplate

When the startmacro of an action in a step ended not with Return “<a string>“, but the resultvalue was provided by another macro with a Call-Statement (e.g.: Return Call <scriptname>.<macroname>), it was not validated and therefore, in case of unknown in the stepresults of the inspected step, it was not noted in the tabulator Unknown Results.

Version 4.86 Build 05.31.2012

Diagnostics can be send to additional mailaddress

With the environment DiagnosticCC a systempartners can be automaticly informed about any diagnostic, sent to the support of OfficeTalk. For details please read OfficeTalk Generals, chapter Diagnostic.

New service cc for systemvariable Mail

With the service cc(…) of the systemvariable Mail you can set the CC address for a mail. For details please read OfficeTalk Script, chapter Mail.

Indicating empty macros

In all listfields for macros (e.g. ScriptBrowser, Export- and Import-Dialog, etc.), the macroname is displayed in red, to indicate, that the macro contains no statements. This is helpfull especially for importing and exporting a process to detect possible problems. For details please read OfficeTalk Business-Process-Management, chapter Scriptmacrolist.

Step with unknown stepresult of a next step ended the process

Scheduling a step with an unknown stepresult (the Return statement of a startmacro), but the step has one ore more succeeding steps, and the stepresult named not one of theses steps, ended the process. Now you get a notification and you must select in the step’s execution dialog the correct result.

Choosing the language in the logindialog

Choosing in the logindialog the language EN English (USA), displayed in a succeeding logindialog the selected language EN English (GB).

Menu Workflowanalysis in dialog Graph for process: <name of processtemplate> for spezial templates

Using in a processtemplate a macro, whitch builds a macro, the tabulators of the dialog Analying graph pror process: <name of processtemplate> shows wrong mismatches, when the building macro writes systemstatements (e.g. Call, processdata…, Return, etc.) into the new macro. The processtemplate MacroBuilder-FilloutPrintSave is an example.

Contextmenu Uses… in SkriptBrowser for macro creating macro

With the services of macro development a macro can create another macro. The processtemplate MacroBuilder-FilloutPrintSave is an example for this. When such a macro writes Call-statements into the new macro, the context menu Uses… shows bad used macros and jumping to such a used does not open the used macro.

Menu View - Workersymbols - Portrait for all kind of organigramdialogs

The menu View - Workersymbols – Portrait is available now in all kind of organigramdialog and in the Functions-/Organigrambrowser. Because of this, for changing this setting you must not switch to the startportal Dialog anymore.

Used icon of process in debuggerdialog

In the listfield of the variables in the debuggerdialog (see chapter Debuggerdialog – Variables: in OfficeTalk Business-Process-Management) an active process is leaded by the icon of its execution state (similar to a process in the tasklist).

Used icon for a worker

Choosing in any kind of organigramdialog or in the Function-/Organigrambrowser the menu View - Workersymbols – Portrait (see chapter Workersymbols in OfficeTalk Business-Process-Management), and the worker has given a portrait (see chapter Portrait in OfficeTalk Business-Process-Management), leads the worker in all list- and comboboxfields not with its default icon, but with its portrait. All dialogs with a listfield of workers and all dialogs with a comboboxes of workers (Organigram, Visibility, Authorizes, Permissions, Substitutes, Adoptvisibility, etc.) are affected by this.

Wrong message in tabulator Visibility and Authorize

Using the option Up to organisation unit in tabulator Visibility or Authorize resulted in the wrong message The visibility is lower then the authorize….

Extension of the service processByIdentity of the systemvariable process

For an extended diagnostic of the service processByIdentity(…) of the systemvariable process detailed information is put into the logfile. Additionally the returned process is updated with its data in the database, if necessary. Because of this, the explicitly use of the service refresh is not necessary anymore. For details please read documentation OfficeTalk Script, chapter processByIdentity.

Version 4.86 Build 05.18.2012

Multiselection in tabulator Processtemplates and Scripts

Performing actions with multiple selected items in the tabulator Processtemplates and in the script listfield of the tabulator Scripts did work only, when the contextmenu is opened with the first selected item. Opening the contextmenu for any other selected item reselected all other items and executed the contextmenu for this item only.

Better controlling of removing a Script/Macro in ScriptBrowser

The removing of a Script/Macro with the contextmenu Remove… in its listfield in the ScriptBrowser is controlled now more detailed. Previous under special circumstances removing of a Script/Macro was denied and under some circumstances the Script/Macro was removed, but it should not been removed. For details please read OfficeTalk Business-Process-Management, section Remove... in chapter Scriptlist and chapter Scriptmacrolist.

Contextmenu Copy/Paste in all listfields

The contextmenu Copy did not copy a changed item (e.g. Script) into the clipboard, when it has been copied allready. As the result the contextmenu Paste inserted not the last copied version, but the previous copied version.

Adjusting Visibility, Authorize and Adoptvisibility when moving a worker

When a worker is moved within the structure of the organigram the settings of the Visibility, Authorize and Adoptvisibility are adjusted according the new position of the worker in the organigram. So the manual adjusting of these settings is not necessary anymore.

Option No Option in tabulator Adoptvisibility

Selecting the option No Option in tabulator Adoptvisibility was not accepted. Additionally the label of the option is changed for better semantic from No Option to No organisation units.

Moving scripts to a worker

For the maintenance of scripts the contextmenu Move to… of the scriptlist in the scriptbrowser is added. With this menu item you can move one ore more scripts from one worker to another worker. For maintenance of processtemplates a reorganisation of scripts is requires sometimes. When doing this the new menu item may be helpful, because is summarizes many single steps. For details please read OfficeTalk Business-Process-Management, chapter Scriptlist.

New services isActive and isPassive of the systemvariable worker

With the new services isActive and isPassive taking a decision in a macro about the type of a worker is more easier. For details please read OfficeTalk Script, chapter Systemvariable worker.

Closing erroneous processdialogs

A processdialog, whitch was configured without enabled Cancel- and OK-Button, could not be closed while working the process. Therefore OfficeTalk had to be stopped hard. Now you can end such a configured processdialog with an emergency exit. Because this is really an emergency case, you must accept two messages, to exit the dialog. For details please read OfficeTalk Business-Process-Management, chapter Enable emergency exit a nd OfficeTalk Script, chapter enableEmergencyExitl (…).
Using macro with processdialog containing no Cancel-Button, because canceling is not allowed, you must configure this macro in the workbench by deactivating the option Enable emergency exit.

Selecting a changed or ended process in the personal tasklist

Using the tasklist as browser OfficeTalk ended since version 4.86 with a diagnostic when a process, whitch is ended or changed in the meantime by another worker, is selected in the personal tasklist. Now you get the notice, that the process is ended and the tasklist’s content is updated.

Columns with icons in a table of a processdialog

With the new datatype Object in the column description of the service addTable(…) tables colums with preceeding icons are available now. This is similar to the tasklist as table. The used icon depends on the content of the column. For an item of OfficeTalk, the icon from OfficeTalk is used. For all other content a default icon is used. With this a visual oriented table in a processdialog is available. For details please read OfficeTalk Business-Process-Management, chapter Propertydialog table and OfficeTalk Script, chapter addTable(…).

New service resultNames of the systemvariable Step

With the new service resultNames of the systemvariable Step you get names of the stepresults of the Step. The service is an alias for the service succeedingResultNames. For details please read documentation OfficeTalk Script, chapter resultNames.

Simplier searching and replacing in textfields of processdialogs

For searching and replacing in textfields of processdialogs with the contextmenues Search, Repace and Paste the search- and repacedialogs of OfficeTalk are used. With this extension searching and replacing offers more advantages. For details of using these dialogs see chapter Contextmenu for textfields in OfficeTalk Setting general.

Setting DatabaseDirectory for use of local databases

The setting DatabaseDirectory as directory for local databases was ignored on start of OfficeTalk, when the startdirectory of OfficeTalk contained any local database.

Version 4.86 Build 04.20.2012

New services preceedingResultNames and succeedingResultNames of the systemvariable Step

With the new services preceedingResultNames and succeedingResultNames of the systemvariable Step you can fullfill in a macro special tasks for timecontrol. For details please read documentation OfficeTalk Script, chapter preceedingResultNames and succeedingResultNames.

Importing an exportfile containing multiple processtemplates

Since update 4.85 Build 03.13.2012 OfficeTalk ended with an error diagnostic, using the contextmenu Import… in tabulator Processtemplates with an exportfile containing multiple processtemplates. An exportfile contains multiple processtemplates, choosing the contextmenu Export... in tabulator Processtemplates with multiple selected processdemplates.

Changing a step of a processtemplate when using the startportal Function-/Organigrambrowser

Changing a step, opened by a doubleclick in the steplist of the tabulator Processtemplates, when using the startportal Functions-/Organigrambrowser, did not reflect consistently by the items Save and Save and close in the menu Step and by the toolbarbutton Save (the disk picture). The menuitems where enabled, where the toolbar button did not reflect the need to save. This was no functional limitation, but a wrong visualisation of the current state.

Changing resource when using the startportal Function-/Organigrambrowser

Changing only the name of a resource in the tabulator Resources, when using the startportal Function-/Organigrambrowser, was not reflected by the toolbar button Save (the disk picture). This was no functional limitation, but a wrong visualisation of the current state.

Open a macro with webservice activities with the Workbench

Opening a macro, containing werbservice activities, with the Workbench, ignored possible settings for Processdata within the group Results of the webservice in the tabulator Webservices.

Sending diagnostic mail to the support

Sending a diagnostic to the support without being logged in, ended OfficeTalk without sending the diagnostic.

Using horizontal und vertical grid for constructing a processdialog

The horizontal und vertical grid in the setting dialog, opened with the contextmenu Grid…, can now be used separate while creating a processdialog. With this the position assistant can layout the dialog items by horizontal or by vertical grid only.

Supported WSDL-Versions of the OfficeTalk-Webserver

OfficeTalk as Webserver supports additionally the WSDL-Version 2.0 now. In the tabulator Webserver of the settings dialog you define the WSDL-Version to be used. The version 1.1 is presetted. The setting depends on the used webclients. Ask the supplier of the used webclients what version is to be set. For details please read doc umentation OfficeTalk Business-Process-Management, chapter Settings, section Tabulator Webserver.

Version 4.86

New service value(…, selectionIndex: …) of the systemvariable ScriptDialog

With the new service value(…, selectionIndex: …) of the systemvariable ScriptDialog you can select one or more lines in a dialogitem of type list. For details please read documentation OfficeTalk Script, chapter value(…, selectionIndex: …).

Switching in combobox of a processdialog between with and without icons

Switching the display of the content between with and without preceeding icons with the services withIcon(…) and withoutIcon(…) works now for a combobox too. The presetted type of display was used only. For details please read documentation OfficeTalk Script, chapter withIcons(…) and withoutIcons(…).

Columns labelled with pictograms in all tasklists

For visual oriented user the columns Process, next Step und Worker in all tasklists are labelled with their related pictogram. Additionally the column Worker may be labelled in all tasklists with the given portrait of the worker, if any is present in its tabulator Address. With this additionally labelling a visual oriented user may more easy find a single process within a large tasklist.

Diagnostic mails sent to the support

For the mail, whitch is sent to the support of OfficeTalk (OfficeTalk@joops.com), when an error is encountered, the mailaddress registered in tabulator HTTP of the settings is used as senderaddress. Because replies may not reach the real sender of the diagnostic, the mailaddress of the current worker, if any is given, is used now.

Extension of dialog of the logged in workers

The dialog of the logged in workers, opened with the menu Extra – Who is logged in… in the startportal, shows now the date and time of the login of the worker. With this information you can easier decide, wether the login is real or is the result of a switched off workstation. For details please read doc umentation OfficeTalk Business-Process-Management, chapter Who is logged in.
In this context the database table locking is extended with the columns date and time. Starting the version 4.86 the first time does this extending automaticly. For this first time starting you must login as company !

Sorting a tasklist of an group by worker of the processes

Sorting a group tasklist as table by worker did not remember the sortcriteria when the tasklist is reopened.

Opening and sorting the tasklist’s content is accelerated

Opening the tasklist in browser- and table-format is accelerated by factor 4. Sorting processes by delay, starttime, step and worker in the tasklist as browser by the sortmenu and in the tasklist as table by clicking the column header is accelerated by factor 4.

Onlinehelp for services of a COM-Component in macro on Windows-Platforms

Activating the onlinehelp for the available services of a COM-Component (space after <variablenname>.,in the sourcefield of a macro), whitch is referenced with the statement Interface, OfficeTalk ended with an error message on some COM-Components, sorry.

Bad Call-Statement in macro is not notified at compiletime

A macro containing a correct Call-Statement with a succeeding Call-Statement for the same named macro, but with a bad argumentlist, is compiled with the contextmenu Compile in the source textfield of the scriptbrowser without notifying the second and wrong used Call-Statement..

Version 4.85 Build 03.13.2012

Exporting a processtemplate with faulty macros

Exporting of a processtemplate with the contextmenu Export in tabulator Processtemplates did not export all scripts in case of faulty macros are detected. A macro is faulty, if it contains a faulty statement as comment. Additionally the message for a missing macro/script is made more detailed. The previous message was general and therefore possible missunderstandable. The message shows in case of a missing macro the name of the macro and the macro where it is called with a Call statement. With this information the error can be corrected more easier.

Extension of exporting a processtemplate

When the export of a processtemplate with the contextmenu Export in tabulator Processtemplates is finished, you get the dialog about the content of the exported processtemplate. This dialog shows you all the components, whitch are exported along the processtemplate. For details please read doc umentation OfficeTalk Business-Process-Management, chapter Tabulator Processtemplates, section Export.

Version 4.85 Build 03.09.2012

Optimized export of processtemplate

The export of a processtemplate with the contextmenu Export in tabulator Processtemplates has exported under rare conditions scripts not uses by the processflow. e.g. The macro Start in script Selling with the statement Call Opportunity.Create exported the same named script contained in the worker hirachically next to the real owner.

Vertical separator in processdialog

The service addDivider(…, left: …, top: …, height: …) of the systemvariable ScriptDialog did not paint the separator correctly in a processdialog. Depending on the position values the separator was not visible in the processdialog.

Version 4.85 Build 03.05.2012

Out-Parameter arguments if services of a class, contained in statement Interface in a macro

Services of a class with Out-Parameters, build by the statement Interface, where not configured properly. This resulted in not providing arguments in the service, whitch where declared by the COM-Component as Out-Parameter, with their result.

Version 4.85 Build 03.02.2012

Delete-Key in OrganigramBrowser-Dialog using startportal Dialog

In some right tabulators of the OrganigramBrowser-Dialog the Delete-Key was interpreted as removing the selected worker in the left organigram listfield, when using the startportal Dialog. The messagebox Do you really want to remove xxx or the messagebox Worker can not be removed was displayed.

Onlinehelp for services in dialog for executing extra statements of the debuggerdialog

The onlinehelp in the executiondialog of the debugger for choosing a service, opened by typing in a variable, a dot and a space, is used as in all other situations. The dialog does not contain anymore the button Copy to copy the selected service into the pastebuffer, with succeeding pasting it in the executiondialog. Choose the service and button OK adopts the service into the execution dialog.

Concurrency of workers using database Oracle-DB and IBM-DB2

When logging in as a worker allready logged in and choosing a worker in OrganigrammBrowser, whitch is logged, notified an aborted database „Lock-Resource“ in front of the notification about „Worker is logged in allready“. The first notification about the „Lock-Resource“ is skipped, because it is not helpful in this context and may shock the user.

Using menu File-Settings in logged out state

Using in the startportal the menu File – Settings in logged out state resulted in an error message with ending of OfficeTalk, sorry.

Version 4.85 Build 02.29.2012

Opening calenderbutton in processdialog resulted in an error message

Opening a calendar button in a processdialog resulted in an error message when the associated datefield contained a date with a month name different to the english syntax written.

Switching between the types of organigramdialogs when using the startportal Dialog

Automatic switching from one dialogtype to another dialogtype of an organigram (Browser, Hirarchy, Diagram, etc.), by choosing the menu (closing the current and opening the selected) did not work in each direction. To open a specific type of organigramdialog sometimes the opened had to be closed first. This is not a real error, but may be a little strange, when an other dialog is opened as the chosen menu says.

Searching worker by description

Searching worker with menu Worker – Search in the Organigrambrowser by description did not open the found description page since version 4.84, but the found worker only.

Opening the Organigramdiagram using startportal Dialog

Opening the Organigramdiagram with the menu Work – Organigram in the startportal Dialog resulted in an error message with ending of OfficeTalk, sorry.

Exporting a processtemplate without named macros

Exporting in a source system a processtemplate without some used script/macros can now be done with the new environment SkipExport. For some special requirements it may be necessary, when exporting a processtemplate, not to export some scripts/macros for not changing these scripts/macros by the import in the destination system. For details please read doc umentation OfficeTalk Business-Process-Management, chapter Settings without userinterface, block SkipExport\<Macroname>.

Extended diagnostic for errors on sending a processtemlate

The menu File – Send in die dialog Graph for process: <processname> writes into the protocolfile, if protocolling is switched on, the detailed errorcode from the mailhost. With this errorcode the reason of the error can be analysed more easy.

Deleting logfiles

With the using level Expert the logfiles could not be deleted in the notification dialog at programstart and in the logfile assistent. The answer No (do not delete) was assumed for the not opened messagebox.

Version 4.85 Build 02.25.2012

Using processes of foreign workers

In some rare circumstances it may be required to change in a script macro a process contained in the tasklist of another worker. This is indeed not the recommended way, but may be required for special applications. To do this, you must lock the foreign process first with the new service lock of the systemvariable process, to be shure, it is not in work currently. For details please read documentation OfficeTalk Script, chapter Systemvariable process.

Extension of history for delegation

To make the history more clear in case of a process delegation, the starter field of the history dialog for a delegation entry is extended with (by: <name>). This is the name of the worker, who has delegated the process. In this context the systemvariable StepHistory is extended with the services initiatingWorker and initiatingWorkerName. For details please read documentation OfficeTalk Script, chapter Systemvariable StepHistory.

Notification on delegation of a process

The receiver of the delegation notification (email on setting eMail on Delegation in tabulator Tasks of the settingdialog) can see in the mailtext the resaon of the delegation now too. This is the comment given by the delegator. The comment of delegation is contained in the email independent of the way of delegation (contextmenu Change/Delegate and goto Services in macro).With this, the receiver of the process is informed about the reason of the delegation too. In this context the systemvariable stepscheduler is extended by the delegation services with comment. For details please read documentation OfficeTalk Script, chapter Systemvariable stepscheduler.

Relogin after logout in evaluation version

In the evaluation version the relogin was blocked under some circumstances. If something was changed and a logout with the menu File - Logout in the startportal was performed, a succeeded relogin was blocked. The messagebox Save changes… was opened, but whatever you answered, the logindialog was not opened. In this situation OfficeTalk had to be ended and restarted to login again.

Error using menu Extras – Importmapping and Extras – Autorize wizard in startportaldialog

Using the menu Extras – Importmapping or menu Extras – Autorize wizard in the startportaldialog resulted since Version 4.81 in an error message with ending of OfficeTalk, sorry.

Informing logged in workers

With the new menu Extras – Who is logged in… in the startportaldialog you can inform currently logged in workers with an eMail. This enables you to notify about some central circumstances without going to the office of each logged in worker. For details please read doc umentation OfficeTalk Business-Process-Management, chapter Who is logged in.

Displaying variables in the Scriptdebugger dialog on Windows platforms

On Windows platforms the right top listfield of the Scriptdebugger dialog displayed for a communication library’s component, an DOTNet-Component and a COM-Component the default icon for a variable instead of its matching component icon.

Extended logging for starting a process with statement Start within a macro

Starting a process with the statement Start within a macro is written into the logfile for later diagnostic.

Version 4.85 Build 02.10.2012

Extended diagnostic for using datatypes of a communication library on all Windows-Platforms

When a datatype within a communication library can not be used with the New statement, because of problems querying its COM interface, you will get an extended notifyer and an entry in the logfile with the errorcode of the query. You can give this errorcode to the supplier of the COM component for diagnosting purpose.

New service removeAll of the systemvariable processdata in scriptmacro

With the new service removeAll of the systemvariable processdata all groups in the processdata are removed. This is a shortcut for the service remove(…) for each groupname. For details please read documentation OfficeTalk Script, chapter Systemvariable processdata.

Managing logfiles

Because logfiles, if switched on, can become very large and make your disk full, you can manage the logfiles with the basket button beside the field Logging in the tabulator General of the settingdialog. The button opens the logfile wizard. With this wizard you can view and delete the logfiles. Additionally the size of the logfiles is tested at programstart. For logfiles, whitch exceeds the watermark of 5MB, you get a notification dialog, where you can delete these logfiles. For details please read documentation OfficeTalk Basics, chapter Managing logfiles and documentation OfficeTalk Business-Process-Management, chapter Settings general.

Selecting a stepresult in dialog Graph for process: <processname>

For more informations, selecting a stepresult (the name) draws its connectionline from the outgoing to the ingoing step orange. This gives you more informations about the conditions of a stepresult. Especially in a processgraph with many connections this is helpful.

New setting SystemLogging

With the new setting SystemLogging systeminformations about scheduling of processes are written into to logfile. With these informations detailed diagnostic of the scheduling of processes is possible. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings without userinterface.

Contextmenu Paste in scriptlistfield of the Skriptbrowserdialog

Pasting a script with same name of an existing script in the worker brings up a dialog, where you can rename the script before it is inserted.

Contextmenu Uses… in Scriptbrowserdialog does not open the selected macro

The macro, selected with the contextmenu Uses... in the listfield of the macros within the Scriptbrowserdialog, was not opened in case of settings General with startportal Function-/Organigambrowser and organigram subordinated Workers, then Content and an expanded worker between this worker and its category Scripts. Instead of the category Scripts of the expanded worker between was selected.

New services of the systemvariable FileSystemObject in scriptmacro

With the new services dateCreated(…), dateLastAccessed(…), dateLastModified(…) and size(…) of the systemvariable FileSystemObject the attributes of a file or directory can be retrieved. For details please read documentation OfficeTalk Script, chapter Systemvariable FileSystemObject.

Choosing date with the calendardialog in a processdialog

Choosing the month February with day 30. and 31. of a selected month resulted in the error message Invalid date... and aborted the execution of the current macro.

Statement New in a script macro for a component of a communication library on Windows-Platforms

In case of no connection (Interface) to a component of a communication library with the statement New, executing the first service of the component failed with the message The service <servicename> is unknown in class <classname>…. In most cases the connection (Interface) to a communication library fails because of a missing registration of the component. The new message for this case The COM interface for <classname> is not accessible. e.g. The application is not installed makes the diagnose of this case more easy.

Extension for importing a processtemplate

Importing a processtemplate (.bos-File) with the contextmenu Import… in tabulator Procestemplates of the workerdialog opens a dialog with the contents of the processtemplate to be imported. This dialog shows you all the components whitch will be imported along the processtemplate. Additionally the dialog shows you the workers, required for the importing. With this informations you can decide wether the import should be proceeded. For details please read documentation OfficeTalk Business-Process-Management, chapter Tabulator Processtemplates, Import.

Importing processtemplate from version 4.81/4.82

Importing a processtemplate, created with version 4.81 or 4.82, ended OfficeTalk with an error message, sorry.

Statedialog of a process in the tasklists

For diagnostic purpose the dialog State for: <processname>, opened with the contextmenu Current State... in all variants of the tasklist, displays now the identity of the process. This is the primary key of the process in the database.

Starting OfficeTalk without licence file

Starting OfficeTalk without a licence file ended OfficeTalk with an error message, when protocolling is activated. Practically this will happen never, because for activating the protocolling OfficeTalk must be started. But you can simulate this situation. And OfficeTalk should be protected against such manipulations !

Resizer in the tasklist as browser

The vertical and horizontal position of the resizer (horizontal line for resizing) between the dialog of the step and the processdata was not adjusted on sizing the tasklist’s dialog. The resizer was drawn partially into the listfield of the processes. This had no functionally restrictions, but was visually bad.

Opening tasklist in Function-/Organigrambrowser with double clicking

The symbols for categories in the left listfield of the Function-/Organigrambrowser are not prepeared for double clicking. To open a category a single click is enough. Opening the tasklist with double clicking its symbol leads to an error message with ending of OfficeTalk, sorry.

Firststart with existing OfficeTalk-Database

Starting OfficeTalk after removing manually the environment item Version goes into the first installation process, but ended OfficeTalk with the message …The database can not be used. Removing the environment item Version manually is no good idea !

Label of stepresult for a self connection in dialog Graph for process: <processname>

The label of a self connection (stepresult) was shifted little down and therefore not totally visible for a step with 2 or more other connections (stepresults) to steps.

Delegating a process in the tasklist with the contextmenu Delegate/Change

The mail about the delegated process, the target worker will receive, contains now the reason of the delegation too. The initiator of the delegation is asked for the reason by using the contextmenu Delegate/Change in the tasklist.

Sorting processes by name in tasklist

Sorting the processes by name in the tasklist with the menu View- Sort by – Processname was optimized. Some combination of names could lead to a wrong sortorder.

Firststart with using a Oracle-Database

Starting OfficeTalk, using a Oracle-Database, the first time, hangs the system after accepting the systemlogin, because the environment „OFFICETA“ was used instead of the users typed in environment.

Version 4.85

Concurrent scheduling of process is slowed down under special conditions

Opening after the service processdata.item(…, with: …, in: …) in a macro an additional userinteraction (a processdialog or a messagebox) could slow down a concurrent process scheduling by another worker.

More historyinformation of a process can be archived

Up to now in a macro the maximal size of a comment, achived with the service comment(…) und comment(…, for: …) of the systemvariable step, was limited to 1024 characters. For special requirements this limit is extended to 4000 characters.
For existing OfficeTalk-Installations the database must be changed manually. Change with the administration application of the database the size of column commentstring in the tables actionhistory, processhistory and stephistory from 1024 to 4000. Ask your database administrator to do this.

Backward connections (Stepresults) in dialog Graph for process: <processname>

In dialog Graph for process: <processname> more backward connections (Stepresult) between Steps within the same column are drawn when possible as separate lines. With this change graphs of complex processes are better readable.

Obscured Fold/Unfold symbol of step in dialog Graph for process: <processname>

Under special circumstances the Fold-/Unfold symbol of a Step may be obscured by the label of a connection line (Stepresult). Clicking the symbol had not the described result. The Stepresult’s label was selected instead. Now clicking the Fold-/Unfold symbol in this case has the described result.

Subject of the notification-mail on delegation of a process

For more information about a running system, the mail, whitch is send with Mail on delegation in tabulator Tasks of the settings to the destination, is preceeded by the name of the database. This is helpful if a productive system and a testsystem is used in parallel.

New option Use permissions of worker in tabulator Taskareas

With the new option Use permissions of worker in the tabulator Taskareas the permissions of the taskarea worker are used for the tasklist of this taskarea in opposite to the using of the permissions of the logged in worker. With the option the tasks of the taskarea with the permissions of the taskarea’s worker are scheduled. The overall sum of the processes noted in the tasklist’s headerline differs from the processes in the tasklist for a used taskarea without option Use permissions of worker and missing Read-Permission for processes in the tasklist. For details please read documentation OfficeTalk Business-Process-Management, chapter Taskareas.
In this context the database table taskarea is extended with the column permissons. Starting the version 4.85 the first time does this extending automaticly. For this first time starting you must login as company !

Setup contained outdated definition of database

The database definition, contained in the setup, was outdated and OfficeTalk ended at the very first start and after the building of the database with an error message, because of some columns of tables stepresult und stepresulttemplate where not build.

Some small changes of tooltips in the tasklist

The tasklist as table did not support the tooltips for all buttons in the toolbar. The rightmost button in the toolbar for opening the workflow documentation displayed in all other types of tasklist the wrong tooltip text.

Version 4.84 Build 12.22.2011

Toolbarbutton Start in the tasklist

Starting a new process with the button Start in the toolbar of the tasklist ended OfficeTalk with an errormessage, sorry.

Executing Smalltalk expressions with service evaluate in a macro

Within the Smalltalk expression of the service evaluate of a String-variable, variables of type Public can be used too. While introduction of the Public-variable with version 4.82 this was forgotten, sorry.

Wizard for renaming a macro

Reordering the arguments of a macro with the contextmenu Rename… in the macrolist of the ScriptBrowser did not work for some class/datatype variants. Renaming war denied with the message, that a macro with same signature exist allready

Version 4.84 Build 12.19.2011

Configure the columns of the tasklist as table

The dialog for configuration of the columns in the tasklist as table, opened with the contextmenu Columns…, contains now on the right border two buttons. With these buttons you can modify the sequence of the columns too. For details please read documentation OfficeTalk Workflow, chapter Configure the columns.

Wizard for renaming a macro

For complex renaming tasks of a macro with the contextmenu Rename... a wizard is used. In this wizard you can change the name of the macro and the order sequence of its arguments. The wizard adapts all users of the macro. These are macros whitch use the renamed macro with a Call-statement. Manually adapting of the users is not needed anymore.

Wizard for renaming a script

The wizard for renaming a script adapts now all users of the renamed script. These are macros whitch use the renamed macro with a Call-statement and all actions in processtemplates pointing to the script as startscript. Manually adapting of the users is not needed anymore.

Sorting the tasklist as browser with the menu Sort by

Sorting the tasklist as browser with the menu Sort by resulted in an error message, when no sorting was done in the tasklist as table or as symbol before.

Version 4.84 Build 12.13.2011

Assignement to a global variable in macro

An assignement to a global variable (worker, process, step, action, stepscheduler) is invalid on general. In the past this was possible, but without sense. An assignement to a global variable is flagged now as error. Check the macros for not using such assignements, because the execution of such a macro is aborted now with an error message.

New setting Indicate subprocesses in tabulator Tasklist

The setting Indicate subprocesses can be set in the tabulator Tasks for processes in the tasklist different from the tabulator Processtemplates now. This may save time opening the Previous execution of a process of the tasklist.

New service items(…, in: …) of the systemvariables processdata and scheduledata

The new service items(…, in: …) of the systemvariables processdata and scheduledata answers the values of all given items for a group. For a group with wildcards the items of all matching groups are answered. For details please read documentation OfficeTalk Script, chapter Systemvariable processdata, service items(…, in: …).

Closing the tasklist with possible automatic processes

The failure assumtion of scheduling automatic processes ended OfficeTalk after closing the tasklist and the timespan for automatic scheduling with an error message. This happened very sporadic and rare.

Menu Extras-Workflowanaysis in dialog Graph for process: <processname>

Anayzing a processtemplate without any error may result in an error message, sorry.

Contextmenu Insert document in descriptionfields

Inserting with the contextmenu Insert document a link into a descriptionfield (e.g. Tabulator Description in a worker’s dialog) surrounds the inserted linktext with spaces, if required. This makes the text as a whole more readable.

Menu Execute and Services in Debuggerdialog

Using the menues Execute and Services of the dialog Executing script macro ’<macroname>’ did not redraw the obscured areas of the menuearea. Moving the opened dialog around resulted in gray areas in the debuggerdialog too.

Defining the columns in the tasklist as table

For more usability you get the dialog for defining the columns of a tasklist not only with the contextmenu Columns… in the listfield, but with click of the right mousebutton on the headerline too.

Acceleration of the tasklist as table

The tasklist as table is accelerated especially using the columns Duedate and Schedulingtime. Using larger processes and these columns, could make the tasklist slow. All kind of tasklists profits by this enhancement.

New button Categories in the toolbar of the tasklist

With the new button Categories in the toolbar of all tasklistdialogs you can filter the tasks be categories fast without navigating throught the structure of the menu View. This accelerates the filtering of processes by categories.

Results of the task filter in the Adopt-Tasks of the tasklist as browser

The results of the taskfilter with the menu View – Filter processes in the group Adopt-Tasks was not indicated like in the group Personal tasks. Within the brackets the second number of the folded out tasks was missing. This may lead to confusion when all processes in the group where folded out, but the group not be unfolded.

Settings for sorting processes in the tasklist (menu View – Sort by)

The selected sorting of processes in the tasklist with menu View – Sort by is remembered now for the next opening of the tasklist.

Version 4.84

Calculating dynamicly the duedate of a process

With the new service minMaxDueDate(…, stopTimes: …) of the systemvariable process you can calculate the duedate of a process or of a processtemplate dynamicly. With the argument stopTimes: you can name stepresult, whitch should not be used for calculation. This is similar to temporarily setting of the option No calculation of times for the succeeding steps in a stepresult. For details please read documentation OfficeTalk Script, chapter Systemvariable process, service minMaxDueDate(…, stopTimes: …).

Modifying lifetimes, schedulingtimes and duedates of a process

With the option No calculation of times for the succeeding steps in the tabulator Stepresults of the stepdialog you can configure the lifetime and scheduletime of a process in the tasklist and the scheduletimes and –paths in the dialog Graph for process: <processname> is a way, that the succeeding steps are not contained in the calculation of the times. For some functional reasons it may be necessary to exclude the flow of some steps from the time calculation. For details please read documentation OfficeTalk Business-Process-Management, chapter Tabulator Stepresults and OfficeTalk Script, chapter Systemvariable process, service minMaxDueDate.
In this context the database tables stepresult and stepresulttemplate are extended by the column stoptime. Starting the version 4.84 the first time does this extending automaticly. For this first time starting you must login as company !

Build new Step, Action or Stepresult in dialog Graph for process: <processname>

Opening the dialog for the new component with menu New and closing the dialog Graph for process: <processname> first without closing the component’s dialog, the components dialog remains open. This may be a little confusing.

Setting the language in the logindialog

Since version 4.82 choosing a language, different from the installation, at login in the combobox Language of the logindialog was not possible.

Modified validation rules for permissions contained in the company

Up to version 4.83 the company had implicitly permissions vor all processes. Permissions contained in the company where used for the permissioninheritance of a worker (tabulator Autorize). Bisher besaß das Unternehmen implizit alle Vorgangsrechte, unabhängig von den eingetragenen Vorgangsrechten. Die Rechte im Unterhehmen fanden nur Ihre Anwendung für die Rechtevererbung von Bearbeitern (Register Autorisierung). Diese Regel wurde geändert ! Wenn im Unternehmen Vorgangsrechte eingetragen sind, finden diese auch für das Unternehmen selbst Anwendung ! Nur wenn das Unternehmen für einen Vorgang keine Rechte eingetragen hat, besitzt es implizit alle Rechte für den Vorgang. Dies hat in erster Linie Auswirkung, wenn Sie sich als Unternehmen anmelden und eine Vorgangsvorlage ändern wollen. Hat das Unternehmen z.B. für die zu bearbeitende Vorgangsvorlage zwar ein Rechte eingetragen, aber ohne die Option Bearbeiten, können Sie als Unternehmen die Vorgangsvorlage nicht ändern ! Passen Sie deshalb die Rechte im Unternehmen, falls erforderlich, an diese neue Regel an.

Visiting the executionflow of a subprocess (menu Previous execution…) in the tasklist

In the dialog, opened with the contextmenu Previous execution… of a process in the tasklist, you see the current state of the process. When the process has started a subprocess, you can open the executionflow of the subprocess with the +-sign of the responsible step. A menu offers all started subprocesses. Choosing a subprocess in this menu will open the executionflow of this subprocess. With this extension you get the overall overwiew of the process without going to the subprocess in the tasklist. This is very helpful, for subprocesses contained in the tasklist of another responsible worker.
In this context the database table process is extended by the column startedby. Starting the version 4.84 the first time does this extending automaticly. For this first time starting you must login as company !

Previous execution of a process (menü Previous execution …) in the tasklist

In the dialog, opened with the contextmenu Previous execution… of a process in the tasklist, some menus, whitch makes no sense here, could be used, These menus (Work, Simulation and Extra) are grayed now. These menus are available in dialog Graph for process: <processname> of a processtemplate only. Additionally using the startportal Functions-/Organigrambrowser the menues for modifying the process where available. These menus must be available in dialog Graph for process: <processname> of a processtemplate only.

Informations about delegated processes

With the new menu Work – Delegated processes… in the tasklist you get a dialog with all processes, delegated by you and currently worked by other workers. Within this dialog you can inspect further informations (History, State, Processflow, etc.) about the delegated processes.

Extended sort functionalities in the taslklists

With the menuitem Due date of the menu View – Sort by in all tasklists the processes can be sorted by their calculated due date.
The toolbar of the tasklist as browser and as symbol contains the new button Sort by. With this button all the possibilities of sorting processes can be accessed fast without navigating through the menuhirarchy

New service of the systemvariable stepscheduler for using a startdate in the past

Defining a past startdate for the next step with startAt(…, time: …) and because of this past date, the next step will be scheduled now, the startdate must be fixed with defineStartDate(False), if the next step is contained in the current schedulingsequence. Else the scheduling is ended with a notification.

Using statement Shell in macro

On Windows platforms using the statement Shell with programs, containing a blanc in the filename, you have to consider some extra rules. The documentation OfficeTalk Script, chapter Shell points to this rules.

Service evaluate of a String-Variable in a macro

The service evaluate of a variable of type String differs between syntaxerrors and errors of execution. The errormessage points to the type of error. With this, the correction of the smalltalk expression in the string is a little bit easier.

n Smalltalk-Syntax, oder ein Ausführungsfehler sein. Die Fehlermeldung wurde erweitert und lautet jetzt entsprechend. Damit ist die Korrektur der Anweisungen einfacher möglich.

Version 4.83 Build 11.15.2011

Opening parts, exported as HTML on Windows-Platforms, with the standardbrowser

Exporting parts of OfficeTalk (Processtemplate, Organigram, Executiongraph of macro, etc.) as HTML with the menu File – Save as HTML, and second answering Yes to the question, wether the result should be opened, displayed since version 4.1 on Windows-Platforms Page can not be displayed for Microsoft-Internet-Explorer as installed defaultbrowser.

Using labelgroups for dialogitems in the processdialog

The labelgroup of the current worker (field Labelgroup in tabulator Address of the workerdialog) was not used while executing the processdialog in the scheduled process. The labelgroup, set by the button Labelgroup in the tabulator Processdialog (service labelGroup of the systemvariable ScriptDialog) of the Workbench was used only. The Processdialog in the Workbench ignored the labelgroup of the current worker too.
Additionally changes of the global labelgroup (service labelGroup of the systemvariable ScriptDialog) with the button Labelgroup in the tabulator Processdialog are reflected in the Processdialog, opened within the Workbench.

Startportal Function-/Organigrambrowser and setting Tasklist on login

Using the startportal Function-/Organigrambrowser and the setting Tasklist on login an automaticly login was performed after logout with the menu File – Logout by clicking onto a category in the left listfield. But after logged in, the clicked category was cleared.

Opening a macro with the Workbench with invalid using of compositing

Using the services of compositing invalid in a macro (startComposite without endCompositeWidth/endCompositeLeft) ended OfficeTalk with an error message when choosing the tabulator Processdialog of the Workbenchdialog.

Extensions of the wizard for searching workers

The wizard for searching workers is extended with two options. First the option Invert filter answers the opposite of the search result (e.g.: all workers with no permission for process Acquire-Sales). And second the option With parts suppresses in the search result the affected parts of workers. This is regarded to Absents, Permissions, Substitutes, Resources, Processtemplates, Macros and Taskareas. With this option the result of searching within large organisations is more clearly regarded.

Searching for macros with a certain sourcetext in tabulator Scripts is performed now fuzzy or exact.

For details of both extensions please read documentation OfficeTalk Business-Process-Management, chapter Worker - Searching.

Debugging a macro with variable of a communication library

Debugging a macro with a variable of a communication library ended OfficeTalk with an error message, when in the variable list of the debuggerdialog the group (Local or Public) with the communication variable is unfolded.

Opening a makro not for a processdialog with Workbench

Opening a macro, whitch defines not a processdialog (Database, Mail, Webservice, etc.), was sometimes denied with the message The maco is not created with the Workbench….

Version 4.83

Creating two connections between two steps with the mouse in dialog Graph for process: <processname>

With pressed mousebutton two connection lines (blue line, stepresult) between two steps could be made by moving the end of a connection line from a step to another step. This should not be allowed in general, but was possible (you get what you want).

Wrong result of the Replace function in a macro under some conditions

The result of the Replace function missed the last character, when the last replaced string is followed by not replaced characters.

New service asPlatformString(…) of the systemvariable stepscheduler in a macro

As counterpart to the service asHTMLString(…) the systemvariable stepscheduler supports now the service asPlatformString(…). With this service a HTML formatted string can be converted into a platform formatted string.

Composing scrollbars für items in a processdialog

For a better design of a processdialog you can compose a scrollarea for items. With the bars of this scrollarea you can scroll the items within this area independently of possible existing scrollbars of the processdialog. With scrollareas you can design a processdialog with larger items in a better way. For details please read documentation OfficeTalk Script, chapter Composing scrollareas for items.

Connecting two steps with the mouse in dialog Graph for process: <processname>

With the pressed mousebutton you could connect two steps, visible in the currently diagrampart only. Connecting a step with a blue line (stepresult) to a step outside the visible diagrampart was not possible. This was possible with the step’s dialog only. Now the diagrampart is scrolled to the direction of the touched diagramborder while pressing the mousebutton.

Drawing a conntection between two steps in dialog Graph for process: <processname>

Connecting (blue line or stepresult) with the mouse two steps, allready connected in the same direction, has no sense, but was possible. Now connecting (blue line or stepresult) with the mouse two steps, allready connected in the same direction, is denied.

Moving an organisation unit into one of its own organisation unit within all kind of organigramdialog

Moving an organisation unit (Department, Office, Team), into one of its own organisation unit is not valid, but resulted in an endlessloop and after some time into an error message with ending of OfficeTalk with the error message No Space.

Sorting a dialogitem Table in a processdialog with columns of type String

Rows with columns of type String where not correct sorted by a string column, when this column contained empty strings (““) and Null. For the user this is both the same, but the sorter put rows with empty column (string ““) at the start and the rows with Null columns at the end of the table.

Extended results of the service properties(…) of the systemvariable ScriptDialog

The service properties(…) of the systemvariable ScriptDialog gets the disabled state of the item too. Because of this extension, the format of the result of the service in modified. For details please read documentation OfficeTalk Script, chapter properties(…).

Better organizing processdialog with many items

In general a processdialog should contain not more than 7 items. But under special conditions this rule may be violated. If your processdialog must contain many items and you do not want to make the dialog itself to big, you can give him with the new With horizontal/vertical scrollbars scrollbars. So you can minimize the size of the processdialog and the user can reach each item with the scrollbars. For details please read documentation OfficeTalk Business-Process-Management, chapter Workbench and OfficeTalk Script, chapter verticalScrollBar and horizontalScrollBar.

Menu Extra – Not used Macros with startportal Dialog

With the startportal Dialog the button Back in the dialog Not used macros, opened with the menu Extra – Not used macros, opened the workerdialog and closed the startportal. Therefore the menues of the startportal, the main funktions of OfficeTalk, could not be used anymore. To use OfficeTalk, the workerdialog had to be closed, and OfficeTalk must be started again.

Menu Macro – Missing… in dialog Callgraph beginning at macro: <macroname> did not show missing macros

The menu Macro – Missing… in dialog Callgraph beginning at macro: <macroname>, opened with the contextmenu Callgraph… in the listfield of macros of the Scriptbrowserdialog, was grayed on missing macros. The missing macros in a callgraph where correct recorded, but not displayed. Because of this, missing macros within a callgraph could not be analyzed.

Optimized usability in all diagrams

In the diagrams for an Organigram, a Processtemplate, a Process, and for a Callgraph of a Macro, the items of the diagram contains in the right top corner a triangle. The triangle is black when the succeeding path is visible (unfolded). The triangle is white when the succeeding path is invisible (folded). By default the triangle is black when the diagram is opened. The triangle is missing for an item without succeeding items. Clicking the triangle with the mouse folds and unfolds the succeeding path. With this triangle larger diagrams can easier be worked.

Wizard for worker searching is extended for searching scripts

The tabulator Scripts in the worker searching dialog is extended with the options Startmacro and Systemmacro to search for macros with these special options.

Version 4.82 Build 10.19.2011

Exporting processtemplates and histories in Windows platforms

Exporting the processtemplate or history into a destination directory without write permission and the exported file was allready existing in the destination, ended OfficeTalk with the error message ERROR_ACCESS_DENIED…, because the fileselection dialog for saving of the Windows platform does not deny a fileselection in a write protected directory, when the file exists.

Checking installed programversion with new menuitem Help - Versioncheck…

With the new menuitem Help - Versioncheck… you can check the actuality of the installed programversion. In the opened dialog you see the number of the installed, the actual available programversion, and hints for the update.

Version 4.82

Better usability in hirarchical listfields

In some hirachical listfields (e.g. analyse of processflow, processsimulation, etc.) the items contained in the leftmost item could be unfolded witch a doubleclick only, but this feature was not displayed. Now folding and unfolding is possible too by a preceeded fold-/unfoldsymbol.

Rejecting dynamicly the option Mandatory for items in a processdialog

With the new service optional(…) of the systemvariable ScriptDialo g you can dynamicly reject for items in a processdialog the option Mandatory. With this you can dynamicly control the filling out of a processdialog.

Extensions of the Scriptdebugger

The menuitem Interfaceservices… is renamed to Services.... It opens the dialog of services for all type of systemvariables, e.g. ScriptDialog, Worker, and not anymore the services of the communication- and interfacevariables only. The onlinehelp in the dialog, opened by the menuitem Run statement(s), opens now the selectiondialog of the services of all type of systemvariables and not the services of the communication- and interfacevariables only.

New service for logging within a macro

With the new services log(…) and log(…, into: …) of the systemvariable stepscheduler you can log your own informations within a macro in the system or in a userdefined protocol file. With these services you can diagnoistic the macroflow easier.

Systemprotocol is extended

For a more easier diagnosting the systemprotocol is extended. The systemprotocol is containing now the messages of the program and the answers of the user too. With these informations the programflow can be easier interpreted.

Service value(…, put: …) with invalid argument put: in macro

Using the service .value(…, put: …) with an invalid value (e.g: formatrule Date and no value of type Date) resulted in the well known errormessage of executing a bad service, but depending on the current situation this error resulted in a recursive loop and OfficeTalk was ended. Because of this such a service was blocked with the errormessage Invalid argument…. For details please read documentation OfficeTalk Skript, chapter value(…, put: …).

Errorinformation not visible in Scriptdebuggerdialog

The error witch caused to open the scriptdebuggerdialog was not contained in the errorvariable Error within the variablelist. Doubleclicking the variable Error did not unfold its contents, the errorinformations.

Importing a Script

The overwritedialog for a macro did not display the option Startmacro for the old and new version. Because of this, the user was not able to see the differences of the both macros in case of this option was different only.

Exporting a processtemplate with empty macro

Exporting a processtemplate with an action, witch referenced an empty macro, resulted in an error message with ending of OfficeTalk after selecting the contextmenu Export… in the templates listfield of the tabulator Processtemplate.

Critical macros can be locked against overwriting by an import

With the setting System makro a macro can be locked against overwriting by an import of a processtemplate or an import of scripts. With this extension managing processtemplates offline is a little bit easier, because when importing the changed processtemplate again, you must not be carefull, not to overwrite macros with critical informations. Up to now, importing the changed processtemplate you had to be carefull when answering the overwrite dialog and importing a processtemplate with many macros was a little bit hard !
In this context the database table scriptmethodsource is extended by the column systemmethod. Starting the version 4.82 the first time does this extending automaticly. For this first time starting you must login as company !

Opening helpfiles and documentlinks on Linux-Platforms

For the association of a dokumenttype to an application on Linux-Platforms the system defined association instead of the userdefined association was used ever. As the result the wrong application or no application was opened. The helpfiles of OfficeTalk (button Help) and the documentenlinks within the textfields where affected by this.

Public variable can not be used in an actionblock within a macro

Using a Public variable within an actionblock (service addAktionButton(…), addAktion(…), etc.) resulted in the errormessage Undeclared variable when compiling.

Skriptdebugger supports new type of variablen Public

The Skriptdebugger supports now the new type of variable Public.

Service applicationFor(…) of the systemvariable stepscheduler on Windows-Platforms

On Windows-Platforms the service applicationFor(…) of the systemvariable stepschedulder now returns the file association of the system. Up to now the service returned on Windows-Platforms the file association of the environment in OfficeTalk only.

New type of variable in scriptmacro for global use

The macro supports the new variable type Public. A public variable is valid within the execution of all macros after declaration. After declaration, it is accessible by all succeeding executed macros. The type of the variable is equivalent to the public Variable in VisualBasic. For details please read documentation OfficeTalk Scipt, chapter Variabledeclaration.

Changing size of dialogitem Register in the Workbench

The height of the Register could not be changed in the Workbench by dragging with the mouse. The height could be changed in the propertydialog only.

New service allChildren(…) of the systemvariable worker

For installations of big organigrams with the new service allChildren(<workertyp>) of the systemvariable worker workers can be fast queried by criterias.

Multiselection in listfields of tabulator Processtemplated and ScriptBrowser

Thje listfield of the processtemplates in tabulator Processtemplates and the listfield of the Scripts in the Scriptbrowser supports now multiselection. With pressing CTRL- or SHIFT-Key you can select more items. The contextmenu Import and Export work one or all selected items.

Version 4.81

Treelists in processdialogs with OfficeTalk-Items on Windows-Vista and Windows-7 platforms

Using in processdialog a treelistitem (Workbench – tabulator Processdialog – item Treelist), containing hirachical OfficeTalk items (e.g. worker), used for the show/hide symbol the standardsymbol (+-/-Block) instead of the symbol for the Windows-7 platform (Square).

Comment of an assignement (=) in source of macro and menu Format

Formating a source of a macro with the contextmenu Format removed the comment of an assignement with a variable or arrayexpression on the right side of = (e.g. name = fields(0)).

Option Mouse-over Indicator in tabulator Gereral of the preferences dialog

On Windows-7 and Windows-Vista platforms the option Mouse-over Indicator in tabulator General of the preferences dialog could not permanently be deativated. The option was activated again on the next start of OfficeTalk.

New symbols in the toolbar of the Scriptbrowserdialog

The buttons Execute macro and Debug macro in the toolbar of the Skriptbrowserdialog have more understandable symbols. Because of this change, the contextmenues Execute and Debug of the macro textfield have changed in the same way. For details please read documentation OfficeTalk Business-Process-Management, Kapitel Source - Toolbar.

Automate a processdialog

To automate a processdialog, execute statements immediate after opening, the dialogitemlist in the tabulator Scriptdialog of the Workbench is extended by the item Dialogstart and the systemvariable ScriptDialog supports the new service addPostOpenAction(…). For details please read documentation OfficeTalk Business-Process-Management, chapter Workbench and documentation OfficeTalk Skript, chapter Action on start of dialog.

Contextmenu Unlock in startportal Function/-OrganigramBrowser

The contextmenu Unlock was immediate after logging in the left list, containing the functions and the organigram, not available. A processtemplate had to be opened and closed to make the contextmenu available.

Using two or more processdiualogs paralell

For special affairs two or more processdialogs may be used parallel or a processdialog independent from the flow of macro may be needed. e.g The first step of a process must perform large initialisations, the initialisations are using more macros and the user must be informed about the progress. Additionally the initialisations must start automaticly and not by the user by pushing a startbutton in a procesdialog. Because of this requirement a default modal processdialog can not be used. Instead of a modeless processdialog must be used. For details please read documentation OfficeTalk Script, chapter beModeless.

Changing processdialogs dynamicly

A processdialog is able to change its size with the new service width(…, height: …) of the systemvariable ScriptDialog while be worked by the user. Because of this, items of the processdialog can be hided or unhided depending on the context and the handling can be made more user friendly. The services width(…) and height(…)of the systemvariable ScriptDialog are changed in the same manner.. For details please read documentation documentation OfficeTalk Script, chapter width(…, height: …).

New service properties(…) and properties in macro

The systemvariable ScriptDialog supports the new services properties(…) and properties. The services gets the most important properties of the visual items in a processdialog or the properties of the processdialog itself. With this service dynamicly tasks in a processdialog can be easier completed. For details please read documentation OfficeTalk Script, chapter properties(…) and properties.

Workbench created bad statement for horizontal Resizer

Inserting a horizontal Resizer with the Workbench in a processdialog, builded with the button Build the addResizer(…)-statement with wrong named arguments. Because of this, compiling the macro resulted in a syntaxerror.

Contextmenu Funvtion – String – Replace in the macrotextfield of the ScriptBrowser

The template of the Funktion Replace was created with wrong named arguments by the contextmenu.

Handling of the dialogitem Combobox on all platforms

On all platforms the item of an opened Combobox, whitch lies under the mouse, is drawn selected. This gives the user a better visual feedback, because he/she can see, what item will be selected by clicking with the mouse.

New structure of menu View in all tasklists

The menu View in all tasklists is grown much in the history of OfficeTalk by all its extensions. Because of this, it has got a new structure for easier use. The description of the menu View you will find in the documentation OfficeTalk Workflow, chapter Menu View.

Version 4.80

Dynamicly sort of table in processdialog

Sorting dynamicly a table in a processdialog by clicking on a columnheader resulted in a macroerror and the execution of the macro was aborted.

Using the service isMandatoryMissing in macro

Using the service isMandatoryMissing after closing the processdialog with the window close box, resulted in a macroerror in case of a required value was missing and the execution of the macro was aborted.

New item Progressbar in processdialogs

For a better visualizing of long term activities in processes a Progressbar can be used in processdialogs. For details please read documentation OfficeTalk Business-Process-Management, chapter Workbench and documentation OfficeTalk Skript, chapter addProgressBar(…).

Exporting the Callgraph of a scriptmacro as HTML

With the menu Callgraph – Save as HTML… in the dialog Callgraph of macro <macroname> the complete callgraph is exported as HTML. For details please read documentation OfficeTalk Business-Process-Management, chapter List of Scriptmacro.

Wrong definition of table in the database

Typing in more than 32 characters in the field Category or Name of a processtemplate ended OfficeTalk with an error message on saving. As documented since version 2 0 64 characters are allowed for namefields. But this extension was not transported to the two tables authorisierung and substitute.
To avoid this error, please your database administrator to change the two columns category und name in these two tables to 64 chars. Version 4.80 works correct with these limited columns, but OfficeTalk ends with an error message when you type in more than 32 characters.

Running under platform Windows-7

Because of its platform usabilities OfficeTalk was able run on platform Windows-7 since the delivering of Windows-7. Only some visual repesentations where not exactly used as Windows-7 (e.g. moving with the mouse over a button, some fonts, etc.).

Scheduling of processes with steps containing optional actions

Scheduling a step of a process with optional actions could result since version 4.75 in the message No parallel scheduling possible. The scheduling worked right, but the message may lead to some confusion.

Extension of Workbench for using dynamic labels

For using dynamic labels in dialogitems Label, Button, Checkmark and Radiobutton, the property dialogs of these items is extended with the button >>. This button opens the dialog for defining the label as simple text, as variable, as processdata, as an expression or as a labelgroup. For details please read documentation OfficeTalk Business-Process-Management, chapter Labes.

Extension of Workbench for labelgroup in a processdialog

The tabulator Processdialog of the Workbench contains the new button Labelgroup…. The button opens the dialog Source of the labelgroup. Within this dialog you can define the labelgroup to be used in opposite to the labelgroup defined by the scheduling worker. For details please read documentation OfficeTalk Business-Process-Management, chapter Labelgroup.

Extension of Workbench for the title of a processdialog

The dialog for defining the title of a processdialog (contextmenu Dialogtitle… in the processdialog of the Workbench) is extended with the option From Labelgroup. With this option the title of a processdialog can be defined by a labelgroup. For details please read documentation OfficeTalk Business-Process-Management, chapter Dialogtitle.

Onlinehelp for services with label and labelgroup

The services using a label (addLabel(…, key: …), label(…, ifNone: …), label(…)) and using a labelgroup (labelGroup(…)) support now an onlinehelp for selecting a valid label or labelgroup, similar to the workbench. For details please read documentation OfficeTalk Business-Process-Management, chapter Onlinehelp for services with label.

Working tables with numeric columns of foreign database

Tables of a foreign database containing columns of type Numeric, Decimal or Money, can now be worked in a macro. Up to now, the macro was aborted with an error message, when accessing a column of these type. This makes the working with foreign database more easier.

Extended analysing the flow of a processtemplate

The using of labels in a labelgroup within a processtemplate is analysed now. The result is contained in the new tabulator Unknown labels of the dialog Analysis of graph: <name>. The tabulator contains the unknown labels and their source, the macro. For details please read documentation OfficeTalk Business-Process-Management, chapter Unknown labels.

Contextmenu Unlock in startportal Function/-Organigrambrowser

The item Unlock in the contextmenu of the organigram listfield was with setting startportal Function/-Organigrambrowsers for the company’s login available only. Now the contextmenu is available under the same conditions as the startportal Dialog.

unter den selben Bedingungen wie im Eingangsportal Dialog verfügbar.

Extended contextmenu of the maxro textfield

The contextmenu for the source of the macro in the ScriptBrowser is extended by the entry Directive. With its submenues you can insert a pattern of the selected directive into the source.

Formatting macro with comments

Comments (strings beginning with ’) after some statements (e.g. Array(…), Join(…), etc.) where moved by the automatic formatting (contextmenu Format) to the next statement.

New functions in scriptmacro for easier working with strings

For complex tasks with strings more functions are added. For details please read documentation OfficeTalk Skript, chapters Split, Filter, Replace, LCase, UCase, LTrim, RTrim, Space, String, StrReverse, InStrRev und StrConv.

Extended webservices ExitProcess und DelegateProcess

The both webservices differenciate between bad permission and invalid parameters. Please read documentation OfficeTalk Workflow, chapter DelegateProcess and ExitProcess.

Webserice VisibleProcessTemplates

Using the webservice VisibleProcessTemplates resulted in the weberror „not understand select:“

Some database messages of stress situations

Some database messages used for stress situations where not localized. Now these messages are localized too for a better understanding.

Opening tasklist as browser with erroneous processes

Opening the tasklist in browser format (Tasklist as browser in tabulator Tasklist of the settings) may end OfficeTalk with a diagnose message, after a failure termination of a process with commiting the transaction.

Terminate process with mail respones

Terminating a process with mail response resulted in an programmend with an error message when the directory of the program (Bin) was writeprotected, sorry. In secure installations the programmdirectory may be writeprotect.

Processtemplace as subprocess

A processtemplate can made be a subprocess in the tabulator Processtemplate with the button Options…. With this setting the processtemplate is not shown in the right listfield of the tasklist (startable processtemplates) and therefore can not be started within the tasklist. Such a marked processtemplate can be started within a macro by the statement Start only. This helps making the tasklist clean of subprocesse, whitch are not directly startable by the user.
In this context the database tables process and processtemplate are extended by the column subprocess. Starting the version 4.76 the first time does this extending automaticly. For this first time starting you must login as company !

Version 4.75 Build 07.18.2011

Imported processtemplate was not complete exported à Message while scheduling Script or Macro was not found

Scheduling a process of an imported processtemplate results in the message Script or Macro not found, because of the processtemplate was not completly exported and imported. This could happen, when the processflow uses a macro, whitch contains the statement addRegister(…) with direct specifyed macros for the tabulators (e.g.: addRegister(Array(Array(“First Page“, “Scriptname.FirstPage“),…) ). Scheduling the process results in the named message. The menu Extras – Processflow will show for such a processtemplate in the tabulators Missing macro or Missing/empty script theese missings.

Muitiselection in Listfield and Table of a processdialog with service value(<Name>, select: <Variable>) in Macro

In the dialogitems Listfield and Table of a processdiaog with setting Multiselection more items could be selected be the user (CTRL + left Mousebutton) only. A programmaticly multiselection with the service value(…, select: …) was not possible. Now programmaticly multiselection with the service value(…, select: Array(<element[,…])) is possible. For details please read documentation OfficeTalk Script, chapter value(<Name>, select: <Variable>).

Extended dialog Graph for process: <processname>

In dialog Graph for process: <processname>, opened with the menu Pre&vious executions... in the tasklist, the startime of the last scheduling of the step is following the scheduling counter. With this most the times looking into the history is obsolete now.

COM-component was not selectable in macro with Interface-statement (Windows-Platforms)

COM-components, installed in the systemdirectory %CommonProgramFiles%, where not selectable in the Interfacedialog, opened with the statement Interface in a macro. The button Accept was grayed. Only Windows platforms where affected by this !

Startmacro ends with Halt

Scheduling an action by executing a startmacro, whitch ends with the statement Halt, resulted in an ending of OfficeTalk with an error message, sorry.

Changing Right only when using the locale database

Ending OfficeTalk after changed a Right in tabulator Rights only, required not the saving when the local database was used. This happened in general using the evaluation version only, because the evaluation version works with the local database.

Small enhancement in contextmenu Find… for textual inputfields

Searching forward and backward did not search after finding the last match with the same dialog. The find dialog had to be opened with contextmenu Find… first.

Searching bachward did not notify after reached the first match, that no match is found.

Version 4.75 Build 07.11.2011

Contextmenu Paste for textual inputfields

The contextmenu Paste may insert an obscure text, if it is used before the first time of contextmenu Copy or Cut. The text was orginated by a Copy or Cut of the JOOPS development.
Choosing the Paste menu with pressed Shift key brings up a selectiondialog with the maximum 10 last items, for whitch the contextmenu Copy or Remove was used. You can select an item for pasting within this list.

Enhanced contextmenü Find… and Replace… for textual inputfields

The input of the find and replace-values in the Find- and Replacedialog can now be used repeatly, because the inputfields are comboboxes and offer the last inputs.

The contextmenues could not be used in modal dialog, because the Find- and Repacedialog was opened, but no input into the textfields was possible. Examples of modal dialogs are the dialog for searching a worker, opened with the menuitem Search... in the organigrammdialog, the contextmenues New… and Rename… of the left listfield in the tabulator Scripts, etc.

The contextmenu of the inputfields in the Find and Replacedialog could not be used, because it was opened behind the dialolg.

Version 4.75 Build 07.07.2011

Textgroups are inherited

A worker uses the textgroup of its superior worker, if it has no. This makes the managing of textgroups more easier:

Textgroups supports Unicode for labels in processdialogs

The names of labels of textgroups in processdialogs are handled now as Unicode. With this in a processdialog a label in the textgroup may use chinese characters. Because of, the file for the textgroups must be created in Unicode.

Contextmenu Find… and Replace… for input textfields

For the dialogs of searching and replacing the installed language is used now. In the past the English language was used in any case. And the both dialogs stay on top of all OfficeTalk dialogs. This makes switching between searching and inspecting result easier.

Contextmenu Ask in the personal tasklist

For the contextmenu Ask in the personal tasklist the logged in worker must have the process permission Schedule.

Dialogfield processtemplates in thev tasklist and dalog Start new process

The dialogfield of the processtemplates contains processes with permission Start or Read only. This helps for large installation, because the dialogfield does not contain unusable processtemplates. Up to now the dialogfield contained the processtemplates of all visible workers without respect to the existing permissions.

Menues and toolbar buttons for selected process in the tasklist

Menues and buttons of the toolbar in the tasklist for working a selected process (e.g.: Schedule, Terminate, Delegate, etc.) inform the user with their visual state (grayed/not grayed) wether the activity is possible.

Displaying further informations of a process in the tasklist

To get further informations of a selected process (e.g. History, Processdata, etc.) the permission Read is required for the logged in worker now. The menu an toolbar buttons are grayed for a missing permission. For passive workers enshure, that the worker owns the permission, if required. Active workers in general own the permission, because it is needed for starting the process.

Displaying processes in the tasklist of a organsation unit

Up to now the logged in worker had to own minimum the permission Read for including the process in the tasklist. This resulted in some confusion when this permission was missing, because the title of the window pointed to the overall amount of processes within the organisation unit, but the tasklist did not contain these processes. Now, the tasklist contains the processes within the organisation unit without respect to the existing permissions. The menues and buttons of the toolbar in the tasklist reflect an existing or missing permission. This optimizes the visual feedback for the possible next steps.

Processstate and processdata in the browsered tasklist

If the logged in worker is missing the permission Read for the selected process, the middle dialogparts for the processtate and for the processdata contain the text No read permission.

Contextmenu Actualize for big tasklists

Actualizing big personal tasklists (> 500 processes) with the contextmenu Actualize in the personal tasklist did not point the busystate for about 10 to 20 seconds while internal work. Now this timespan of internal work is pointed with an active mousepointer to give the user visual feedback of busy state.

Opening the tasklist in browserformat (Settings - tabulator Tasks) as unit (Company, Department, Office, Team) and many tasks (> 500) the symbol of the tasktemplate was used shortly for the tasks of an unfolded worker, when actualising the tasklist with the menu Actualize.

Kontextmenu Paste in tabulator Stepresults

Inserting with the contextmenu Paste a stepresult used in the questionmessage as the name of the stepresult <name> [nil], because the result could not calculate its sequencenumber. This is a small issue, but small issues count in OfficeTalk too.

Version 4.75 Build 06.27.2011

Menu View-Actualize in the tasklist did sometimes no correct job

The tasklist of an unit (Company, Department, Office, Team) contained under some circumstances after using the menu View-Actualize terminated processes and new started processes where missing.

New commandline option /NoVersion

With the new commandline option /NoVersion and –NoVersion checking of the version and possible update of the database is skipped. This option is usefull for a network installation with many clients when the clients are missing the permission to perform a database update. This commandline option must not be used on a local installation !

Working with processdata

The dialog Processdata for <processname>, opened with the contextmenu Processdata… in the tasklist, showed after actualizing outdated processdatas in case of changed by a process of another worker. The service refresh of the systemvariable processdata worked in a macro incorrect too.

Autocomplete-Function for editable comboboxes

The Autocomplete-Function for editable comboboxes is now case sensitive. This gives more flexibility for the input and detection of hits.

Sending mail with setting Use SSL

With the setting Use SSL in Tabulator Mail of the settings dialog, no mail could be send. The reason was shown in the protocol with (The identifier Net.SMTPSSLConnection has no binding).

Logindialog has a menu

The logindialog has now a menu. The function of the Help-button is moved there (Help – Login) and das menu Extras contains the item Forget logins. With this menuitem you can clear the remembered logins in the combobox Login:.

Version 4.75 Build 06.10.2011

New setting for items in a processdialog for quicker working

Buttons, Options, Calendar and Checkboxes supports the option Not tabable. With this option an item ignores the TAB-Key and keyboard freaks are able to fullfill the dialog a bit faster, because of the TAB-Key skips these items. For details please read documentation OfficeTalk Business-Process-Management, chapters Propertydialog Checkbox, Propertydialog Calendar, Propertydialog OK-Button, Propertydialog Option, Propertydialog Cancel-Button und Propertydialog Actionbutton and documentation OfficeTalk Script, chapter notTabable(…).

New services for navigation within a process

To make the navigation within a process easier for a macro, to fullfill special requirements, some services are added to the systemvariable Step and documentated. For details please read documentation OfficeTalk Script, chapter Step.

Column Duedate in the tabbled tasklist

Displaying the column Duedate in the tabbled tasklist ended OfficeTalk with an error message for tasks with some exception conditions.

Login using the Autocomplete function

Login using the Autocomplete function of the combobox Login leads most the time to the message Can not find the licence… . If an allready used loginname should be reused, this name had to be selected with the mousebutton from the comboboxlist.

Version 4.75 Build 06.09.2011

Opening Step in the tasklist with the contextmenu Processflow…

The option Starttime at was choosen in any case additional to the really choosen start time option, when opening the step within a processgraph, whitch is opened with the contextmenu Processflow… in the tasklist. This leads sometimes confusion.

Service addTable(…) of the systemvariable ScriptDialog is extended

For the description of the columns with argument column: in the service addTable(…) must not be used literals anymore. You can use variables or functions for any aspect now. This gives you more freedom for generating dynamic tables.

Autocomplete for editable comboboxes

The editable comboboxes in dialogs (e.g. Loginfield in Logindialog, Namefield in Resourcedialog, etc.) supports now autocompletion. This means, that typing a character completes the rest with a matching entry within the list of the combobox. The autocompleted rest is selected in the case of an unwanted completion and is replaced by a subsequent typing.

Version 4.75

Startable processtemplates in dialog Start new process (menu Start new process)

The listfield of the startable processes used the process permission Read instead of Start. The option All workers hided all startable processtemplates. When open the startdialog for an organisation unit (Company, Department, Office or Team), the listfield did not contain the processtemplates of the subordinated workers, allthough the processtemplates of subordinated workers must be visible. In these cases the listfield contains the processtemplates of the subordinated workers with the option All.

Aborting a process in group tasklist

In the group tasklist with symbols (logged in as Company, Department, Office or Team) double clicking a process aborts its execution. But you where asked wether to adopt the process. Answering Yes aborted the process as described.

Automatic scheduling of a process

With the automatic scheduling of a process (contextmenu Execute automaticly in the personal tasklist) an execution of processes without interaction of users is realized. Because it was supported experimentally only, automatic scheduling ended on delegation of the process, closing the tasklist or ending OfficeTalk. Now an automaticly scheduled process stays automatic in any situation up to the end of scheduling or cancelling by the contextmenu Execute automaticly in der personal tasklist. As an additional information the starttime of the next step of an automaticly scheduled process is displayed blue in all variants of the tasklist.
In this context the database table process is extended by the column cyclic. Starting the version 4.75 the first time does this extending automaticly. For this first time starting you must login as company !

Extended statement Start in Scriptmacro

The statement Start for starting a process within a macro in extended by the option Automatic. With this option, the process is started for scheduling automaticly, similar to the contextmenu Start automaticly in the tasklist.

An active worker can not export/import processtemplates

An active worker (Desk, Machine) can not export its processtemplates and can not import any processtemplate. The required menus are missing in the contextmenu of the listfield in the tabulator Processtemplates.

Version 4.74 Build 05.27.2011

Extension of the dialogitem Table in processdialog

The column of the dialogitem Table supports now background colors for a better visualisation. For this extension the service addTable(…) of the systemvariable ScriptDialog, and the propertydialog of a Table in the Workbench are extended. For details please read documentation OfficeTalk Script, chapter Table and documentation OfficeTalk Business-Process-Management, chapter Propertydialog Table.

Starting OfficeTalk with commandline options –login and –pwd

Since version 4.40 starting OfficeTalk with the commandline options resulted in an error message and OficeTalk ended, sorry.

Contextmenu Callgraph of the macro listfield in the SkriptBrowser

Under some rare conditions of the Call statement using the contextmenu resulted in an error message with ending of OfficeTalk, sorry.

New service item(…) of the systemvariables processdata and scheduledata

The systemvariables processdata and scheduledata support the new service item(…). The service gets the data for the given entyname. The entry is searched within all groups. Because of, the entryname must be unique within all groups. For details please read documentation OfficeTalk Script, chapter Systemvariable processdata.

Version 4.74 Build 05.20.2011

Displaying the currently used database

The title of the startportal points now the used database as (Database: <name>). This supports testteams and productiveteams to indicate their currewntly workingarea. In this context the systemvariable stepscheduler supports in macro the new service databaseName. The service gets the name of the used database.

To point the worker to his used database environment, the title of the portalwindow shows the used database.

Layout of a process in dialog Processgraph: <name of process> is optimized

The layoutmanager positions stepresults (the blue connection lines with label) more better. In general horizontal connections are affected by this optimisation.

Contextmenu Schedulingoptions – Scheduling is in dialog Processgraph: <name of process>

The scheduling mode with the contextmenuOptional and Mandatory for a step was set correctly,but was not visualize (exclamation mark) correctly. This could result in little confusing.

Wrong assigned comments of a Call-Statement in Scriptmacro

A comment whitch is typed after a Call-Statement with arguments was assigned by the formating to the following statement.

Assigning in a macro a string with = to another string

Assigning with = a string with emphasis (service color or bold as result of a ScriptDialog) to another string assigned the emphasis too and did not remove the emphasis for the assigned string. As result an inputfield of a dialog with this string has the same emphasis as then inputfield with the original string in the preceeding dialog.

Workbench ignores statements for a dialog in an opened macro

Opening a macro with the Workbench does not recognize statements of a dialog with the notification No statements for a dialog found…, when the case of the dialog variable in the declaration (Dim-statement) differs from the case of the usings within services. This could happen only, writing the macro by hand, because writing the macro with the Workbench uses the right case. Now the case of the dialog variable is not important anymore.

Version 4.74 Build 05.10.2011

Service bold of the systemvariable ScriptDialog

The service bold of the systemvariable ScriptDialog did not work correctly, when the inputfield was empty at opentime of the processdialog.

New services for extended control of processdialogs

The systemvariable ScriptDialog supports new services for controlling a processdialog with the keyboard. For details please read documentation OfficeTalk Script, chapter isCtrlKey, isAltKey and isShiftKey.

Version 4.74 Build 05.03.2011

Button ScriptBrowser (>>) in tabulators Start-, User- and Endaction

When the process is opened within the tasklist (e.g.: contextmenu Processflow), the ScriptBrowser (button >>) in the actions tabulator can be used only, if the logged in worker is the owner of the script, the action points.

Extended test of permission for exporting a processtemplate as HTML

Exporting a processtemplate as HTML exports the used scripts and macros only, if they belongs to the logged in or any subordinated worker. For scripts and macros belonging to another worker the text Not found or no read permission is printed instead. This prohibits unauthorized persons to inspect the content of scripts and macros.

Extended design facilities for a processdialog

For spezial purpose you can use large sized labels with userdefined background and forground color. For details please read documentation OfficeTalk Business-Process-Management, chapter Propertydialog Inputfield.

For many dialogitems extended design facilities are available to adjust a processdialog more closer to the CI of a company. Within this context the semantic of the service color of the Systemvariable ScriptDialog is modified. The service color is changed to control the foregroundcolor of a dialogitem only. In general this is the color of a text within the dialogitem. The new service backgroundColor controls the backgroundcolor of dialogitems in the future. If you use the service color to control backgroundcolor of dialogitems, please use instead the new service backgroundColor. For details please read documentation OfficeTalk Business-Process-Management, chapter Workbench and documentation OfficeTalk Script, chapter Define and request item properties.

Language could not be reset

The selected language in the combobox Language of the dialog Login and Databaselogin could not be reset to the system language. To reset to the system language its settling had to be removed manually.

Version 4.74 Build 04.27.2011

Selecting the language in dialog Login and Database login

The combobox Language contains for an easier selection now additional the flag of the country and its name.

Version 4.74

Error message while using the ADO communicaton library

Using the ADO communication library in a macro resulted very rare in an error message like „does not understand asInterfacePointer…“.

Set the language to be used dynamicly

When more languages are installed, you can define with the new combobox in the logindialog the language to be used for this run. For details please read documentation OfficeTalk Introduction, chapter Logindialog.

Messages with strings in Unicode

Messages with strings in Unicode (e.g. Chinese version) resulted in an endless loop. OfficeTalk had to be closed with the taskmanager.

Earliest und Latest Enddate in dialog State of: <processname>

The dialog contains with introduction of the Enddate two new fields Earliest Enddate and Latest Enddate, like the column Enddate in the Tasklist (as table).

New column Due Date in tha tasklist as table

The tasklist as table supports the new column Due Date. This column contains the assumed earliest and latest scheduling end of the process. For details please read documentation OfficeTalk Workflow, chapter Tasklist as table. Important in this context is the interpretation of the times Estimated worktime and Start after. For details please read documentation OfficeTalk Business-Process-Management, chapter Tabulator Schedulingoptions and Tabulator Stepresults.

Workday has nnn Hours in Tabulator Description

The tabulator Description of a worker contains the new field Workday has nnn hours. With this field you can define the amount of hours of a workday for a worker. A worker inherits this value from his superordinated worker. This value is used in conjunction with the Due Date of a process. For details please read documentation OfficeTalk Business-Process-Management, chapter Tabulator Description. In this context the database table bearbeiter is added the column workdayhours. Starting the version 4.74 the first time does this adding automaticly. For this first time starting you must login as company !

Contextmenu current worker of the step in dialog Processgraph: <name of process>

Choosing the contextmenu Worker – current worker of step did not actualize the step in the diagram.

Dynamicly changing timeconditions of any step while executing a process

With the services startDate(…, time:…, for:) and startAfter(…, for: …) of the systemvariable Step you can dynamicly modify the start time of any step within the process without respect to its definition. With these services the conditions of time can be changed according to dynamic conditions. For details please read documentation OfficeTalk Script, chapter Systemvariable Step.

Version 4.73 Build 04.07.2011

Column Remaining Lifetime in tasklist as table

Tasks with uncomplete Remaining Lifetime provacated.on opening the tasklist as table the end of OfficeTalk with an error message. The originated processtemplate has incomplete scheduling times.

Labelfile DialogLabels.ini with labels with Unicode characterset for the Label in a processdialog

The label in the labelfile DialogLabels.ini can be written now with Unícode characterset too. This makes the using of labelgroups for a Label in a processdialog easiers (e.g: China).

Option No change of Organigram in tabulator Authorize

The option did not prohibit the worker to move in the functionlist a subordinated worker into another organisation unit when the startportal Organigram-/Functionbrowser was used.
This option prohibit now changing of vital data in the workers adresscategory. Theese are in general the Login, the Mailadress, the setting for the Textgroup and the main descriptions of an organisation unit.

Menu for inserting a Step in dialog Processgraph: <name of process>

The menu New in the contextmenu and in the menu Work of the dialog differs for an easier using between appending a new step (Quick-Step und Step) and inserting a new first step (Quick First-Step).

Named visibility in the detailed view of the organigram

Setting the visibility of a worker in the tabulator Visibility to a named worker, ended OfficeTalk with an error message when displaying this visibility in the detailed view of the organigram, sorry.

Menu View – Workercontent – All in Function-/Organigrambrowser

Since the new items Rights and Development of the menu Workercontent the menu item View – Workercontent – All could not be deactivated and because of the categories of the workers could not be folded out.

Extended support of Unicode for the database of OfficeTalk

Using Unicode characters, whitch was mainly done in the chinese version, was not possible for entities of OfficeTalk (worker, processtemplate, etc.), because storing Unicode characters in the OfficeTalk database was not fully supported.

Removing histories

After removing histories with the contextmenu Remove Histories in the listfield of the Processtemplates in the same named tabulator the toolbar button for save and the menu File – Save were enabled, but the histories where persistent removed allready. Additionaly you must accept the removing of the histories with an additional message when other changes where not saved.

Version 4.73

ScriptBrowser-Dialog is read only

Opening a SkriptBrowserdialog with the button >> in an action tabulator of the stepdialog made the ScriptBrowserdialog completely read only under a special circumstance: The owner of the opened processtemplate is a subordinated worker, and the superordinated (logged in) worker contains the script referenced by the action. This rule is too restrictive !

Opening an allready opened tasklist

Opening an allready opened, but minimized tasklist with the menu Processes - Open Taskist and the toolbar button for opening the tasklist did nothing. The same was right for all variants of the organigram dialogs and the dialog to start a new process.

Optimized prozessflow for changes of many macros

Saving the changes in a macro with the Save-Toolbarbutton closes all other opened dialogs and then saves the changes in the database. With this proceeding changing many macros is little worse. The search result has to be rebuilt after each save. Now the Save-toolbarbutton near the textfield of the macro in opposite to the Save-toolbarbutton near the menu leaves the dialog of the query results opened.

Combobox Scripts in the tabulators Start-, User- und Endactions of the stepdialog

The combobox contained a scriptname twice, when the script was found within the visible hierarchy of workers more times.

Executing a macro with to much arguments

Executing a macro with the statement Call using to many arguments than the called macro defined, ended OfficeTalk with an errormessage. This was possible only by ignoring warning messages when writing the Call-statement.

Using an empty SQLString-argument in a Call-statement

Using a variable of type SQLString-without content (Null) in a Call-statement as argument resulted in the called macro in an argument with the string content “Null“.

Creating and updating a database user

Creating a database user with the contextmenu Create database user of the left listfield in the ScriptBrowser dialog and updating the database user with the login dialog, opened with the button Login and Password… in the worker’s dialog, shows on errors the detailed reason. With this information you can decide better, how to proceed.

Onlinehelpdialog for Call statement displaying empty macro

The dialog Choose a macro, opened is the ScriptBrowser dialog by the onlinehelp for the Call-statement was aborted with an error message, if it had to display an empty macro (containing no statements and no directives) where the macroname was not followed by a linefeed, sorry.

Using in macro with the Call statement an empty maco

Because of using an empty macro is wrong in general, the places where the using by a Call statement is displayed, an empty macro is displayed with red name. Affected by this is the contextmenu Uses… of the listfield of macros in the Skriptbrowser dialog and the onlinehelp dialog Choose a macro for the Call-statement. A macro is interpreted as empty, if it contains no directive and no statement. For details please read documentation OfficeTalk Business-Process-Management, chapter Scriptmacrolist contextmenu Uses.. and Onlinehelp for Call-Script statement.

Accelleration in working within the dialog of the SkriptBrowser

The contextmenu of the sourcecode field in the ScriptBrowser supports the item Format+Compile. This item is a shortcut for the two items Format and Compile. The toolbar of the sourcecode field contains a new button for this menuitem. The image of this button is a combination of the buttons Format und Compile. Additionally the toolbar contains a new button with a discimage for saving all changes. The button does the same job as the diskbutton in the main dialog. This extension is mainly for an excelleration of working with scripts and macros in the ScriptBrowser.

Abandon changes in a macro with usinglevel Expert

Working with the usinglevel Expert did not let you abandon changes of a macro in an easy way. You had do be a real expert, to do this. Now with the usinglevel Expert changes in a macro are abandoned anyway when you select another macro, script of category without compiling.

Moving dialogitem Register with the cursor-keys in the Workbench

Moving a dialogitem Register in tabulator Processdialog with the cursor-keys resulted in an error message with end of OfficeTalk, sorry.

Compiling macro with incomplete For-Next-statement

Compling a macro with For-Next-statement without Step resulted in an error message with end of OfficeTalk, sorry.

Controlling dialogitems in a tabulator of a processdialog

The dialogitems in a tabulator of a processdialog can now be controlled by services of the systemvariable (ScriptDialog) of the main processdialog too. You must not use the systemvariable ScriptDialog of the tabulator. With this enhancement organizing of processdialogs with tabulators is more easier. For details please read documentation OfficeTalk Script, chapter addRegister(…).

Contextmenu Unlock in dialog OrganigramBrowser

The contextmenu Unlock can be used now for subordinated workers as logged in Department, Office and Team too. You must not be logged in as Company anymore, to unlock a worker.

Extended saving a processtemoplate as HTML

The HTML export of a processtemplate may contain not only the startmacros, but all used macros. With this extension, a processtemplate can be completly be documented and reviewed. For details please read documentation OfficeTalk Business-Process-Management, chapter Save as HTML.

Extended view settings of the Function-/Organigrambrowser

The menu View – Workercontent in the dialog of Function-/Organigrambrowsers supports the two new settings Authorizing und Development. With theese new settings of view working for rights of workers and development of processtemplates is a little more easier. For details please read documentation OfficeTalk Business-Process-Management, chapter Workercontent in Function-/Organigrambrowser.

Inserting a new worker in organigram graph

After inserting a new worker in the graph of the organigram Organigram for: <workername> with the contextmenu New or with the menu Worker – New a bad area remained in the graph. The diagram had to be made clean with the refreshkey F5,

False matchings of the usings of a script and macro

The matchings, created with the contextmenu Usings… of the listfield of the scripts in the Scriptbrowserdialog, contained sometimes bad matchings. e.g: Searching for usings of the script Service answered usings of the script FirstService too. The contextmenu Usings… of the listfield of the macros was affected by this also, because searching the usings of a macro must take its scriptname into respect.

Display paths of execution of a processtemplate

The dialog Paths of process <name of process>, opened with the menu Statistics - Executiontimes/-paths of the dialog Processgraph: <name of process>, asked for saving the changes for a modified process. This is not necessary here, because the process can not be changed within this dialog.

Button Test in tabulator Mail of the settings dialog

The button Test in tabulator Mail of the settings dialog resulted in an error message, if the logging in the tabulator General was activated.

Changing in the Workbench a Table- or Listfield of a processdialog with responsible item

Changing the properties of a Table- or Listfield resulted in removing its name in responsible items (Action, Doubleclick, Resizer and Groupbox). The name of the changed item had to be set in the responsible item again.

Function-/Organigrambrowser and contextmenu in dialog Processgraph: <name of process>

The contextmenu Open a the step resulted in very rare situations in an error message with end of programm after the step was opened, sorry.

Beginnin Drag+Dop in listfields and wanting a contextmenu in real

If you began to do Drag+Drop with pressing left mousebutton, move the mouse a little an pressing then the right mousebutton the get the contextmenu, could lead to an error message with ending of OfficeTalk, sorry. This is a real rare situation, because different mouse buttons are pressed the same time while moving the mouse.

Better designing a processlayout with more userdefined variants

In dialog Processgraph: <name of process> you can affect the desing of the graph more individually. With the new contextmenu Reorder successors… you can reorder the successors of the step in the horizontally direction. Because of this new feature designing an extended processgraph is easier. For details please see documentation OfficeTalk Business-Process-Management, chapter Reorder steps.
For this extension the two database tables stepresult and stepresulttemplate are extended by the column sequ at the first start. For this you must login as company.

Version 4.72 Build 2.16.2011

Logging in tabulator General of the settings dialog

Activating the Logging in the tabulator General of the settings dialog prevented OfficeTalk to be ended normal. This happened since Version 4.72 Build 2.10.2011 ! Earlier versions where not affected by this !

Setting Wait for answer in tabulator Mail in Workbenchdialog

A macro with the option Wait for answer could be reopened with the Workbench as usual, but the option was not recognized.

Tabulator Mail in Workbenchdialog is extended

The tabulator Mail in the Workbench is extended for the last extensions of the systemvariable Mail by the options Use SSL and No Authenticate. For details please read documentation OfficeTalk Business-Process-Management, chapter Workbench, Tabulator Mail.

Sending and receiving mail with and without login (anonymous login)

For an anonymous login on a mailserver (without using user and password) the tabulator Mail of the settings contains the new option Authentication required. Because of the login is required on a mailserver, this option is the default. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings tabulator Mail.
To use this option in a scriptmacro dynamicly, the systemvariable Mail supports the new services authenticate and authenticate(…). For details please read documentation OfficeTalk Script, chapter Systemvariable Mail.

Sending a mail in dialog About OfficeTalk

Running the Windows-Platforms Windows-2000, Windows-NT and Windows-95 resulted in an error message with end of program, when in the dialog About OfficeTalk a mail was sent by clicking the link at the bottom of the dialog. Because of these platforms are rare, the error was not detected up to now.

Dynamic using of von SSL for sending mail in a scriptmacro

Sending a mail in a scriptmacro you can overwrite with the service ssl(…)of the systemvariable Mail the setting for using SSL in the general settings. This helps, when you will use a different host than defined in the general settings. For details please read documentation OfficeTalk Script, chapter Systemvariable Mail.

Version 4.72 Build 2.10.2011

Sending secure mails

The tabulator Mail in the settings dialog contains the new option Using SSL to send mails via the SSL port. This option was accessible allready manually in the Registry on Windows-platforms and in the settings files on Linux-platforms. The setting Using SSL is used for sending mails within a scriptmacro, and for the Question/Answer communication of a process.
The tabulator Mail contains the new button Testing. With this button the current settings are validatable by sending a testmail to the logged in worker. The sending is accepted by a notification or by a message with the error reason. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings tabulator Mail.

Extended service evaluate of datatyp String in scriptmacro

The expression in a String, whitch is executed with the service evaluate, can use now all variables of OfficeTalk. Theese are arguments, locale und global variables. For details please read documentation OfficeTalk Skript, chapter Special service of datatyp String.

New services of the systemvariable FileSystemObject

For OEM-Users the systemvariable FileSystemObject supports the new services validateMessages(…) and translations(…, proofings: …). For details please read documentation OfficeTalk Skript, chapter FileSystemObject.

Missing service of systemvariable FileSystemObject

The service createFile(…)of systemvariable FileSystemObject was documented but not supported.

Format and compile a macro with activate colorizing

    Formating or compiling a macro with activated colorizing resulted in an error message, when in a few type of statements an expression was used instead of a variable ( e.g. open temppath & "Log-File.txt" for output instead open dateiname for output).

Version 4.72 Build 2.2.2011

Very first start after installation

When starting OfficeTalk the very first time after installation, the creation of the database tables was aborted. OfficeTalk had to be restarted to create the database tables in the right way.

In the database table absent a new additional column was not inserted as required. So switching to the category Absents resulted in an error message and OfficeTalk was aborted.

Using startportal Dialog with local database of the evaluation version

When using the startportal Dialog, the menuitems Save and Save and Close in the dialog Organigrambrowser, opened with the menu Overview, store the local database not anymore. The changes are prepeared for storing only. The changes are stored into the local database on closing the dialog of the startportal.

Changing the layout of a processtemplate in the evaluation version

On end of program changes in processtemplate’s layout where not saved running the evaluation version. After restart of the program, the old settings of the processtemplate’s layout where active.

Version 4.72

Scheduling a systemprocess with a Step containing a Startaction only

Starting a systemprocess (System – Start, System – Login) by the login of a worker runned into an infinite loop when a Step in this process did contain a Startaction only.

Systemprocesses where not started on login of a worker as described

The systemprocesses named System-Start and System-Login where not started automaticly on a login of a worker, as described in documentation OfficeTalk Business-Process-Management, chapter Start of systemprocesses.

OfficeTalk as Webserver

The settings in tabulator Webserver of the setting dialog are stored in the userdefined settings and not in the global settings anymore. Because of this, you must not start OfficeTalk as administrator to activate the functionality of the webserver anymore. And OfficeTalk can be started twice on the same machine using different webserverports. See documentation OfficeTalk Business-Process-Management, chapter Tabulator Webserver.

Webservices VisibleProcessTemplates and StartProcess

The webservice StartProcess ended with an error, using a processtemplate of a superior worker and without option View – All processtemlates in the tasklist of the logged in worker. See documentation OfficeTalk Workflow, chapter Webservice StartProcess and Webservice VisibleProcessTemplates.

Logging the installed version

For diagnostic affairs the used version with its environment name is logged with activated logging into the logfile,

OfficeTalk uses update 7.7.1 of the development platform

OfficeTalk is based now on the version 7.7.1 of the development platform. This is visible in the dialog The development platform, opened with the button Development platform… in the helpdialog OfficeTalk/MSP/OfficeTalk/MS.. The using of OfficeTalk is not affected by this change.

Using Void-Functions of extern DotNET-Systems in a scriptmacro

In the past using Void-Functions/Services of extern DotNET-Systems, loaded with the directive Assembly, resulted in an error message. The function was executed in the extern DotNET-System, but ended with an error message.

Moving worker within the organigram structure

Moving a worker within the organigram structure was made persistent only, if any other changes where done and not made persistent. This resulted sometimes in curious effects.

Toolbarbutton Save in Organigrambrowser dialog

The toolbarbutton Save in the Organigrambrowser did not work correctly, using the startportal Dialog. Changes had to be made persistent with the menus Save and Save and Close.

Using globale and locale settings under Windows-Vista and Windows-7

Differentiating the settings in globale and lokale settings was not possible in any case using the platforms Windows-Vista or Windows-7. By the way this was visible in a few situations only ! The setting dialog for the used type of database server was such an example. Selecting the option Use permanent did not prevent the dialog to be opened when starting OfficeTalk the next time.

Filling out processdialogs under Usinglevel Webserver

Filling out a processdialog and leaving a mandatory field empty, skipped the information message about the missing input, when trying to close the dialog. when the Usinglevel Webserver was used. This looked curious, because the dialog ignores the close, but did not say why.

Using a webservice with an invalid login

Using a webservice with an invalid login by a webclient resulted in OfficeTalk in an endless loop, if no valid login was preceeded. As a result OfficeTalk had to e killed manually.

Using portrait in workerdialog

Using a portrait in the worker’s dialog did affect the windows icon of the worker’s dialog only for the logged in worker, The dialogs of all other workers contained the portrait of the logged in worker. Changing the portrait in the worker’s dialog did not modify all other relevant opened dialogs (startportal, workerdialog and ogganigrammgraph). The file of the inserted portrait could not be removed ore moved within the filebrowser as long as OfficeTalk was not ended. Theese are no important changes, but we want all to work all as described !

Directive Assembly with filename

Loading an Assembly with the directive Assembly worked with a given signature only. Typing its filename resulted in an error message like Invalid Assembly… The filename is typed into the sourcefield of the SkriptBrowsers after the keyword Assembly, or selected in the dialog Select an Assembly, opened in the onlinehelp for the keyword Assembly, with the button Seaching. See documentation OfficeTalk Business-Process-Management, chapter Tabulator Assemblies.

Extended diagnose for login using MS-SQL-Server and PostgreSQL-Server

Using a MS-SQL-Server and a PostgreSQL-Server the diagnose for log in is extended. If you get the message Invalid ODBC-Entry…, you will get more diagnose information with switching on in the settings Logging.

New webservice Delegatables und extended webservice ActiveProcesses

The new webservice Delegatables gets the workers, whitch are allowed to adopt a process. Such a worker can be used in the webservice DelegateProcess as argument to.
The webservice ActiveProcesses answers now the priority, runtime, lifetime and the semaphore of each active process. For details please read documentation OfficeTalk Workflow, chapter Delegatables.

Extended onlinehlep for the tasklist’s dialog

The tooltip of a grayed button in the tasklist’s dialog (Finish, Adopt, Schedule,…) gives additional informations about the reason of the grayed state. Sometimes this may be more helpfull.

Controlling process by a received eMail

With the new services receiveFrom(…) and receiceAndRemove(…) of the systemvariable Mail you can control a process with receiving eMail. Receiving the eMail can be configured as needed by the process. For details please read documentation OfficeTalk Skript, chapter Mail, services receiveAndRemove and receiveFrom(…).
Receiving an answer (eMail) for a question by a process resulted since version 4.60 into an error message, when the answer did not contain an attachment, sorry.

Searching for permissions in dialog Assistent for workersearch in: <workername>

Up to 4.71 with the tabulator Permissions in the dialog Assistent for workersearch in: … the permission name was used for searching only. The marked rights in the tabulator where ignored. Now you can search for specific rights offered in the tabulator too.

Opening a macro containing a processdialog and database with the Workbench

Opening with the Workbench a macro containing values for both a processdialog and any database activity lost the settings for the columns in the tabulator Database.
Opening a database macro with the Workbench filled in the tabulator Endstatements not needed statements

Absents and offlines with overlapping timespans

Previous, an absent and offline containing an overlapping timespan with an existing absent/offline could be inserted in tabulator Absents/Offlines. This had no further effect, but was irritating. Now creating an absent or offline with overlapping timespan is denied with a message.

Substituting supports part time workers

With the new option Daily absents in tabulator Absents the using of part time workers for scheduling processes is supported. With this option part time workers can be used for scheduling processes more effective. For details please see documentation OfficeTalk Business-Process-Management, chapter Absents.

Substitute is extended

With the new option All processtemplates in tabulator Substitutes you can define a substitute for a process from a parallell organisation unit. With this extention the usage of substitutes is made more flexible. For details please see documentation OfficeTalk Business-Process-Management, chapter Substitutes.

Version 4.71

Use a comment for the last statement in a macro

A comment for the last statement in a macro was not possible. The contextmenus Compile and F ormat removed this comment again.

Layout of processes in tasklists with symbols

The layout of the processes in all tasklists with symbols (colored folders) is optimized. Because of ,you have a better overview about the processes in this kind of tasklists.

Display items in Listfield an Combobox of a processdialog with their symbols

In the Workbench for a processdialog with the new option Icon preceeds text in the propertydialogs of the dialogitems Listfield and Combobox the content is preceeded by the associated symbols (Icon). This functionality is supported by the new services withIcons(…), withIcons(…, textWith: …, iconWith: …), withoutIcons(…) and addCombobox(…, type: “Object“) of the systemvariable ScriptDialog. It makes the recognition of many items easier. For details please see documentation OfficeTalk Business-Process-Management, chapter Workbench und OfficeTalk Script, chapter Fieldproperties.

Inputs in tabulator Mail of the Workbenchdialog

Typing in a space into some inputfields in the tabulator Mail of the Workbenchdialog directed the cursor to the beginning of the line. e.g. When typing in “Call “, the cursor jumped back to the beginning of the line.

Working processdialog containing disabled dialogitems with Workbench

Building the macro for a processdialog in the workbench with the button Create did not include the statements to store the content of locked items with processdata.item(…, with: …, in: …)). This is right, but with the exception the item is filled programmaticly within an action block with the statement value(…, put: ). Because of this, the statements to store the content of an item (processdata.item(…, with: …, in: …)) are build without respect to its lock state.

Mandatory Checkbox in processdialog

Setting a Checkbox with the option Mandatory in the Workbech did not behave as mandatory input. As a result the processdialog could be closed with the OK-Button without checking the mandatory Checkbox.

Onlinehelp for dialogitemnames in the Workbench

The onlinehelp of all services using itemnames (e.g. value(…) ) did not contain the groupname of radiobuttons. Because of, the onlinehelp could not be used for e.g. dialog.value(…) to use a radiobutton.

Moving a worker in the Organigrambrowser to another organisation unit

Moving a worker in the Organigrambrowser with the mouse into an other organisation unit seemed to work. But after a restart of OfficeTalk the moved worker was staying in the old organisation unit.

Version 4.70

Creating histories as HTML-file

Creating histories as a HTML-file with the menu File- Create as HTML in dialog History for: <templatename>, opened with the contextmenu History… in tabulator Processtemplates. is executed much faster now. This improvement most takes affect on large histories (> 1000).

New menu View – Life- and Runtimes in historydialog of a processtemplate

With the new menu View – Life- and Runtimes in dialog History for: <templatename>, opened with the contextmenu History… in tabulator Processtemplates. you can swap the displaying of the live- and runtimes of histories. Displaying the live- and runtimes is switched off for large histories (> 1000) by default.
The dialog History for: <templatename> is opened about 20 times faster and the histories, selected with the menu View - Select by... , are displayed after accepting of the selectiondialog about 10 times faster. This improvement most takes affect on large histories (> 1000).

Input Environment in the logindialog

The connectionname for the database in the inputfield Environment of the logindialog is managed not in the common settings anymore, but in the userdefined settings now. This was neccessary for the more automated installation. This change is completely transparent for the user.

Creating an ODBC-Entry for PostgreSQL- and Microsoft SQL-Server

On the first start OfficeTalk the ODBC-Wizard will create the ODBC-Entry for the PostgreSQL- and Microsoft SQL-Server. Manually creating the ODBC-Entry is obsolete now.

Statement Dim- and New for libraries loaded with directive Interface

The onlinehelp for the statements Dim-As and New contained for libraries, whitch where loaded with the directive Interface, no interfaceclasses. Only coclasses (application classes) where contained. To use an interfaceclass, the datatype Object had to be used. Now interfaceclasses can be used in the statements Dim-As and New like coclasses.

Displaying processflow in dialog Processgraph: <name of process>

The label of a stepresult (blue connectionline) is for a better visual effect colored in the color of the connectionline.

Simulating processflow in dialog Processgraph: <name of process>

The simulation of processflow with the menu Simulation – Open und Simulation – Start shows in the second line of a passed stepresult (blue connectionline) the executionsequence, similar to menu Statistic – Executiontimes/paths. The executionsequence shows the sequence of the passed stepresult. If a stepesult is passed more times, the label contains the sequences separated be a colon. e.g. [2,5]

Dialog of onlinehelp for statement Dim-As

Double clicking the category DotNet in the onlinehelp dialog of the statement Dim As resulted in an error message and termination of OfficeTalk, sorry.

Displaying the process in dialog Processgraph: <name of process>

The blue connectionline (Stepresult) to from the rightmost or topmost Step to itself in the processgraph is layouted more better to save space.

Synchronize userlogin of the database with the workerlogin of OfficeTalk

Up to version 4.70 a modified workerlogin in OfficeTalk had to be propagated manually to the database with the administationtool of the database. E.g. A modified login or password had to be actualized manually in the database. Now, accepting the dialog Login and Password, opened with the button Login and Password in the workerdialog, actualizes after an additional questionmessage the login in the database for Oracle-SQL, Micosoft-SQL and PostgreSQL automatically. For the database IBM-DB2 the actualizing must be made manually only.

Extended settings for the view of a processtemplate

In tabulator Processtemplates of the general settings and in the dialog View-Settings of dialog Processgraph: <name of process> the new option Indicate subprocesses is available. The presetting of the option is Yes. Setting the option to No, skips indicating subprocesses of steps with +. Setting the option to No accelerates the open of a processtemplate with steps using many macros.

Exporting worker in Organigrambrowser and processtemplates in tabulator Processtemplates with the contextmenu Export

Exporting a worker with a many times used processtemplate or with a large tasklist with the contextmenu Export in the Organigrambrowser and exporting a processtemplate with the contextmenu Export in the tabulator Processtemplates is accelerated.

Working processtemplate in tabulator Processtemplates with the contextmenu Copy/Paste

Copying a processtemplate in tabulator Processtemplates with the contextmenu Copy and inserting it into another worker with the contextmenu Paste copied the history of the template too. Because of this is dynamic data the history must not be copied with by actions.

Working a worker in the Organigrambrowser with the contextmenu Copy/Paste

Copying a worker in the Organigrambrowser with the contextmenu Copy and inserting it into another worker with the contextmenu Paste copied the tasklist and the history of its processtemplates too. Because of this is dynamic data the history and tasklist must not be copied by such actions.

Presentation of processtemplate in dialog Processgraph: <name of process>

The blue connection lines (stepresults) to a backward step within the same row touched sometimes steps between. Now these connection lines are organized for both presentationtypes (rectangle and circle) in a better way.
The design of the steps is made more better for both presentationtypes (rectangle and circle).

Menu View – Select processcategory in the tasklist

Selecting a processcategory take to long for actualizing the tasklist with the processes of the selected category.

Automaticly positioning of cursor in inputfields of a processdialog

With the new service focus(…, proceed: …) of the systemvariable ScriptDialog you can automaticly position the cursor to the end of the text in a processdialg’s imputfield. This enhances the usibility of processdialog with a presetted inputfield, because for fullfilling the input, the cursor can be automaticly positioned at the end of the text and must not be positioned by manually by hand.

Weeknumbering in datedialog of processdialogs

The dialog for selecting a date in processdialogs, opened with the date button, did not label the weeks with their correct number in any case. This had no further consequences, but the orientation within a month may be more difficult with a bad numbering of the week.

Indicating subprocesses in dialog Processgraph: <name of process>

The starting of one ore more subprocesses in a step is indicated in the dialog Processgraph: <name of process> with the BPMN-Notation + at the affected step block. Clicking with the mouse the + opens the subprocess, similar to the contextmenu Subprocesse.

Starting a process with unsufficient Takeovervisibility

Starting a process, whitch is taken to an organisation unit (Department, Office, Team), because the first step defines this, and the Takevovervisibility was defined unsufficient for the worker, nothing happened. It seemed, that the process was not started, but it was started well and taken to the defined organisation unit.

Contextmenu Create database user in Organigrambrowser using Microsoft SQL-Server

Since version 4.60 the contextmenu Create database user in the Organigrambrowser did on Microsoft SQL-Servers not create for the worker the complete database user. The contextmenu notified the creation of the database user, but it was not created completly. The accessright for the database where missing.

Accessing the OfficeTalk-database by other database clients

To accept the international standard for computersystems (EU-GMP Annex 11) other database clients (e.g. Microsoft-Access) are not able to login to the OfficeTalk database with the same login as used in OfficeTalk anymore. OfficeTalk uses for the login starting with 4.70 a fingerprint as password. This fingerprint is an irreversible encoding of the password. Because of this fingerprint, the same login used in another database client does not work anymore. This modification is compatible back to version 2.00. For accessing a database you can not use the login of a worker, because its password is encoded irreversible. Instead of, you must use a seperate database user. Please read documentation …\JOOPS GmbH\OfficeTalk\Help\ADO.pdf.

Version 4.61 Build 10.14.2010

Importing a processtemplate in tabulator Processtemplates

Importing with the contextmenu Import… in the tabulator Processtemplates a processtemplate, whitch was exported with an older OfficeTalk version was aborted with an error message. Since version 4.61 exports of processtemplates, made with version <= 4.60, where not usable anymore. Sorry for this mistake, but it could is solve very fast !

Version 4.61

Formating a macro containing a call of an unknown service

Formating a macro, whitch uses an unknown service of an Integer variable substituted the unknown service with service *. e.g.
Dim count As Integer
count.xxx was changed by the formater to count.*. Because of services of Integer variables are used very rare, this bad formating was not detected yet.

Removing last step of processtemplate in dialog Processgraph: <name of process>

Removing the last step of a processtemplate in dialog Processgraph: <name of process>, whitch had a succedding link to a higher step was denied with an error message and OfficeTalk ended, sorry,

Requesting selected row and column of a table in a processdialog

With the new service rowAndColumn(…) of the systemvariable ScriptDialog you can request in actionblocks the selected or activated row and column of a table item. With this information you can control column dependent activities. For details please read chapter Control item properties in documentation OfficeTalk Script.

Defining textattribute in processdialogs dynamicly

With the new service emphasize(…, with: …, from: …, to: …) of the systemvariable ScriptDialog you can dynamicly define color and emphasis of texts in dialogitems. For details please read chapter Control item properties in documentation OfficeTalk Script.

Selectiondialog of services of a component loaded with directive Interfaces

The selectiondialog of available services of a component, whitch was loaded with the directive Interface, did not offer the variants of services with optional arguments. e.g. A service with optional arguments was not offered with all its variants. The selectiondialog is opened in the ScriptBrowser or in the Workbench by typing in a space after the dot (e.g. component._).

Import processtemplate with contextmeni Import in tabulator Processtemplates

Importing an allready existing processtemplate with the contextmenu Import in the listfield of the processtemplates imports the different scripts and macros only, if any. After the import is finished, you are informed about this special circumstance.

Conditional statements to disable a dialogitem in tabulator Openstatements of the Workbench

When the tabulator Openstatements contained conditional statements for disabling a dialogitem (IF <condition> Then dialog.disable(…) End If), opening the macro with the Workbench puts the disabling into the properties of the dialogitem too. Building then the macro with the button Build created the disabling twice. First the unconditionally disabling of the properties and second the conditional disabling of the Openstatements.

Inspecting processdata with menu Processdata as tabulator in category Processtemplates and in the tasklist

Not all groups of processdata could be inspected, when opening the processdata with the menu Processdata – As Tabulator, because clicking onto a tabulator did not work. Inspecting all groups was possible with the menu Processdata – As Table only.

New services for better managing dynamic processdatas of a proces

To manag dynamic processdata in a better way, the systemvariable ProcessData is extended by the services in(…), namesIn(…) and valuesIn(…). For details please read chapter ProcessData in documentation OfficeTalk Skript.

New services of the systemvariable FileSystemObject

The systemvariable FileSystemObject supports the new service compileMessages(…). This service is for special purpose only. For details please read chapter FileSystemObject in documentation OfficeTalk Script.
The services readMessages(…) and writeMessages(…) of the systemvariable FileSystemObject are modified, to support 2-bytes charactersets, as used in Japan or in China. This service is for spezial purpose only. For details please read chapter FileSystemObject in documentation OfficeTalk Script.

Working with ActiveX-components loaded with Interface in a macro

ActiveX-components, whitch are loaded with the directive Library, could not execute all services. Some special services where denied with an error message.

Extended Workbench to build macro for a mailactivity

The Workbench supports the new tabulator Mail for building a macro to execute a mail activity. With the tabulator the macro can be configured in any way. For details please read chapter Tabulator Mail in documentation OfficeTalk Business-Process-Management.

Using Logging on platforms with 2-byte encoding

Activating the Logging (Settings, tabulator General, field Logging) was not possible on all platform with a 2-byte encoding (e.g. Chinese). After activation OfficeTalk was ended with an error message and was not startable again. The logging had to be deactivated manually first.

Removing and renaming items of a processdialog with the Workbench

Renaming an item with ist propertydialog or removing an item in a processdialog with the Workbench resulted in ending OfficeTalk with an error message, sorry.

Version 4.60

Extended selection of processhistories

The filterdialog, opened with the menu Filter by…, of the dialog History for: <processname>, opened with the contextmenu History… in the tabulator Processtemplates, contains the two new selections Worker and Step. With theese new selections you can e.g. display the runtime for all selected histories of a specific worker or of a specific step. For details please read chapter select by in OfficeTalk Business-Process-Management.

New button Developmentplatform… in Copyrightdialoh

The new button Developmentplatform… in the Copyrightdialog, opened with the menu Help - About OfficeTalk of the startportal, opens the dialog The Developmentplatform with informations about the used developmentplatform, -version, e.g. This may be helpful for the support.

Using digital signatures in processes on all platforms

With the new services MD5String(...) and MD5File(...) of the systemvariable stepscheduler you can use digital signatures on all platforms without installing additional programs. e.g. Save the digital signature of a file in the processdata and verify the integrity of the file in a later step. For details please read chapter MD5File(…) and MD5String(…) in OfficeTalk Script.

Supporting shortcuts for processdialogs

To support you as keyboardfreak, each item in a processdialog can be a target of a shortcut now. By extensions in the Workbench and in the services of the systemvariable ScriptDialog each item in a processdialog can be defined as a target of a shortcut.
The shortcut character in the label of selectable items (Button, Checkbox, Radiobutton, etc) must be proceeded by a &. In the propertydialog of a Label you prefix the character in its label with & and select in the listfield Shortcut for the target item. For details please read chapter Propertydialog Label and Label Courier in OfficeTalk Business-Process-Management and chapter shortcut(…, for: …) in OfficeTalk Script.

Jump to the inputfield in a tabulator of a processdialog with the TAB-key

Jumping to an inputfield in a tabulator of a processdialog with the TAB key instead with the mouse denied in some rare situations the positioning of the cursor with an error message. This could happen only after the tabulator is leaved to another tabulator before the TAB-key is used.

Changing the Date in a inputfield with spinbuttons

Changing a part of a date with the spinbutton may change the cusors position and with the next click on the spinbutton an unwanted part of the date is modified. e.g.: Switching from September 1. 2010 to August 31. 2010 may modify at the next click an unwanted part of the date (e.g. year instead of the month).

Unfolding the content of a worker in the Function-/Organigrambrowser

Unfolding the content of a worker with the click onto the square in front of its name now leaves the current selection unchanged. This behaviour matches more better to similar windows of the used platform like the KDE-Explorer of the Linux-platform and the File-Explorer of the Windows-platform. Up to now unfolding with the square selected the unfolded worker and opened its address tabulator in the right dialogpart. For details please read chapter Handling of listfields in Generals.

Building a macro for an Oracle database activity with the Workbench

The tabulator Database in the Workbench ignored, when building the macro with the button Build, with the setting database type Oracle SQL-Server and all other settings but Results all given columns. The syntax <columnname> = :<column> was not possible in the input field SQL-Command.

New tabulator Openstatements in the Workbench for a more flexible way to build a macro for a Processdialog

With the new tabulator Openstatements in the Workbench you can specify statements whitch are executed after building the dialog and right before the dialog is opened. With this tabulator you can e.g. fill an items content with your own rules not using the possibilities of the add-statement

Processdialogs without Returnvariable in tabulator Processdialog of the Workbench

Omitting the Returnvariable in the tabulator Processdialog of the Workbench inserted statements of the tabulator Endstatements into the tabulator Startstatements when reopening the macro with the Workbench.

Menu Same as HTLM in tabulator Processtemplates and in dialog History of <Processtemplate>

Some words in the HTML-Export contained the character &, because the word is used in the UI too. And there the character & is the indicator for the shortcut _.

Opening tabulator Processdialog in the Workbench containing a scaled Label

Opening a processdialog with the tabulator Processdialog of the Workbench did not draw the hole labeltext of a Label, if the text was scaled high and the text itself was long.

Scaling of the font of the title of a GroupBox

Defining the scale of the font of a GroupBox’s title only (field Scale in its property dialog or the statement scale(…, by: ….) in the macro) was ignored when the processdialog was used later when scheduling the process.

Defining the scale of the font of the title of a GroupBox to large (field Scale in its property dialog) resulted in overlapping the groupbox’s title with the first item inside the groupbox. Now for the calculation of the GroupBox bounds, the scale of the font of its title is included.

Used font of a Label was lost when its text is changed

Changing in the Workbench the text of a Label in its propertydialog resulted in loosing the font setting of the Label. The font had to be set again.

Scriptdialog is named now Processdialog

The name for dialogs used by the process while scheduling is now Processdialog and not Scriptdialog or userdefined dialog anymore. Because the dialog is used by a process for execution, Processdialog matches the functionality much more. Scriptdialog and userdefined dialog are definitions, oriented on the used internal technology (script and macro).

Opening a macro with manually inserted statements with the Workbench

Statements for writing processdatas with unknown format are ignored by the Workbench when opening the macro and therefore are lost. Now, statements for writing processdatas with an unsupported format are inserted in the tabulator Startstatements or Endstatements when opening the macro. This helps for statements like processdata.item(…, with: <Variable/Expression>, in: …).

Changing the layout of an userdefined dialog in tabulator Scriptdialog of the Workbench

For easier changing the layout of an userdefined dialog (ScriptDialog) in the tabulator Scriptdialog of the Workbench, you can select with the left mousebutton and pressed Shift-key or with a rubberband (selectionband with left mousebutton) a group of dialogitems. For details please read chapter Select dialogitem in the documentation OfficeTalk Business-Process-Management.

Import a processtemplate with the contextmenu Import in the tabulator Processtemplates

Importing a processtemplate with the contextmenu Import removes a same named processtemplate after asking you first, before the import is proceeded. In the past the import was aborted if a same named processtemplate was found. You had to remove the processtemplate with the contextmenu Remove first and then to start the import with the contextmenu Import again. A small change, but small things can make a system easier too !
If you try to import a processtemplate with the contextmenu Import and an identical processtemplate is found, the import is not performed. Two processtemplates are identical, if they have the same settings and the same steps with the same pathes of execution.

Different height of userdefined dialogs (ScriptDialog) while using and while buildung in the Workbench

The height of a userdefined dialog (ScriptDialog) was not exact the same as defined in the workbench in tabulator Scriptdialog. The difference was minimal, but is was. Now the height of a userdefined dialog is exact the same as defined in the workbench in tabulator Scriptdialog.

Moving dialogitem with the mouse in an userdefined dialog (tabulator ScriptDialog) in the Workbench

Moving a dialogitem with the mouse did not work easy. Moving a longer distance the item followed not exactly the moved mouse. This was visible especially moving a Label. Now, moving a dialogitem follows exactly the moved mouse.

Optimized (changed) creation of macro for a userdefined dialog (ScriptDialog) with the Workbench

After closing the dialog with the statement open the content of the dialogitems is not taken (processdata.item(…, with: …, in: ….)) for locked dialogitems anymore. In general this is not necessary, because the content of a locked item can not be changed. For details please read chapter Destination of content in the documentation OfficeTalk Business-Process-Management.

Working items within GroupBox in ScriptDialog in the Workbench

The propertydialog of a dialogitem whitch was contained within a GroupBox, could be opened in the listfield of the workbenchdialog only. Double clicking or the right button opened the propertydialog of the GroupBox only. Now dialogitems, whitch are contained within a GroupBox, can be worked like all other dialogitems.

Contextmenu Callgraph in macro listfield of the separate opened Scriptbrowserdialog with the startportal Function-/Organigrambrowser

Using the startportal Function-/Organigrambrowser and opening the Scriptbrowser with the button >> of the actiondialog in a separate dialog, the contextmenu Callgraph opened the graph in the underlying right dialogpart of the Function-/Organigrambrowser. Because of the graph was not fully visible first, the graph is opened now in a separate dialog on top of all other opened dialogs.

Details of a process in the tasklist with the startportal Function-/Organigrambrowser

With the startportal Function-/Organigrambrowser the last sortorder of the tasklist was not reloaded after closing a detail (contextmenu History, Processtate, Processdata, etc.) with the menu Back. The sortorder had to be reloaded manually. Now the last sortorder is reloaded automaticly on closing the detail with the menu Back.

New Menü Extra of the tasklist

With the new menu Extra – Maintenance you can maintenance processes in the personal tasklist with the maintenance assistant. You can remove or repair incomplete processes and repair wrong assigned processes. Incomplete processes can not be worked nor terminated in the tasklist. In general an incomplete process is a very rare result of a faulty processflow. Bad assigned processes are responsible for a longer opentime of the Tasklist as Browser only. For details please read Maintenance in documentation OfficeTalk Workflow.

Input of variable in tabulator Arguments und Variables in the Workbench

The input of the classname is in both tabulators, like in all other places of source input, not case sensitive anymore.

für die Variable unterscheidet in den beiden Registern, wie an allen anderen Stellen der Quelltexteingabe, nicht mehr Groß-Kleinschreibung.

Inputfield Expression in propertydialog of listtyped dialogitems in the Workbench

The inputfield Expression in the propertydialog of listtyped dialogitems (e.g. List, Combobox, etc.) is now tested for its correct syntax when the button Accept is pressed. If the input is not a syntactical correct expression, the detected error is inserted at the errorposition and the propertied is not closed.

Extension of all propertydialogs in tabulator Scriptdialog in the Workbench

All propertydialogs with input for an expression (e.g. Scriptdialogtitle, Source… and Target…, etc.) tests the given expression for syntaxerrors before the dialog is closed with the Accept button. If a syntaxerror is detected, the errortext is inserted at the errorposition and the propertydialog is not closed.

Leave the Workbench without changing the userdefined dialog (ScriptDialog)

Leaving the workbenchdialog with the button Build with an unchanged userdefined dialog displayed the source of the macro as modified, but the toolbarbutton for compiling was grayed. The source could be compiled with the contextmenu Compile only.

Using the dialogitem Label with settings for color and font in a userdefined dialog (ScriptDialog) and in the Workbench

A Label’s font was visualized different in the Workbench and in the userdefined dialog (ScriptDialog) if it was using both a font and a color.

in einem benutzerdefinierten Dialog sowohl eine Schriftart, als auch eine Farbe verwendete, wurde die Schriftart des Bezeichners in der Workbench und im Dialog unterschiedlich dargestellt.

Setting the defaultfont with different scalingfactor in the Workbench for a item in a userdefined dialog

The defaultfont could not be set in the Workbench with the propertydialog of the dialogitem of a userdefined dialog with a different scalingfactor. The default scalingfactor was used instead of,

Working dialogitem Label of a userdefined dialog (ScriptDialog) in the Workbench

After working a Label of a userdefined dialog (ScriptDialog) with its propertydialog, the horizontal bounds of the Label where marked to large. This had no further effects, but was wrong in general !

Settings for font and scalingfactor of dialogitem Combobox in userdefined dialogs

The settings for the font and scalingfactor (service font(…, use: …, scale: …) of systemobject ScriptDialog) to be used in a Combobox was used for the selected part only. Now the settings are used for both the selected part and the selectionlist part.

Propertydialog of the dialogitems Listfield, Combobox and Table in the Workbench

On close of the peopertydialog the content of the input field Choices of the tree dialogitems was not tested for syntax. As a result you got a syntaxerror when compiling the macro at the last step, if the content of the field Choices was not a valid expression.

Version 4.51 Build 07.19.2010

Variable font und variable size for items in a userdefined dialog (ScriptDialog)

For a smarter design of the userdefined dialogs (ScriptDialog) you can specify the font to be used for labels and textitems and scale the label an the text in textitems. Scaling means increasing and decreasing the text size. For details please read chapter Workbench in documentation OfficeTalk Business-Process-Management und the chapters scale(…, by: ….) and font(…, use: ….) in documentation OfficeTalk Skript.

Filtered tasklist by date typ containing an incomplete process

If a tasklist was filtered by a kind of date with the menu View – Filter by and it contained an incomplete task, OfficeTalk was ended with an error message. Such an incomplete task was created in an earlier version or was created by an incorrect handling.

Version 4.51

New webservice TakeoverProcesses

The new webservice TakeoverProcesses gets the processes in the takeoverlist of an active worker (Desk, Machine). Use the new file OfficeTalk.wsdl for it ! For details please read chapter Webservices in the documentation OfficeTalk Workflow.

Onlinehelp for Return while working a macro in Scriptbrowserdialog

The onlinehelp for Return while working a macro in the Scriptbrowserdialog has inserted the selected Stepresult behind Return without space, when the onlinehelp was not opened with Return “.

Contextmenu Hide in dialog Callgraph start at macro: <macroname>

The contextmenu Hide of a macro in the dialog Callgraph start at macro: <macroname>, opened with the contextmenu Callgraph in the listfield of macros of the Scriptbrowser did hide the first call level of macros only. The succeeding levels remained visible in the graph, but without their connections.

Export of workers was not possible

Since version 4.50 exporting of workers with the contextmenu Export… in all dialogs of organigrams was not possible, because the menu was allways grayed, sorry.

Database server IBM DB2 Version 9 is supported

The database server IBM-DB2 Version 9 is supported now. Please read documentation OfficeTalk Installation, chapter DB2 Database server.

Changed syntax of the functions Shell and Shell Wait in macro

The last argument in the functions is not optional anymore. If a program shall be started without arguments, use an empty string (““) as the last argument. Complete in your macros these both functions with the last argument. If you are not shure, wether Shell or Shell Wait is used in a macro, you can search for the usings with the menu Work – Search.

Onlinehelp for systemvariable Error did not work

The onlinehelp for the systemvariable Error did not offer the available services (error. + space). Now it works again.

Wrong solutions from onlinehelp while working a macro

Under special circumstances the onlinehelp gave unwanted solutions while typing in a macro. e.g. Typing in Return Call the onlinehelp opened the possible variants of Return instead of the useable macros. Such a missinterpretation happened, when two ore more onlinehelp items where given in a single textline.

Statement Shell and Shell Wait in macro raises an exception on error

The statement Shell and Shell Wait raises an exception, if the executed command fails. Please encapsulate Shell and Shell into Try-Chatch, if the execution is not save. For details please read the chapter Shell Wait in OfficeTalk Script.

Version 4.50

Using digital signatures in prozesses on Windows platforms

On Windows platforms the program md5.exe is installed in the directory …\JOOPOS GmbH\OfficeTalk\Bin. On Linux platforms the pendant is md5sum and is part of the operating system. With this program you can encode within a processflow strings and files with the MD5-Algorythm. With md5.exe you can use digitale signatures within a processflow. e.g. Save the digital signature of a file in the processdata and test in a later step wether the file is unchanged. The files md5.html, rfc1321.html und rfc1321.txt in the same directory contains the description of md5.exe. A macro for creating the digital signature of a file may look like:

MD5 (filename As String)
Dim encoded As String

encoded = Shell Wait Encoding oem, CurDir, "\..” & ".\Bin\md5.exe" " –n ” & filename"
Retrun encoded

Extended functions Shell and Shell Wait in macro

The functions Shell and Shell Wait are extended by the argument Encoding for supporting programs, who return their result not with Unicode, but with OEM characterset.

Startportal restricted Browser and full Bowser on all Windows plattforms

OfficeTalk could not be started, if the Startportal in the tabulator Gerneral of the settings was set to restricted Browser or full Bowser and the Microsoft InternetExplorer was not installed correctly. An entry in the Windows-Registry-had to be changed manually, to make OfficeTalk working. Now, the startportal Dialog is used automaticly, if the startportal restricted Browser or full Bowser can not be used.

New menu Extra – Authorize wizard in startportal

The new menuitem opens the wizard for changing the extended permissions in the Authorize tabulator. With this menuitem you can easier change the extended permissions in lager organigrams. For details please read chapter Authorize wizard in the documentation OfficeTalk Business-Process-Management.

New contextmenu Reset password resets the password of a worker

If the password of a worker’s login is lost, you can reset it with the contextmenu Reset password in the OrganigramBrowser. As a prerequisite the email address of the worker must be given. The contextmenu resets the password to a random value and sends this new password by email to the worker.

Changing the mail address of a worker

To be more secure, the worker’s mail address can be change by himself only. This means, the worker must be logged in, to change his mail address.

New service identify of the systemvariable worker

With the new service identify you can enforce an identification of a worker within a macro. The service opens an identification dialog where the user must give the login. The identification dialog ends with True, if the login matches with the worker’s login, else it ends with False.

Tabulator Resource im Assistent für die Bearbeitersuche

Searching for a resource by costbase is possible now. To reset a selected costbase, use the new option No Option in the tabulator.

Extended wizard for searching workers

The wizard for searching workers is extended with the tabulators Visibility and Authorize. With these new tabulators you can search for workers by visibility- and authorizerules.

New authorizes for passive workers (Department, Office and Team)

The tabulator Authorize of a passive worker contains with the new option Do not change worker’s content and Do not change organigram possible restrictions of organisational work for a passive worker. A logged in passive worker is not allowed to change subordinated workers with the option Do not change worker’s content. A logged in passive worker is not allowed to create new workers, remove workers and move workers with the option Do not change organigram.
The first start of the version 4.50 must be done with the login of the very first start, because some database tables must be extended. This login is named OfficeTalk, if it is not changed in the meantime.

Security rules for changing a login are changed

To enshure, that an authorized worker is able to change the login of a worker only, the current password must be given. This rule is valid for all workers including the company !

Not more workers with same login in an organisation unit

An organisation unit (Department, Office, Team) must not contain more workers with the same login. The dialog for defining a login, started with the button Login and Password… in the workerdialog, ensure this rule.

Modified process for removing an entity (worker, script, macro, resource)

The contextmenu Remove in the Organigramm-, Scriptbrowser- and Resource-Dialogs is not grayed anymore, when the entity must not be removed. Removing such an entity, whitch is referenced by another entity, opens a notifyer. Answering the notifyer Yes opens the references of the to be removed entity. e.g. A macro is used with the Call-statement in other macros. A worker is used in the tabuator Schedulingoptions of a Step in a processtemplate.

Sort tasklist as table by steps

Sorting the personal tasklist in the tasklist dialog by steps with clicking the columnheader Step aborted OfficeTalk with an error message, sorry.

Excelerated Tasklist as table

The tasklist as table (Settings: Tasks – Processes in table) is opened with the factor 2 faster now by the menu Processes – Open tasklist. You can see this especially with tasklist containing many processes (> 500).

Extended Tasklist as browser

The grayed groupfolders in the Tasklist as Browser show after the groupname (Personal Tasklist or name of the worker) the count of the visible processes in the group and the count with the menu View-Select processes by folded out processes. With this extension you see more information especially in tasklists of a passive worker (Company, Department, Office, Team).

New service refresh of the systemvariable process

With the new service refresh a process is synchronized with its database content. The service should be used for processes of other workers only to actualize the internal cache.

Version 4.40

Contextmenu History, Processdata, etc. in the tasklist with activated taskarea using startportal Function-/Organigrambrowser

Using the startportal Function-/Organigrambrowser and selecting a contextmenü with a selected taskarea in the tasklist, whitch switched the dialog (e.g. History, Processdata, etc.), aborted OfficeTalk after selecting the menu File – Back in the switched dialog with an error message.

History of process execution in an activated taskarea

The history of the process execution within an activated taskarea contains the real logged in worker, instead of the worker of the taskarea.

Wizard for searching worker extended with Taskareas

The wizard for searching a worker, started with the menu Work – Search in the Function-/Organigrambrowser and in Ogranigramdialog, supports now searching for taskareas with the tabulator Taskareas.

New service workingWorker of the systemvariable stepscheduler

The new service workingWorker of the systemvariable stepscheduler answers the logged in and real working worker. In general this is the same as the systemvariable worker. But activating a taskarea worker will be the worker of the activated taskarea.

Asynchron waiting of processes

With the schedulingoption Wait for started processes in tabulator Schedulingoptions of the step’s dialog and the services asynchronWaitFor(…) of the systemobject process an asynchrony waiting of a process can be defined. Asynchron waiting means, that the scheduling is proceeded after the service asynchronWaitFor(…) and stops at the step with the scheduling option Wait for started processes. After the processes, for whitch the process is waiting, are ended, the scheduling of the process can be proceeded in a normal way.
The first start of the version 4.40 must be done with the login of the very first start, because some database tables must be extended. This login is named OfficeTalk, if it is not changed in the meantime.

Version 4.33 Build 06.12.2010

New symbols for steps and actions

In the listitem Symbol of the tabulator Schedulingoptions, Start, User- and Endactions of the step’s dialog new symbols for the visual presentation are available.

Version 4.33 Build 06.11.2010

Contextmenu Historie in listfield Processtemplates of the tasklist and in dialog Start new process

Displaying the processtemplates in the listfield Processtemplates with the owner (menu View – Processtemplates – With Owner in dialog of the tasklist) ended OfficeTalk with an error message when the contextmenu History was choosen for a template, sorry.

Sequence of services startDate(…, time: …), defineStartDate and undefineStartDate in scriptmacro

The startdate of a next step, defined with the services startDate(…, time: …) and defineStartDate, could not be undone with the service undefineStartDate. The defined startdate was used instead of the original startdate from the processtemplate. (All services are services of the systemobject stepscheduler.)

Sequence of execution of New-statement and Interface-directive in scriptmacro

Execution in macro the statement New with a .NET- class within a communication library (directive Library) before the directive Interface resulted in denying succeeding Interface-directives with the hint Invalid library….

Version 4.33 Build 06.09.2010

Changed servicename in systemobject process

The service processByID(…) in the systemobject process is renamed to processByIdentity(…). For compatibility the old name exist to the next mainversion.

Onlinehelp for services of the systemobjects Desk, Office, Department, Team and Company

The selectiondialog of the onlinehelp for the services of the named systemobjects did not contain all possible services.

Contextmenu Run in sourcefield of the scriptbrowser

With the contextmenu Run a single statement could be executed only. Selecting more statements resulted in the error message Internal error while…. And the macro had to be started with its signature (name and possible arguments).

Version 4.33

Onlinehelp for services of the systemobject worker

The selectiondialog of the onlinehelp for services of the systemobject worker did not contain the service children, but the service was supported. Now the services in contained in the selectiondialog of the onlinehelp.

Entries in the selectionfield Textgroup of the addressdialog

The entries in the selectionfield Textgroup of the addressdialog of the worker was proceeded by [ from the INI-file. But a textgroup must be saved without this [. Now the entries are not proceeded by [ anymore.

Using the directive Assembly before the directive Interface

Executing in a macro the directive Assembly first before executing the directive Interface, resulted in unsable directive statement Interface. Inserting in the workbench in tabulator Assemblies an assembly first, denied inserting an Interfaces in the tabulator Interfaces.

Emergency exit of tasklist

The emergency exit of the tasklist (CTRL+ALT+SHIFT) did not work in the startportal Function/Organigrambrowser.

Contextmenu Format in Scriptbrowser and statement addDoubleAction

The contextmenu Format of the sourcetext field in the scriptbrowsers did no format for the block in the statement addDoubleAction.

Contextmenu History of finished processes in the tasklist

The contextmenu History in the listfield Processtemplates of the tasklist is usable for all contained processtemplates. With this contextmenu the worker can open the history of finished processes for processtemplates within this listfield.

Starting a new process with setting tasklist in browserformat

When the tasklist in browserformat was used, starting a new process with where the current worker for the first step was defined, the started process was not displayed in the personal tasklist. The personal tasklist had to be closed and opened to show the started process and to schedule its first step.

Execution time of the scriptmacro is accelerated

The execution time of a macro is made dramaticly faster. Especially macros with more variables and variables whitch are originated in the directive Assembly and Interface are made much faster.

Opening macro of a scriptdialog with a colored item with the Workbench

Choosing the tabulator Scriptdialog in the Workbench for a macro with an colored item resulted in an error message and OfficeTalk was ended sporadicly, sorry.

Switching login with setting Tasklist as Browser

Under rare performance conditions switching to a new login with second clicking on the Takeoverlist in the tasklist to fast resulted in an error message and OfficeTalk was ended.

Using directive Assembly with missing .NET-Framework

Using the directive Assembly with missing or wrong installed Microsoft .NET-Framework resulted in an error message and termination of OfficeTalk, sorry.

Onlinehelp for directive Assembly in Scriptmacro

The directive Assembly supports now while writing a macro an onlinehelp like the other directives. For details please read chapter Onlinehelp of directive Assembly and Tabulator Assemblies in documentation OfficeTalk Business-Process-Management.

Dialog Available Classes, category Assemblies on Windows-Platforms

The dialog Available Classes of the onlinehelp for Dim-As and New-statements contains each Assembly in a category of each own within the category Assembly. In the past the classes of all assemblies where contained in the category Assemblies without an additional subcategory. Because of, finding a class within more loaded assemblies was a little bit difficult

Version 4.32

Dynamic integration of DotNET-Systems in a process execution on Windows-Platforms

With the tabulator Assemblies of the Workbench and the new directive Assemblies you can integrate DotNET-System dynamical in the execution of a process without using a communication library. With Assemblies you can integrate and control all systems, build with the Microsoft-Technology .NET, in the processflow. For details please read chapter Tabulator Assemblies in the documentation OfficeTalk Business-Process-Management and chapter Assemblies in the documentation OfficeTalk Skript. Using dynamic DotNET-Integration is supported on Windows-Platforms only.

DotNET-Class Calendar in selectiondialog Available Classes

In the selection dialog Available Classes of the onlinehelp for the Dim-As-statement the class Calendar was contained in the group DotNET-System-Globalization. But this class is not usable in a macro. The statement New with this class resulted in an error message. Therefore this class in not contained anymore in the group DotNET-System-Globalization.

Executing a selected part of a macro in the SkriptBrowser

When the result of the execution of a selected part of a macro was not a variable, OfficeTalk ended with an error message, sorry. An example of such an ending , was the execution of a selected part of a macro with a Halt-statement as the last statement.

Skipped set-services in the selectiondialog of the onlinehelp for an interface

In the selectiondialog of the onlinehelp for services on an Interfaces the get-service was skipped when a same named set-service was available.

Version 4.31 Build 05.07.2010

Extended tabulator Interfaces in the workbenchdialog

The tabulator Interfaces in the workbenchdialog provides the button Search…. With it you can search similar to the tabulator Libraries the required interface. The selectiondialog for interfaces is opened like in the onlinehelp for the statement Interface.

Onlinehelp for statement Interface

The selectiondialog of the onlinehelp for a required interface did not insert an interface with missing programversion independent ID. Such an interface was contained within the list, but not accepted for selection. The interface Application in Microsoft Access 9.0 Object Library is such an example.

New menuitem Interfaceservices… in debuggerdialog

With the new menuitem Interfaceservices… in the debuggerdialog you can display the services of an interface obtained by the statement Interface (Coclass), or obtained by a service of an interface (Dispatchinterface). This is the only one way to get the services of a Dispatchinterface.

Firststart using Microsoft- or PostgreSQL-databaseserver with different environmentname on Windows-platforms

OfficeTalk stopped the database creation with the message ODBC entry is not found… when using Microsoft or PostgreSQL database server with other environmentname than recommended (OfficeTalk or PostgreSQL) for the ODBC-entry.

Version 4.31

Dynamic integration of systems in a process execution on Windows-Platforms

With the tabulator Interfaces of the Workbench and the new directive Library you can integrate extern system dynamical in the execution of a process without using a communication library. As a prerequisite the extern system must support automatisation. The onlinehelp for serives is available for the interface of the statement Interface only. For all other interfaces no onlinehelp of services is available. For details please read chapter Tabulator Interfaces in the documentation OfficeTalk Business-Process-Management and chapter Interfaces in the documentation OfficeTalk Skript. Using dynamic integration is supported on Windows-Platforms only.

Integration of Microsoft Excel in processes execution

To integrate an control Microsoft Excel in process execution the communication library Microsoft Excel Small.pcl is contained in the distribution. Functions for filling out worksheets are supported by the library.

Onlinehelp in tabulatorr Endstatements and Return of the Workbench

In the inputfield Statements of the tabulator Endstatements and in the inputfield Expression of the tabulator Return the onlinehelp did not offer the available dialogitems for the expression after typing in the first “ (e.g. .value(”).

Version 4.30 Build 04.19.2010

Move dialogitem Groupbox in tabulator Scriptdialog of the Workbench with the mouse

Moving a dialogitem Groupbox in tabulator Scriptdialog of the Workbench with the mouse resulted in some obscure visual effects, because the size and position of a Groupbox is defined by its contained items. Now moving a Groupbox with the mouse is not possible anymore.

Coloring and emphasis for dialogitem with labeltext in tabulator Scriptdialog in Workbench are lost

Changing in tabulator Scriptdialog the labeltext of an item Label, Groupbox, Actionbutton, Checkmark or Optionfield removed an used coloring and emphasis. To reactivate the used coloring and emphasis the tabulator must be changed shortly. Coloring and emphasis are not lost anymore on changing the labeltext.

Label in SkriptDialog within the Workbench on Linux platforms

Within the Workbench a Label was drawn in the ScriptDialog with a white border.

The Workbench and dialogitem Label on Linux-Platforms

Inserting in the Workbench with the tabulator ScriptDialog an item Label in an userdefined dialog ended OffieTalk with an error message, sorry. Only Linux-Platforms where affected !

Inputfield Keyname in propertydialog of Label in the Workbench

The inputfield Keyname in the propertydialog of a Label gives you a selection of all names within the installed file for labelnames. This makes its easier to define a label to be used, if a labelname-file exist. Because all names of all groups are offered, you must know the name without seeing the group. For many groups you can open with the button >> a selectiondialog. In this dialog you can see the groups and their names. For details please read chapter Propertydialog Label and Label Courier in OfficeTalk Business-Process-Management.

Version 4.30 Build 04.14.2010

Moving a macro from one script to another script

You can move a macro from one script to another script with changing all Call-statements in other macros using the moved macro. Press in the Scriptbrowserdioalog the macro in the right listfield and drag it to the script in the left listfield. You must accept to move the macro, if a macro has to be changed and is owned by another worker.

Wrong column name in table adresse

The column labelgroup in the table adresse was named wrong. Because of OfficeTalk ended with an error message after starting, sorry.

Contextmenu Export in Organigrambrowserdialog

Using the contextmen Export… in the left listfield, the organigramm, within the organigrambrowserdialog resulted in some situations in an error message and OfficeTalk was ended, sorry.

Version 4.30 Build 04.10.2010

Systemobject Resource is in Scriptmacro accessible

The systemobject Resource is available in a macro directly for reading functionality to make visualisation of processcosts in a userdefined dialog more easier. Additionaly the cost of a consumed resource can be requested. For this, in the systemvariable stepscheduler the new service resource(…) is available. For details please read chapters Resource and stepscheduler in OfficeTalk Skript.

New service asJSON(…) of Systemvariable HTTPClient

To work with webservers, whitch uses JSON for encoding/decoding data, the service asJSON(…) is added. This service can be used to encode any data to a JSON-String. For details please read chapter HTTPClient in OfficeTalk Skript.

Version 4.30 Build 04.06.2010

Assigning a String to an Arrays in a macro

In rare situations after assigning an Array to a String (e.g. myString = myArray) the string was not assigned. Because of this type of assignement in not really practical, it was not recognized yet.

Supporting webserver with answer in JSON format

OfficeTalk supports now webservers, whitch answers to a HTTP-request not with XML- but with JSON-data. (see chapter WSDLClient in OfficeTalk Script). OfficeTalk recognizes this case by itself and handles JSON answers within the services of the systemvariable WSDLClient in the right way. The well known CRM-System vtiger answer JSON data for example.

Update to version 4.30 with using the server for Oracle- or DB2-database

While updating to version 4.30 the new tables HISTORYPROCESSDATAENTRY and HISTORYPROCESSDATAITEM where not created automaticly. Because of and an error message from the database was opened when starting OfficeTalk.

Version 4.30

New contextemenu Render hirarchy in Tabulator Processtemplates

The listfeld of the processtemplates in the tabulator Processtemplates contains the new contextmenu Render hierarchy. With this menuitem all processtemplated, whitch call one ore more subprocesses are emphasizes with a special hirarchy picture. And you can see the processtemplate available for the HirarchyBrowser. On large processtemplates this can take some time. For details please read chapter Processtemplates in documentation OfficeTalk Business-Process-Management.

New menu Extra – Unuses macros in Startportaldialog

The new menu Unused macros scans the macros in the logged in worker in and all its subordinated workers for using. In the proceeded dialog all macros are listed, whitch are not used in the analyzed workers not as startmacro nor by a Call-statement. Double clicking a macro within the list jumps to this macro.

. im angemeldeten Bearbeiter und seinen untergeordneten Bearbeitern alle darin enthaltenen Makros auf Verwendung. Makros, die von niemandem verwendet werden, weder als Startmakro noch durch eine Call-Anweisung, werden im anschließenden Dialog Nicht verwendete Makros aufgeführt. Ein Mausklick auf einen Eintrag darin springt zum Makro.

New services of systemvariable ScriptDialolg in conjunction with Labelgroup

The systemvariable ScriptDialog supports the new services labelGroup, labelGroup(…), label(…, ifNone: …) and label(…). This services in conjunction with Labelgroup can control userdefined dialogs more flexible for each using worker. For details please read the chapters labelGroup, labelGroup() and label() in OfficeTalk Script.

New inputfield Labelgroup in adresstabulator of Desk and Machine

The adresstabulator of Desk and Machine supports the new inputfield Labelgroup. In conjunction with the inputfield Key in the propertydialog for a label the text for a label in the userdefined dialog is defined. The labelgroup of an organisation unit is responsible for all subordinated workers without labelgroup. The text is stored in the file named ScriptLabels.ini. The key defines the entry in the group named with Labelgroup. With Labelgroup you can adopt the labels of a userdefined dialog easy to the rules of a usergroup within the OfficeTalk workers. For details please read chapter Adress and Propertydialog of Label in OfficeTalk Business-Process-Management.

New service processByID of the systemvariable process

With the new service processByID(…) you can request a process with the given identity. This can be a process owned by another worker !.

History and processdata of an active process

In the dialog of the processhistory, opened with the contextmenu History… for the selected process in the tasklist, you can open with the button right the processdata similar to the contextmenu Processdata… in the tasklist.

New service inputItems of the systemvariable ScriptDialog

For generic working with userdefined dialogs ScriptDialog supports the new service inputItems. The service gets the names of all input items in a userdefined dialog. For details please read chapter inputItems of the documentation OfficeTalk Script.

Storing the result of the content ofd a dialogitem

To store the content of a dialogitem the field Expression of the propertydialog for an dialogitem within the Workbench can contain a complex expression too. e.g.: dialog.value(“asd“).identity. With this extension writing separate lines is not needed anymore.

Table with empty column in an userdefined dialog

To display an empty column in a table not with text ‚Null’, the column had to be filled with an empty string first. Now empty columns in a table are displayed really empty.

Running OfficeTalk on slow machines

Using the contextmenu in dialog Processgraph: <name of process> und switching the tabulator from the same dialog to another category finished OfficeTalk on slow machines sometimes with a diagnostic message.

Keyboardcontrol in textfields

A textfield is leaved with the key Tab to equalize the using of textfields with the other input fields. The description of a step in tabulator Description of the stepdialog, the propertydialog for an action in the workbench are such textfields. In theese fields use the key CTRL+Tab to insert a tabulator. The only one exception of this rule is the textfield for the source in the ScriptBrowserdialog. In this field you use the key CTRL+Tab to leave the field.

Version 4.24

Working with userdefined dialogs contaning a tabled item

Working with a userdefined dialog containing a tabled dialogitem (e.g. Table) is optimized. This is expecially seen when such a dialog is opened and its tabled item contains 1000 ore more items.

Importing a processtemplate or a worker from an evaluation version

Importing a processtemplate or a worker from an evaluation version into a production version was denied with an error message, because of using data from an evaluation version for a production version was not planned.

Selecting an optional Action while scheduling a process

Selecting an optional Action while scheduling a process in dialog Schedule step <stepname> ended OfficeTalk since version 4.23 with an errormessage, sorry.

Installation with using database PostgreSQL or Oracle

Since version 4.23 the first start of OfficeTalk was ended with an errormessage („…can only store characters…“), using the database PostgreSQL or Oracle.

Version 4.23 Build 03.18.2010

Contextmenu Schedulingoptions of the Stepp in dialog Processgraph: <name of process>

Since version 4.23 using the contextmenu Symbol or Worker in the contextmenu Schedulingoptions of a step resulted in an error message and OfficeTalk was terminated, sorry.

Version 4.23 Build 03.17.2010

Running outside of MEZ-timezones

For the times in the history the MEZ timezone was used instead of the local timezone. The funtion Time within a macro answered a time of the MEZ-timezone instead of the local timezone.

New service directory(…, :title: …) of the systemvariable FileDialog

With the new service directory(…, title: …) of the systemvariable FileDialog you can request in opposite to the other services a selection of a directory only. For details please read chapter FileDialog in documentation OfficeTalk Script.

Using the service send() of the systemvariable Mail in macro

Since version 4.23 using the service send() of the systemvariable Mail in a macro resulted in the error message “This message is not a propper…“ and the mail was not sent, sorry.

Changing the name of aSkript or a Macro in Scriptbrowserdialog

The contextmenu Rename… in the listfield of the Scripts did not accept changing the case of a name. e.g. Changing the name from Customerorder to CustomerOrder was not accepted.
Changing the case of the name of a macro with the contextmenu Compile… was not accepted. e.g. Changing the macroname from Gutsorder(…) to GutsOrder (…) was not accepted.

Technically the case of the name of a script and a macro is not required for processing. But for more easier readness the case of the name of a script and a macro may be important. Because of, changing the name of the name of a script and a macro, the case is taken into respect.

Selecting the datatype SQLString in the selectiondialog of the onlinehelp for a variabledeclaration

In the selectiondialog of the onlinehelp for a variabledeclaration (Dim xx As yyy) the datatype SQLString was contained in the group/namespace Scripting. Because of SQLString is a base datatype like the others (String, Integer, Long, usw), it is not anymore contained in the group Scripting, but beside the other base datatypes after String.

Version 4.23 Build 03.11.2010

Tabulator Common Processtemplates in startportal Function/OrganigramBrowser

A read only processtemplate, opened in the tabulator Common Processtemplates was modifiable after a step was opened and closed. But modifying a processtemplate within the tabulator Common Processtemplates is not allowed !

Version 4.23 Build 03.09.2010

Using the Worbench with startportal Function/OrganigramBrowser

The button Create in the workbenchdialog did not create a macro since version 4.22. The button Create created a macro with the startportal Dialog only as documented.

New service of the systemvariable FileSystemObject

The systemvariable FileSystemObject supports for special tasks the new services readMessages(…) and writeMessages(…, to: …). For details please read chapter FileSystemObject of the documentation OfficeTalk Skript.

New service of the systemvariable stepscheduler

With the service applicationFor(…) you can get a application, responsible for working with the given file. On Windows-platforms this association is activated in general. On Linux-platforms this service is usefull for the function Shell. For details please read chapter applicationFor(…) of the documentation OfficeTalk Script.

Changing the worker in the tabulators Visibility, Authorize and Adoptvisibility

Changing the worker of the option up to Organisation Unit in theese tabulators with a worker was not adopted completely. After restarting OfficeTalk the given worker was missing.

Changing the worker in tabulator Schedulingoptions of the step

Changing the worker in Step is scheduled by in this tabulator with a worker was not a adopted completely. After restarting OfficeTalk the given worker was missing.

Version 4.23

Process in tasklist with empty column Startdate and Step

In rare situations the columns Startdate and Step of a process in the tasklist was empty, because the process did not know its step next to schedule. Now these processes are corrected automaticly on opening the tasklist.

Tasklist in browserformat extended

The tasklist in browserformat is able to show directly the processdata of a selected process. Because of, the contextmenu View-Processdata must not be used anymore to see the processdata of a process when using the tasklist in browserformat. For details please read chapter Dialogfield Processdata in documentation OfficeTalk Workflow.

OfficeTalk uses the new systembase 7.7

Starting with this build OfficeTalk uses the version 7.7 of the systembase. This is a system notification for history only, and not relevant for all the OfficeTalk-users.

Contextmenu Delegate/Change in the tasklist’s dialog

In rare situations OfficeTalk ended with an error message chooseing the contextmenu Delegate/Change in the tasklist when the setting for the tasks was set to use the browserformat for tasklists and the left and right mouse button was clicked within short interval.

Version 4.22 Build 02.21.2010

Contextmenu New –Stepresult in dialog Processgraph: <name of process>

Inserting a stepresult and connected step with the contextmenu New –Stepresult of the Step, the new features, described in “New action or new result in dialog Step: <name of step>” and “Using of the Workbench while working a step”, are available.

Version 4.22

New action or new result in dialog Step: <name of step>

Typing in a new action or a new result in the dialog of the step and choosing another tabulator or the menu Save or Save and close without pressing the button New first, forgot the typed in item without any notification. In these cases you are informed now with a message and you get the chance to add the new item with the button New first.

Localisation for other countries

OfficeTalk is for the most countries localized. This means the country specific format of dates, times and currencies is used in all dialogs and outputs.

Using of the Workbench while working a step

While working a step in a processtemplate the using of the Workbench was not possible because of technical restrictions. The toolbar item for the Workbench and the contextmenu Workbench… in the listfield of the macros was grayed. It the practical work the process of the work with a processtemplate had to be interrupted for creating a macro for an action of the process with the Workbench. Now the workbench can be used in any situation without restrictions and the process of working a template must not be interrupted anymore.

Version 4.21

Not allowed keyboard shortcuts in input fields

Some keyboard shortcuts are reserved for the development system and therefore reserved. Typing in such a shortcut ended OfficeTalk with an error message.

Menu File –Save as HTML in dialog History for: <name of process>

The HTML-Export of the histories of processexecution, opened with the menu File – Save as HTML in dialog History for <name of process>, contains the used processdata after the last executed step. The dialog of histories for a process is opened with the contextmenu History... in the tabulator Processtemplates.

Delegation of a process with missing rights

Ending a step and delegating the process to a worker for the execution of the next step, as defined in the template, leaved the process at the current worker, if the worker of the next step was missing required rights. This could happen, when rights in a worker where removed after assigning the worker to a step of a process. Now do disturb not the planned execution path, the process is delegated to the worker in any case. The worker’s tasklist contains the delegated task, but then worker can schedule the task only after he has been assigned the removed rights.

Color for a groupbox in a userdefined dialog (ScriptDialog)

Using a color for a groupbox in an userdefined dialog (ScriptDialog) used the color for the background of the text instead for the text itself.

Remove the color for an item in a userdefined dialog (ScriptDialog)

To remove the selected color for an item in an userdefined dialog (ScriptDialog), the statement color(…) had to be removed by hand in the macro. Now, the combobox for selecting the color has the first item Standard for removing the color.

Version 4.20 Build 01.29.2010

Searching for worker with the search wizard

The given values in the comboboxes of the tabulators Rights, Substitutes, Resources and Processtemplates in the dialog Wizard for finding a worker in: <name of worker> contains now items whitch exist within the hierarchy of the worker and not items outside the hirarchy of the worker too. Because searching for a given item existing outside the hirarchy did not find any worker, whitch is right, but will the user suprise.

Version 4.20

Extension in tabulator Rights

The tabulator is extended by the option All Processes. With this option a worker can be assigned a right for a process template, whitch is located outside its directly organisation hirarchy. This extension is required because of the new tabulator Taskareas. With Taskareas a worker can schedule a process, where the orginated process template is located outside the directly organisation hirarchy of the worker. For details please read chapters Tabulator Rights in the documentation OfficeTalk Business-Process-Management.

New tabulator Taskarea for a worker

The new tabulator Taskarea enables a worker to be part of a taskarea of another worker. If the worker is part of a taskarea of another worker, he can dynamicly switch in his tasklist to the tasklist of another worker and start and schedule processes with the identity of this worker. This extension is similar to an assignement of a worker to roles. For details please read chapters Tabulator Taskareas in the documentation OfficeTalk Business-Process-Management.

Version 4.12 Build 01.21.2010

Optimization of working as Webserver

Starting a process from a webclient on the same machine as the webserver OfficeTalk is running, a userdefined dialog of the process is put on top of all dialogs, to notify the user of the required work. This is done if the weblient and OfficeTalk as the websrver are running on the same machine only.

Assigning a String-Variable with a SQLString-Variable in a macro

Assigning in a macro a String-variable with a SQLString-variable did not substitute the placeholders with their variable content. The substitution worked over boarders of macros and services. e.g.
Dim text As String
Dim name As String
Dim textWithPlaceholder As SQLString

name = “Clarc”
textWithPlaceholder = “This is the worker $name“
text = textWithPlaceholder

text contained “ This is the worker $name“ instead of “ This is the worker Clarc“

New service of the systemvariable worker

With the new service activeProcesses(…,timed: …, priority: …, logicalName: …) you can access the active processes of a worker by filtering for some values. Using workers with many processes you may get a much better performance for the execution of the macro.

Version 4.12 Build 01.18.2010

Using the startportal Limited or Unlimited Browser

Using the startportal Limited or Unlimited Browser OfficeTalk aborted at start time with an error message, sorry.

New usinglevel Webserver

The combobox Usinglevel in the tabulator General of the dialog Settings supports the new usinglevel Webserver. This setting is connected with the setting Server in the tabulator Webserver. For OfficeTalk working as webserver this setting must be set additional to the setting Server in the tabulator Webserver. If you run OfficeTalk as webserver, you must set the usinglevel Webservice immediately after the start of this update ! For details please read chapters General and Webserver in the documentation OfficeTalk Business-Process-Management.

Version 4.12 Build 01.14.2010

Using Oracle-Database with system authentification as OfficeTalk-Datastore

For OfficeTalk you can use the Oracle database server with system authentification. Therefore the logindialog is skipped and you are logged into the database server with the system login. If system authentification should be used, die workers shortcut must match to the name of the user in the OS-system. For details please read chapter Settings, pragraph OSAuthent in the documentation OfficeTalk Business-Process-Management.

Extension of the tabulator Database in the Workbench

The tabulator Database for building databaseoriented macros supports now the ADO communication library for the database Oracle. For this support the dialog Database and connection, opened with the button Database… contains the option Oracle-SQL-Server (ADO). Supporting the ADO communication library enables the login to the database with the systemlogin (OS-Autentification). The inputfields for Login and Password are nor required therefore. For details please read chapter Databaseconnection in documentation OfficeTalk Business-Process-Management.

Option Startmacro in tabulator Scripts (SkriptBrower-Dialog)

The option Startmacro was not grayed after the tabulator is opened, but no script and no macro was selected. Choosing the option at this state had no consequence, but a dialog should show, what is allowed and what is not allowed.

Version 4.12 Build 01.11.2010

New service scheduleProcess of the systemvariable stepschedulder

With the new service scheduleProcess(…) of the systemvariable stepscheduler you can schedule programaticly after the end of the current scheduled step a process within the tasklist. With this service a change of processcheduling can be realized within a macro similar to the doubleclick within the tasklist. For details please read chapter scheduleProcess(…) of the documentation OfficeTalk Script.

Using the service activeProcesses of the systemvariable worker in the evaluation version

Using the service activeProcesses of the systemvariable worker (worker.activeProcesses) within a macro answered in the evaluation version not the running processes of the worker. Only the evaluation version was affected by this !

Array-assignement in databasemacro and contextmenu Workbench

Assigning a variable in a databasemacro with an Array like variable = Array() and opening the macro with the contextmenu Workbench resulted in the message The macro can not be opened by the workbench… I general this could happen for a macro written by hand only, because the workbench do not use such kind of statements. But the workbench should be able to open all kind of macros !

Extended Propertydialog Dialogitems for focuscontrol in tabulator Scriptdialog of the Workbench

In the propertydialog Dialogitems for focuscontrol you can use with the new option Use expression instead of itemnames an expression in the inputfield Items or Expression for getting the itemnames instead of typing in the names. With this extension you have more flexibility using the extra control of focus.

Version 4.12

Extension for special focuscontrol in userdefined dialogs

The proprertydialog of the most inputfields contains the new option Focus. Using this option defines the focus for the dialogitem at opentime. For this task the systemvariable ScriptDialog supports the new service focus(...). With the button Focus in the tabulator Scriptdialog of the Workbenchdialog you can define the first empty or not empty dialogitem of a list of dialogitems to get the focus at opentime. For this task the systemvariable ScriptDialog supports the new service focus(..., empty: ...).Theese extensions optimizes the usability of a userdefined dialog. For details please read chapter Tabulator Scriptdialog and the chapters of the Propertydialogs of the affected dialogitems in the documentation OfficeTalk Business-Process-Management and the chapters focus(...).and focus(..., empty: ...) in the documentation OfficeTalk Script.

Option Dialog kann nicht abgebrochen/beendet werden und Dialogelementeigenschaft Sperren in der Workbench

Die Optionen Dialog kann nicht abgebrochen werden im Register SkriptDialog und Sperren in der Abbruch-Schaltfläche im benutzerdefinierten Dialog und die Optionen Dialog kann nicht beendet werden im Register SkriptDialog und Sperren in der OK-Schaltfläche im benutzerdefinierten Dialog sind jetzt werden jetzt gemeinsam betrachtet. Wenn z.B. die Option Dialog kann nicht abgebrochen werden im Register SkriptDialog gesetzt wird, wird automatisch auch die Option Sperren in der Abbruch-Schaltfläche im benutzerdefinierten Dialog gesetzt, so eine vorhanden ist und wenn die Option Sperren in der Abbruch-Schaltfläche im benutzerdefinierten Dialog gesetzt wird, wird automatisch auch die Option Dialog kann nicht abgebrochen werden im Register SkriptDialog gesetzt.

Acceleration for building a processtemplate

Opening of the contextmenu of a step in a processtemplate the busybee mouse was displayed a long time, when the actions of the step used large macros. Now the busybee mouse acts the first opening only.

Single-Sign-On did not work using Oracle 10g

When using the database Oracle 10g the login had to be done for the company first, because the contextmenu Create database user was aborted with the Oracle message ADMIN for CONNECT not granted.

Unneccessary message of commiting changes

Using the Oracle- or DB2-database required the commiting of changes at the end of the program with the message Do you want to save the changes… no matter wether changes had to be commited.

Version 4.11

Changing properties of a button in a userdefined dialog (ScriptDialog)

Changing the properties of a button by doubleclicking the button in the dialogitemlist while the tabulator Scriptdialog was closed, ended OfficeTalk with an error message.

New documentation Basics.pdf

The new documentation Basics.pdf contains the concepts and basic usingrules of OfficeTalk. You will find the documentation in …\OfficeTalk\Help.

Ending OfficeTalk with opened tabulator ScriptDialog of the Workbench

Ending OfficeTalk with the windowclosebox when the tabulator ScriptDialog of the Workbench was opened, aborted OfficeTalk with an error message, sorry.

New dialogitem Treelist for userdefined dialog (ScriptDialog)

In userdefined dialogs you can use the new hirachical organized listitem Treelist. Its organisation is similar to a filebrowser. For this extension the Workbench supports the Treelist and the systemvariable ScriptDialog is extended with the service addTreeList(…). For details please read chapter Workbench in the documentation OfficeTalk Business-Process-Management and chapter addTreeList(…) in the documentation OfficeTalk Script.

Dialog Assignement of attributes

Clicking on the columntitle Name in OfficeTalk in the dialog Assignement of attributes, opened with the menu Extras – Importassignement, ended OfficeTalk with an errormessage, sorry. The importassignements are used by a processimport from MO²GO of the Fraunhofer Institut IPK.

Browserentry in group Applications of the OfficeTalk-Environment

For an URL (www., http://) and the fileextensions *.html and *.htm the group Applications of the environment must not contain an entry for the browser anymore. Activating of such an link the standard browser of the OS-platform is opened. An entry for the browser in the group Applications is used in any case, if it is contained.

Version 4.10

New services in systemvariables

To investigate the processdata in the executionhistory programaticly, the systemvariable ProcessHistory is extended with the service processData and the systemvariables stepscheduler and worker are extended with the service processTemplates. For details please read documentation OfficeTalk Script.

Processdata of closed processes remain avaiulable

Up to now the processdata of a closed process was destroyed. Now the processdata of a closed process is available via the history in its process template. With this extension the retival of processinformation in the history with comments is not needed anymore. Instead of the retrival of information of closed processes can be done more easier with the processdata in its history.
For this extension, the OfficeTalk-database is extended with two new tables (historyprocessdataentry und historyprocessdataitem). These two tables are installed automaticly when the version 4.10 is started the first time. For this start you must login as company !

Inserting the dialogitem Picture in a userdefined dialog with the Workbench

Since the extension with colors and fonts for dialogitems OfficeTalk ended with an errormessage when a Picture was inserted in a userdefined dialog (ScriptDialog), sorry.

Colors for the dialogitems Resizer and Seperatorline in the Workbench

With the Workbench the color for a Resizer and for a Seperatorline within a userdefined dialog (ScriptDialog) can be defined by the propertydialog. For details please read chapter Workbench in d ocumentation OfficeTalk Business-Process-Management.

Changing cursor in dialogfield of the macro in SkriptBrowser

The cursor over the inputfield of the macro changed permanently between arrow and glasses. This was no functional restriction, but irritated sometimes.

Expression with multiple lines in tabulator Return of the Workbench

Leaving the tabulator Return with an expression with more lines e.g.
If dialog.value(“option“) = True
Then line = 1
End If
was denied with the insertion <- Deklaration is missing at the beginning of the first line.

Version 4.04

Extended properties in workbench for extra designing items in a userdefined dialog (ScriptDialog)

With the extended properties in the workbench you can colorize end emphasize labels and you can define the color of input fields to inform the user visuell about important inputs too. The services bold(…), bold(…, register:…), color(…, with: …) and color(…, register:…, with:…) are responsible for. For details please read chapter Fieldproperties in documentation OfficeTalk Script.

von Eingabefeldern gestaltet werden. Damit kann z.B.auf besonders wichtige Eingaben in einem Dialog auch visuell hingewiesen werden.

New service identity of the systemvariables process and worker for a macro

The systemvariables process and worker support in the macro the new service identity. The service answers the identity of the process or worker within the database. For details please read chapter process and worker section identity in documentation OfficeTalk Script.

Arithmetic with Date and Time in macro

Calculations with Date und Time-variables resulted sometimes in wrong results or in an errormessage.

New menuitem for insertin a dialogitemaccess

The contextmenu Function – Dialogs – Itemcontent inserts at the cursorposition the statement for accessing the content in the choosen dialogitem.

Version 4.03 Build 11.26.2009

Canceling changes in the SciptBrowser dialog

Canceling changes of a macro in the ScriptBrowser dialog aborted OfficeTalk with an error message, sorry.

Version 4.03 Build 11.18.2009

New service for table and listfields in userdefined dialogs (ScriptDialog)

In tables and listfield of userdefined dialogs (ScriptDialog) you can update a single line with the new service value(…, relpace: …, with: …) and you must nor actualize the hole content anymore. Especially in tables and listfields with many lines this is much faster for updating a single line. For details please read chapter Fieldproperties, section value(…, relpace: …, with: …) in documentation OfficeTalk Script.

Wrong message “The macro is changed and must be compiled…” after compiling the macro

After compiling a macro in the scriptbrowserdialog the contextmenu Compile was not grayed and going to another tabulator resulted in the message “The macro is changed and must be compiled…”.

Version 4.03 Build 11.16.2009

Better usability in dialogs with hotareas

In dialogs with a hotarea, an activities can be started by clicking into the hotarea. Moving the mouse over a hotarea, it gets a hand with pointing finger. An example is in the Doabout-dialog the left link to the JOOPS site and the right link to the OfficeTalk-Support. Moving the mouse over one of these both hotareas, the mouse gets a hand with pointing finger and a click in the left link http://www.joops.com opens the JOOPS-Homepage by the installed browser and a click in the right link OfficeTalk@joops.com opens the mailclient for a mail to the OfficeTalk-Support. The hotareas are decribed in documentation OfficeTalk Business-Process-Management. This is a small, but a usefull enhancement.

Menu Usings… in tabulator Resources

The resultdialog with the usings of the resource did not contain the usings outside the visibility of the worker of the tested resource.

Change or delegate a process in the tasklist

The dialog Delegate/Change: <processname>, opened with the menuitem Change/Delegate… in the tasklist, contained in the inputfield Comment: the comment of the last change/delegation.

Version 4.03 Build 11.10.2009

Better readability for all HTML-Exports

For a better readability in all HTML-Exports each entity (worker, step, etc.) is preceeded with its symbol.

Simulating a process of another worker

Opening a process of another worker with the dialog Processgraph: <name of process> and simulating the execution, the closing simulation leaved the executes steps colored.

More information about consumed resources while simulating the execution of a process

In die simulationsdialog of a processexecution (Simulation of process: <name of process>), opened with the menu Simulation – Open… in the dialog Processgraph: <name of process>, the tabulator Resources shows for each consumed resource the responsible step.
A consumed resource was not reported here, when the resource was consumed in a macro with the statement stepscheduler.consumed(…) while executing a step without named worker (scheduled by current worker).

Userdefined dialog (ScriptDialog) with more table items

Sorting the content of a table in a userdefined dialog (ScriptDialog) with the column title sorted sometimes the content of the other table item.

The dialogs for help

Some helpdialogs (Button Help in the tasklists, dialog of workerexport, etc.) where not closed automaticly and stayed open. e.g. After pressing twize the button Help in the tasklist, the helpdialog was opened twize.

Statusline in the dialogs of the tasklist

For a better usability of the tasklists the statusline is preceeded by buttons for activating/deactivating an inverting the selection values. The left button for activating/deactivating shows his current functionality with its symbol. The dialog Select processes can be opened by clicking on the selction values in the statusline too. For details please read chapter Statusline in the tasklist in documentation OfficeTalk Workflow.

Unneccessary request for saving the local database

Starting OfficeTalk and executing a macro inside the testenvironment or changing the filter in the tasklist only requested the save of the unchanged local database at the end of OfficeTalk. This war requested using the local database only ! The using of any SQL-database was not affected by.

Diagnose of the execution of a HTTP-Request in the Skriptdebugger is made easier

The debugger displays in the listfield of the variables the result of the execution of a HTTP-Request in the HTTPClient-variable. Doubleclicking the variable opens the result in a seperate dialog for larger results. With this enhancement the diagnose of the execution of a HTTP-Request is made more easier.

Version 4.03 Build 10.15.2009

Directory with missing permissions for local database

Login and logout resulted in an errormessage, if the file permission for the local database was missing. This did not affect the working with a productive database.

Diagnose of the execution of a Webservice in the Scriptdebugger is made easier

The debugger displays in the listfield of the variables the result of the execution of a webservice in the WSDLClient-variable as structured text. Doubleclicking a structured text opens the part of result in a seperate dialog for larger results. With this enhancement the diagnose of the execution of a webservice is made more easier.

Version 4.03

Extended settings for selecting processes in the tasklist

Processes can be selected not only by control of flow informations, but by informations owned by the process too. With this extension you can control the working with processes more effective. An Example: A selling process has the processdata of the sum (Sell – Sum) and you want to show only processes with sum more than 20.000,--. With the menu View – Select processes by you can define this condition in the filterdialog now.

Version 4.02 Build 10.08.2009

Kontextmenü Anweisungen – Schleifen – While im Dialogfeld des Makroquelltextes

Wenn mit dem Kontextmenüs Anweisungen – Schleifen – While im Dialogfeld des Makroquelltextes im Skriptbrowserdialog ein Gerüst der While-Anweisung eingefügt werden sollte, beendete sich OfficeTalk mit einer Fehlermeldung, sorry.

Using an unknown or bas environment at login

The messagetext for using a bad or unknown environmentname is more clearified. Now the reason for the failure of identification is described for a better understanding.

Responsibilities of the steps of a processtemplate

The dialog Responsibilities of Steps in: <name of processtemplate>, opened with the contextmenu Responsibilities… in Tabulator Processtemplates, a step with scheduling option Current Worker is not contained in Current worker anymore, but is contained in the worker found in the reverse order of the scheduling path. For details please read chapter Responsibilities... in d ocumentation OfficeTalk Business-Process-Management.

Analyse of the graph of process in dialog Analysis of graph: <name>

In tabulator Empty Steps of the dialog Analysis of graph: <name>, opened with the menu Extra – Analysis of processgraph in the dialog Processgraph: <name of process>, the wrong responsible worker was displayed in case of horizontal flow. Instead of, the processowner was displayed.

Version 4.02 Build 09.30.2009

Installation is extended by dialog for selection of the database system

The process of the very first installation is extended by a dialog for selecting the database system to be used.

Version 4.02 Build 09.29.2009

Processhistory support dokumentlinks

The dialogfields Description and Comment of the Historydialog supports links to extern documents (blue underlined text) like the other descriptionsfields.

· The Description contains the links of the orginated processitem description.

· The Comment contains links added with the service comment(…) while the execution of the process. For details please read chapter step in documentation OfficeTalk Script.

With this extension a processhistory can be linked to extern documents.

Let a process wait for the end of another process

Letting a process wait for the end of another process in all forms of a tasklist requires now the reason of wait in the waitdialog. The reason is archived in the history.

Delegating and/or changing a process in the tasklist

Delegating and/or changing a process in all forms of a tasklist with the contextmenu Delegate/Change… requires now the reason of delegation/change in the delegationdialog. The reason is archived in the history.

Terminating a process in the tasklist

Terminating a process with the contextmen Terminate in all forms of a tasklist requires the reason for termination with a new dialog. The reason is archived in the history.

Dialog Responsibilities of step for <worker or processtemplate>

Opening a Step in the dialog Responsibilities of step for <name>, opened with the contextmenu Responsibilities… in the Organigram or in the listfield of Processtemplates opens the step’s dialog with its tabulator Schedulingoptions. In this tabulator you can see the reason of the responsibility (Step is scheduled by).

Version 4.02 Build 09.23.2009

Calldiagram for a macro (contextmenu Callgraph in listfield of macros of the ScriptBrowserdialog)

Calling a macro, whitch is positioned direct below the caller in the next line below crossed the macro in the line between with the blue connection instead of surrounding it. This was the reason for a bad readable diagram sometimes.

Version 4.02 Build 09.20.2009

Leaving the described way to create or to change a macro in tabulator Scripts

When using the Function/Organigrammbrowser a macro is created or changed not the way as recommended, resulted in messagedialogs, whitch where not god worded. Now the wording of theese messagedialog is much better.
In the Function/Organigrammbrowser the steps Change macro – Switch function – Close OfficeTalk with window closebutton resulted in the messagedialog Transaction is in use, Commit or Rollback.

Button WSDL-Schema in tabulator Webservice of the Workbench

Errors on opening the WSDL-Schema with the earth-button are described detailed in an error message now.

Inputfield URL in tabulator Webservice of the Workbench

In the inputfield URL you can use now both seperators (\ and /). In the past writing an URL, the seperator / was allowed only.

Tabulator Return in the Workbench and Return a service

If the macro was ended with Return with a service (e.g. Return wsdl.value), the workbench did not build the tabulator Return right.

Tabulator Webservice in the Workbench

Omitting input in the field WSDL-Client of the tabulator Webservice resulted in termination of OfficeTalk when another tabulator is selected, sorry.

Tabulator Database and Return in the Workbench

Typing in a wrong expression in the input field SQL-Command of the tabulator Database and in the input field Expression of the tabulator Return the text was marked at the wrong position with the syntax error.

Removing a macro with the contextmenu Remove in the ScriptBrowserdialog

Removing a macro with the contextmenu Remove in the listfield for macros of the SkriptBrowserdialog is extended with additional verifications.

· Removing a startmacro is denied with a detailed message, if its script is assigned in any action.

· Removing a macro with is called with the Call-statement recursive is allowed now. In the previous versions the Call-statement had to be removed first.

Controlling of cursor with CTRL- and specialkeys in the dialogfield of the macrosource

The controlling of the cursor in the dialogfield of the macrosource in the SkriptBrowserdialog with CTRL- and spezialkeys (e.g. Pos1, End, PageUp, PageDown, etc.) is available like in all other dialogfields. “Keyboardfreaks“ will be happy about !

Version 4.02 Build 09.14.2009

The name of a script and a macro was lost when the name was changed

Changing the name of a script in the scriptbrowser with the contextmenu Change and of a macro in the first line of the sourcecode of the sciptbrowser lost sometimes the changed name. Restarting OfficeTalk displayed for those modified artefacts the name (unlabeled).

Tabulator Read before written in dialog Analysis of processgraph: <name>

The tabulator Read before written in dialog Analysis of Processgraph: <name>, opened with the menu Extra – Analysis of processgraph in the dialog Processgraph: <name of process>, is not displayed red anymore, because a missing read before written of processdata may not be an error in any case.

Cursor displayed no Busybee on long activities

If the cursor displayed a Busybee to reflect its busy state and the cursor was moved to another window and back, the cursor became not a Busybee again. This resulted in some misunderstanding about the busy state.

Using webservices with complex datatypes as arguments

Up to now only webservices with scalare arguments where useable. Now you can use webservices with arguments of complex datatype too. For details please read chapter WSDLClient in documentation OfficeTalk Script.

SQL-Command are denied in tabulator Database of the Workbench

Using the startportal Dialog each SQL-Command in the input field SQL-Command of the tabulator Database in the Workbench was denied with an error message, but the macro was build correct.

Using the webservice VisibleProcessTemplates

The webservice VisibleProcessTemplates was not executed, but resulted in a Webservice-Exception.

New webservice UsedProcessData of the webservers

The webserver supports the new webservice UsedProcessData, to answer the names of the processdataitems of a processtemplate, used in its execution. For details please read chapter OfficeTalk as Webserver in the documentation OfficeTalk Workflow.

Logging for systemobject Mail is extended

For sending an eMail with the systemobject Mail the logging is extended with the detailed errortext. With this information you can correct wrong settings easier.

Texts of the Webservice-Exceptions are localized

For all texts of the Webservice-Exceptions the installed language is used now.

New Exception of Webservices

A Webservice ends on bad permission and unknown identification of a process with a specified Exception, and not with False anymore, to inform the webclient about the detailed reason. For details please read chapter OfficeTalk as Webserver in the d ocumentation OfficeTalk Workflow.

Creating a database macro by the Workbench with duplicated Dim-statements

Creating a macro with arguments with the tabulator Database of the Workbench and specifying the used columns with the button Columns, the macro was build with additional Dim-statements for the arguments. Because of, a succeeding compilation was aborted with the message for duplication of variable.

Opening a macro with the Workbench containing a conditional Return

Opening a macro, whitch contains a conditional Return statement (e.g.. If a = b Then Return x End If), resulted in an error message.

Version 4.02 Build 08.21.2009

Helpdialog for the tabulator Database in the Workbench

Some message in the helpdialog for the tabulator Database where not clear.

Tabulator Database in the Workbench with using IBM-DB2- or Microsoft-SQL-Servers

Building a macro with the option Result is not used, the macro was create using the services updateBatch and close. Executing the macro resulted in an error message at the services close. Reopening the macro with the Workbench, the tabulator Database displayed the wrong option Update record. This happened, if the macro used the IBM-DB2- or Microsoft-SQL-Server only !

Version 4.02

Workbenchextension for building a more flexible database macro

The tabulator Database contains the new option Retreive single record. With this option exactly one retreived record is put into the resultvariable. This option make sense, if a single record is requested only. In this case the result variable contains a one dimensional array instead of two-dimensional array in normal retreivings. For details please read chapter Tabulator Database in documentation OfficeTalk Business-Process-Management.

In the dialog of the database connection, opened with the button Database in the tabulator Database, you can select with the button >> the macro containing the connection informations. This macro must contain a Return-statement with the connection informations as argument. Because of, you can hold such important informations central in one macro and reference them with this feature. If a macro is selected, its connection informations are displayed in the dialog and are not changeable. For details please read chapter Databaseconnection in documentation OfficeTalk Business-Process-Management.

The input field SQL-.Command in the tabulator Database can contain now an expression too for more flexible SQL commands. As change a simple string must be enclosed in “ (e.g.: “SELECT * FROM …“). For details please read chapter Tabulator Database in documentation OfficeTalk Business-Process-Management.

Use of systemvariable scheduledata is supported by the Workbench

The use of the systemvariable scheduledata is supported in the dialogs Source of the item's content and Target of the item's content of the dialog item properties. If used, source and target must be written in the option Expression because the option Processdata is reserved for the permanent processdata.

Contextmenu Usings… in listfield of the macros in the Skriptbrowser dialog

In reare cases the contextmenu Usings… notified a macro as unused, but it was used by another macro. e.g. The caller used in the Call-statement an String-argument and the called macro used a SQLSting-argument instead.

Using contextmenu Remove Histories in the evaluation version

Removing the histories of a process with the contextmenu Remove histories in category Processtemplates or in dialog for starting a process did not ungray the menuitem File - Save in the evaluation version only.

Making an option in a userdefined dialog with the Workbench mandatory

Making an option in a userdefined dialog with the Workbench mandatory created a mandatory(…)-statement for each option in the group. This resulted in no error, but was to much, because in the mandatory(…)–statement the group is used but not all options within the group.

Size of names of a resource and a script

The input in the namefield of the resourcedialog and in the dialog for a new script is limited now to 64 characters. This limit was valid in the past, but was not explicitly verified.

Setting Animate red delay in tabulator Tasks of the general settings

Animating the red delayed processes in the tasklist and resorting the processes by the menuitem Sort processes by or by a columntitle could corrupt the displayed processes in very reare cases. In such a case the tasklist had to be reopened to correct the display of the processes.

Menuitem View – Filter processes by in tasklists

The dialog for setting the filter for processes contains the new setting up to yesterday. This filter selects the delayed processes only.

Contextmenu Columns in the tabeled tasklists

Using the contextmenu Columns the very first time in a tabeled tasklist , the opened columns dialog displayed all columns as not used, instead of used. This could be made a little confused.
Configuring the column Starttime only ended OfficeTalk after closing die columndialog, sorry.

Right mousebutton (contextmenu Insert) in textfields

Inserting in the past a text into a textfield with the contextmenu Insert, first the cursor had to be put to the insertion point. Now the right mouse button (contextmenu) sets the cursor to the clickposition of the right mousebutton first.

Version 4.01 Build 08.01.2009

Optimized usage of calendar in userdefined dialogs (ScriptDialog)

A date in the calendar, inserted with the workbench in a userdefined dialog, can be choosen by double clicking the day. The calendar is closed by the doubleclick without pressing the button Accept. And the date of the corresponding datefield is preselected in the opened calendar.

Optimized usage of a link in descripion fields

A link (blue underlined filename or URL) in a description field of a dialog (e.g. tabulator Description of the worker dialog) is used exactly like in a browser. Touching a link with the mouse the cursor becomes a tipping hand. Clicking a link with the left mouse button opens the link. Before this change, to opened a link with the contextmenu Open selected document, the cursor had to be moved inside the link first.
After inserting a link with the contextmenu Insert document, you can proceed with typing in without any additional action. In the past another text had to be pasted first at the end to proceed typing in without blue underlining.
For details please read documentation OfficeTalk Business-Process-Management, chapter Integrate external documents.

For a better overview in larger models

The get a better overview for a larger model, the workers of an organisation unit, the processtemplates, the resources, the rights and the substitutes are ordered alphabetical in the listfields.

Version 4.01

Contextmenu Open selected document

Using the contextmenu Open selected document with selected blank or seperator only ended OfficeTalk with an error message, sorry.

Start OfficeTalk as Webserver

Starting OfficeTalk with the option Webserver – Yes, and the webserver functions could not be activated, OfficeTalk was ended with an error. Now you can go on.

The webserver was not stopped on an unexpected end

Ended OfficeTalk unexpected with option Webserver – Yes, a relogin must be done before starting OfficeTalk again.

Create a database macro with the Workbench

Creating a macro with the tabulator Database of the Workbench the option Results did not handle variables and processdata in the columns.

Changing the height of inputfields in userdefined dialogs with the Workbench

The height of inputfields and inputfields with arrows in the Workbench can not be modified by dragging the mouse on the horizotal line anymore. Only the width can be modified by dragging the mouse.

Shortcut for menuitem History in the tasklists changed

To avoid double using of the shortcut with the menu Help, the shortcut for History in all tasklists is changed to Y.

Using an invalid macroname in the Workbench

The Help in the Workbench notified a missing macroname, if an invalid name (e.g. „this-is“) was used.

Opening a databasemacros with the Workbench with the option Trusted Connection

Opening a databasemacro with the Workbench, whitch uses the option Trusted Connection, loosed the option.

Start- and Endaction running a scriptmacro whitch uses the systemvariable stepscheduler

Scheduling a start- or endacion with a scriptmacro, using the systemvariable stepscheduler, ended OfficeTalk with an error message.

Typing in more then 64 characters for a name

Typing in into a namefield of a processtemplate, step, action or stepresult more then 64 characters ended OfficeTalk on saving the changes. In general 64 characters are much enought, but some people want to write more…

The option -oem in the commandline and OEMOFFICETALK in the environment variables

With –oem and OEMOFFICETALK another database must be used for testcases. Using a Microsoft SQL-Server database, this alternate database was not build correctly on the first start of OfficeTalk.

Version 4.00 Build 07.16.2009

Hyperlinks for inserted documents in the description of processtemplate and step

The context menu Insert Document in the register Processtemplate and in the register Description of the dialog Step did not underline the inserted link.

Version 4.00 Build 07.11.2009

Contextmenu History in the tasklist using the Organigram-/Functionbrower

Using the startportal Organigram-/Functionsbrower ended OfficeTalk with an error message, when the contextmenu History in the tasklist was choosen, sorry.

WSDL Definition od the SOAP-Datatype SOAPProcessData is simplified

The Element type was removed and the elements xxxValue of the SOAP-datatype SOAPProcessData are optional. See line <complexType name="SOAPProcessData"> in the WSDL-file OfficeTalk.wsdl.

Version 4.00 Build 07.07.2009

Onlinehelp for services of built in DotNET-systemclass

Writing a macro, the onlinehelp for services of a built in DotNET-systemclass offered no services. The systemclass DotNET.System.Globalization.Calendar was such an example.

Version 4.00 Build 07.02.2009

New commandline option -OEM

With the new commandline option–OEM important settings (database, gallery, etc.) can be done. For details please read documentation OfficeTalk Business-Process-Management, chapter commandline options.

Animated buttons in the toolbar of dialogs

In all dialogs with a toolbar the button for Save and in all variants of the startportals the buttons for Save and Exit in the toolbar are animated if required, to show what to do next.

Tabulator Webservice in the Workbenchdialog

Pressing the WSDL-button prefixes the name of the WSDL-schema in the input field URL: with “http://“, if needed.
Pressing the WSDL-button with an invalid or missing WSDL-schema in the input field URL: notifies you with a propper message. In the past, invalid input in the input field URL: was simply ignored.

Version 4.00 Build 06.27.2009

Menuitem Simulation in dialog Processgraph: <name of process> of the evaluation version

Choosing the menuitem Simulation for some processtemplates terminated the evaluation version with an error message, sorry

Contextmenu History in the tasklist of the evaluation version

Some processes in the tasklist of a few workers in the evaluation version manage their history. Choosing the contextmenu History opened an empty historydialog. Now you get a notification on such processes of the evaluation with no history.

First installation using database Oracle, DB2 or PostgreSQL

Installing OfficeTalk the first time and using the database Oracle, DB2 or PostgreSQL, created the owner of the database OfficeTalk as databaseuser without password. Because of, OfficeTalk could not access its database. The problem occurred since Version 4.00.

Onlinehelp of services for manipulating and controling dialogitems of the systemvariable ScriptDialog

The onlinehelp of services to control and retreive dialogitems (e.g. dialog.disable(…)) contained labels and groupboxes, but theese items are not retreivable and controlable. This change is related to the onlinehelp in the sourcefield of the Skriptbrowser and to the tabulators Startstatements, Endstatements and Return in the workbenchdialog. Additionally this onlinehelp in the tabulator Return of the workbenchdialog contained all option items instead of the groupname for theese options.

Version 4.00 Build 06.18.2009

New servive invalidate(…) of the systemvariable ScriptDialog

The service updates at once the contents of the given dialogitems. For details please read d ocumentation OfficeTalk Script, chapter invalidate(...).

Service addAccessButtonLeft(…) and addCancelButtonLeft(…) and opening the dialog with the Workbench

The services addAccessButtonLeft(…) and addCancelButtonLeft(…) without argument default: for inserting an OK- and Cancel-button where ignored by the Workbench. Inserting such a service in the macro manually and opening the dialog with the Workbench ignored this button, witch was a little confusing.

Version 4.00

OfficeTalk acting as Webserver

The variant OfficeTalk/MSP can act as webserver now. The available webservices support working with processes. Starting, scheduling, finishing and requesting informations about active processes is the scope of the published webservices. Applications supporting webservices on base of SOAP can use OfficeTalk as „Workflowengine“. To support the connection to the webserver, the dialog Settings was extended with the tabulator Webserver. For details please read d ocumentation OfficeTalk Business-Process-Management, chapter Tabulator Webserver and OfficeTalk Workflow, chapter OfficeTalk as Webserver.

Contextmenu Insert document…

In the dialogfields with the contextmenu Insert document… the item was not grayed in readonly state of the dialog. Because of this, an invalid change of the content of the dialogfield was possible. An example is the dialog State of: <Processname>, opened with the contextmenu State… in the Personal Tasklist and in the Takeoverlist.

Notification in case of an outdated licence for an evaluation version

For an outdated licence of an evaluation version an invalid licence was notified. Now in case of an outdated licence, this is notified with an understandable text.

Version 3.14 Build 05.11.2009

Starting OfficeTalk with an unknown environment name (MS-SQL-Server and PostgreSQL Server)

Using a MS-SQL-Server or a PostgreSQL Server and starting OfficeTalk with a bad environment name, an invalid login was notified instead of an unknown environment.

Environmentnamen zu beanstanden.

Settings for an OEM-version

With the setting for an OEM-version OEMOfficeTalk in the environmentvariables not only the galery for the customers pictures is used, but the specific messagetextfile for this OEM-version in the directrory …\OfficeTalk\messages is used too. You get the file from JOOPS. If the OEM-specific messagetextfile is missing, OfficeTalk uses the default one.

Menu View – Workersymbols in organigramdialogs

The menu View – Workersymbols in the most types of an organigramdialog resulted in an abnormal end of OfficeTalk with an error message, sorry.

Version 3.14

Menu Statistic – Executiontimes/-paths in dialog Processgraph: <name of process>

The sequence of execution for a selected execution path in dialog Executionpaths of process: <name of process> is shown in dialog Processgraph: <name of process> at each stepresult with its sequence of executionnumber. This information is very helpfull on large execution paths. For details please read documentation OfficeTalk Business-Process-Management, chapter Executiontimes/-paths.

Menu Extra – Workflowanalysis...in dialog Processgraph: <name of process>

Analyzing the flow of process with the menu Extra – Workflowanalysis... in the dialog Processgraph: <name of process> is extended for inspecting the misuse of temporary processdata within the processflow. The tabulators Missing Prepearation and Not used contain now possible misuse of temporary processdata with the services of the systemvariable scheduledata too. For details please read documentation OfficeTalk Business-Process-Management, chapter Dialog of Workflowanalysis.

New systemvariable scheduledata for temporary processdata

With the new systemvariable scheduledata you can manage in a macro the temporary data for a process similar to the systemvariable processdata. The restrictions of processdata are not current for the temporary scheduledata. For details please read documentation OfficeTalk Script, chapter scheduledata.

Variable with Null-value in the column of a table in an userdefined dialog (ScriptDialog)

The column of the row in the table of an userdefined dialog (ScriptDialog) was displayed with text “Null“, if the source of the column, the variable was empty (Null value). Now such columns are leaved empty (displayed without text).

Multiple usings of a script with contextmenu Usings... in dialog ScriptBrowser

If a script was used multiple in the same macro with the statement Call, opening the second using did not select the correct position of using in the opened macro.

Removing a script in dialog Skript-Browser-with the contextmenu Cut

Since version 3.13 a script must not be used by a Call-statement in a macro, to be removed (contextmenu Cut in the script listfield). This test for usings was designed a little to heavy, because Call-statements in a macro of the script to be removed, whitch uses the same script must be ignored.

Version 3.13 Build 29.04.2009

Saving the local database with newly created processtemplates

Ending OfficeTalk, after creating new processtemplates, with saving the local database aborted OfficeTalk with an error message and the local database was not saved. This happened not in the productionsystem using an SQL-database. This happened in an evaluation system using the local database only !

wurde, beendete sich OfficeTalk mit einer entsprechenden Fehlermeldung. Dies trat nicht in der Produktivversion bei Verwendung einer SQL-Datenbank, sondern nur in der Testversion bei Verwendung der lokalen Datenbank auf !

Executing service of systemvariable with a required context

Some service of a systemvariable constrains a defined context. If this context is not given, an exception is raised. This exception can be catched with the statement Try-Catch. For constrains while executing services please read documentation OfficeTalk Script

Errorhandling while executing a scriptmacro

If an error was detected while executing a macro, the error was nor notified and the proceeding was not handled well. Instead of OfficeTalk was ended. This happened since version 3.11.

Service activeProcesses of the systemvariable worker

The service activeProcesses of the systemvariable worker answers all processes without respect to the selected filter within the tasklist.

Contextmenu Usings… for Scripts in dialog Skript-Browser

The contextmenu Usings… in the listfield of scripts shows additionally where a script is used within a macro by a Call-statement . e.g.: Call Customer.Create in macro Dialogs.Customer displays in the usings dialog the macro Customer as user of the script. Double clicking the entry opens the macro. For details please read documentation OfficeTalk Business-Process-Management, chapter Scriptlist.

Contextmenu Remove for Scripts and Macros in the dialog Skript-Browser

The contextmen Remove for a Script or Macro in the corresponding listfield is denied with a warning, if the Script or Macro is used by another entity. By this enhancement a removing of an used Script or Macro is avoided.

Startportal Function-/OrganigramBrowser and separate opened dialogs

Using the startportal Function-/OrganigramBrowser some dialogs are opened for a better overwiew separate. The resultdialog of the workersearch (menu Worker – Search…) and the usingsdialog (contextmenu Usings... in the listfield of the organigram) are such examples. The previous version closed these dialogs automaticly at the end of the program. Now these separate dialogs are closed, if a task relevant item is selected in the left listfield, because working with tasks do not need these dialogs anymore.

Locale database for an evaluation version

On Windows-platforms OfficeTalk can be started by double-clicking a local database (*.bos). With this enhancement a local database must not be named OfficeTalk.bos anymore and more local databases can be exist and used.

Version 3.13

Service goBack with more preceeding steps with same name

The service goBack delegated the workflow of a process to the wrong step back, if more direct preceeding steps of the current step had the same name. The step for delegating back was searched without respect to the scheduling worker.

Selecting the next Step on errors of a Stepresult

If a Step is finished with an unknown result, the dialog for Step execution is opened without the possibility to select the result manually, if the required right Select next Step was missing for the process. But in case of a result error the selection of the right result must be possible ever !

Setting Toolbarlabeling in tabulator General

The setting Toolbarlabeling in tabulator General of the dialog Settings is available now on all Linux platforms.

Dialog Select a color to set the backgroundcolor in the tabulator General

The dialog Select a color for setting the backgroundcolor in the tabulator General of the dialog Settings did nor select the current background color in opposite to the dialog for setting the toolbarcolor. This is not very important, but a choosen option should be visible in any case.

Opening an item in the Using dialog

The first opening of the using location of an item within the Using dialog (by doubleclick or by the context menu Open…) was denied with the message …because the worker is not contained in the visible organigram, if the startportal Dialog was used and the Using dialog was indirect opened by the result dialog of Searching worker.

Stepresults in dialog Processgraph: <name of process>

The stepresults (blue connection lines) of the steps in the diagram of processflow for a processtemplate and for a process displays a timepictogram for the setting after > 0 seconds, at, Weekday, Day of month only to make the graph more intuitive for recognizing the delay times and execution without delay.

Contextmenu Usings for a resource in tabulator Resources

If a same named resource was contained in the logged in worker and in a subordinated worker and the resource was used in a macro (service consumed(…)), the Using dialog showed the macro with its owner, but open the using with the contextmenu Open did not open the location of the using, the macro.

Version 3.12 Build 06.04.2009

Syntaxcoloring of a macro in the source field of the ScriptBrowser-dialog

Because of changes in Version 3.12 Build 01.04.2009 the Syntaxcoloring in the source field of the ScriptBrowser-dialog was deactivated, sorry.

Version 3.12 Build 02.04.2009

Searching workers by scripts with macroname and source

Seaching for workers with the dialog Searching Worker by a macroname and sourcepattern in tabulator Script, skipped the using of the given macroname for the match.

Version 3.12 Build 01.04.2009

Input of name for all named items

The input of a name in the namefields of the dialog for a named item (e.g. Processtemplate, Step, Stepresult, Resource) disables all invalid characters and subsequent messages for saving an item with an invalid name is not needed anymore.

Sorting processe in the tasklist by Runtime

If a tabeled tasklist, containing a process without next step, was sorted by the column Runtime, ended OfficeTalk with an error message, sorry. A process without next step is resulted by a previous error while scheduling.

Version 3.12

Sorting processes within the tasklist

For an extended sorting of the processes within the tasklist in browser- and pictogram-format the new menu View – Sort processes by is available. The possibilities of sorting are nearly the same as in the tabled tasklist. The new menus are needed, because for a better performance for many tasks within the tasklist (> 500) the build in sort is removed. Additionally with these new menus sorting is available in all formats of tasklists.

Modified sortrule for processes within the tasklist

Sorting the processes within the tasklist by name sorts the processes by the name only. Processes with the same name are sorted by the additionall name. To get the previous behaviour, you must set the setting Name for Sorting: within the tabulator Tasks of the general settings to Complete processname.

Performance optimizing for some operations

Working with Tasklist, Processhistory, Processtemplates, etc. is made faster. This is most visible in a Tasklist with more than 200 processes and in a History with 500 or more entries. e.g. Opening the Tasklist is enhanced by factor 10 by this change !

Missing SQL-tool while creating the database

When OfficeTalk creates it’s database at the very first start and the required SQL-tool (e.g. DB2CMD.exe for DB2-Server) is missing, the message The database is created is displayed but nothing is done and the succeeding login failed. The SQL-tool can not be found, if it’s path is missing in the environment variable PATH or the program is simply not installed. Now you get a message if the SQL-tool can not be found.

SQL-tool must not be installed on every case

The SQL-tool, e.g.. DB2CMD.exe for a DB2-Server, must be installed for the very first start to create the database only. The tool must not be installed for all succeeding actions (e.g. Create the database user with the same named menu in the OrganigrammBrowser dialog. This makes some processes easier, because the menu item can be used on each workstation without respect to the installed SQL-tool. On installed systems the existing database users for the company, departments, offices and teams must be extended with the permission for creating a role/user. An example for the PostgreSQL-Server: Set in all existing users of OfficeTalk, found in the chapter Login-roles, the option Can create roles.

Searching for a scriptcontent in the dialog of searching a worker

Choosing the tabulator Script in the dialog for searching a worker, OfficeTalk aborted with an error message, sorry.

Version 3.11 Build 18.03.2009

Mandatory input in userdefined dialogs (ScriptDialog) must contain a real input

The validation of mandatory inputs in a ScriptDialog accepted an input field with only blanks. But blanks only are not a right input.

Removing the portrait of a worker in its dialog

Clicking the mouse with pressed CTRL-Key in the worker’s dialog removes the containing portrait.

Version 3.11 Build 09.3.2009

Additional support for problems while executing a macro

To support you more efficiently on problems of executing a macro, whitch are notified with the notifyer The service ‘<servicename>’ is unknown in ‘<objectname>’… , the diagnosticfile OfficeTalkDiagnostic.log is created in the temporary user directory. The temporary directory is named by the environmentvariable $TEMP. This diagnosticfile contains detailed information about the reason of the problem. If you see no light, you can send the file to the support of JOOPS for additional help. The setting ScriptSyntax\Diagnostic=No/0 suppress the creation of the diagnosticfile.

Version 3.11

Settings are checked at programmstart

To optimize the settings, the personal and common settings are checked at programstart. With the answer Yes in the questiondialog you can remove personal settings for whitch a common setting with a different value is found. With the option Settings check at start in the tabulator General settings in dialog Settings you can skip this check at programstart.

Anonymous process history

Because of a employers law the association of an executed step to its worker is not allowed. To fullfill this constraint you can suppress this association with Anonymous history in the tabulator Task of the setting dialog.

Accellertation of the contextmenu for processtemplates

The contextmenu of the listfield for processtemplates in the tabulator Processtemplates is especially for many histories (> 10.000) accellerated.

Extended onlinehelp for service selection

The onlinehelp dialog for selecting a service shows a short description for each service. Because of, you may not need to look into the documentation to decide whitch service to use.

Control the processflow to the last executes step back

With the service goBack of the systemvariable stepscheduler you can control the flow easy back to the last executed step. Similar control works with the service goToPredecessor and an additional stepresult, if only one predecessor is possible.

Version 3.10 Build 21.02.2009

New services for testing and notifying wrong and missing input in an userdefined dialog (ScriptDialog)

The systemvariable ScriptDialog supports the new services isValid, isValidSilent(…), isMandatoryMissing and isMandatoryMissingSilent(…). With these services you can test in the statements of an actionbutton the correctness and completeness of the input values. Syntactical wrong or missing inputs are visual marked and notified. Because of, extra testing is not needed anymore.

Inputfields with spinbutton for time and date

In inputfields with spinbuttons you can decrement and increment a part of the field with positioning the cursor to this part before clicking the spinbutton. (e.g. the month of the date).

Service addTable(…) for adding a table in a userdefined dialog extended

The argument colums: of the service addTable(…) is extended. As the forth argument of a column description you can specify the datatype for the column different to the column’s content. The property dialog of the table in the Workbench is extended to support this new feature too. An example: With the forth argument ”Date” of the column Orderdate, the content of the table is sorted by this column in a right way allthough the column is containing a date as string.

Version 3.10

Updateprocess saves existing settings on Windows-platforms

The updateprocess resetted some settings, e.g. the setting for the Startportal, with the default value of a first installation. Only the Windows-platform was affected !

Extended selection of webservice

The dialog for selecting a webservive in the tabulator Webservice of the Workbench dialog and the contextmenu Webservice of the Scriptbrowser’s dialog displays now the documentation for a selected webservice for an easier select of the required service.

Secure the inputquality in a userdefined dialog (ScriptDialog)

Typing a wrong character in an inputfield of a userdefined dialog (ScriptDialog, e.g. A character in a date field), the input field flashed, but the dialog could be accepted. It was hard to identify the wrong input. Now accepting the dialog is denied with a notifier and the wrong field is identified with a questionmark.

Case sensitivity of names in a userdefined dialog (ScriptDialog)

Writing a macro for a userdefined dialog (ScriptDialog) with hand or with the Workbench, the names of dialog items in all used services are not case sensitive anymore. This makes the building of such a macro more easier.

More personalizing of the work with organigram

A worker may can contain its portrait and this portrait is used as the window’s icon for the workerspecific dialogs (Startportal, Tasklist and Workerdialog). If the worker has no portrait defined, its symbol is used for. Working with the organigram as graph is more intuitive with portraits instead of abstract symbols. Organisations like Office, Team can contain a portrait too. In this case a portrait may be a logo. The database table adresse has to be extended for portraits. OfficeTalk does this automaticly at the first start of the update.

Tasklist with red delayed processes

The icon of a red delayed process in all type of tasklists (personal, takevover and group) is animated, to be recognized more intensive. The semaphore of a red delayed process in a tabled tasklist flashes. In the tabulator Tasks of the dialog General Settings you can activate and deactivate this behaviour with the option Animate Red delay.

Using an alternate database in a very rare situation

In extreme rare situations using an alternate database may be successfull. How to do this, is described in chapter Using an alternate database in the documentation OfficeTalk Business-Process-Management.

Settings for the sourcefield of macros in the scriptbrowserdialog

After accepting the settings in the dialog Settings for the Scriptmacrocompiler the changed settings are taken by the sourcefield of the macro. In the past the tabulator Script had to be reselected for taking the changed settings.

Version 3.01 Build 01.21.2009

Removing important settings in dialog Settings

Removing some important settings (e.g. Host in Tabulator Mail) resulted in a notification dialog about the failure, but the setting was removed correctly.

Searching for a macro with Wizard for finding a worker

Searching for a worker by a source pattern (e.g. *dialog*) within a macro in the tabulator Scripts of the search dialog Wizard for finding a worker resulted in a listdialog The workers containing the searched items of the matched, but unnamed macros and not at the first match, if the option Stop searching at first match was set.

Setting the background color for toolbars in dialog Settings

Setting the background color for the toolbars in the tabulator Scripts of the dialog Settings resulted in an error message with termination of OfficeTalk, sorry.

Version 3.01 Build 01.14.2009

Optimized handling of user settings on a workstation

To simplify the realisation of company rules for user settings on a workstation, you can put these settings into the common settings. Each user setting is taken from the common settings, if it is not found in the user settings.

Changed filenames for diagnose and protocol

The filename for protocol is changed from protocol.log to OfficeTalkProtocol.log and the filename for the diagnose is changed from error.log to OfficeTalkError.log. Because of the location of these files in the temporary user directory, this names are easier to find.

Pictures in userdefined dialogs (ScriptDialog)

With the service addImage(…) and the Workbench pictures are inserted in an userdefinded dialog (ScriptDialog) opaque. The border of the picture is painted with the background color of the dialog.

Executing a selected directive Library in ScriptBrowser

A selected Library-directive could not be executed if the succeeding source used a systemvariable of the to be loaded communication library. With this strategy you can simply load a needed communication library while writing a macro.

Version 3.01 Build 12.22.2008

Extended functionality of the service anyEnvironment(…) of the systemobject stepscheduler

The service answers the content of the environment variable of the current platform if the name in unknown in the OfficeTalk’s own setting (common and user). e.g. stepscheduler.anyEnvironmemt(“temp“) answers the temporary directory of the logged in user.

Easier using filenames in the context of network

To simplify the use of files within a network you can use filenames in

· Scriptmacro (see chapter FileSystemOpject and chapter Open in documentation OfficeTalk Scripting)

· Contextmenu Insert Dokument of description fields in dialogs (see chapter Insert Document in documentation OfficeTalk Business-Process-Management)

· Items Picture, Cancel-, OK- und Action-Button of a userdefined dialog (ScriptDialog) (see chapter Workbench in documentation OfficeTalk Business-Process-Management)

· Settings without userinterface using filenames (see chapter Settings without userinterface in documentation OfficeTalk Business-Process-Management)

with a symbolic prefix. This prefix is an entry of the OfficeTalk environment DocumentLinks or an environment variable of the current platform and names the directory of the file. For details please read documentation OfficeTalk Business-Process-Management, chapter Insert Document, File/URL.

Define a picture for a button of a userdefined dialog

With the new service label(<itemname>, with: <picturename>) of the system object ScriptDialog you can define a button with a picture instead of text. Because a picture says more than 1000 words. For details please read d ocumentation OfficeTalk Script, chapter label ( <Name>, with: <Variable> ).

Version 3.01 Build 12.11.2008

Using Microsoft SQL-Server version 8 or higher on Windows platforms

The settings for the Microsoft SQL-Server to use is corrected automaticly, when OfficeTalk is started on a client. The user is informed about the correction with a messagedialog. The correction is necessary, if Microsoft SQL-Server version 8 or higher is installed and on the client the systemservice for the SQL-Server is installed only. Only the Windows platform is affected by this change !

Using Microsoft SQL-Server Version 8 or higher

Because OfficeTalk can not decide in any case wether Microsoft SQL-Servers Version 8 or higher is used, you can prepeare OfficeTalk for using Microsoft SQL-Servers Version 8 or higher on a failure start with answering a messagebox.

Detailed message on problems for accessing the licence file

Detecting a problem when accessing the licence file you get a detailed message. On the plattform Microsoft Windows Vista accessing the lizence file after installation is sometimes not possible.

Opening the der BPM-Help in startportal with the menu Help-Content

In the testversion the menu opens after an additional question the help for the testversion or the default help for BPM. This choose is possible using the testversion only. Using the production version the menu opens the standard help for BPM as usual.

Extended general settings for message

In the general settings you can select default or large font for the text within messages. A large font makes messages, whitch contains important informations in general, more striking. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings, Tabulator General.

Version 3.01

Selecting an object within the group of DotNET components

The onlinehelp (editing macro Dim <variablename> As …) and the tabulators Arguments and Variables of the Workbench offered internal objects in the group of DotNET-components too. Because of possible misuse, these objects should not be used and are not offered anymore. The Windows-platform is affected by this change only !

Onlinehelp for services of the object Recordset from the communicationlibrary Microsoft ADODB.pcl

The onlinehelp for choosing a service did not offer since version 2.96 Build 03.03.2008 all available services of the object SmallCOM.ADODB.Recordset. The not offered services could be used, but where not offered by the onlinehelp.

Extended setting for scripts for making remote support easier

To make the remote support with a desktop-sharing system like z.B. PC-Visit easier, in the tabulator Scripts of the settings dialog a larger font can be selected for the macro’s text field. With this setting a remote visitor can read the macro’s source more easier.

Changed default settings for the background color in dialogs and toolbars

To use the background color of the settings from the OS, the option Standard in the General Settings uses the color settings of the OS, but not the OfficeTalk default setting anymore. In general you can define theese settings in the Systemcontrol of the OS. To use the OfficeTalk default color setting after the installation of this update, you must define theese colors in the General Setting by yourself.

Extended general settings for messages

In the general settings you can decide, wether the platform specific dialogs or the OfficeTalk specific dialogs for messages should be used. Both types of message dialogs have the same behaviour. Your design will decide the setting. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings, Tabulator General.

Storing system files on servercentric installation

To simplify a servercentric installation, write permission for the program directories of OfficeTalk (…\JOOPS GmbH\OfficeTalk and …\JOOPS GmbH\OfficeTalk\Bin) on the server must not be given any more, because the files for protocolling and diagnostic are stored in the users local directory.

Optimized process for generating the analyze

Creating the analyze results is accompanied be progressbars to show for a large analyze the current state and to enable the user to abort the analyze.

Version 3.00 Build 11.18.2008

Extended setting for creating a database macro with the Workbench

Creating a macro for a database action the settings for using the system service to comunicate with the database server can be given in the Workbench. This offers more flexibility for the use of the system services for databases. For details please read documentation OfficeTalk Business-Process-Management, chapter Databaseconnection.

Contextmenu Webservices in textfield of the script macro

Writing a macro the contextmenu Webservices did not show the services of a selected WSDL-Definition since version 2.99 Build 08.20.2008.

Version 3.00

Roundtrip-Engineering for business processes

With the assistant for optimisation of scheduletimes of a process the results of the real process execution can be transformed back into the process template. The planned times for execution can be optimized with the times of the real execution, the history. With this a process template can be put into a more real state on base of its execution history.
The contextmenu of the listfield in the tabulator Processtemplates supports for the assistant the new item Assistant for time optimisation. The assistant helps you in many ways to perform this optimisation. For details please read documentation OfficeTalk Business-Process-Management, chapter Assistant for time optimization.

Assistent for searching workers opened the first hit only

The assistant for searching worker content opened the first matched macro and not the selection dialog with all hits. Because of, only the first hit was opened independent of the count of matched macros.

Open the documentations on Linux-platforms with menu an toolbar

On Linux-platforms the documentations are not opened with the Help-menu and with the Help-button of the toolbar since version 2.99 Build 08.20.2008, sorry.

Version 2.99 Build 10.23.2008

Actualisation of the version at the worksation after update

After updating to version 2.97, 2.98 or 2.99 the version actualisation was done on the first workstation only. On all other workstation the message Database is updated now... ,a database access error war notified and the version actualisation was not performed.

Version 2.99 Build 10.21.2008

Using the database PostgreSQL Version 8.1 or lower

Usind the database PostgreSQL Version 8.1 or lower, an error message was displayed when reading an item containing a string with vovel (e.g. Scriptmacro).

Login as company after a reset of the workstation

Killing OfficeTalk with a reset of the workstation, all subsequents logins of the workers, whitch where logged in at the reset time, are denied because of possible double logging in. With the login as company this lock can be removed, as described. If the company was logged in at the reset time, this unlocking is not possible. In this case you are asked with tree additional questions to unlock the company, when you log in as company.

Version 2.99 Build 10.17.2008

Unneccessary save request for the local database

After a process template or a worker was exported and after using the process simulation and after openig the tasklist, saving the local database was requested at the end of OfficeTalk but nothing was changed. The saving was requested, using the local database only.

Automatic logout after no activities for a given time

To optimize the usages of the Concurrent Licences, OfficeTalk performs an automatic logout of the current logged in worker, if a given time not useractivity is detected. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings.

Version 2.99 Build 10.10.2008

Unfolding a worker in startportal Function-/Organigrambrowser

Unfolding a worker in the left listfield of the startportal Function-/Organigrambrowser displays all categories of the worker in the left listfield, and because of all items of the worker are accessible without additianal mouse clicks.

Version 2.99 Build 10.07.2008

Automatc sending the diagnostic file on program errors

If OfficeTalk notifys a program error, a diagnostic file is send to the support team OfficeTalk@joops.com. A send dialog is opened. In this dialog you can type in additional informations for the support team. If you close the dialog with the window close button, no diagnostic file is send. Only diagnostic informations about OfficeTalk are sent !

Dynamicly changing the format rules for an input field of an userdefined dialog

Changing the format rules for an input field with the service format(..., with: ...) of the systemvariable ScriptDialog after the dialog was opened, keyboard input into this inputfield was disabled.

Toggeling worker in the startportal Function-/Organigrambrowser

Toggeling a passive worker (Office, Department and Team) in the left listfield with the preceeded +/- selected the worker, but its details where not displayed in the right part of the window. The previous displayed information remained in the right part of the window and could be missunderstood. Now, toggeling a worker with the preceeded +/- displays its details in the right part of the window too.

Version 2.99 Build 09.29.2008

Ending with the window close button when using the startportal Function-/Organigrambrowser

Ending OfficeTalk with the window-close button in the dialog Function-/Organigrambrowser resulted first in an error message before OfficeTalk was ended. This happened after the using sequence "Double clicking in the organigram", any action, "Login", "Double clicking the Tasklist", "Scheduling process", or a similar sequence.

Version 2.99 Build 09.25.2008

Insert a new step into a process template with menu New - Step using the startportal Function-/Organigrambrowser

Inserting a new step with the menu New - Step into a process template terminated OfficeTalk with an error message. This happened under the startportal Functions-/Organigrambrowser using the menu New - Step only !

Executing a process with incomplete Mail settings

If a process was executed and the general settings in the tabulator Mail where incomplete, OfficeTalk ended with an error message, sorry.

Missing columns in database table stephistory using Microsoft SQL-Server

The first installation did not create two new columns in the table stephistory. As the result execution a process terminated OfficeTalk with an error message. The installation of an update created this two new columns right. This happened only, if Microsoft-SQL-Server was used, sorry.

Inserting a register into a userdefined dialog with the Workbench

Inserting a register into a userdefined dialog (ScriptDialog) with the Workbench was not possible since version 2.98.

Version 2.99 Build 09.19.2008

Starttime in tabulator Stepresults was changeable if step was opened throught the tabulator Common processtemplates

Opening a step when its process was opened in the tabulator Common processtemplates, the starttime in the tabulator Stepresults of the step was changeable without respect to the read only openmode of the process.

Shifting or selecting items (e.g. worker within the organigram)

Selecting or shifting a worker within the organigram produced is very rare situations and on very fast computers an error messsage and OfficeTalk terminated, sorry.

Create a substitute for scheduling a step

In tabulator Substitutes an assignement of a step for substituting was not possible, in contrast to the For:-combobox. Substitites for processes and categories could be created only.

New dialogitem for inserting a date with help of a calendar in userdefinded dialogs

A userdefined dialog (ScriptDialog) supports a button for choosing a date with the help of a calendar now. With this calendarbutton you can choose a date with help of a calendar and insert the selected date into the an input field. Inserting a calendarbutton is supported by the workbench and programmaticly by the sercive addCalendarButton(...). For details please read documentation OfficeTalk Business-Process-Management, Chapter Calendarbutton and OfficeTalk Skript, chapter Calendarbutton.

Version 2.99 Build 09.12.2008

Abort when saving on platforms Windows Vista

Saving changes in the local database aborted on Windows Vista platforms OfficeTalk with an error mesage (Permission access denied...) if write permissions for applications where missing for the directory ...\OfficeTalk\bin. The evaluation version was affected only !

Contextmenu Uses... in listfield of macros in the SkriptBrowser

The contextmenu contained wrong macros if a scanned macro contained a statement like Call <Skriptname>.Start("...", "...").

Menu New - Quickstep in dialog Processgraph: <name of process>

The menu New - Quickstep was in some situations enabled but not useable. Nothing happend if it was choosen, but the GUI must display the current state ever !

Contextmnu Open selected document in description fields

The contextmenu did not open the selected document, if the name ends e.g. with a point and the point was emphased with the hyperlink color (blue).

Delegation a process while scheduling to a worker may end OfficeTalk

If the process should be delegated while scheduling to another worker and the field Host: in the general settings for tabulator Mail was empty, OfficeTalk was ended with an error message, sorry.

Tabulator Ressources in simulationdialog

The tabulator did not display the sum of the cost of consumed resources as described, but the sum of the amount of the consumed resources.

Field next Step in simulationdialog

The field did not display the next step to be scheduled, but the first scheduled step ever.

Contextmenu Scheduling is of the step in dialog Processgraph: <name of process>

The contextmenu is not chooseable anymore, if the step contains start- or endaction and the selected scheduling option is not set to the step but to all contained useractions, if the step contains any useraction. This is conform to the processrules in OfficeTalk.

Version 2.99 Build 08.28.2008

Optimized removing of a step from the execition path in a process template

Removing a step from the execution path in dialog Processgraph: <name of process> and in the tabulator Processtemplates you get an additional question wether to remove the linking step results too. You get this additional question only if the step's position is at the end of a path. Under some rare circumstances not only the selected step but its successors where removed too.

Analyzing the processflow of a process template is extended

The dialog with the results of analyzing a process template's flow contains the new tabulator Empty stepresults. This tabulator displays the stepresults with no refenze to the next step. In general this is an error while modeling. For details please read documentation OfficeTalk Business-Process-Management, chapter Empty stepresults.

Installing OfficeTalk in a readonly directory

Installing OfficeTalk in a readonly environment, which is possible in a network installation, the very first start within the network was aborted with an error message, because the licence file must be actualized. Now, a production version can be installed in a read only environment. A evaluation must not be installed in a readonly environment, in general an evaluation is installed local.

Version 2.99 Build 08.20.2008

Changed settings for Applications

The entries within the groupsetting Applications must not be preceeded by a point (.) anymore. Please change the entries in Applications, if used. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings without userinterface, Applications\<Dateityp>.

Contextmenu Open selected document in all dialogfields with text

If two documentlinks where separated by a linefeed only, no document of both could be opened with the contextmenu. The contextmenu was answered with the message The document <link1><link2> is not found. Should the associated application be opened.

Version 2.99 Build 08.10.2008

Extension of the execution of a selected piece of a macro

Executing a piece of a macro with the contextmenu Execute in the macro dialogfield of the ScriptBrowser answers the result of the last statement, if the statement is able to return any result. e.g. An assign statement answer the content of the assigned variable.

Version 2.99

Changing the sequence of columns in the tabeled tasklist dynamicly

In the dialog Columns of the personal tasklist and in the dialog Columns of the group tasklist, both opened with the contextmenu Columns in the tasklist, you can change the sequence of the columns dynamicly with the mouse without reconfiguring all columns.

Cursor remains a clock

After opening the installed browser with an HTML-exported processtemplate, the cursor remains a clock. After clicking twize within the dialog, the cursor is restored to an arrow again.

Executing program returning results with no standard characterset

Executing in a macro a program or a batch with the funktion Shell or Shell Wait, whitch returns its results not with the default characterset, you must use the new argument Encoding. For details please read documentation OfficeTalk Skript, chapter Shell.

Search-Assistent for workers in all organigram dialogs

Searching for worker or content of a worker the Search-Assistent is restricted to the selected worker and its subordinated workers. If no worker is selected or the topmost worker in the organigram is selected, the Search-Assistent works as usual.

Timeprecision for human and machine oriented activities in a process

For the precision of time in the activities (Step and StepResult) of a process, scheduled by a human, seconds are not very important. Because of this fact, seconds for Steps and Stepresults, scheduled by a human, are not displayed in the tasklist and in the dialog Paths of the process: <processname>. Only for Steps and Stepresults scheduled by a machine, times are displayed with seconds. This makes the work with most processes a little easier.

Displaying the Stepresults in dialog Paths of the process: <processname>

The name of a Stepresult (the blue connectionline) is preceeded by a clock- or calenarsysmbol depending on the type of starttime of the next step. For details please read documentation OfficeTalk Business-Process-Management.

Importing a Processtemplate or a Script created with OfficeTalk version <= 2.00

Importing a Processtemplate in the tabulator Processtemplates with the contextmenu Import war aborted with the notifyer The file contains no valid Processtemplate, when the Processtemplate was created with version 2.00 or lower. You got the same result, importing a Script in the tabulator Scripts, when the Script was exported with version 2.00 or lower.

Version 2.98 Build 07.23.2008

Startportal Function-/OrganigramBrowser and contextmenu Subprocesses in dialog Paths of the process: <processname>

Running OfficeTalk with the startportal Function-/OrganigramBrowser and opening a subprocess of a step with the contextmenu Subprocessses opened the dialog Paths of the process: <processname> for this subprocess and ended OfficeTalk with an error message, sorry.

Version 2.98 Build 07.19.2008

Extended dialog for execution times and execution-paths of a process

The dialog Paths of the process: <processname>, opened with the menu Statistic - Times/Paths in dialog Processgraph: <name of process>, contains now for each path the consumed costs, if any action within the process is associated to a resource. Additionally the dialog is organised in columns and because of you can sort the displayed paths by each column (Minimum, Maximum, Cost, etc.).

Personal settings vs. Common settings

If a Personal setting obscured a Common setting, you got a message at the start of OfficeTalk. Answering the message with Yes, all Personal settings, whitch was able to obscure a General settings, where removed.

First start on a workstation

Starting OfficeTalk on a workstartion, after it was installed on the server, the message Error while creating the database schema... was shown since version 2.98 and OfficeTalk ended.

Tooltips in all dialogs presenting a kind of graph

Since version 2.98 not tooltip is shown for the item of a graph in the dialogs Tasklist, Processgraph: <name of process> and Organigram as graph, when the mouse touches an item of the graph.

Menue Extra - Flowanalyse in dialog Processgraph: <name of process>

Using the menuitem, OfficeTalk terminated with an error message since update 2.98, sorry.

Version 2.98 Build 07.11.2008

Service disable(...) of systemvariable ScriptDialog

The service disable(...) did not work for Textfields, editable Comboboxes and editable Inputfields with spinbuttons. An input by keyboard was possible in these fields in opposite to the contextmenu, whitch offers reading actions only.
With the Tab-Key you can leave fields, disabled with the service disable(...) too.

Startportal full and restricted. Browser on Windows-Platforms

Starting OfficeTalk with the full or restricted Browser as startportal resulted in an infinite loop since Version 2.98. OfficeTalk had to be terminted with the Taskmanager, sorry.

Version 2.98 Build 07.09.2008

Setting input focus in userdefined dialogs with service focus(...)

The input focus was set with the service f ocus(...) of the systemvariable ScriptDialog in an action (a ddAction(...)) to the following dialog item, if the action was activated by a Tab-key and not to the given dialog item.

Onlinehelp for service focus(...) while writing a macro

Typing in the service focus(...) of the systemvariable ScriptDialog did not show the available dialog items as e.g. typing in the service value(..).

Menu View - Functions+Organigram in dialog tasklist

With the new menu item Functions+Organigram you can hide and unhilde the left listfield of the dialog (functions and organigram), if the startportal Functions-/Organigrambrowser ist used. Hiding the left listfield supports more space in the dialog for the items, related to the tasklist. The default setting is compatible to the previous versions (left listfield is unhided).

Version 2.98 Build 07.07.2008

Inserting and importing script, processtemplate or worker in the evaluation version

After adding or importing a script, the menu for saving the changes was enabled. But saving the changes did not update the local database. This happened with importing a processtemplate and a worker too. Only the evaluation version with the local database was affected by this !

Saving an export (HTML, Worker, Processtemplate, etc.) into an existing file

If an existing file was selected for an export, the security question wether to overwrite the file was missing.

Version 2.98 Build 07.03.2008

Export Organigram and Processtemplate as HTML

The menue commandAs HTML... in dialog OrganigramBrowser and Processgraph: <name of process> open the HTML-dialog for the exportoptions. The button >> did not open the dialog for selecting the outputfile. Because of an Organigram nor a Processtemplate could be exported as HTML.

Version 2.98 Build 06.27.2008

Result of function Shell Wait contains bad characters instead of vovels on Windows-platforms

The result of the function Shell Wait contains bad special characters instead of vovels. e.g. The result of the function Shell Wait "dir" "c:\temp" contains filenames with bad characters, if a filename contains a vovel. This change affected the Windows-platforms only !

Testing selected lines of a macro while constructing a macro

If you select some lines within the dialogfield of a macro in the ScriptBrowser, and you choose the contextmenu Run oder Debug, you can run or debug the selected lines only. This is helpfull while constucting a macro for testing some parts of the macro.

Faster selection of a macro in the ScriptBrowser

Selecting a macro in the ScriptBrowser dialog is much faster now, especially for large macros with many Call functions.

Changes in tabulator Scripts of the General Settings dialog

Changing some values in the tabulator Scripts of the General Settings dialog leaved the menu File - Save grayed. To save theese changes, a value in another tabulator had to be changed.

Version 2.98 Build 06.19.2008

Using a variablename start, library, call or return in a scriptmacro

Using the variable name start, library, call or return in a macro, the onlinehelp for macrowriting opened the selectiondialog for the corresponding function instead of the selectiondialog for services of the systemvariable (if the variable was used for a systemvariable).Now you can use these names for the onlinehelp both (as function and as variablename).

Version 2.98 Build 06.10.2008

Open a step in the processgraph with the startportal Fuction-/Organigrambrowser

Opening a step within a processgraph with the contextmenu Inspect and the startportal Function-/Organigrambrowser is used, OfficeTalk ended with an error message, sorry.

New service page(..., register: ...) of the systemvariable ScriptDialog

The systemvariable ScriptDialog supports the new service page(..., register: ...). This service makes the working with a tabulator within userdefined dialogs more easier. The onlinehelp for writing a macro supports the service with page- and tabulator-selections. For details please read documentation OfficeTalk Skript, chapter page(..., register: ...) and documentation OfficeTalk Business-Process-Management, chapter Onlinehelp for completition of service page(..., register: ...).

Version 2.98 Build 05.28.2008

Modified functionality and return of the function Shell

The return of the function Shell is NULL and not a Boolean anymore. The function starts the given program and does not wait for it's end. Please check your macros for the correct use of the function. For details please read documentation OfficeTalk Skript, chapter Shell.

New function Shell Wait for script macros

With the function Shell Wait you can synchronize the calling of a program with the control flow of the macro. The function waits until the called program is finished. The function returns the stdout of the called program. For details please read documentation OfficeTalk Skript, chapter Shell Wait.

Version 2.98 Build 05.05.2008

Opening a macro containing locked dialog items with the workbench

Defining with the button Dialog locking some items to lock under some circumstances and reopening this macro with the Workbench, theese item where assumed to lock in any case in the item's property dialog.

Version 2.98 Build 05.03.2008

New function Call Super to execute a macro in a superior worker only

With the new function Call Super searching the macro to be executed is started at the superior worker. With this function a macro with the same name as the macro in the superior worker can be created in a workergroup (e.g. Department) to realize a different behavior for this group. When this macro is executed instead of the same name macro in the superior worker you can call the macro in the superior worker with the function Call Super. In the world of objects this in called Polymorphy. For details please read documentation OfficeTalk Skript, chapter Call Superscript.

Version 2.98

Following an item of a worker for all workers in OrganigramBrowser of the prortal Dialog

To follow the existence of e.g. a macro for all workers where a same named macro is contained, selecting a worker does not only open the same tabulator as the preceeder has opened, but tries to select the same named item in the tabulator as selected in the preceeder tabulator. This rule is valid in the portal Dialog only for all tabulators within the OrganigramBrowser dialog (menu Overview). This automatic selection mode makes the organisation of larger models easier.

Onlinehelp for displaying and selecting a service of a system variable on Linux-platforms

Calling the onlinehelpe while editing a macro (space + .) within the ScriptBrowser for displaying and selecting a service of a system variable resulted on Linux-platforms in an error message and OfficeTalk was terminated, sorry.

Anzeige und zur Auswahl eines Dienstes einer Systemvariablen resultierte nur auf Linux-Plattfomen in einer Fehlermeldung. Anschließend beendete Sich OfficeTalk, sorry.

Onlinehelp for dynamicly executing statements while debugging a macro

In the dialog Excuting statements in the context of the macros <name>, opened with the menu Execute statements, not all online helps where supported (e.g. displaying available dialog items).

New service values for simply retreiving complex results of a webservice

The systemvariables WSDLClient and WSDLStruct supports the new service values for retreiving complex results of a webservice. For details please read documentation OfficeTalk Skript, chapter WSDLClient and WSDLStruct.

Web-Wizard for selecting a Webservices while creating a script macro

The contextmenu of the source in the ScriptBrowser dialog contains the new item Webservice. This menu item offers all WSDL-schemas used within the macro. Choosing a schema opens a dialog with all webservices defined by this WSDL-schema. Selecting a webservice inserts it at the current cursor position of the source. The tabulator Webservice of the Workbench contains a new button with the same functionality for the WSDL-schema defined in the field URL:. A WSDL-schema can be defined with a filename and with a HTTP-adress. If a HTTP-adess is used, the schema is dynamicly requeste from the internet. For details please read documentation OfficeTalk Business-Process-Management chapter Contextmenu of the source and chapter Dialogs for creating macros.

Contextmenu Workbench for script macros using a Webservice

Opening macro for a Webservice using the service request(..., with: <Array>) resulted in the message Can not open the macro because it is not build by the Workbench....

Integration of webapplications with the HTTP-Request-protocol

With the new system variable HTTPClient the HTTP-request-protocol for communicating with webapplikations is supported. With this new system variable webapplications can be integrated in workflows not only with the SOAP-protocol, but with the HTTP-request-protocol too. For details please read documentation OfficeTalk Skript, chapter HTTPClient.

Version 2.97 Build 04.12.2008

Logindialog on each use of a WebService

When the service url(...) of the systemvariable WSDLClient was used to prepeare using a WebService, the login in the HTTP-Settings was ignored. Because of, the login dialog was opened on each use of a WebServive.

Version 2.97 Build 04.10.2008

If mandatory input is missing in an userdefined dialog

If a mandatory input in an userdefined dialog (systemvariable ScriptDialog in a skriptmacro) is missing, attention is given to the missing input with a red questionmark additionally to the notifyer. With this questionmark the missing input is identified more easy.

Version 2.97 Build 04.07.2008

New service focus() in systemvariable ScriptDialog

The systemvariable ScriptDialog supports the service focus(...) in userdefined dialogs. With the service you can set the cursor to a defined dialog item to give the user attention on a specific dialog item in special situations. The service is usefull in services with action blocks only ! For details please read documentation OfficeTalk Skript, chapter focus.

Dialogitem Option in a userdefined dialog

The service value("<name>") answered for a not selected option (some radiobuttons) in a userdefined dialog False instead of the expected value Null. Please check your macros for using this effect and adjust the affected sourcecode lines ! The workersearch for script macros containing *addRadioButton* finds the macros using options.

Statement addAction(...) in tabulator of a userdefined dialog

The statement addAction(...) in a macro, used as tabulatorpage of a userdefined dialog (ScriptDialog), was sometimes not executed when the content of the dialog item was changed.

Statement mandatory(...) in tabulator of a userdefined dialog

Using the statement mandatory(...) in a macro of a tabulatorpage did not test the content of the field at OK-button and the dialog was closed with no input.

Unneccessary request for saving using the evaluation version

Using the evaluation version a save was requested at a second login, but nothing was modified.

Start variant OfficeTalk/MS

With the update of version 2.97 an error was inserted into OfficeTalk/MS. After starting of OfficeTalk/MS the program was ended with an error message, sorry.

Default setting for Authorize for new Desks and Machines

For created Desks and Machines the Authorize is initialized to Inherit from Organisationunit instead of Inherit no rights. This is similar to the default setting for the Visibility. Especially for greater organisations, this behavior is more usaeble, because a Desk/Machine must inerit the permissions of its organisation unit.

Error message at saving using an evaluierungs version

Under reare cincumstances an error message appeared when changes are saved and OfficeTalk was terminated. This happened using the local database only ! The local database is used by the evaluation version most.

Onlinehilfe für die Anzeige von verwendeten Dialogelementen

Im Quelltextfeld eines Makros zeigte die Onlinehilfe bei Diensten, die ein Dialogelement als Argument erfordern (z.B. value(...), mandatory(...)) die gemeinsame Gruppe einer Option (addRadioButton(...)) nicht an. Damit konnten derartige Dialogelemente nicht mit der Onlinehilfe ausgewählt werden, sondern mußten manuell eigetippt werden.

Onlinehelp for the existing dialogitems in a userdefined dialog

In the source field of a macro, the onlinehelp for services, whitch requires a dialogitem (e.g. value(..), mandatory(...)) did not show the groupname for an option (addRadioButton(..group: <name>,...)). Because of this, such itemnames could not be added by the Onlinehelp, but must be typed in by hand.

Version 2.97 Build 03.31.2008

Executing dynamic statements within a stopped macro

In the debuggerdialog you can execute statenments of your own within the context of the stopped macro. With theese statements you can change e.g. variables of the stopped macro. For details please read documentation OfficeTalk Business-Process-Management.

Version 2.97 Build 03.25.2008

Reacting on doubleclicks in a list and table within an userdefined dialogs

With the Workbench you can insert into an userdefined dialog an action for a doubleclick in a list- and tablefield within an userdefined dialog. Therefore the systemvariable ScriptDialog is extended with the service addDoubleAction(...). With this doubleclick action you can work on a selected item not only by pressing a button, but with doubleclicking the item too. For details please read documentation OfficeTalk Business-Process-Management, chapter Propertydialog Action and Doubleclick and OfficeTalk Skript, chapter Reaction on a Doubleclick.

New services doubleClick(...) and press(...) of the systemvariable ScriptDialog

To react on doubleclicks in list- and tablefields within an userdefined dialog with an userdefined action and to use buttons in an userdefined dialog with actions the systemvariable ScriptDialog is extended with the services doubleClick(...) and press(...). For details please read documentation OfficeTalk Skript, chapter Systemvariable SctiptDialog.

Option Execute Aktion on each change in propertydialog of an Aktion in the Workbench

The option Execute Aktion on each change in the propertydialog of an Aktion was ignored on a succeeding opening of the macro with the Workbench.

Version 2.97

Processhistory extended by the planed execution time

The dialog of the processhistory is extended to show the delay of the execution time of a step. The textfield Start planned: contains the planned execution time of a step. In the filter dialog steps with a later execution time than the planned time can be filtered. For this extension OfficeTalk changes the database at start time. For details please read documentation OfficeTalk Workflow, chapter History.

Outdated services of systemvariable ScriptDialog

The use of an outdated service of a systemvariable ScriptDialog in a script macro resulted in the error message Unknown service <name>, but theese service where supported yet.

Callgraph of a macro opened from an action in startportal Function-/Organigrambrowser

If the Callgraph of a macro was opened in a ScriptBrowser, whitch was opened in an action, and the ScriptBrowser was closed before the Callgraph, OfficeTalk ended with an error message at closing the Callgraph. Now the Callgraph is opened in this case modal and must be closed first.

Empty items in dialog Processdata of a process

In the dialog of processdatas, opened with the contextmenu Processdata of a process in the tasklist, empty items where displayed with the text Null. Now for empty items an empty line is used too.

Menu View - Settings in dialog Processgraph: <name of process>

Changing the settings for Labelposition in the settings dialog resulted in an error message and OfficeTalk was ended, sorry.

New splitterbar in tabulator Processtemplates

The tabulator Processtemplates contains a new splitterbar between the description field and the steplist, to be able to adjust the description field for a larger text.

Version 2.96 Build 03.07.2008

Evaluation boolean Or-expressions in a script macro

The right argument of a boolean Or-expressions was evaluated in any case without respect to the evaluation result of the left argument. e.g. In condition If (var1 = True) or (var2 = True) then ... End If the expression(var2 = True) was evaluated although the left argument evaluated to True.

Contextmenu Open marked document... in all documentation fields

The contextmenu could not open hyperlinks containing spaces. Instead of, you got the message The document <name> could not be found. Should the associated application be opened instead.

Version 2.96 Build 03.03.2008

Some filenames of documentations changed

The filenames of the documentations for communication libraries are changed inJOOPS GmbH\OfficeTalk\Help:

Old filename | New filename | Description
MSSQLForOfficeTalk.pdf | ADO.pdf | Communication library for all ADO-compatible databases
OracleForOfficeTalk.pdf | Oracle.pdf | Communication library for a Oracle-database
DocuWareForOfficeTalk.pdf | DocuWare.pdf | Communication library for the DMS DocuWare

You can delete all old documentation files after the update.

Windows-Platform: Version 1.10 of the communication library for ADO compatible database access

On all Windows platforms the default distribution does database access within script macros by using ADO 2.7 instead of the older ADO 1.0 now. Because of, the programfile msado10.dll must not be installed and registrated anymore. ADO 2.7 is based on the programfile msado15.dll and this file is installed on your comuter by the installation of Windows. If msado15.dll is missing on your computer, you can install it by installing of MDAC. You get the current version of MDAC from msdn.microsoft.com/data/ref/mdac/downloads. Using ADO 2.7 some problems on Windows-Vista computers (e.g. SmallCOM.ADODB.Connection New -> results in error message Missing licene for class ...) should be solved. If you want to use ADO 1.0 further, change in the relevant macros the statement Library "..\Library\MSADODB.pcl" to Library "..\Library\MSADODB10.pcl".

Version 2.96 Build 02.28.2008

Services for dynamicly creating macros within a macro

You can create new macros insine a macro. For this functionality the system variable worker supports some new services. The processtemplate for building a macro to fill out a document is an example of theese new services. For details please read documentation OfficeTalk Script, chapter Systemvariable worker.

Contextmenu History... in the Tasklist

Since version 2.96 using the contextmenu History... in the dialog of the tasklist terminated OfficeTalk with an error message, sorry.

Version 2.96 Build 02.21.2008

Storing content of a dialog item into a variable with the Workbench

Storing the content of a dialog item with the propertydialog in the workbench into a macro's variable build the macro the first time in the right way. But if the macro was reworked with the workbench, theese statements where put into the tabulator Termstatements. Because of building the macro the next time created wrong statements for theese dialog item targets.

Version 2.96 Build 02.19.2008

Onlinehelp for services of the systemvariables

The onlinehelp for services in the script macro editor does not contain the old services of systemvariables. Theese old services are supported by the workflow engine, but should not be used anymore.

Better error recognition in service mailFrom(...) of the systemobject Mail

The error recognition of using the service mailFrom(...) is optimized. In the past, a wrong argument may be notified, if a bad argument was used. This was a little confusing. Additionally the validation of all arguments is optimized. e.g. Using an empty receiver mailadress is notified with a propper error mesage.
And some servicenames where renamed for a better understanding. The old names are available, but should not be used anymore. For details please read documentation OfficeTalk Script, chapter Systemvariable Mail.

Version 2.96 Build 02.8.2008

State of menu- und toolbar in dialog Processgraph: <name of process>

The state of some toolbar buttons and menu items was displayed wrong in some situations. e.g. The menu New - Step was enabled but nothing happened if choosen. Because of the user usability a menu should reflect the current state !

Modifying arguments of type Array within the macro

For safetyness modifying any argument within the macro is not allowed. To make the transport of data between macros easier, modifying an argument of type Array is allowed now. Modifying an Array changes the Array in the caller macro too.

Onlinehelp for the servicenames was not opened under special circumstances

If the name of the variable and the name of the macro was equal, the onlinehelp for the possible servicenames of this variable was not opened.

e.g.: Dialog(....)
...
Dim dialog As ScriptDialog
...

Under above circumstances typing in dialog. did not open the onlinehelp of the available servicenames.

Selective export of workers

In the different Organigram dialogs you can export a single worker by selection this worker and answering the following question with Yes. In the past, you had to login as the worker, to export this worker only. For details please read chapter Save as HTML... in the documentation OfficeTalk Business-Process-Management.

Version 2.96

Selective export of process histories

In the history dialog History for: <processname> of a process template you can define what histories should be exported by selecting the requested lines. In the past all visible histories where exported. To export a single history, you had to set the view settings for this history. For details please read chapter Histories in the documentation OfficeTalk Business-Process-Management.

Setting for All processes in Group Tasklist

The setting was forgotten after the programm end if the logged in user was not a mainuser (on Windows-platforms), or did not have write permission to the common settings OfficeTalk.ini (on Linux-platforms).

Accellerated opening of the tasklist with many tasks

If you have many tasks in your tasklist, you can accellerate the opening with setting the displayed processes with the menu View - Select by to the current year, month or day.

Version 2.95 Build 01.31.2008

Export Organigram in graph dialog as HTML

With the new menu item Organigram - Save as HTML... you can export tho opened organigram, like in the Organigrambowser- and Organigramdialog, as HTML-File. In difference to the other saving variants the picture of the organigram is stored as a graph.

HTML-Export of an organigam in the organigram dialogs is extended

The HTML-export, started with the menu Organigam - Save as HTML in the organigram dialogs can now export all items, owned by a worker. Theese are Permissions, Absents, Substitutes, Resources and Processtemplates. To enable this extension the export dialog Options for HTML-export is expanded. With this extension you can export a hole organisation unit with all its owned items up to a complete organisation. For details please read documentation OfficeTalk Business-Process-Management chapter Organigram, section Save as HTML.

Version 2.95 Build 01.28.2008

Extended process for installation

An additional installationprocess is available. The installationmedia is responsible for the type of installationprocess. The new process does not define the database system to be used. You must select the database system at the first start of OfficeTalk with a database selection dialog. For details please read documentation OfficeTalk Installation.

Version 2.95 Build 01.25.2008

More save process for installation and update and for changing common settings

For installalling and updating OfficeTalk you must own write permission for the common settings. Theese processes resulted in the past in obscure results. Now, theese processes are aborted with an error message, if the logged in user miss the required permission. For details please read documentation OfficeTalk Installation.
Changing common settings without required write permission was ignored without notification in the past. Now theese values are stored into the user oriented setting, if write permission for the general setting is missing, and you are informed about this fact with an information dialog. For details please read documentation OfficeTalk Business-Process-Management chapter General settings.

Version 2.95 Build 01.22.2008

Automatic scheduling of a started process

Starting a process with the function Start in a script macro, schedules the started process too, if the process is ready to run and the scheduling of the current process is finished for now (see service waitFor(...)). With this automatism the fluently execution of a complex task is more optimized. For details please read documentation OfficeTalk Script chapter Functions, Part Start.

Version 2.95 Build 01.16.2008

Extended dialogs for displaying the usings of resources, scripts, macros and morkers

All dialogs for displaying the usings of resources, scripts, macros and workers are extended. The results are organized by rows and columns. You can sort the results by different criterias and because of analyze easier. The columns of a row contain the propper symbol for the entry to handle the results easier for visual oriented peoples.

Version 2.95 Build 01.11.2008

Display organigram depending on the type of task

Depending on the type of your task you can organize the organigram in different ways. Espezially for big organisations this in an efficient way to do organsiational tasks. For details please read documentation OfficeTalk Business-Process-Management chapter General settings.

Selection dialogs of the onlinehelp while writing a script macro

All selection dialogs of the onlinehelp (Script/Macro-, Process-, Return-, Resourceselection) are optimized. Each column of the lines in theese dialogs are preceeded with their associated symbol. Visual oriented humans are able to indentify the content of theese dialogs. For details please read documentation OfficeTalk Business-Process-Management chapter Onlinehelp for input of source.

Dialog <workername> is used in

Changing in the dialog, opened with the context menu Usings... in the listfield of an organigram, the scheduling worker and cancelling the changes with the window close button, OfficeTalk terminated with an error message, sorry. Closing the dialog with the button Close, those changes where lost after the next start of OfficeTalk.

Used space in all listfield within dialogs

The space in listfields with entries leaded by an icon is used more oconomic. More lines fit into a listfield and you can see more information without using the scrollbar.

Version 2.95

Analyzing the structure of calls of script macros

If a macro calls with the statement Call other macros and theese macros call further macros, the result of this hole call structure may become complex. With the new context menu Callgraph... in the right listfield (the macrolist) of the ScriptBrowser you can inspect the call structure of the selected macro and change macros within this call structure. For details please read documentation OfficeTalk Business-Process-Management.

Analyzing the control flow over the borders of a single script macro

Now you can anlayze the contol flow over the border of a single macro and as the result you can validate the logic of the control flow before the macro is used by a process. To do this, the context menu of the listfield of the macros in the SkriptBrowser dialog contains the new menu item Uses.... This item contains all called macros within the selected macro (function Call). Choosing such an item opens the SkriptBrowser dialog for this macro. There you can repeat this game. With the item Back you can traverse back the inspected macro hiraychy. For details please read documentation OfficeTalk Business-Process-Management.

Sorting process histories extended

The process histories, opened with the contextmenu History in the tabulator Processtemplates can be sorted by start and end date. For this extension the menu View-Sort by was expanded with the new item Enddate-/time. With this new sorting mode you can analyze the finishing of the processes easier.

Opening a locked worker in the OrganigrammBrowser's dialog

If a locked worker (e.g. he has logged in on another workstation) was selected in the left listfield, you got the message The worker is opened read only..., but the input fields of its adress dialog where editable.

Version 2.94 Build 12.11.2007

Exporting a worker in variant OfficeTalk/MS

Exporting a worker with the contextmenu Export in the listfield of the OrganigramBrowser dialog, the fact, that the MS-variant does not handle processes was ignored and therefore OfficeTalk was hanging. It had to be ended hard (Taskmanager on Windows-platforms or kill 9 on Linux-platforms).

Importing a worker with the contextmenu Import in the listfield of the OrganigramBrowser dialog

Using the contextmenu Import resulted since the Version 2.94 Build 12.8.2007 in an error message an OfficeTalk ended abnormaly.

Version 2.94 Build 12.08.2007

Menu Save and toolbarbutton Save in the portal Function-/Organigrambrowser using the local database

Changes in the dialog Processgraph: <name of process> or in another dialog with the menu Save where, because of the optimization for the local database, not saved in real and the menu Save and the toolbarbutton Save in the portal Function-/Organigrambrowser where grayed and does not reflect the current change state.

Version 2.94 Build 12.07.2007

Contextmenu Responsibilities in tabulator Processtemplates

Using the contextmenu Responsibilities for a process template in the tabulator Processtemplates resulted in an error message with ending of OfficeTalk.

Delaying a step's execution in the dialog Step '<name>' schedule

Delaying a step's execution by closing the dialog Step '<name>' schedule with the window close button and answering the succeeding question with Yes, OfficeTalk was aborted with an error message, sorry.

Double clicking a worker in the portal Function/Organigrambrowser

Double clicking with the mouse a worker in the left organigram listfield of the portal Function-/Organigrambrowser aborted OfficeTalk with an error message, sorry.

Function StrComp and message Variable <name> is not used... when compiling the macro

If a variable was used as the second argument of the function StrComp only, this variable was noted as not used and after removing the declaration with answering the message with Yes, this variable was noted as not declared again !

Displaying a macro containing funktion StrComp and activated Syntaxcoloring

If a macro contained the function StrComp with the argument Comparemode, Sytnaxcoloring must be dactivated in the general settings for opening the macro with the Scriptbrowser dialog.

Displaying the variable Error within the dialog of the Skriptdebugger

If the variable Error contains informations about an error (a Catch-Block was reached), you can expand the variable by double clicking it within the variable list top right and see the details of the raised exception (Source and Description).

Dynamic changing of a variable's content in the Scriptdebugger's dialog while the macro is executed

The variabledialog with whitch a variable's content can be changes in the dialog of the Scriptdebugger behaves like the type of the variable. An illegal input for the variable is notified. A variable of type String (Dim <variablenname> as String) with the content exceeding the limit of 1000 characters or containing a CR or LF is opened with a special dialog for text. In the past such a string was cutted to the maximum of 1024 characters. For details please read documentation OfficeTalk Business-Process-Management, chapter The Debuggerdialog and OfficeTalk Skript, chapter Stringsyntax of Variables.

Function ChrB in scriptmakro

The function created in the past a String with the given character. Now the result of the function is a real Character. This change should not affect existing macros, but for safty check the macros using the function ChrB.

Version 2.94 Build 11.30.2007

Extended validation of arguments in a systemvariable's service

Executing a script macro, the arguments of a systemvariable's service are validated more detailed. Using a service with an argument of wrong datatype resulted in the past in an error message describing not the wrong argument but the resulted error. Now, you get an error message whitch describes the wrong argument without performing the service. e.g. The service processdata.item(100.10, in: "groupname") uses the Integer variable (100.10) instead of a String variable and an error message was produced, whitch did not describe the argument with the wrong datatype, but the resulted error. Now you get an error message whitch describes the argument with the wrong datatype (100.10). For details please read documentation OfficeTalk Script.

Version 2.94 Build 11.28.2007

Error message on opening a macro with the Workbench containing a dialog item using a cascaded function

Opening a macro with the context menu Workbench in the ScriptBrowser, which contained e.g. a statement addInput using a cascaded function to get the field content (addInput(process.currentStep.startAt.date,.....)), was denied with the error message The macro was not build with the Workbench....

New services currentStep and scheduleAt(...) in systemvariable process

For special tasks the systemvariable process supports two new services for affecting a process. For details please read documentation OfficeTalk Script, chapter Systemvariable process.

New service isLoggedIn in systemvariable worker

To decide wether a worker is currently logged in, you can use the new service isLoggedIn of the systemvariable worker. To ask a worker wether logged in, you must first get the worker to be asked by stepping the worker hirarchy. For details please read documentation OfficeTalk Script, chapter Systemvariable worker.

Version 2.94 Build 11.24.2007

Extended function MousePointer in script macro

The funktion returns the name of the previous mousepointer. So, you can reset the mousepointer to the prevoius state without knowing it.

Allowed characters for process template names in Category and Term

In the past all special characters (+,-,/, etc) in the input fields Category and Term of process templates where forbidden. This limitation is disabled to make more readable names possible.

Wrong expression in tabulator Return of the Workbench was not notified

Inserting in the expression field of the tabulator Return in the Workbench a wrong expression was not notified, when the soure of the macro was created with the button Create. Now leaving the tabulator with a wrong extression is notified like in the other tabulators and you must first correct the expression.

New service entries of the systemvariable processdata

The new service entries answers all groupnames in the processdata of a process. e.g. It can be used, to copy all processdata from one process into another process. For details please read documentation OfficeTalk Script, chapter Systemvariable processdata.

Working with the local database is accellerate

The local database required in the past the saving of any changes. Now changes are saved on ending of OfficeTalk or on an user request with the menu Save. This change affects the variants using the local database only and accellerates this workflow dramatically. In general the evaluation version uses the local database only.

Error when using the menu Work - Pfath as new Processtemplate in dialog Processgraph: <name of process>

Using the menu Work - Pfath as new Processtemplate in the dialog Processgraph: <processname> aborted OfficeTalk with an error message, sorry. This occured since Version 2.94 Build 11.12.2007.

Error when using the contextmenu Hirarchybrowser in tabulator Processtemplates

Opening the Hirarchybrowser for a processtemplate with the contextmenu Hirarchybrowser in tabulator Processtemplates resulted in an error message and OfficeTalk was terminated, sorry. This occured since Version 2.94 Build 11.12.2007.

Missing function templates in context menu Functions in the source field of the scriptbrowser dialog

The menu items for the templates of the functions Line, Input Line and Print have been missed and where added.

Version 2.94 Build 11.15.2007

New service quote(...) of the systemvariable stepscheduler for script macro

With the service quote(..., in: ..., with: ...) you can quote a given character with another given character within a string. For details please read documentation OfficeTalk Script, chapter Systemvariable stepscheduler.

Compiling a Startmacro without Return

If a Startmacro (option Startmacro is selected in the Scriptbrowserdialog) without Return is compiled, you are notified about and the compilation is stopped, because a Startmacro without Return is an error in general.

Function MsgBox of the script macro without icon

Using the function MsgBox without an icon aborted OfficeTalk with an error message, sorry. e.g. MsgBox("Do you want to search the adress", vbYesNo). Using the function with an icon worked well. e.g. MsgBox("Do you want to search the adress", vbYesNo,vbQuestion)

Version 2.94 Build 11.12.2007

Dialog Pocessgraph: <name of process> and Organigram for: <name of worker>

Menue and toolbars of both dialogs are extended with often used functions. e.g. Insert new step/worker. Because of working with theese dialogs is a little more easier, in using the functions with shortcuts too.

Accellerated selecting and deselecting in the dialogs Processgraph: <name of process> and Organigram for: <workername>

Selecting and deselecting a step/worker within theese both diagram dialogs works mutch faster now. So working within theese dialogs is much easier especially with great organigrams or process templates..

Answering message- and questiondialogs displayed with the OfficeTalk format

If you use for message- and questiondialogs the OfficeTalk- but not the platformformat, you can answer the dialog with the first character of the required button's name too. Because the first character is not underlined, you need not press the ATL-key additional. On a Windows platform this is the general rule. On a Linux platform you can answer theese dialogs in the same manner, if you use the OfficeTalk format for messages. You define the format to be used with the environment Message. For details please read documentation OfficeTalk Business-Process-Management.

Closing the Organigramoverview- or the Organigramdialog in the startportal Dialog

If from both dialogs a Usingdialog (Worker, Script, Resource, etc.) or an Analyzedialog in the dialog Pocessgraph: <name of process> was opened, and within this opened dialog subsequente dialogs where opened (e.g. a step in tabulator Empty Steps) and the base dialog of the organigram was closed, the Analyze- or Usingdialog remained opened. Opening an item within a tabulator of the Analyzedialog resulted in an error message and OfficeTalk was ended, sorry. This is a very special using, but OfficeTalk should not make possible such usings !

The result dialog of a workersearch was non closed in any case using the startportal Dialog

The result dialog, the found workers, was not closed in any case if its Organigrambrowser- or Organigramgrapghdialog was closed. Trying to open a found artefact after resulted in a programm abort with an error message.

Tabulator Return in Workbench dialog with a wrong expression

The tabulator Return with a wrong expression in the inputfield Expression could be leaved. Now a hint at the error position is displayed and the leaving is denied.

More better search for a Return name in Workbench and in Sciptbrowser

The dialog Select a Returnname, offers the Return names useable in a macro. In the past all existing Return names where offered in a Skriptbrowser and in a Workbench. Now in theese situation the dialog tries to find out, in whitch context (steps) the macro will be used and offers the results of theese steps only, like the script macro editor started within an action. This optimisation does not work for a macro with arguments because such a macro will not become a start macro.

Create a new process template in tabulator Processtemplates in the worker dialog

If a new process template was inserted with the New-button into the left listfield only without saving the template with the menu File - Save, succeeding inserted steps in the dialog Pocessgraph: <name of process> where not really saved. Now you get a message dialog in such cases and answering Yes saves the template automaticly.

Wenn die Vorgangsvorlage nur mit der Schaltfläche Neu in das linke Listfeld der Vorgangsvorlagen übernommen wurde ohne diese auch mit dem Menueintrag Speichern zu speichern, wurden u.U. die nachfolgend im Dialog Ablauf des Vorgangs: <Vorgangsname> eingetragenen Arbeitsschritte nicht dauerhaft gespeichert. Jetzt werden Sie mit einer entsprechenden Meldung darauf hingewiesen und bei Beantwortung mit Ja erfolgt die Speicherung automatisch.

Extended menue View - Workercontent in startportal Function-/Organigrambrowser

The menueitem Workercontent is divided into All and Processtemplates. The item All is the previous item Workercontent. It displays all setting and content of the workers within the left listfield. The menu item Processtemplates display the process related worker content only. Depending on the type of task you can select the optimal setting. All is best if you must manage the worker and their content. Processtemplates is morr better if you must work within the process templates of the workers. For details please read documentation OfficeTalk Business-Process-Management.

Dialog All inheerited and own permissions for: <workername>

The diaog, opened with the button all Rights in the tabulator Authorize, shows all rights of a worker now. In the past the rights inherited by the used organisation where not displayed. Now theese rights are shown too, because the worker inherits theese rights too.

Export of a company missed some settings

If a company was exported, the setting of a named worker in the tabulator Visibility, Adposvisibility and Permission where not exported and where missed after importing this export. The export opened a notifyer, whitch displayed such missing exports.

Not all parallel opened windows where closed unsing the startportal Function-/Organigrambrowser

If OfficeTalk was started with the startportal Function-/Organigrambrowser, in some rare situations parallel opened windows like Usings stayed open after closing the main window with the window close button.

Contextmenue Remove in the organigramlist dialog

The contextmenu Remove could be choosen for used workers too (e.g. a worker is reponsible for the execution of a step). In such a case you got an error message like Primary key can not be... and the removing was cancelled. Now in such cases the contextmenue is grayed and not useable anymore.

Menü Work - Path as new processtemplate in dialog Processgraph: <name of process>

If only one step result was selected and this menu was choosen, OfficeTalk was aborted with an error message, sorry.

Variant OfficeTalk/MS and menu Extra - Importmapping

Choosing the menu in the startportal dialog OfficeTalk/MS was aborted with an error message, sorry.

Menu Extra - Importmapping in the Startportal dialog

The menus Save and Save and close in the dialog The mapping of the attributes where ever enabled without respect to the changestate of the mappings. Now theese menus are enabled if the mapping is changed only, because saving an unchanged mapping does not make any sense..

Removing step results

In a process template a result could be removed without respect to the succeeding steps. In some situations succeeding steps where unlinked from the process template's flow. In the tabulator Stepresults of the step dialog and in the diagram flow Processgraph: <name of process> removing was allowed. In general this is a false using of the process mabagement by the user, but OfficeTalk should permitt such kind of user errors.

Extended onlinehelp while writing a script macro

The dialogs of the onlinehelp for selecting and setting parameters of the statements Call, Start, stepscheduler.consumed() und Return are extended. Theese dialogs are all organized with columns for sorting the contents by different order to find a requested value easier.

Login for active and passive workers

The login is required for an active worker (Desk, Machine) only. For a passive worker (Department, Office, Team) the login is not mandatory anymore, because it must not be able to login. This kind of worker may exist for organisational matter only.

Version 2.94 Build 10.16.2007

Update from 2.90/1/2 with used Microsoft-SQL-Servers 8 or higher

Trouble and pain for us ! Using the Microsoft SQL-Server 8 or higher did not add at the first run the needed table adoptvisibility in the database and most of the succeeding work was not possible. But this happened only using Microsoft SQL-Server 8 or higher !

Version 2.94

Extended dialog All inherited and own rights of: <workername>

Activating an entry in the dialog opens the dialog of the worker, containing the right, with the tabulator Permissions and the activated right. With this dialog you can organize the permissions within a workerhirarchy in an easier way. For details please read documentation OfficeTalk Business-Process-Management, chapter Register Authorize.

Tabulator Absents/Offline in workerdialog extended

The tabulator contains the new button all Absents.... The button opens a dialog with all relevant absents for the worker. With this dialog you can organize the absents within a workerhirarchy in an easier way. Activating an absent opens the worker, containing the absent, with its tabulator Absents and the activated absent. For details please read documentation OfficeTalk Business-Process-Management, chapter Register Absents/Offlines.

Missing environment variable on Linux-Platforms

On Linux-Platforms the environment variable OFFICETALKMESSAGES is required. Starting OfficeTalk with a missing environment variable opened an empty window and the OfficeTalk's task had to be ended with kill 9. In general, the setup routine creates this environment variable. Now, if the environment variable is missing, you get an extra warning when starting OfficeTalk.

Contxtemenu Copy in the listfield of the historydialog

Using the contextmenu Copy for the entries Scheduletime and Runtime terminated OfficeTalk with an error message. It makes no sense to copy theese entries to the clipboard, but OfficeTalk should ignore such invalid ctions, sorry.

Version 2.93 Build 10.10.2007

Tabulator Worker and History in dialog of a simulating a process in dialog Processgraph: <name of process>

If the current scheduled step is executed by the current worker, the same worker as the last step, in the two tabulators this last real worker is archived. In the past for this kind of step the unnamed current worker was archived. For details please read documentation OfficeTalk Business-Process-Management, chapter Register Simulation.

Simulation of the processflow in dialog Processgraph: <name of process>

The simulation (menu Simulation-Start and -Open) ot the processflow is better simulated visually:

- The step's symbol is animated to the next step before it is executed.
- The executed times are displayed within the step similar to the normal execution.
- The executed steps are colored with the execution color.

With this extension you can easier follow the processflow. For details please read documentation OfficeTalk Business-Process-Management, chapter Register Simulation.

Menu File in dialog Function-/Organigrambrowser

The menuitems Close and Save and close in the dialog Function-/Organigrambrowser are labeled Back and Save and back to detail the user, that the dialog is not closed here, but it jumps the hirarchy of visited dialogs one step back. The menuitem Back is additional labeled with an back arraow.

Version 2.93

New tabulator Adoptvisibility for active workers

All kind of worker dialogs for active workers (Desk and Machine) contains the new tabulator Adoptvisibility. With this setting you can specify the company units whoose tasks the worker can see in its adopt part of the tasklist. e.g. The worker should see the tasks of its own department only in opposite to its general visibility settings where he must see the hole company for starting some processes.
When starting the version 2.93 the first time, the required extensions in the database are made and notified with messages.
For details please read documentation OfficeTalk Business-Process-Management, chapter Tabulator Adoptvisibility.

Version 2.92 Build 09.28.2007

Aborting when the Workbench is used for a failure macro

If the workbench is used (contextmenu Workbench in scriptbrowser) for a macro with a false statement addGroupbox(...), OfficeTalk is terminated with an error message. This happened when the named of the surronding items where wrong given by hand in the statement addGroupbox(...). In general this is an user error, but OfficeTalk should ignore such errors.

Labeling of horizontal connections in dialog Processgraph: <name of process>

The labeling of horizontal step results (blue connection lines) without time setting is optimized for a better reading.

Dialog for database login with LRU list for Environment

When logging in, OfficeTalk remembers the used environment name and offers all used names in a combobox. Because of you can easier switch between different databases if neccessary.

Extended menu and extended toolbar in all tasklists of the portal Function-/Organigrambrowser

Using the portal Function-/Organigrambrowser all dialogs of the tasklist contain the new menu File and the new toolbar button painted as a key. With theese you can login and logout without need of selecting a worker function in the left list field.

Version 2.92 Build 09.17.2007

Changing the selected worker in the Organigrambrowser

If a tabulator of the worker contained incomplete values, and another worker was selected within the left listfield of the Organigrambrowser, the incomplete item was stored without warning. All other steps notified the user about the incompletness and denied saving.

Searching in organigramdialog for worker by a permission

If the permission pattern for searching was given the category only, the result contained permissions with this category but with any additional name too.

Differrent case writing of arguments resulted in an error message when executed

If an argument's case was written different to its using in opposite to a variable, you got an error message (Variable ... was not found...) on the macro's execution.

Inserting a Groupbox with the Workbench in a Scriptdialog

The button Build in the Workbench dialog created a wrong statement for a Groupbox in the macro. The contained items where written with double ". To compile the macro you had to remove the double " first by hand.

Searching for a macro with menu Searching in the Organigramdialog

Searching in all kind of organigram dialogs a macro with the menu Searching... may display the wrong result if the found macro and the displayed macro differed in their arguments only.

Version 2.92 Build 09.10.2007

Searching worker in organigramdialog as graph

Searching for permission, resource and processtemplate resulted in an error message witch terminating of OfficeTalk after opening the found worker, sorry

Extending the menu Search worker

For inspecting the found workers in sequence with the menu Search worker in all kind of organigram dialogs double clicking a found worker closes the found workers dialog not any more. You must not start the searching process for each worker now.

Version 2.92

Worker is informed about processes whitch must be scheduled by mail

If a new process is started for a worker or a process is delegated to a worker and the new option Send mail on delegation is set in the tabulator Tasks, the worker is additionaly notified with a mail about the new work. With this new feature a worker should be informed in any case about a new process to schedule no matter wether he has started OfficeTalk. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings.

A process waits for the end of another process

If a process has to wait for the end of another process (dragging it to another process within the tasklist or service waitFor(...) within a script macro), the step of the process, for whitch has to be wait, is scheduled automaticly next, if the required conditions match. You must not do an extra doubleclick to begin its scheduling anymore. If OfficeTalk recognizes, that a process has to wait for the end of another process, and this process can be scheduled, OfficeTalk schedules it automaticly.

New service refresh in the systemvariable processdata

If an extern system manipulates the data of a process in OfficeTalk, they must be actualize with the service refesh in the macro before reading.

Version 2.91 Build 09.5.2007

Seconds installation with using DB2- or Oracle-database server

Deleting the OfficeTalk-database and recreating it with the installation of OfficeTalk prohibited from process scheduling in the newly installed system, because some behaviour of this two servers was responsible not to find required data for schedulung.

Startportal Function-/Organigrambrowser and executing the contextmenu Usings in the tabulatorr Resources

Running OfficeTalk with the startportal Function-/Organigrambrowser, the using list of a resource was opened inside the startportal dialog, in opposite to the usings of a script. Because of, enumerating all usings was a little bit unhandy. Additionally the contextmenu Open in the using listdialog opened not the exact using location (the action) of the resource, but its step only. So each action had to be visited, to find the exact using location.

Onlinehelp for inserting a class/datatyp

Typing in a space in the startline of a macro or in the New-statement did not open, as documented, the onlinehelp for inserting a class/datatyp.

Version 2.91 Build 08.31.2007

Refreshing the processes with the menue item Refresh

With the context menue Refresh and the same named menue item in all tasklist dialogs the content of the Personal tasklist, the Take-Over taskliste and the Group tasklist is refreshed about 20 % faster.

Version 2.91 Build 08.17.2007

Adopting new startet processes from the adoptlist

If a process was because of his definitions started into the adopt list, the message Do you want to adopt the process did not appeare without respect to his scheduling possibilities.

Displaying the processes in the tasklist of an organisation

If you where logged in as company, department, office or team, and the tasklist was displayed as browser, the processes where not displayed with their colored symbol, but with the symbol for a processtemplate.

Scheduling new started processes in the browser tasklist

If the tasklist was opened as browser, new processes could be started but not scheduled correctly. e.g. The system variable processdata was undefined within script macros. This happened using the tasklist as browser only !

Extended onlinehelp for the Return statement

It the scriptbrowser is opened from an action page of the stepdialog, you get an extended onlinehelpdialog for a return statement. Within this dialog you can see for each return the next step and its scheduling worker. With this information you can easyer select the right result.

Onlinehelp for the declarations with required classes/datatypes is extended

Writing an element with a required class-/datatypename (Dim, New) the onlinehelp opens the available names in a browser-like dialog. Within this dialog the required name is found easyer because of the groupings.

Onlinehelp for choices in dialogelements Listfield, Combobox and Table

Typing in the statements for the choices in the named dialog elements, the well known onlinehelp is available now. Because of creating such elements is a little bit easyer.

Using the function MsgBox in script macro with extended arguments

If the function MsgBox was used with extended arguments, OfficeTalk aborted under rare constellations, sorry.

Service anyEnvironment(<Name>) of the sytemvariable stepscheduler

The service gets the entry <Name> of the settings. The entry is retreived form ther user oriented setting. If the entry does not exist, it is retreived from the common settings. For details please read documentation OfficeTalk Script, chapter stepscheduler.

Using message dialogs of the running platform

Since this build OfficeTalk uses on Linux- and Windows-platforms its own message dialogs for a quicker recognition. With the user specific or common envirnoment entry Message=P[latform] you can advise OfficeTalk to use platform specific message dialogs instead of its own message dialogs. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings without userinterface.

Version 2.91 Build 08.03.2007

Define what application to use for opening extern files (hyperlinks)

If you choose the kontextmenu Open selected document in a description field, the application, assigned to the filetype, is opened. On Windows- and Linux-platforms this assignement is done on system level. With the environment Applications you can use your own assignement. With this assignement you can e.g. use a different Acrobat-Reader version for your PDF-documents. For details please read documentation OfficeTalk Business-Process-Management, chapter Settings without userinterface.

Version 2.91 Build 07.30.2007

HTML-Exports with hyperlinks in description fields (worker, process, step, etc.)

Links where not displayed as hyperlinks (blue and underlined) in the HTML-Exportfile, created by the menu Save as HTML. Now these links are displayed as hyperlinks and clicking onto such a link opened the file in the browser if a propper application for this filetype was registered. If the hyperlink names a website, the registered browser is opened with this site, if the network permissions do not deny.

Inserting a file link in the description field of the dialog Processtemplate <name>

Links, created with the contextmenu Insert document... in the description field where not displayed an hyperlink (blue underlined).

Description strings in the HTML-file, created with the menu Save as HTML...

Creating a HTML export, the descriptions in worker, process, history, etc. are no longer stored as unstructured text. The lines are put into the HTML file in the same format as in the orginal. So larger descriptions are readable easyier in the HTML exportfile.

Mailadress in the adress dialog of the worker is validated

The typed in mail adress in the inputfield eMail: of the adress dialog must be compatibel now to minimal RFC rules. This means: Minimal 3 charactes, and @ and . must be contained. If a workers adress conains an invalid mail adress you get a message when the adress is changes in any way. You must correct the invalid mailadress or delete it first to go forward.

Function Source of the systemvariable Error

The function answers the script- and macroname as <scriptname>.<macroname> and not only the macroname alone. With theese informations finding a macro is a little bit easier.

Version 2.91 Build 07.24.2007

Exporting worker with the contextmenu Export in the dialog Organigrambrowsers or Organigram

If a worker or a part of the organisation was exported with the contextmenu Export..., OfficeTalk was aborted on some constellations. Most the time this happened if the company's model was new and incomplete. But OfficeTalk should block such errors too.

Simulation ofv the processflow with the menu Simulation in dialog Processgraph: <name of process>

If a simulated step contained a result without a succeeding step, OfficeTalk was aborted with an error message. In detail this is a configuration error and would be notified by the Workflowanalyse but OfficeTalk must ignore such problems too !

Moving a worker with the mouse within the organigram

In some situations OfficeTalk was aborted with an error message if a worker was moved with the mouse into another worker. This happened most when the worker to move was not selected completly (inverse drawn) before he was moved.

Onlinehelp for the systemvariable Error at writing a macro

Typing in the systemvariable Error with succeeding dot and space (error._) you get, like for all another systemvariables, a dialog with the available services of Error.

Version 2.91 Build 07.22.2007

Function Start in a script macro could not start the process

If the function Start could not start the process, an exception is thrown and you get an messagedialog, whitch decribes the reason. As usual you can decide with your answer (Yes, No, etc.) how to proceed. With the statement Try-Catch you can catch the exception without getting a messagedialog and decide progammaticly how to proceed.

Tabulator Resources in dialog Simulation of process:

Selecting the tabulator Resources in dialog Simulation of the process: <processname> resulted in an ending of OfficeTalk with an error message, sorry.

Dialog Delegate/Change: <processname> in the tasklist

In the dialog, opened with the context menu Delegate/Change..., the combobox with the workers and the option only substitutes was gayed ever. Because of you could not delegate a process with this dialog. Additionaly because the OK-button stayed gray on some other dialog changes, the dialog could not be closed with accepting the given changes.

Onlinehelp for typing in a Dim-statement in the macroeditor

The onlinehelp for selection a datatype within a Dim statement presented in the list dialog only the basic datatypes (Boolean, Integer, etc.) and the namespaces but no datatypes within the namespaces.

Onlinehelp for typing in a Start-statementin the macroeditor

The onlinehelp for startable processes did not work if the statement Start was used in conjunction with an assignement to a similar named variable like started = Start "<category>" "<name>".

Version 2.91 Build 07.16.2007

Toolbar for dialog Responsibility and History for: <processname>

The dialog History for: <processname>, opened with the contextmenu History in the tabulator processtemplate and in the different types of tasklists, and the dialog Responsibility, opened with the contextmenu Responsibility... supports now a toolbar, containing the most important functions. To show and hide the toolbar the menu View contains the new item Toolbar. With this toolbar the dialog is useable a little bit faster.

Extended menu View and extended toolbar of dialogs Organigramoverview and Organigram for: <workername>

The menü View and the toolbar of the dialogs Overview and Organigram for: <workername> are extended with item and toorbar button Contract all hirachies for contracting all expanded organisations. With this function you can set a defined state in a fast way.

Version 2.91 Build 07.13.2007

Toolbar for dialog Organigramoverview and Organigram for: <workername>

The dialog Overview, opened with the menu item Overview, and the dialog Organigram for: <workername>, opened with the menu item Organigram in the main dialog of the startportal Dialog, support both now a toolbar, containing the most important functions. To show and hide the toolbar the menu View contains the new item Toolbar. With this toolbar the dialogs are useable a little bit faster.

Version 2.91 Build 07.09.2007

Menuitems Search and Workersymbols in portal Function-/Organigrambrowser

The menu items Search and Workersymbol where selectable in logged out state too. For security you must be logged in to use theese menu items.

Toolbar of portal Function-/Organigrambrowser extended

The toolbar is extended with the buttons Search and Workercontent to access theese functions easier.

Service openHistory() of the sytemvariable stepscheduler

The service displayed the history of the currently scheduled step too. Because this is the present not the past, this history entry is hided now.

Emphasize the content of Listfield, Table and Combobox of the systemvariable ScriptDialog

In the named dialog elements you can emphasize the content of the dialog item with formats and colors. The emphasize is content specific and not specific to the dialog item (list or column). For details please read documentation OfficeTalk Script, chapter Listfield, Table and Combobox.

Version 2.91 Build 07.04.2007

Extended dialog items Listfield and Table of the systemvariable ScriptDialog

A Listfield and a Table can be configured for multiple selection. Multiple selections enables the user to select more items at the same time. A multiple selection works with the keybord key Ctrl and Enter. With multiple selections such tasks, which requires for a click more items, can be easier realized.

Displaying the usings of a script macro

The contextmenu Usings... in the right listfield of the Scriptbrowser-Dialog found usings of a macro within comment lines (with leading ') too.
If a macro was used by two or more Call-funktions within the same macro, the using dialog contained two lines, but double clicking both lines opened the first using ever.

Wurde eine Makro in einem Makro zwei mal durch 2 verschiedene Call-Funktionen verwendet, wurde das zwar im Verwendungsdialog auch zwei mal angezeigt, ein Doppelklick auf beide Verwendungszeilen öffnete jedoch das Makro immer mit der ersten Verwendungsstelle.

Version 2.91 Build 06.28.2007

Renamed services of the systemvariable ScriptDialog

For a better semantic the servicename addNotebook(...) is renamed to addRegister(...) and the servicename notebookPage(...) is renamed to registerPage(...). The old names are valid up to the next maior version.

New service values(...) of the systemvariable ScriptDialog

The service values(...) answers for combobox, list- und tableitems the whole content as an Array.

Processdiagram in dialog Processgraph: <name of process> and in dialog Hirarchybrowser for: <processname>

Crossing connection lines (Stepresults) from a step to his successor in the next line are, if possible, avoided. This makes a diagram more readable.
The connection line (Stepresult) to a step in a top line, witch defines a recursive workflow, surrounds a step between in a better way. This makes a diagram more readable too.

Version 2.91 Build 06.23.2007

Displaying numbers in dialog The Processdata of: <process name>

Processdata entries with numbers are displayed with a seperator for the thousand point for faster and easier reading theese kind of values in the dialog. For details please read documentation OfficeTalk Script, chapter format(..., as: ... with: ...).

Send a process template in dialog Hirarchybrowser for: <processname>

Sending a process templates with the menuitem Send... in the dialog Hirarchybrowser for: <processname> terminated OfficeTalk after the generation of the HTML-files with an error message, sorry.

Exporting the complete hirarchy of templates in dialog Hirarchybrowser for: <processname>

With the menuitem As HTML save the complete hirarchy of workflow of templates is exported. All templates started within the workflow are exported as HTML. The HTML-files containes links to the started template at the action, whitch starts the template. With this extension, you can follow within a browser the workflow over all processes. With this extension you can publish hirarchies of templates in web too.

Menuitem Path as new Process in dialog Processgraph: <name of process>

Canceling the dialog for the name of the new process terminated OfficeTalk with an error message, sorry.

Version 2.91 Build 06.19.2007

Menuitem Workersymbol did not reflect the current setting

The current setting for the workersymbol was not shown by the menuitems of Workersymbol. After some activities the menuitems of Workersymbol reflected the current setting.

Version 2.91 Build 06.18.2007

New type of view for processdata in a tasklist

In all kind of tasklists you can view the data of a process in two different modes. For this, the menuitem Processdata contains two subitems, as Table... and as Tabulator.... The item as Table... displays the processdata as usual in a single table for all entries. The item as Tabulator... displays the processdata in a tabbed dialog. Each tabulator is named and contains all the items of the entry. For details please read documentation OfficeTalk Business-Process-Management , chapter Processdata. The tabulatordialog has advantages to the tabledialog if a process has many datas.

New service can(..., work: ...) of the systemvariable stepscheduler substitutes service canWorker(..., handle: ...)

The service can(<worker>, work: <process>) substitutes the service canWorker(<worker>, handle: <process>). The substituted service exits anymore, but should not be used in future, because it will be removed in the next main version.

Version 2.91

Contextmenu in the resource using dialog

The menuitems New, Copy and Paste in the contextmenu of the list field where chooseable. This makes no sense here, but resulted in a termination of OfficeTalk, sorry.

Changing the Usinglevel in the Settings

Changing the Usinglevel within the tabulator General of the dialog Settings, the new value was accepted after the newstart of OfficeTalk only. Now changing the Usinglevel is accepted after closing the dialog Setting.

Version 2.90 Build 06.12.2007

Dialog of used resource shows script macros using the resource too

The dialog of resource usings, opened with the contextmenu Usings... in tabulator Resources of the worker dialog, shows where the resource is used by a script macro with the service stepscheduler.consumed(...). Double clicking such a line opens the macro within the scriptbrowser and selects this service.

Extended analyze of resources within analyzing a process template's workflow

The tabulator Unknown Resources shows now resources, assigned to an action of a step or a script macro without finding it. If the unknown resource is assigned to an action, the columns Action and Step contains the name of the action. If the unknown resource is used in a macro, the columns Macro and Script contains the name of the macro where the unkown resource is used with the service stepscheduler.consumed(...). This can happen if a resource is removed without testing the usings with the context menu Usings... in the tabulator Resources.

Dialog of the resource usings, opened with the contextmenuu Usings.. in tabulator Resources of the worker dialog

The dialog of the used resources contained a wrong calculated sum of resources the title line. The column Cost contained the cost base but not the cost, orginated by the actions scheduling time.

Version 2.90 Build 06.8.2007

Contextmenu Usings...... in Tabulator Resources of the worker dialog

The menuitem was most grayed and not useable. Because of it was not possible to identify where the resource was used.

Contextmenu of the source field in the Scriptbrowser and Debugger dialog

The most contextmenu items of the named dialogs contains a symbol now. Visual oriented humans will find the required item with theese symbols faster.

Version 2.90 Build 06.01.2007

New service for requesting current version in script macro

The systemvariable stepscheduler supports the new service version. The service answers the version of the OfficeTalk system. With this service you can ensure a required version of OfficeTalk.

Ner service of systemvariable ScriptDialog for double clicking dialog elements

ScriptDialog supports the new service addDoubleAction(...) to execute special statements if a dialog element is double cicked. With this you can e.g. close a dialog, if the user double clicks an item in a list field. For details please read documentation OfficeTalk Script, chapter addDoubleAction(...).

Onlinehelp in comment lines for writing a script macro

If an online help specific activity happened while writing a macro (e.g.: typing in stepscheduler.) , the help dialog was opened if this typing was done within a comment line (a leading ') too. Opening the help dialog is not neccessary in this case !

Function pattern in source field of the Scriptbrowserdialog

With the new context menu Function and its submenues you can insert a function pattern at the current cursor position. Parts in <> must be substituted with the current values.

Version 2.90

Scriptmakro/-makrokette im Debugger neu starten

If a macro is opened within the debugger dialog, no matter because, you can restart the macro of the selected context in the listfield Stack. The restart starts at the macro of the selected stack entry. Locale and temporaray variables are initialized for the restart. Performed services by systemvariables (e.g. processdata, stepscheduler, etc.) can not be rolled back for the restart !

Statement pattern in source field of the Scriptbrowserdialog

With the new context menu Statement and its submenues you can insert the a statement pattern at the current cursor position. Parts in <> must be substituted with the current values.

Breakpoint in the source field of the debugger

In the source field of the debugger you can set and remove dynamicly brackpoints mit the context menu Halt. Wirth this extension testing macros is more dynamicly and easyer.

Syntaxcoloring and modifying a variable's contents in the Scriptdebugger

The dialog field of the macro source supports Syntaxcoloring now. If Syntaxcoloring is switched on, the source is colored for better reading.
Double clicking a variable in the variables list field opens the dialog with the contents of the variable. In this dialog you can modify the variables contents and affect the further execution. Only a scalar variable (Integer, Long, Boolean, Date, Time, etc) can be opened.

Changing the worker symbols in the organigrambrowser dialog

Changing the symbol for worker with the menu View - Workersymbols did affect the right dialog part with the worker after changing of the worker's selection and not at once. Additionally the busy bee is shown while changing all worker's symbol, because this may take about 4 seconds.

Version 2.84 Build 05.17.2007

To much question when starting a new process if using level Beginner

If the Usinglevel in the general setting was set to Beginner and the Tasklist as browser was set in the tasks settings, you where asked twize to schedule the first step. Asking once is enought !

urde 2 mal gefragt ob der Arbeitsschritt eines neu gestarteten Vorgangs ausgeführt werden soll. Eine einzige Frage ist natürlich hier ausreichend !

Layout of the Browser-Tasklist in portal Function-/Organigrambrowser

Hiding and unhiding the process templates and the template description obsured the description field partially with the middle dialogpart (the current task).

Login entries in the logindialog of the evaluation version

The combobox list Login of the same named dialog contained sometimes the same login name twice in different case. This effect happened in the evaluation version only !

Version 2.84 Build 05.14.2007

Inserting a new first step in dialog Processgraph: <name of process>

The documentation tells to insert a new first step with the contextmenu New - Quickstep, but the context menu New was disabled on not empty templates ever, sorry.

Header of the organigram dialog

The header of the organigram dialog titled the company instead of the logged in worker.

Version 2.84 Build 05.11.2007

Analysing the workflow of a process template extended

The workflow analysis (dialog Analysing the workflow of processtemplate <templatename>), started with the menu Extra - Workflowanlysis... in dialog Processgraph: <name of process> was extended. Die tabulator Unknown Resources contains the script macros, where an unknown resource is used. This resource was tried to book with the statement stepscheduler.consumed(<Resourcename>, amount: ...). Such kind of errors can be catched within the macro with a Try/Catch statement.

Displaying the Usings of a script macro

Usings of a script macro with the context menu Usings... in the macro listfield of the Scriptbrowser where not shown when the declaration of an argument in the Call-Statememt and in the macro header did not match exacly. e.g. The argument in the Call-Statement was declared with ScriptDialog and in the argument list of he macro with Joops.Scripting.ScriptDialog.

Content of the process template listfield within the tasklist

With the new menu item With Owner of the menu item View - Processtemplates you can specify wether the owner of a process template should be displayed in the process template's listfield. In the past, owners of foreign templates (the container of the process template is another worker) where displayed ever. This setting is user specific and stored in the environment ProcessTemplateWithOwner.

Version 2.84 Build 05.08.2007

The state line in the tasklist

The state line at the bottom of all tasklist dialog variants is drawn with the color of the menu line now. With this change the filter information is recognized faster.

Picture of a scheduled step in the history dialog

For scheduled step, containing one scheduled action only, the picture of the action is used instead of the step's picture. This give you faster overview about the scheduled acitivities.

Dialog Additianal Processname while starting a new process

The title of the dialog contains the name of the process to start. If you have double clicked the wrong process template, you can cancel at this point without any consequences.

Organigramlistfield in dialog Function-/Organigrambrowser, Organigrambrowser and Organigramdialog

The label, left the symbol, was positioned a little to high. This was a visual misfit and recognized from a few customers only, but the visual effects are important.

Organigramdialogs with different visualization types for workers

In all dialogs, displaying workers within an organigram (Function-/Organigrambrowser, Organigrambrowser and Organigramdialog), you can choose from four types of visualization for workers with the new menu View - Workersymbols. With this new feature you can optimize the working with OfficeTalk. The flexibility of OfficeTalk is extended with theese variants !

Version 2.84 Build 04.27.2007

Saving general Settings in the portal Function-/Organigrambrowser

If some general settings where changed, and in the left list field another function was selected without saving the changes first, you got the message wether to save the changed settings. But answering Yes did not save the changes. This happened in the portal Function-/Organigrambrowser only !

New service consumed(..., amount: ..., cost: ..., unit: ..., description: ...) of the system variable stepscheduler

In oposite to the service consumed(..., amount: ...) you can assign with this service a yet undefined consumed resource to the history of an executed action. Such a resource can be an income or an outcome resource. For details please read documentation OfficeTalk Skript, chapter Systemvariable stepscheduler.

Dragging stepresults (blue connections) in dialog Processgraph: <name of process>

Dragging the end of a connection from on step to another step leaves the stepresult (the blue connection) selected for a better overview.

Version 2.83 Build 04.25.2007

Optimized and more intuitive symbols

Because of customer wishes the symbols are redesigned for a more intuitive and interpretative picture. The symbols for company, substitute and permission have changed totally for a better understanding. For details please read documentation OfficeTalk Business-Process-Management and OfficeTalk Workflow.

New symbols for steps and actions

For steps and actions you can choose two new symbols (Take something and Calculate something). With theese new symbols you have for such kind of activities a matching picture. For details please read documentation OfficeTalk Business-Process-Management.

Version 2.83 Build 03.24.2007

New service nextStepCategory(..., name: ...) of the system variable stepscheduler

With the service nextStepCategory(..., name: ...) you can name in special cases the next step with the given name parts. With this service you can adjust the abstract name of a step to his concrete task. The process template Ad - hoc is an example for this requirement. The step Task - Work is named abstract because the template is used for different tasks and the task of the step is known at execution time. For this concretisation you can name with the servive the step concrete.

Analysing the workflow of a process template extended

The workflow analysis (dialog Analysing the workflow of processtemplate <templatename>), started with the menu Extra - Workflowanlysis... in dialog Processgraph: <name of process> was extended. Die tabulators Unknown returns and Unknown macros contains columns with the step an action, where the failure activity starts. With this information of the hole picture the error can easier be corrected.

Wrong configuration of a table-item with the service addTable(...) of the system variable ScriptDialog

If the count of columns of the header in the service a ddTable(...) did not fit to the count of columns of the table's contents, you got an error mesage and OfficeTalk was terminated. This was an user error, but OfficeTalk should be tolerant against such errors ! Now, you get an expressive message and the column number of each row is adjusted to the column number of the header.

Exporting a process template as HTML

Exporting a process template with the menu Process - Save as HTML... in the dialog Processgraph: <name of process> resulted in an error message and OfficeTalk terminated, sorry.

Opening a label in a skript dialog within the Workbench

Opening a label in a script dialog with double clicking, while building the dialog with the Workbench, resulted in an error message and OfficeTalk terminated, sorry.

Version 2.83 Build 04.16.2007

Displaying the current filter values in the status line of all tasklist dialogs

The current filter values are preceeded now by a symbol, to visualize current filters faster.

Recognizing the installed Microsoft SQL-Server version

If a Microsoft SQL-Server is to be used, OfficeTalk must know what version is installed, because the different versions (7,8,9) behave different. In general OfficeTalk can find out what version is installed. If this detection fails, you can sepcify with the environment MSSQL7=0 and MSSQL7=1 wether version 7 or a higher version is installed. Attention: 0 oder 1 must be a string !

Setting Logging in tabulator page General of the dialog Settings

To change the setting you must not be logged in anymore. This is more usefull.

Display of the filter settings in the tasklist dialogs

The setting Delay is displayed as green, yellow or red after the other filter settings at the dialog bottom.

Valid/invalid characters für a script dialog item's name

In the property dialogs of all the dialog items only valid character input (numbers, letters and underscore _) in the name field is allowed. All other characters are ignored. This avoids possible problems for later.

Version 2.83 Build 04.14.2007

Exporting a process template with script macros using the service addNotebook(...)

If a process template was exported and the script macro of an action used the service addNotebook(...) with naming the macro for the tabulator page, this scripts where not exported and was missing after importing the template into another system. (e.g.: addNotebook((Array(Array("Page 1", "Customer.Adress"),...),...) ).

Menu item Organigram in entry portal

Using the menu item Organigram in the dialog of the entry portal or the toolbar button Organigram in the entry portal's dialog terminate OfficeTalk with the error message Message isWithTime not unterstood..., sorry.

Displaying process templates in the task list dialog

In the list field containing the startable process templates, the owners name (a worker) of the process is appended to the process name only if the list field contains process templates from foreign owners to save space in the list field.

Per-Usage-Licence for variant OfficeTalk/MS

In the past the Per-Usage-Licence handling was equal to both variants OfficeTalk/MSP and OfficeTalk/MS. Because in the variant OfficeTalk/MS working with processes is not possible, the Per-Usage-Licence handling is disabled in this variant.

Version 2.83 Build 04.10.2007

Login using Microsoft SQL-Server with NT-Authentification

If an ODBC-Entry with NT-Authentification was used and the Windows-Login missed the permissions for the database OfficeTalk, the login runs into an endless loop interrupted by a message about the denied login. This happened when the windows login missed the db_owner right for the database OfficeTalk.

Working- and Delaytime in dialog Processgraph: <name of process>

In the process diagram you can hide or show the different times (estimated working time of the step and delaytime of the step result, the blue connections). For this, the tabulator Processtemplates in the dialog Settings and the dialog Settings of the process template was extended. In large diagrams and in design mode this information may be hided to make the process graph more clearly. Details about you will find in the documentation OfficeTalk Business-Process-Management.

Start with entry portal Limited Browser und Full Browser

Since the last build an error occured when starting OfficeTalk with Microsoft InternetExplorer. It was finished suddenly after started with an error message. You had to change the entry portal by hand with the system program Regedit.exe first, sorry.

Performance optimisation in the tasklist dialog

The cyclic reading of new processes in the personal tasklist is optimized. The reading runs in the background but the working in the foreground is optimized by this too.

Error messags while execution a service in a script macro

The error message depends now on the reason of the aborted service. The message text differs depending if the error occured because an unkonwn or wrong service is used, or id an error was detected while executing the service. With this differentiation you can easier find and reasolve the error reason.

Version 2.83 Build 03.27.2007

Checking the different licences is made equal

The testing of the licence and transaction licence is made equal and easier. Because of this change you may have to change the contents of the two tables trans and serialnumbers.
If you get after the update the message The licence is not found in the database... when starting OfficeTalk, verify with the database administration program (Enterprise Manager, PGAdmin III, ...) the table trans in the database OfficeTalk. The table must contain one row only with 1 in the column id. Remove all other rows. Start OfficeTalk again. If you get the same message again, empty the table trans and and write into the column lastnumber of the row with the contents trans into the column tablename the digit 0. Ensure that the correct licence file Licence.dat is stored in JOOPS GmbH\OfficeTalk\Bin. Now starting OfficeTalk should work.

You can perform the same tasks with the following SQL statements in the query tool of database administration program:

PostgreSQL datenbase:
DELETE from "OfficeTalk".trans where id <> 1;
UPDATE "OfficeTalk".serialnumbers set lastnumber = 1 where tablename = 'trans'

Or emptying the table trans
DELETE from "OfficeTalk".trans;
UPDATE "OfficeTalk".serialnumbers set lastnumber = 0 where tablename = 'trans'

All other datenbases:
Preset the database OfficeTalk in the query tool first.
DELETE from trans where id <> 1
UPDATE serialnumbers set lastnumber = 1 where tablename = 'trans'

Or emptying the table trans
DELETE from trans
UPDATE serialnumbers set lastnumber = 0 where tablename = 'trans'

Filename of protocol file is changed

The protocol for process activities (Setting Protocol in tabulator General of the dialoges Settings) is stored in the file protocol.log instead of protocol.txt in the past.

Version 2.83 Build 03.26.2007

Service addNotebook(...) of the systembariable ScriptDialog extended

In the first argument of the service addNotebook(...) you can use the ScriptDialog created by the macro, whitch build the registerpage, or the name of the macro whitch will build the registerpage. In the first scenario the registerpage is build at start of the main macro. In the second scenario, the registerpage is built when the registerpage is choosen by the user within the dialog. With the second case you can save time, because the macros for building the registerpages are executed when needed in oposite to the first case.

New services symbolNames and actionSymbol(...) of the systemvariable action and step

With the services you can specify for special cases the picture of the currently scheduled action in its history. For details please read chapter Sytemvariable Action and Step in the documentation OfficeTalk Script.

Showing same named process templates in tasklist

The predefined behaviour suppresses same named process templates within the worker hirarchy in the right side list field of the tasklist dialog. With the environment DuplicateProcessTemplate=1 you can overwrite this behaviour. With this setting same named templates are added into the list field. After the name is the owner of the template inside brackets displayed.

Login running the evaluation version

Using the evaluation version and the internal database the password is not required in the login dialog. To make this fact clear, only in this scenario the input field for the password is not visible.

Version 2.83

Setting Actualize processes in tabulatorr Tasks of the dialoges Settings

Changing of this setting was accepted wrong. On opening this setting dialog again, the previous value was shown.

FlyByHelp-texts of the step in dialog Processgraph: <name of process>

The FlyByHelp-texts, theese are the short text blocks, inserted if you touch a step with the mouse, where cutted at the first blank if the hole text was larger than the maximum predefined size (environment ProcessLayout/DescriptionSize).

Wait-Cursor was not shown the total compile time of a big macro

If the message Variable is not used, remove it... was answered with Yes, the Wait-Cursor was not shown the rest of the compiling time. This could be missunderstood by the user.

Wenn beim Kompilieren größerer Makros z.B. die Meldung Variable wird nicht verwendet, soll sie entfernt werden... mit Ja beantwortet wurde, wurde der weitere Kompiliervorgang nicht mehr mit einem Eieruhr begleitet. Das konnte u.U. Mißverständnissr auslösen.

Using of group- and itemnam in the services of the systemvariable processdata

Names in the arguments of the services processdata are cleared by leading and ending blanks. This kind of mistake is not possible anymore:
Processdata is written with processdata.item(" name", with: "Josef", in: "Customer") and with processdata.item("name", in: "Customer") not found, because the itemname "name" is used in the first statement with leading blank, but without in the second statement.

Missing declaration of variable in array access function was not detected

Using an not declared variable in an array access function as index (e.g.: name(i)) was not detected by the scriptcompiler. Because of execution the macro produced an error message line Subscript out of bounds....

New servicees ask( ..., subject: ..., question:..., attachments: ... ) and askWorker( ..., subject: ..., question: ..., attachments:... )

With the new services you can attach files to the mail like sending mails with the systemvariable Mail, when you want ask anyone. For details please read documentation OfficeTalk Script.

New service copy(..., to: ...) in the systemvariable processdata

The service copies the items within a named group into a second named group of the same processdata. The service is helpfull if items of a group should be accessible within another named group too.

Services addEntry(,,,, from: ...) and add(..., from: ...) in the systemvariable processdata renamed

The service addEntry(...,from:...) was renamed to copyEntry(...,from:...) and the service add(...,from:...) was renamed to copy(...,from:...). The old services exits for compatibility up to the next main version.

Wrong answer of service selectionIndex(...) if service addComboBox(Null, ...) is used

If a Combobox was inserted in a script macro with the statement addComboBox(Null, choices:...), a succeeding selectionIndex(...) answered 0 in any case. Instead of argument Null an empty string ("") had to be used.

Protocol activities of process scheduling extended

The protocol of the process scheduling (Option Protocol in tabulator General of the dialog Settings) is extended and detailed. This protocol is very helpfull for difficult errors in the processflow.

Progressdialog while loading process templates and processes

The progress of loading of 50 or more processes is protocolled with a progress dialog. This dialog is displayed when opening or actualizing a task list.With the new setting Progressdialog from <nn> processes in the register General of the Settings dialog you can specify the minimum number of processes protocolling with a progressbar. With the environment 0 not progress dialog is opened when loading processes.

Displaying the process questions and received answers in the tasklist

When you schedule a process, waiting for answers to sent questions, you get the dialog Answers of process questions for: <processname>. In this dialog you can see all the questions and answers reveived yet. In the past you got a messagebox in this case, notifying you about the wait state only.
Additionally the dialog State for: <processname>, opened with the context menu State in the task list, is extended with the button Process questions.... This button is clickable if the process is waiting for answers and opens the same dialog. For details about please read documentation OfficeTalk Workflow.

Version 2.82 Build 08.01.2007

Opening the tasklist and process history is made faster

Opening the tasklist with many processes is made faster about 50 percent. Opening the history for a process template and for a process is made faster about 30 %.

Displaying process templates within the tasklist dialog

Becasuse of the last update same named process templates of different owners where displayed all. The owner was shown in the list field at each template, but this could be interpreted false. Now the process template list field in the task list behaves like in the past. Same named process templates are skipped.

Durch die Anzeige des Eigentümers zur Vorgangsvorlage wurden in der Aufgabenliste gleichnamige Vorgangsvorlagen aus verschiedenen Bearbeitern innerhalb der sichtbare Bearbeiterhierachie angezeigt. Zwar wurden die unterschiedlichen Eigentümer dieser gleichnamigen Vorgangsvorlagen mit angezeigt, aber es war trotzdem etwas verwirrend. Jetzt werden, wie bisher, gleichnamige Vorgangsvorlagen im Listfeld der Vorgangsvorlagen ausgeblendet.

History of running and finished processes

Building the history list (contextmenu History in dialog Processtemplates and contextmenu History in the tasklist), OfficeTalk ended with the message Object deleted... when the history has registered the process as running, but it was not found within the database. In real situations this can't happen but sometimes...

Color settings for toolbars

In the tabulator General of the dialog Settings you can define the color for toolbars in the dialogs. With this setting you can adjust the toolbar color with the dialog color. Because of eyes eat...

Displaying processtemplates in dialog Tasklist and Start process

Beside the termplate name the name of the owner, in whitch the template is located, is displayed in brackets. If you have same named templates in different workers, you will have a better orientation.

Importing a hole company in the Organigrambrowser

Importing a company skipped items because of missing forward references. e.g. A department contained a process template with a step assigned to a worker within another department. This process template was cutted at the assigned step. You are right, importing a company is very rare needed, but exotic functionality must work right too !

Version 2.82

Analyzing the workflow of a process

In the dialog Processgraph: <name of process> you can validate with the new menu Extra - Analysis the using of different workflow aspects of a process on base of its process template. With this analyzing you can see, wether the process will fullfill in a later workflow executing the OfficeTalk rules. The progess is documented with a progess dialog. As the result you get a dialog with the locations of possible errors. e.g. Using of macros, rights, processdata (processdata.item(<Item>, with: <Value>, in: <Group>) and processdata.item(<Item>, in: <Group>)), etc. With this feature you can easyly verify possible errors within the workflow.

Importing a company sipped all references to the company

Importing a company ignored all references to this company. e.g. In the tabulator Authorize of a worker an explicit assigned company was missings after the import. The same happened for the Visibility, Substitutes and Workingoptions of all steps.

Usings of script macros

The contextmenu Usings for a makro in the Scriptbrowser did not differate macros by their arguments. Because of, searching for the usings of a macro returned usings of a same named maro, but with different arguments.

Version 2.81

Exporting a worker in the organigramm

The contextmenu Export in the organigram listfield protocols the proceeding with a dialog, showing the finished percents and the worker whitch is currently exporting.

Size of the debugger dialog and content of the list fied for the variables

Die debugger dialog is opened 3/4 of the screen size now by default.
The horoziontal scrollbar of the list field for the variables did not fit to the size of the displayed lines. e.g. If an Array was expanded with new entries, the scrollbar did not expand too.

Version 2.81 Build 02.16.2007

Assingnin a Resource to an Action

The assign button (>>) may be selectable, but no resource in the left list field ia choosen.

Firsat start using PostgreSQL-database

If a PostgreSQL-database is used and OfficeTalk was started the first time, a wrong environment was noted, but the ODBC-entry for the database connection exist.

Importing a worker

Importing a worker with a processtemplate containing a step with an unkonwn assigned worker, OfficeTalk ended with an error message, sorry.

Item with reference to an extern document

If a worker contained in his description a reference to an extern document (named in blue), OfficeTalk ended with error message selection the despription tabulator in die worker dialog.

Menu Work - Searching in Organigram dialog

If in the search dialog, opened with the menu Work - Searching in the organigram dialog, you searched for Processtemplate, Absent, Permission or Substitute within the portal Function-/Organigrambrowser, OfficeTalk was ended with an error message, sorry.

Version 2.80

Usings of script macros pointed the macro written within comment

The context menu Usings in the macro list field of the Scriptbrowser displayed using locations where the macro was written within a comment line.

Version 2.80 Build 02.03.2007

Assigning a resource to an action of a foreign process template

Opening a process template within the tabulatr Common process templates enabled to assign a resource to an action of a process template owned by a foreign worker. This must not be allowed !

Changing scripts and macros of a foreign worker within the script browser

Opening an action from the tabulator Common process templates enabled to change scripts and macros owned by a foreign worker. This must not be allowed !

Version 2.80 Build 01.29.2007

Microsoft SQL-Server Version 9 is fully supported

Version 9 of the Microsoft SQL-Server, named SQL-Server 2005, is supported fully. You must take a look at some details, if used by OfficeTalk. Read the documentations Install.pdf and BPM.pdf.

Database installation support for Microsoft SQL-Server with NT-Autentication

Installing the database at the first run of OfficeTalk using Microsoft SQL-Server with NT-Autentication no database OfficeTalk was created and the tables where created in the database master. Now, using Microsoft SQL-Server with NT-Autentication all is installed as described. This installation variant is documented in detail in the documentation Install.pdf.

Version 2.80 Build 01.24.2007

Hyperlinks to extern documents in description fields are displayed underlined blue

Inserted references to extern documents in the description fields of workers, processes, steps, resources and absents are displayed like in a browser blue underlined. With this extension, reference to extern documents are easily recogniced.
If you are using references allready, you must insert theese references again, because old references are not displayed blue underlined !

Fileselection dialog for import oder export did not open

Selecting for import or export (Script, Processtemplate, Worker, etc.) a folder on a memory stick and removing it, succeeding imports or exports did not work, because the required fileselection dialog did not open. After restarting OfficeTalk the fileselection dialog was opened again.

New Services of the systemvariable Worker

The systemvariable Worker supports the new services company, allChildren and allParents. For details please read documentation OfficeTalk Script, chapter worker.

Displaying the consumed resource in the process simulation and in the process history

If a resource was defined with Hours and Factor 1.00, the consumed value was displayed wrong.

Tabulator Datenbase in the Workbench

It the communication libraray for databases was not loaded, OfficeTalk ended with an error message if in the tabulator Database of the Workbench an input was made into the fields Connection or Recordset, sorry.

Shifting a worker within an organigramm into aother owner

Shifting a worker using the portal Function/Organigrambrowser to another owner within the organigram listfield (e.g. to a Department), OfficeTalk ended with an error message, sorry.

Scheduling a process and resources of an action

Scheduling a process all associated automatic resources of an action are booked and not the first one only.

Version 2.80 Build 01.22.2007

Simulation of processes using resources

Simulating a process with the menu Simulate in the dialog Processgraph: <name of process> an assigned resource was not found, if it was not located in the logged in worker or a superior worker. Now the assigned resource must be contained within the step executing worker or within the process owner.

Shortcut CTRL-X, CTRL-C and CTRL-V for input fields

The shortcuts CTRL-X, CTRL-C, CTRL-V did not work in inputfields of the dialogs.

Skriptdialog supports tabulators (register)

In a script dialog you can insert now Tabulators (called Registers too). Each page of the tabulator is created with a simple macro. With a Tabulator you can group informations to themes together and easy display and work. Details about you find in OfficeTalk Script Chapter Services for inserting items subchapter Register.

Version 2.71

Starting worker of a process was not visible in the history

The worker, who had started the process, was not shown in the right dialog part of the history dialog when the process was selcted in the left list field.

Scheduling processes without history

It the process history was deactivated in the task settings, OfficeTalk terminated sometimes with an error message when a process template was removed, or a process was finished. This error was not seen because only a few customers work without process history .

Executing a script macro with missing rerult

When a script macro with a missing result (without Return <String>) was executed, and a next step in the path was found, some synchronisation problems occurred. The next step was executed while the dialog for defining the result was opened. On the next start of OfficeTalk sometimes the process did not kow the next step and OfficeTalk terminated with an error message when opening the task dialog. The orginator of this error was a user definition error in a script macro, but OfficeTalk should be robust again such errors !

Using a not available item in a script macro results in an exception

Using a service for a not available item in a macro results in an exception. If the exception is not catched with the Try/Catch statement, you get a error message and the macro's execution can be debugged or aborted. The exception may be thrown by the services stepscheduler.consumed(..., abount: ...), if an unknown or not accessible resource is used, process.activeHistory, process.finishedHistories and process.activeHistories, if process history is not activated.
e.g. Using the service process.activeHistory in a macro without activated process history results in the message, that process history is not activated in the task setting.

Assignement of an entry in an array resulted in an error message

Assigning an entry in an Array argument (e.g.. columns(1) = "Text") resulted in an error message when the macro was compiled, instead of a hint at the assigning line.

Sizing a table in the script dialog while building it in the Workbench

When a table was resized by dragging at the corner in the Workbench, OfficeTalk ended with an error messqge, sorry.

Sorting lines in a table within a script dialog by clicking a column title

Sorting the lines within a table in a script dialog by clicking into a columns title positioned the horizontal scrollbar to the initial left side. Now the scrollbar is leaved at its current position.

Duplicated histories for steps when using service activeHistory

If the service activeHistory was used in a script macro by executing a process the step histories where duplicated.

Missing licence after update

After an update the Per-Usage-Licence Unlimited was overwritten with the default Per-Usage-Licenc of the update (Per-Usage-Licence 15). This fact was visible in the dialog Help - About OfficeTalk. The Per-Usage-Licence Unlimited (Licence.dat) had to be copied into OfficeTalk\Bin after the update.

Version 2.70

Changed fileformat for changes und readme

On the CD you find the files for the history (changes) and the installation information (readme) not as a Microsoft-Word file (.doc) anymore, but as a HTML file (.html). With the changed distribution theese files can easyer be readed on other installtions but Windows platforms. You must delete the files with old format by hand, because the installation process do nor delete theese files.

Installation preset Portal in the environment

To make the programm functionality and view equal to the documentation, the Portal Dialog is preset by the installation instead of the Portal Function-/Organigrambrowser.

Setting for Database moved from common to userdefined settings

The setting Database in den General setting is stored now in the user setting and not in the common setting anymore. This has the advantage for a normal user to be able to switch from the internal database (examples) to the external database (the productive data). To set the required mode, you must open the General setting with the menu File - Setting in the main dialog and choose the wanted mode, because the update procedure does not move the mode from the common setting to the userdefined setting. After the first start of this update you can delete on Windows-platforms the Registrykey HKEY_LOCAL_MACHINE\SOFTWARE\JOOPS GmbH\OfficeTalk\UseDatabase, because it is not used here anymore. On Linux-platforms you can delete the Line UseDatabase=... in the common settings /opt/OfficeTalk/OfficeTalk.ini.

Version 2.70 Build 12.26.2006

Storing common- and userdefined-settings on Linux platforms

On Linux platforms between common and user setting is differenced like on Windows platforms. Common setting is readed and stored in the directory, defined by the environment variable OFFICETALKHOME. If this is located in the common OfficeTalk directory opt/OfficeTalk, the OfficeTalk user must own write permission to store common setting. If the environment variable OFFICETALKHOME does not exist, the common setting is managed in the home directory. The Details about you will find in the documentations OfficeTalk Installation and OfficeTalk Business-Process-Management.

Evaluation for Linux platforms

For the Linux-platform an evaluation is available now like for Windows-platforms. Select on the downloadpage of JOOPS (http://www.joops.com/JDownlF.htm) the product OfficeTalk Evaluation and the platform Linux. The rest of the download process is identical to the other downloads. You get the TAR-archive OfficeTalk.tar. Login on the Linux machine as root. Read the archive with the commandline tar -xf OfficeTalk.tar into a directory. Start the installation in this directory with the commandline sh setup -c -u <user>. Substitute <user> with the loginname of the user for whome you want to install OfficeTalk.

The version requires Suse-Linux with installed KDE !

You find the complete description of the installation process for Linux in the documentation Installation.pdf.

Version 2.70 Build 12.17.2006

Linetype for the grid in a script dialog within the Workbench

In the dialog Grid for the dialog, opened with the button Grid in tabulator Scripts of the dialog Settings you can choose between broken and consecutive lines for the grid.

Version 2.70 Build 12.14.2006

The communication library docuware.pcl is distibuted now for DocuWare Version 5. The name of the library (Library\docuware.pcl) is unchanged. If you use DocuWare Version 4:

- Make a backup from OfficeTalk\Library\docuware.pcl.
- Install this Update
- Rename OfficeTalk\Library\docuware.pcl to OfficeTalk\Library\docuware5.pcl
- Restore the backuped OfficeTalk\Library\docuware.pcl

Version 2.70 Build 12.12.2006

Canceling the dialog Settings after changes within the tabulator HTTP

Closing the dialog Settings with the window close button after changes in the tabulator HTTP, the changes where discarded without the message Do you want to save the changes....

Not allowed changes in settings

Changes in the tabulators Scripts, Templates, Tasklists, Mail and HTTP where possible without logging in. Now most fields are disabled in logout state.

Version 2.70 Build 12.8.2006

The column witdh in the tasklist as table

Opening the tasklist in table view, the columns width was set to the predefined width but not to the last used width as decribed.

Version 2.70 Build 12.5.2006

Call-Statement does not find the called macro a special situation

When formating a macro you got the message, that the called macro was not found, because the argument' s type was not recognized right.

An example: The called macro: Sub( number As Integer )

....

The caller macro:

Test
Dim a As Integer
a = 10
Call Skript.Sub( a + 1 )

Skript.Sub was not found, because the expression a + 1 could not be converted to Integer. A possible work arround in Test was:

Test
Dim a As Integer
a = 10
a = a + 1 'Calculating variable first
Call Skript.Sub( a ) 'Using variable instead of expression

Version 2.70 Build 12.04.2006

Optimizing speed in Scriptbrowser dialog

Selecting a macro in the macro list started some internal tasks on each selection. Theese internal tasks are started now only at the first selection. As a result, selecting and displaying a macro runs from the second time of selection much faster.

Option Default can be used within the Workbench in buttons

The option Default was reserved within the Workbench for the OK-button. Now you can define in the property dialog of a button this option. A default button has a thick border and is activated by the ENTER key.

Version 2.70 Build 12.01.2006

Tabulator Scripts in dialog Settings for Script settings

The dialog Settings contains the new tabulatorr Script. In this tabulator you can specify the settings for the SyntaxColoring and with the option Debug all macros you can define the type of error handling on an execution error in a macro. With the default setting No you can open the debugger on macros belonging to the logged in or a subordinated worker only. With the setting Yes you can open the debugger on each macro no matter to whome is belongs. The Details about you will find in the documentation OfficeTalk Business-Process-Management.

ScriptDialog with grid for a better build

On creating an script dialog you can show and hide with the new context menus Show grid and Hide grid vertical and/or horizontal lines for helping while adjusting dialog elements. With the context menu Grid... a setting dialog is opened to specify the grid details. If the grid is shown, inserting, moving and sizing an item is adjusted on the given grid size. The Details about you will find in the documentation OfficeTalk Business-Process-Management.

Version 2.70 Build 11.28.2006

Performance of script macros wirth action blocks in service addAction(...) dramaticly optimized

When executing a script macro, using an action block of the the service addAction(...) resulted in compiling the block first on each call. This caused extra time. Now action blocks are cached like macros and because of this cache, macros with action blocks are executed dramaticly faster. This resulted in faster execution of processes whitch use actions with such kind of script macros.

Version 2.70 Build 11.25.2006

New service inlineActions(...) for systemvariable ScriptDialog

Actions, installed with addAction(...), are started by default on changing the content by a user interaction only (e.g. typing in something). Changing of a item's content with the service value(...,put:...) or value(...,select: ...) do not start such actions. With the service inlineActions( True ) theese actions are started by such programmatic (inline) changes too. For this new setting the Workbench contains in tabulator Scriptdialog the new option Trigger actions on programmatic changes too.

Service value(..., put: ...) for a combobox in scriptdialog

The service value(..., put: ...) for a combobox should put the choices with the argument put: into the list. Instead of the execution of the macro was ended with the error message ... Stop execution of the macro....

Wizard for searching a worker do not open the matching worker when started within organigram dialog

When the wizard was started from the organigram dialog (menu Organigram in portal Dialog), a matching worker was selected in the list, but not opened.

Wizard for searching a worker select text in the result if given as pattern

The wizard select the text or text part within the script macro or worker description, if the pattern contained a text.

Version 2.70 Build 11.24.2006

Wizard for searching a worker extended

Searching a worker, you can define wether to stop searching at the first match or scanning all visible workers. If more workers are found, you can select the wanted worker within a list dialog. For details please read documentation OfficeTalk Business-Process-Management.

Parallel scheduling of processes

If a worker scheduled a process (e.g. He filled out a dialog while scheduling the current step), a second worker could start a new process, but the scheduling of the first step was serialized with the ending of the current step of the first worker. The continuing of a started process by scheduling the next step had to wait for the ending of the step of a previous first worker too. This happened if the database Microsoft-SQL-Server or PostgreSQL-Server was used only !

Logged in worker is changeable in Function-/Organigrambrowser

If OfficeTalk was started with the portal Function-/Organigrambrowser, other visible workers could be changed if they where logged in. The message The worker is used by another and can not be changed like OfficeTalk is started with the portal Dialog.

Wizard for searching any item within the organigram

For searching an item with specific criterias you can use the search wizard Search.... With the wizard you can find a worker containing a specific item with given criterias. You an use all items starting from the Adress to Scriptmacro content. If the item is found, its owner, the worker is opened and the tabulator with the found item is opened.

Version 2.67

Additional command window on Windows platforms on some situations

Creating the database on the first start, or executing the Shell function in a script macro or opening any help started first an empty command window before the related task was performed. Now, opening this empty command window is skipped.

New services in system variable ScriptDialog

The system variable supports the new services value(..., put: ...) and value(..., select: ...) to make the semantic of the value-service names equal. The services put(..., value: ...) and select(...,value: ...) exist further, but should not be used anymore.

Function Ubound not recognized in Script macro

If the funcion war written Ubound but not UBound, it was interpreted as a variable name and formating or exercuting the macro resulted in wrong results.

Version 2.67 Build 11.10.2006

Export a worker or a hirarchy of workers in the Organigrambrowser dialog

If you export with the context menu Export... in the organigram list field a worker or a hirarchy of workers, you get an information dialog after the export is done, if some aspects of a worker had to be changed in the export file. Theese modifications are neccessary to be able to import the exported worker into another OfficeTalk-System.

Version 2.67 Build 11.07.2006

Backward links of steps in dialog Processgraph: <name of process>

Backward links, a step in a lower row has a successor in a higher row, where connected with a straight connection line. If another step lied between, it was crossed by this line. Now the connection line of a backward link is directed arround steps between and the diagrams readability is a little bit better.

The path of a process template can be extended at the start in the dialog Processgraph: <name of process>

In the dialog you can extend the path with a new step at the beginning. If you insert a step with click into the template with steps, the new step is inserted at the beginning.

Version 2.67 Build 11.04.2006

Removing the first step of the process in dialog Processgraph: <name of process>

Up to now, the first step of the process could not be removed. Now the first step can be removed too, if it has maximum one successor step (not counting himself).

Version 2.67 Build 11.01.2006

New services enableRecursion and disableRecursion of the systemvariable StepScheduler

The services allow or disallow a recursion of the step execution. In some situations it is reccessary to execute the same step twice without delay. In this case you must enable recursion with the service enableRecursion. It the recursion is not neccessary anymore, you must disable it with the service disableRecursion. By default recursion is disabled.

New symbols for database actions and webservices for steps and actions

In the tabulators Processoptions, Startactions, Useractions, and Endactions of the stepdialog you can use special symbols for a database action and the use of a Webservice the demonstrate the reason of the step or the action for theese task types.

Version 2.67 Build 10.31.2006

Opening a process template with button Diagram in tabulator Processtemplates

If a diagram of a not stored process template was opened with the button Diagram in the tabulator Processtemplates of a worker's dialog and the template was stored in the opened dialog Processgraph: <name of process>, the template was not inserted in the template's listfield and some error messages might occure later.

Version 2.67 Build 10.30.2006

Inserting an element in the list field with the context menu Paste

Inserting an element (Process template, Absent, Right or Resource, ...) with the context menu Paste in the list field inserts the element not in the list field but inserts the element in the dialog field at the right side. So you can make the neccecaray changes first ans add it with the New button second.

Version 2.67 Build 10.27.2006

Pasting a process template and creating a process template with selected step of another template

If you insert a process template in the tabulator Processtemplates with the context menu Paste or you create a new template with the menu Work - Create process from path in the dialog Processgraph: <name of process> with seleced steps of the displayed process template, you get a name dialog, to change the given template's name, if you want. Because a process template's name can not be changed later.

Version 2.67 Build 10.18.2006

Start with tasklist in startportal Full Browser

With the General settings Full Browser and the Task settings Open with Tasklist, OfficeTalk was terminated with an error message when started, sorry. The startportal had to be changed by hand first in the settings (Registry on Windows platforms or file OfficeTalk.ini on Linux platforms).

Syntaxcoloring of the argument title in the function MsgBox

The argument title of the function MsgBox was never colored.

Debugging of a macro called with Call

When a macro was started with the context menu Debug of the script list in the ScriptBrowser. and a macro was called with the Call statement, it could not be debugged when it was contained in an worker superior to the owner worker of the start macro. The Call statement answered the result of the macro execution, but the debugger did not visit the macro itself.

Import of processes from the system AENEIS of the company intellior AG

You can now import process definitions from the BPM-system AENEIS of the company intellior AG and after completing the required supplements you can execute/schedule it.

Version 2.67 Build 10.14.2006

Opening a Hirarchybrowser with used Function/Organigrambrowser

If a Hierarchiebrowser of a process template should be opened in the register Processtemplates of the worker's dialog with the context menu Hirarchybrowser..., OfficeTalk was terminated with an error message, sorry.

Syntaxcoloring for a macro executed with the debugger

The Syntaxcoloring of a macro, witch was executed with the debuffer because of an error, was sometimes false.

Formating of a script macro and case writing of names in Call- and Start-statements

Formating a macro within the Skriptbrowser with the context menu Format of the source dialog field, case writing errors of process template names within the Start-statement and script and macro names within the Call-statement where not corrected as documented. Case writing of theese names do not affect the execution of the macro, but formating should correct theese errors too !

Context menu Unlock in startportal Function-/Organigrambrowser

The context menu Unlock was not available in the organigramm list dialog if OfficeTalk was started with the Function-/Organigrambrowser portal. This context menu was available, if OfficeTalk was started with the portal Dialog only.

Using existing files for the export

If in the file selection dialog a filename of an existing file is used, the user is warned and can type in another filename to avoid overwriting an existing file.

Version 2.67 Build 10.08.2006

New service selection() of the systemvariable ScriptDialog

The new service selection() answers for any type of list field (Listfield, Combobox and Table) similar to the service value() the selected item. For input fields the service answers the part of the input text if selected any.

Service selectionIndex() of the systemvariable ScriptDialog

The service selectionIndex() answers the number of the selected item in a combobox field or table field. For an input field the service answers the cursor position. The answered index is based on 1.

Formating a scriptmacro with Syntaxcoloring switched on

Formating a scriptmacro with activated Syntaxcoloring in done now about 100 percent faster. Displaying a macro with selecting its entry in the macro list of the Scriptbrowser is affected by this change too.

Version 2.67 Build 10.05.2006

Extended onlinehelp for typing in a Return value while writing a script macro

Opening the onlinehelp for a required Return value opens the selecting dialog with all possible values in a tabeled list field with 3 columns, if you are writing the macro within the tabulator Scripts. You can sort the lines in this list field by the different columns and can find faster the required value.

Formating the source of a script makro in tabulator Scripts (the Scriptbrowser)

If the source input was done without any basic format (e.g. one line with two ore more statements) and Syntaxcoloring was required, formating was aborted with the message The macro could not be compiled because of a general syntax error.... Compiling the macro was possible ever.

Saving in portal Function-/Organigrambrowser using the Evaluation version

Saving the data into the internal database with the toolbar button Save or with the menu File - Save in the Function-/Organigrambrowserdialog did not really save the data into the internal database. Only the Evaluation version was affected by this error !

New organigram format (traditional) is supported

The toolbar with the traditional organigram symbol open the organigram in the new supported traditional format. For the old format (organigram as list/browser) you find new toolbars with a list symbol. For details please read documentation OfficeTalk Business-Process-Management.

Version 2.66

String with containing character " in a script macro

If a string contained the character " (e.g.. "this is my ""name"""), formating the macro removed the double ".

New services mandatory() and mandatoryMessage() of the systemvariable ScriptDialog and extended property dialogs in the Workbench

With the service mandatory() you can define, what dialog items must be filled out in any case, to accept the dialog. With the service mandatoryMessage() you can specify the message text to notify missing mandatory inputs. For details please read documentation OfficeTalk Scripting.

The property dialogs of the affected dialog items in the Workbench contain the option Mandatory. If you choose this option, the line dialog.mandatory("<dialog item name>") is inserted in the macro.

Menu item Debug und Run in the Scriptbrowserdialog

The context menu of the source's dialog field of the Scriptbrowserdialog supports the commands Run und Debug. Theese items and their shortcuts F10 and F11 run and debug the displayed macro.

The shortcuts Run and Debug in the contextmenu of the script macro list field (the list field right top in the Skriptbrowserdialog) were changed to F10 und F11 like the context menu of the source.

Infinite loop when logged in with a wrong Environment name

If the PostgreSQL variant was started and in the login dialog an enviroment of a valid MS-SQL database connection (ODBC entry) was typed in, OfficeTalk run into an infinite loop. The same happened with the vice versa combination. This problem happened, if both databases PostgreSQL and Microsoft-SQL where installed, and the database type defined by the environment DatabaseType (on Windows platforms in the Registry HKEY_LOCAL_MACHINE\SOFTWARE\JOOPS GmbH\OfficeTalk\DatabsseType, on Linux platforms in the file OfficeTalk.ini) matched to a wrong, but existing database connection defined by the environment name in the login dialog. This error did not happen on Oracle and DB2 databases !

Version 2.66 Build 09.18.2006

Removing temporary Halt in script macro

To remove a temporary Halt within a macro, the macro had to be compiled. The context menu Halt did not remove the temporary Halt.

Name and label of an action button in the Workbench

In the Workbench you can define for an action button the name and the label different. To enable this, the name field in the action button property is editable. If an existing macro is opened with the workbench, the name is used as the label.

Version 2.66 Build 09.16.2006

Assigning a process template in tabulator Substitutes

Selecting a process template in the combobox Process did not fill out the combobox field with the selected entry. Assignig a process template was not possible.

Opening the Hirachybrowsers in the tabulator Common Processtemplates

If the Hirarchybrowser for a process template was opened in the tabulator Common Processtemplates, the template must be read only, because it is owned by another worker.

Copying a worker with the context menu Copy running the portal Function-/Organigrambrowser

If the portal Function-/Organigrmmbrowser was used and a worker in the left organigram list of the Organigrammbrowser was copied with the context menu, OfficeTalk was terminated with an error message, sorry.

Abandom Scriptmacro changes with Using level Expert

If changes of a macro in the tabulator Scripts should be abandomed by cklicking another item (macro, worker, e.g.), the message Do you want to save, abandom or abort the changes... did not appeare. The answer abort was assumed instead.

Wromg onlinehelp writing a Sktiptmacro

Writing Library and two spacs did nor open die file selector dialog for choosing the commnication library, but the dialog for selectiong a service if after Library a declaration like Dim <xxx> As ScripDialog was found.

Usingdialog of a script opens the calling action

Double clicking an entry in the script using dialog opens the step and the tabulator containing the action and now the action itself too. With this opening you can see within more actions whitch one uses the script.

Result of evaluating a script macro in testmode

The result of a macro evaluated in testmode with the context menu Schedule... in the scriptbrowser notifies with a dialog the result. In some cases, e.g. Return stepscheduler.currentEnvironment(...), not the result, but the result's datatype was displayed.

New service userEnvironment() of the systemvariable stepscheduler

With the new service userEnvironment() you can ask for the value of a user enviroment. On Windows-platforms the user environment is defined with Systemcontrol - System - Environmentvariables. On Linux-platforms the user environment is defined with Login-Scripts.

Property dialog Actionbutton in the Workbench

The input fields Name and Label in the property dialog of the action button where not initialized with the same name ever. Changing the input field for the Label synchronisized the name and label, but it was somehow suspect.

Alt Gr-keyboard combinations while editing a macro in the Workbench

The last change (Wrong CTRL-keyboard combinations while editing a macro in the Workbench) has switched off any Alt Gr-key too. Because of this, typing in a file path for the Library directive was not possible anymore. This is a good example of making something more worse than better. But because of our users, such error is corrected fast !

Function MousePointer with Syntaxcoloring in Scriptbrowser dialog

Using the function MousePointer in a script macro with activated Syntaxcoloring resulted in an error message and termination of OfficeTalk, when the macro should be displayed in the Scriptbrowser's dialog, sorry.

Contextmenu Format for Scriptmacro with comments

Formating a macro does not change the position of comments of statements anymore. The position of theese comments is preserved as possible. Only the header of the macro (name, comments, declarations, etc.) is formated with the built in rules.

Wrong CTRL-keyboard combinations while editing a macro in the Workbench

Some forebidden CTRL-combinations where not ignored. Instead of intern menu actions where performed and resulted in some curious text within the source.

HTML-Export of a process template contains resources used by actions

The HTML-Export of a process template lists the ressources, used by actions too.

Name and label of action buttons in the Workbench

Action buttons use the label as their name, but in the property dialog a name different from the label was possible. After compiling and opening the macro the name field contains, as documented, the content of the label field. Now the input field for the name is read only.

Displaying source faster if Syntaxcoloring is switched on

Macros, containing no actionsblocks (e.g. dialog.addActionButton(...) ), are displayed in the Scriptbrowserdialog faster if syntaxcoloring is switched on.

Syntaxcoloring of Stringliterals containing the character '

The brackets ( and ) are not colored after a string literal containing the character '.

Syntaxcoloring for an argument in the headline of a scriptmacro

If the argumentname begin with 'Dim...', this namepart was colored with the keyword color.

Content of tabulator Database in the Workbench

If for the scripdialog a result variable and minimum one result target for a script element is given, database statemenmt are put into the OK-block of the dialog (If answer = True Then ... End If). With this change, the database statements are executed, if the dialog is closed with accept or with the OK button only.

Temporary und static halts in script macro

With the function Halt you can set a static halt to open the debugger at this point. With the context menu Halt in the input field of the source you can set a temporary halt. In opposite to the first one, the last one is forgotten on logout. For details please read documentation OfficeTalk Scripting and OfficeTalk Business-Process-Management.

Syntaxcoloring of the header line of a script macro

The header line of a macro(<macroname> (...)) was not colored in the right way, if Syntaxcoloring was switched on. This was seen especially on a black background.

Syntaxcoloring for the syntaxelements (, ) and ,

For the syntaxcoloring of the special characters (, ) and , you can use the two new buttons in the compiler setting dialog. The button (...) is responsible for the color of the brackets. The button Delimiter (,) is resposible for the color of the delimiter ,

Syntaxcoloring for = in assignements

In an assignement the special character = was not colored if Syntaxcoloring was switched on. Now it is colored with the color Keyword.

Syntaxcoloring for commnts in variable declaration

A comment in the declaration line of a variable (Dim <name> As <datatype>) was not colored if Syntaxcoloring was switched on.

Syntaxcoloring of the function Enum

The argument Enymtype (the last argument) of the function was not colored if Syntaxcoloring was switched on. Now it is colored with the color Class/Datatype.

Syntaxcoloring of the directive Library

If the filename of the directive was given as literal, it was not colored as required if Syntaxcoloring was switched on.

Opening extent of the online help dialog is optimized

The width and height of the selection dialog for the online help in wrinting script macros is optimizes for extra large entries and only one entry. For extra lage entries the dialogs width is made 3/4 of the screen size. For only 1 entry the dialogs height is increased, because otherwise the vertical scrollbar is displayed wrong. Theese are small modifications, but in OfficeTalk small things are important too.

Onlinehelp writing Call-statement in a script macro

The selection dialog shows for macros with arguments the argument names too similar as the declaration (e.g.: name As String, town As String, ...). This makes the writing of Call-statements with a macro with arguments easyer.

Onlinehelp for services with dialog item arguments

The online help for the selection of dialog item names for services requiring an item name did not support some newer services.

Property dialog for tables in a Scriptdialog of the Workbench

On some using sequences (create column, remove column, ...) in the property dialog for a table, OfficeTalk was terminated with an error message, sorry. Additionally the scrollbar of the column list was not actualized in any case.

Selecting a service of a variable using a datatype within a communication library

If a service of a not loaded communication library's datatype should be selected by typing in <variablename>. Space, die service dialog was not opened and OfficeTalk was terminated with an error message. This error occurred since intrioducing the Sytaxcoloring.

Filtering processes in tasklist by delay type

The filter dialog Filter processes opened by the menu View - Filter processes by in the tasklist, supports now to filter processes by the delay type (red, yellow or green). Select the delay mode in the new combobox Delay:. For details please read documentation OfficeTalk Workflow.

Creating a process template from some steps of another template

The menu of the dialog Processgraph: <name of process> supports in Work the new entry Create process from path. This menu item creates a new template from the selected steps of the current template. The name of the template is taken from the step's name. All other properties are taken from the current template. The worker gets the same permissions for the new created template as he owns for the visible template. Consecutive steps must be selected, to create a template in this manner !

Formating script macro and the Library-Directive

A Library directive is not executed at format time anymore (loading of a communication library). Additionaly Class-/Typnames are not validated at format time. The extension Syntaxcoloring is the reason of this change. Because of the Syntaxcoloring, Library directives where executed and given Class/Typenames where validated when a source was displayed by selecting the macro in the list field of the Scriptbrowser.

Error when a wrong assignement of an Array variable to a String variable

Assigning an Array variable to a String variable affected in an error message and OfficeTalk was ended, when dthe macro was executed. Now assigning such varriable types, an automatic type converting is performed.

Usings of a resource in all process templates

The list field in the tabulator Resources of the worker dialog supports the item Usings.... This menu item opens the using dialog for the selected resource. The dialog shows all places (step and aktion), where the resource is used. Double clicking a single use place opens the step and the action, where the resource is assigned.

New services show() and hide() of the systemvariable ScriptDialog within script macros

With the new services dialog items can be made invisible and visible dynamicly. In normal cases theese services are used in action blocks (addAction(...), addActionButton(...). For details please read documentation OfficeTalk Scripting.

Processright required for assigning a worker as executer

To assign a worker as executer in the register Options of the Stepdialog, the worker needed the Abort-permission for the process. This is not neccecary !

Number/Currency format in property dialog of input fields of the workbench

The preseted format for currency and numbers was set to anglo format (0,000.00) instead to the european format (0.000,00).

Invalid character for variable name in tabulator Variable of the Workbench

In the tabulator Variable variable names containing _ where rejected. But this character must be accepted for variable names.

Contextmenus in scripteditor accessable with shortcuts

All context menus of the source text field in the tabulator Scripts are accessable with shortcuts for faster typing.

Syntaxcoloring for source in tabulator Scripts

In the text field for the source within tabulator Skripts the source text is colored with syntax rules. The used syntax colors can be predefined with the new toolbart button. Syntay coloring needs a few seconds, but the reading of longer sources is much easyer. For deatails please read OfficeTalk Business-Process-Management.

Version 2.65

Messagebox for discarding changes in Organigram-/Functionbrowser

Selecting another entry within the left list field resulted, if not all changes where saved, in few cases in a message box with Save/Cancel only. So, some modifications where not be made simlpy rolled back. Now in any case the mesagebox with Save/Discard/Cancel is used to roll back all changes simply. Only the portal Organigram-/Functionbrowser was affected.

Contextmenu Workingoptions - Worker in dialog Processgraph: <name of process>

The menuentry did not contain all possible workers to assign the step.

Using the portal Organigram-/Functionbrowser and login for a selected worker

If in the portal Organigram-/Functionbrowser a worker was selected in the left list field and a login for this selected worker was started, the login was denied with the message This worker is logged in allready. The selected worker had to be deselected first.

New system type for basic file operations within script macros

With the new system type FileSystemObject you can perform basic file operations like removing directory, renamig a file and accessing a filename. For details please read documentation OfficeTalk Scripting, Chapter Systemvariable FileSystemObject.

New services in script macros for reading and writing INI-files

The sematic of INI files offers a powerfull way to read and write parameter files in a defined way. To support this within script macros, the systemvariable stepscheduler supports two new services environment(<Key>, category: <Category>, in: <File>) und environment(<Key>, category: <Category>, in: <File>, put: <Value>) an. Details about you find in the documentation OfficeTalk Scripting.

Importing from MO²GO of Fraunhofer Gesellschaft IPK is much flexible

To make importing processes and organigrams from a MO²GO-System more flexible, you can define a mapping between attributes in MO²GO and in OfficeTalk. To define this mapping, open the mapping dialog with the menu Extra -Importmappings. This mapping can be defined for workers, processes and steps separatly. Additionally document references for process- and step-description are taken over at import time.

Unneccessary creating the internal database on menu File - Exit

If OfficeTalk was ended with the menu File - Exit of the main dialog in the internal database OfficeTalk.bos was written in the directory OfficeTalk\bin.

Login after Logout on using Microsoft SQL-Servers with NT-Autentification

If a login was performed after a logout (menu File - Login/Logout) was done, for the login on the SQL-Server the given login was used. But for the SQL-Server login, the windows login must be used in this case ever.

Exporting a macro and its called macro when exporting a process template

Exporting a process template means exporting the used scripts and macros too. Used submacros are detected by a Call-statement within a macro. But, if such a Call-statement was commented with a preceeding ', the export mechanism tryed to export the called macro wihout respect to the commentation. Now commented lines are ignored by the export.

Wenn eine Vorgangsvorlage exportiert wird, werden auch die davon verwendeten Skripts und Makros exportiert. Wird in einem Makro mit der Call-Anweisung ein weiteres Makro gerufen, so wird auch das Skript, in dem dieses Makro enthalten ist, exportiert. Wenn nun die entsprechende Call-Anweisung mit einem vorangestellten ' auskommentiert war, wurde totzdem versucht, das angegeben Skriptmakro zu exportieren. Jetzt werden auskommentierte Zeilen eines Makros auch als solche behandelt, nähmlich ignoriert.

Missing script when exporting a process template

If a process template is exported and a used script of an action is not found, the error message names the step and action of the using location too. This helps you the localize the error faster.

Starting and executing System-Login processes at login

This process was started, if in the settings of the worker the option autom. tasklist was set to Yes only. Now this process is started and executed in any case, if it is accessable.

Export Process/Organigram with high color settings as HTML

If the settings for the display contained a high color setting, exporting a process or an organigram including the image as HTML was denied with an error message.

Changing a worker remains the selected tabulator

If you select another worker in the left list field of the organigram browser, the selected tabulator remains unchanged for the next worker. This makes working withing many worker easier.

New tabulator Common process templates in worker dialog

The worker dialog and the Function-/Organigrambrowser supports the new tabulator Common process templates. This dialog contains all process templates of all visible superior workers (Department, Office. etc.). Additional you must have the permission Process read to see a process in this dialog. The processes can be worked as described in tha tabulator Process templates. But you can not change a process in this way, because this is a read only dialog. A process may be changed by its owner on another computer, you must actualize the dialog with the context menu Actualize to update this view.

Mit Ausnahme des Unternehmens enthalten die Bearbeiterdialoge und der Funktions-/Organigrammbrowser für nun das Register Gemeinsame Vorgangsvorlagen. Darin werden die Vorgangsvorlagen aller übergeordneten Bearbeiter (Abteilung, Büro, usw.) gezeigt, die der Bearbeiter laut seines Sichtbereichs sehen kann und wofür er das Recht Vorgang sehen besitzt. Im Listfeld der Vorgangsvorlagen wird neben dem Namen in Klammern auch der Eigentümer gezeigt. Die Vorlage kann, wie jede eigene Vorgangsvorlage, mit den im Register Vorgangsvorlagem beschriebenen Aktionen geöffnet werden. Sie kann jedoch nicht verändert werden ! Da hier Elemente anderer Bearbeiter angezeigt werden, und diese während Ihrer Anmeldung ja vom Eingentümer an einem anderen Arbeitsplatz geändert werden können, müssen Sie die Liste eventuell mit dem Kontextmenü Aktualisieren auf den aktuellsten Stand bringen.

Displaying step description in dialog Processgraph: <name of process>

When you touch a step with the mouse within the dialog, its description of the tabulator Description in displayed in a FlyByHelp window.

Version 2.64

Mögliche Vorgangsvorlagen in der Auswahlliste Vorgang des Registers Rechte

Die Auswahlliste hat auch Vorgangsvorlagen von Bearbeitern, die sich in der selben Organisationseinheit (Abteilung, Team, usw.) befanden, angezeigt, obwohl diese Vorgangsvorlagen nur vom Eigentümer selbst gestartet werden können. Jetzt werden nur noch die startbaren Vorgangsvorlagen angeboten.

Portal Full and Restricted Browser

Starting OfficeTalk with the Full or Restricted Browser terminated the application with an error message since the change Picture "Chaotic chairs" can be replaced by a picture of your own. The start portal had to be changed first to Dialog by changing the environment OpenWithBrowser to "0".

.Net Systems and components are supported in nativ mode

In script macros native .Net-Systems and components are supported now. The supplier must not deliver the system or component with COM support, to be used within a OfficeTalk script. Only Microsoft window platforms are affected by this extension !

Typing in values in dialogs with time and duration fields

In the dialogs with time and duration input fields, typing in a not allowed character was possible. The unallowed character was displayed but not accepted. Now, unallowed typed in characters are not displayed anymore.

Option with Details affect step result

The option with Details in the dialog Settings of the dialog Processgraph: <name of process> affects the labeling of the step results (the blue connection lines) too. Without this option, the step result is labeled with its name and without sequence number and delay time. This gives more overview !

Systemprocesses for program start where not started at first login

If you logged in as Company, Department, Office or Team the first time, existing system processes System - Start where not started.

Comunication library for Docuware 5

The communication library for Docuware Version 5 is installed by the setup. If you have installed DocuWare 5, and want to integrate it into a process, you must load the communication library within the script macro with the directive Library ..\Library\Docuware5.pcl.

Start of OfficeTalk with commandline arguments

OfficeTalk can be started now with arguments within the commandline. On Windows platforms theese arguments must be given in the property dialog of the desktop icon. On Linux platforms the arguments must be given within the commandline. Details about the supported commandline arguments you will find in the documentation OfficeTalk Business-Process-Management.

Login in evaluation version

The login in the evaluation is much simplified. If OfficeTalk runs with the internal database (option Datenbase: No in Settings), all possible login names are given within the combobox field Login: and no password is required. All other login modes are unchanged and available in the evaluation version too.

Removing an element in dialogs combined with a list- and a dialogfield

If an element was removed with the button Remove... of a combined dialog, this element could not be inserted later with the context menu Paste in other allowed list fields. In other words: The clipboard did not work with the Remove button of combined dialogs.

Opening a step with double click in dialog Processgraph: <name of process>

Using the portal Function-/Organigrambrowser and opening a step within the dialog Processgraph: <name of process>

with a double click, OfficeTalk was ended with an error message. This error did not occurre, if another portal (Dialog, Browser, etc.) was used !

Starting OfficeTalk with an invalid database environment setting

If OfficeTalk was started with an invalid environment for DatabaseType, no useraction was possible and the consumed memory runned out. This error occurred using Microsoft-SQL-Servers or PostgreSQL-Servers only !

Choosing toolbar button Settings in logged out state

If the startportal Function-/Organigrambrowser was used and the toolbar button Settings was clicked without first login, the message Server not reacheable... appeared infinite. OfficeTalk had to be terminated hard (Taskmanmager on Windows-platform or kill -9 on Linux-platform). This error occurred using Microsoft-SQL-Servers or PostgreSQL-Servers only !

Scriptbuilder supports buildung macros with using a DB2 SQL-Server

In the tabulator Database you can build a macro with using a IBM-DB2 SQL-Server. Select in the dialog Define used databse the option DB2 SQL-Server the create the macro fitting for use a DB2 SQL-Servers.

Import of a complete organisation from the system MO ² GO (Fraunhofer Gesellschaft IPK)

In the dialog Organigrammbrowser and in the dialog Organigramm for: <workername> you can import a full organisation with its processes from the system MO ² GO. After imported, you can schedule the imported processes. Select in the context menu the item Import... and choose the file type MO ² GO Organigram in the file select dialog. The organisation with its processes is imported from the selected shx-file. If problems where detected, you get a notifyer dialog describing theese problems.

Integration of external documents in descriptions of OfficeTalk elements

In description fields of the elements you can define external documents too. The context menu contains the two new entries Insert document... and Open selected document. With theese new menu entries you can extend your descriptions with external text, video- and audio documents. For details please read documentation OfficeTalk Business-Process-Management.

Installation of OfficeTalk with using a PostgreSQL database server

Using a PostgreSQL database server the OfficeTalk database was not created automaticly at the first start of OfficeTalk and it could not be used after, sorry.

Choosing the tabulator Mail in dialog Settings

If in the variant OfficeTalk/MS the tabulator Mail was selected within the dialog Settings, OfficeTalk was teerminated with an error message, sorry.

Skriptbrowser was in Read-only state

Opening the Scriptbrowser within the tabulator Useraction of the step dialog, creating, removing and changing a macro was not allowed. To create, change or remove a script or macro you had to switch to the tabulator Scripts within the workers dialog.

Abort if online help for a Return statement is used

If the online help for a Return statement was used, OfficeTalk was terminated with an error mesage after selecting a returnvalue. This happened only it the macro was edited within the script browser, opened from a steps tabulator Useractions.

Missing aggregates in an imported worker

If a worker was exported and imported into another OfficeTalk system, some contained aggregates (script macro, authorize, permission, ...) may be missing in the imported worker.

Programm aborted on removing a step result in dialog Step <stepname>

Removing a step result in the tabulator Stepresults of the dialog Step <stepname> and second closing the dialog with the menu Save and Close, OfficeTalk was terminated with an error message. This error occurred if the step dialog was opened from the dialog Processgraph: <name of process> only !

Conncting steps or changing connections with the mouse in the dialog Processgraph: <name of process>

Up to now connecting two steps with a new connection (blue line as step result) by dragging the mouse from the source to the target step, only a symbol was shown to visualize the dragging. Now, for a better visualization a temporary connection line is dragged from the source as you move the mouse.

Bisher wurde das Einziehen neuer Verbindungen oder das Ändern vorhandener Verbindungen (die blaue Linie als Arbeitsschrittergebnis) nur durch ein entsprechebndes Symbol angezeigt. Jetzt wird zur besseren Visualisierung zusätzlich eine temporäre Verbindungslinie für die zukünftige Arbeitsschrittverbindung entsprechen Ihrer Mausbewegung gezeigt.

In the evaluation version changes were not stored into the database in every case

If a dialog was closed with the window close button (cancelling) and the question Do you want to save the changes..., was answered with Yes, the changes where not stored into the internal database. Only the evaluation version was affected by this change !

Entries for waiting where not displayed with the semaphore

The entries for waiting for thevend of another process or for getting the mail answer where not displayed with the semaphore symbol in the history list dialog.

Changing the execution time of a running process

Changing the execution time of the next step of a running process can be done with the menu Delegate/Change within the tasklist, if the worker owns the required permissions. This change is now historied with a special clock-entry within the process history.

Database DB2 is usable for OfficeTalk

OfficeTalk runs under the database system DB2 of IBM. Only the installation of OfficeTalk is specific to the database. The dayly using is equal to the other database system types (Microsoft-SQL, PostgreSQL and Oracle-SQL). For detail of database specific installation please read documentation OfficeTalk Installation (Installation.pdf).

Picture "Chaotic chairs" can be replaced by a picture of your own

The picture "Chaotic chairs" in the main dialog and in the dialog About OfficeTalk can be replaced because of CI reasons by a picture of your own. Put a file named Picture with the extension GIF, PGN or BPM into the folder OfficeTalk\Gallery. The size of the pictures should be 235 x 238 pixel.

Passing an argument, received from a service, to the Call statement in script macros

If the result from a service was passed as argument to the called macro without an extra assignement, not required transformation was done and the called macro got a date in the wrong format.

An example: Call Text.Substitute(word, bookmark, processdata.item("Datum", in: "Kunde")).

If the service processdata.item(...) returned a Date but the macro assumed a String as thirt argument , the macro may have been aborted because of handling a wrong data type.

Communication library Microsoft Word Small.pcl is extended for inserting pictures into a document

The communication library is extended with the system variale SmallCOM.Word.InlineShapes to be able to insert a picture into a document without using the large communication library Microsoft Word.pcl . This saves time, because the communication library Microsoft Word.pcl needs much more time than the smaller library Microsoft Word Small.pcl to load with the directive Library inside a script macro.

Error when inserting a picture in a document with the communication library Microsoft Word.pcl

Inserting a picture with the service addPicture( ..., linkToFile: ..., saveWithDocument: ..., range: ... ) of the systemvariable SmallCOM.Word.InlineShapes resulted in an error message. Inserting a picture with the service addPicture( ...) worked without problems.

Service processdata.item(..., with: ..., in: ...) with numbers and digits after the decimal point

The service of the systemvariable stepscheduler stored numbers with digits after the decimal point under some rare circumstances in the wrong way.

Call-Function as left operand in &-expressions building a script macro

A Call function was not possible in binary &-expressions as the left operand. Compiling or formating a macro with such a statement was aborted with an error message.

Opening a modified macro with the Workbench

If a macro, built with the Workbench, was modified later by hand (processdata.item(...) was inserted at the beginning), this macro could not opened with the Workbench again.

Statements in tabulator Startstatements, Endstatements and WebService in the Workbench

The syntax of the content of the statements field in the named tabulators is verified at leaving the tabulator and when pushed the button Build. If a syntax error is detected, a hint is inserted at the error position.

New services for systemvariable stepscheduler in script macros

The systemvariable stepscheduler supports the new services format(..., as: ..., with: ...), format(..., as: ...) and format(...). With theese services you can convert a variables content with the format rules, dscribed in chapter Rooles [Colors] of the documentation OfficeTalk Script, to a string.

The presetted format string for dezimal fields in the Workbench

The presetting format sting for decimal fields in the property dialog of input fields in the Workbench was wrong. The decimal and thousand separator was changed. In this field the characher . is used as the decimal- and the chartacter , is used as the thousand separator.

Workbench readed a script macro with statement processdata.item(..., with:..., in: ...) in the wrong way

If the Workbench opened a script macro containing a named statement within the result block of the dialog (accepted = dialog.open If accepted = True Then ...) the processdata was inserted into the tabulator WebServices.

A Return block was readed wrong by the Workbench

If a script macro with a Return condition block like If accepted = True Then Return "geschlossen" Else Return "abgebrochen" End If was opened by the Workbench, the tabulator Return was filled with the expression "abgebrochen". The rest of the Return condition (If accepted = True Then Return "geschlossen" Else ...) was lost.

Version 2.63

Importing a comlete company

You can now import the complete structure of an organisation. All workers of the company (Desk, Machine, Office, Department, Team) and its content is imported. If a same named element (resource, script, permission, process template, etc.) should be imported, you get a dialog with the old and new version. Within this dialog you can choose the further strategy. With this extension you can build a comany's structure in an OfficeTalk system, export this and import it into another OfficeTalk system. Supporting and building a company offline is much easier with this feature.

Importing process templates

Importing a process template, the used workers had to exist in both systems (sender and target). The import is extended to ignore missing workers. You can decide with the answer of a messagebox how to proceed. For details please read documentation OfficeTalk Business-Process-Management.

Inserting a new step result (connection line) in dialog Processgraph: <name of process>

To insert a new step result (connection line) between two existing steps, you must not open the start step, choose the tabulator Stepresults, aso.

You can connect two steps simply with pressing the left mouse button onto the start step and dragging it to the end step. After this you get a dialog for the name and the time settings. Choosing the Accept button inserts the new connection line.

Label of step result in dialog Processgraph: <name of process>

With the settings At, Weekday and Monthday in the group file Starttime, the label of the connection line displayed immediatly ever.

New symbol for step results

Step results are displayed with a new symbol, a connection line between two steps. This symbol is more intuitive than the previous one. This is a small change, but for beginners this symbol is more declarative.

Removing histories of finished processes

You can remove the histories of finished processes now within the tabulator Processtemplates too. The context menu of the left list field contains the new entry Remove History.... For details please read documentation OfficeTalk Business-Process-Management.

Exporting the organisatuin structure as HTML-file

The menu Organigram in the dialog Organigram for: <workername> contains the new item Save as HTML.... The HTML export contains the organigram and the description of the visual workers within the listfield only. The get the complete organisation structure in the HTML file you must unfold all + signs in front of the passive workers. With this feature you can easily publish parts or the complete organisation structure, starting at the top level worker in the opened organigram. You can define the size of the export within an opened option dialog. For details please read documentation OfficeTalk Business-Process-Management.

Importing a process from the system MO ² GO of the company Fraunhofer Gesellschaft IPK

If a process with errors was imported, a dialog, describing problems found, is opened. With this descriptions you can remove the problem in the MO ² GO-process easy.

Writing a macro for database access with the Workbench

The Workbench dialog contains new the tabulator Database for creating a script macro to access an extern database. Yes, you can write such a script macro by hand too, but creating with the Workbench is much easier. For details please read documentation OfficeTalk Business-Process-Management.

Dialog History for <Processname> displays history count

The dialog, opened with the context menu History... in the listfield processtemplates, displays the number of the histories in the dialog title. The count depends on the number of filtered processes, if the history of finished processes is displayed. If the history of a running process is displayed, this count depends on the number of scheduled steps. The count is affected by the current filter. The HTML-export of finished processes contains the history count in the browsers window title.

Properties of a picture in the dialog building with the Workbench

While building a macro for a dialog with the Workbench, the property dialog for a picture was opened by double clicking its entry in the list field Statements it the tabulator Scriptdialog only. Now, the property dialog is opened on double clicking the picture itself in the dialog, as usual for all other statement types.

Menu- and toolbarentries in the tasklist after ending the last process

The process oriented menu- and toolbarentries where not disabled after finishing the last process in the list. Choosing such an entry did nothing, but not available entries should be grayed ever !

Menuentry All Windows in portal OfficeTalk

If the entry All Windows of the menu Windows was choosen and not an entry of All Windows, some other menu entries did not work propperly after. Some other effects could happen too. Choosing All Windows and not a submenu makes no sense, but OfficeTalk should ignore such wrong usings !

Inserting element in the dialog within the Workbench

Building a dialog with the Workbench within the tabulator Scriptdialog you drag and drop as usual the requested item from the statement list onto the dialog. For details about please read documentation OfficeTalk Business-Process-Management.

Dialog Ask and wait for answer canceled or no mailserver available, new login and second open the tasklist

This sequence of activities resulted in an error message with termination of OfficeTalk, sorry.

New button Help in Workbench dialog

The dialog for creating a macro, the Workbench, contains now the button Help. This button open the Dialog Result of the macro analysis with incomplete or wrong elements for creating the macro. With this information, you can easily correct the macro base.

Menu command Save in evaluation version

In the evaluation version changes are stored only on program end. Now, changes are stored in the evaluation version if the menu command Save is choosen too. With this modification changes in the evaluation version are not lost on program abort.

Creating macro with the workbench for a WebServices

With the workbench you can create a macro for executing a WebService now. For this feature the dialog contains the new tabulator WebService. Within this tabulator you can define all needed details for executing a WebService. For details about please read documentation OfficeTalk Business-Process-Management.

OfficeTalk denied user activities when started without visual reflection

When OfficeTalk ist started, it tries to start existing system processes. While starting theese processes all user activities are denied. This is done now with visual reflection, the hourglass mouse, to advise the user to wait. This is a small but usefull extension !

HTML-Export of the history, the responsibility or the simulation results of a process with additional name

If the proces contained an additional name, choosing the menu Save as HTML terminated OfficeTalk with an error message, sorry.

Extended syntay of the function MsgBox in script macro

Now for the function MsgBox the syntax without ( ) is allowed like in VisualBasic. e.g. MsgBox "This is my message". If you format the macro with the menu Format, paranthesis are put arround the arguments again.

Sometimes a script macro in the Skriptbrowser was read only

Sometimes the scripts and the script macros of the logged in worker where read only within the Scriptbowser. The items where changeable in the tabulator Scripts of the worker only. For details see documentation OfficeTalk Script.

Argument of the service processData was extended

The argument of the service processData of the systemvariable process can be now any process data or any process.

Change a script macro and deny closing the dialog without saving resulted in an abort

If a changed script macro was compiled and closing the dialog without saving the changes was denied, OfficeTalk aborted with an error message. The error occured using the portal Function.-/Organigrambrowser only, sorry.

Using a variable in the action argument of an action button or an action

If a variable was used within the action argument of an action button or an action only, the message Variable <name> is not used. Do you want to remove it ? appeared. Now using a variable within the action argument of an action button or an action is recognized and the question does not appeare anymore.

Using a non declared variable inside the action argument of an action button or an action

If a variable was used inside the action argument of an action button or an action, but was not declared, executing the macro was aborted with a message. Now, the compiling is aborted with a message and you can correct the macro. If a undeclared variable is used inside the action argument, the making is not started with a declaration dialog, because the declaration can be put into the action block or into the macro header.

The action of the property dialog Action and Actionbutton in the Workbench

The statements in the textfield Statements of the property dialog for an Action and for an Actionbutton are validated on Accept. If a syntax error is detected, a short explanation is inserted and selected at the affected statement. With the Del-key you can easy remove the explanation and second correct the errornous statement.

Button Help... in dialogs open hints about the next actions

The important dialogs contain the button Help.... This button open hints for the next actions. In this version the dialogs for the login and the tasklists are extended with this botton.

First start of OfficeTalk with an existing database

The messages for the first start with an existing OfficeTalk database where retexted for a better understanding what to do.

Choosing a menu and a toolbar button while a process is scheduled

Choosing a menu or a toolbar button in the main or in the tasklist dialog while a process was scheduled was possible. But this action disturbed OfficeTalk and it was terminated with error.

Export resposibilities, processhistories and simulation results as HTML files

The named informations can be exported in HTML format. The relevant dialogs contain the menu entry Export as HTML in the menu File. With this function you can publize additional process informations easy.

Onlinehelp of the Return statement while writing a script macro

Selecting a Return value from the dialog Select a Return value inserted the sequenze number ([n]) of the associated step result too. The sequence number had to be removed after, because it is not part of the name itself.

Version 2.62

Infinite loop in tabulator HTTP of the dialog settings

Typing in some characters into text field Repeat OfficeTalk run into an infinite loop. Ending was possible in a hard way only (Task-Manager on Windows-platforms or kill -9 <pid> on Linux platforms).

Some labels in dialogs contained a context menu

Some labels and non editable fiels (e. g. in Copyright dialog) supported a context menu. The menu contained the entry Search, Copy, a.s.o, but such fileds must not support any context menu.

Showing the unknown statement when opened the script macro with the Workbench

When a macro is to be opened with the Workbench choosen the context menu Workbench in the listfield of the script macros within the Scriptbrowser dialog and the macro contains a statement unknown by the Workbench, you get a message with the line number and the detected statement. With this information you can simply change the related statement.

Displaying the consumed times in scheduled steps in dialog Processgraph: <name of process>

In the dialog Processgraph: <name of process>, opened with the context menu Executed path in the task list, the execution time in displayed in scheduled steps only. The estimated execution time is displayed in not scheduled steps only. And a more dark color for the execution time is used.

SQL-scriptfile SerialNumbersForODBC.sql is renamed to SerialNumbers.sql

In the installation the script file SerialNumbersForODBC.sql in the folder Library is renamed to SerialNumbers.sql.

Because of a wrong entry in this SQL-script (row with column scheduldedesource instead of scheduldedesources), OfficeTalk was terminated with an error message if a process with a resource assigned action was scheduled. This error did not occure using an Oracle SQL-Server.

Direct use of Array results from a system object service as argument in a Call-statement

If the Array result of a system object service was direct used as the argument in a Call statement, the error message Undefined service in UndefinedObject ... was given and the called macro was aborted when any Array element was accessed.

e.g.. Call Script.Macro(worker.children) ... If children(1).name = '...' --> Error message ans macro abort..

New service of address in the systemvariable Worker.adress

The address of a worker answer with the service surName the last name of the worker or of the responsible person. The service (name) will be removed for the next major version. Please change your script macros if this service is used.

New services of the systemvariable Worker

The systemvariable Worker (the current worker) supports the new services isDesk, isOffice, isDepartment, isTeam and isCompany. With theese services you can evaluate what type of worker is current. The german named services ( isSchreibtisch, ...) will be removed for the next major version. Please change your script macros if theese service are used.

Abnormal program end if a wrong ODBC-entry for PostgreSQL- oder Microsoft-SQL-Server was made

If the ODBC-entry was created in the wrong way (e.g. the Microsoft-SQL-Server use NT authentification and the OBBC-entry use SQL-Server authentification), OfficeTalk ended abnormal. Now you get the error message No Licence is found... and you can end OfficeTalk as usual.

OfficeTalk aborted when installed using an Oracle SQL-Server database

Starting the first time in an Oracle SQL-Server database environment, an error message was given, OficeTalk ended and the database was not created, sorry.

Smaller enhancements in Organigrambrowser and Function-/Organigramportal

Changes within an addressdialog are reflected in other relevant dialogs on using the menu Save or Save and Close only, and not on every typed in character. With this change the flickering of the Organigrambrowsers title is solved, when typing into the addressdialog part on the right side of the Organigrambrowser.

Installation while using a Microsoft SQL-Server and PostgreSQL-Server enhanced

When OfficeTalk is using a Microsoft SQL-Server or PostgreSQL-Server, is starts two batches only for creating the database environment instead of many batches before. Therefore the synchronisation of the batch sequence is not needed anymore and the flickering of opening so many command windows is skipped. The installation is more robust in different stress situations.

More useable handling of die dialogs for creating a new step and a new step result

Creating a new step or step result within the dialog Processgraph: <name of process> with the context menu New - Step/Stepresult was made easier. A single tabulator of the opened dialog must not filled out complete before stepping to the next tabulator. The validation is done at the end with the menu Step/Stepresult - Save and Close. This makes the creating of new stepresults and steps easier, because you can jump between the tabulators as you want.

Inserting a step into a process without responsible worker or without name

Inserting a new step without defining the responsible worker for this step or without a name was possible with the menu New - Stepresult in the dialog Processgraph: <name of process>. A step without any associated responsible organisation or worker is not allowed !

Using the Microsoft-SQL Server running with NT-Authentification

In the past a SQL-Server had to be run with authentification SQL-Server Authentification, to be used by OfficeTalk. The authentification NT-Authentification was not supported fully. Now OfficeTalk support both authentification modes.

Installation of the Microsoft SQL-Servers as MSDE

OfficeTalk runs in the newest version with the MSDE (Microsoft SQL-Server Desktop Engine) too. Previous the compete SQL-Server had to be installed. But for smaller companies a MSDE may be enought.

Aborting execution of a script macro chain on errors

If an error occures while executing a macro, you get a message. If the error occures within a macro chain you can now abort the hole chain or the current macro only. You get the confirmation The error occured within a macro chain.<n>Abort the hole chain ?...

Service visibleWorkers in systemvariable stepscheduler was missing

Reorganisizing some developed artefacts the service visibleWorkers of the system variable stepscheduler was removed. The service was not displayed in the listfield of the online help anymore, sorry.

User defined settings are stored now for each user separate

The most settings are user specific. To enable each user in future his private settings, they are stored on Windows-platforms in the section HKEY_CURRENT_USER\Software\JOOPS GmbH\OfficeTalk of the registry. On Linux-Plattformen they are stored in the file $HOME/OfficceTalk.ini.

After installing this update, you must reset your private settings with the menu File - Settings because they are set to the default value.

New service currentEnvironment(...) and currentEnmvironment(..., put:...) in script macro

With the new services currentEnvironment(...)and currentEnvironment(..., put:...) of the systemvariable stepscheduler you can read and write environment settings for the current logged in user. On Windows platforms the registry HKEY_CURRENT_USER\Software\JOOPS GmbH\OfficeTalk is used. On Linux platforms the file $HOME/OfficeTalk.ini is used.

Version 2.61

Debugging a script macro on error in not possible, if the owner of the macro is another worker

For security debugging is not possible, if the error occured in a macro owned by a higher leveled worker. Because this macro may contain informations important for security, it can not be opened.

Within this context the message, notifying an error, is appended with the scriptname, the macroname and the name of the owner (a worker).

Message using Function-/Organigrambrowsers and inserting a new worker

If the Funktions-/Organigrammbrowsers was used and in the left Organigram a new worker was inserted, the message The worker is used by another ... and can not be modified appeared without reason. The new worker was modifiable after reselecting only.

The content of the last worker was not scrolled if the worker was unfolded

In the dialog Oranigrambowsers and Function-/Organigrambrowser the content of the last worker was not made visible if the last worker was unfolded. The user had to make the content visible by scrolling

The Workbench supports creating dialogs with pictures

Writing a macro you could create a dialog containing pictures before. Now, you can create a dialog with the workbench containing pictures in a mutch easier way. The list field on the right side of the tabulator Scriptdialog contains the entry Picture. Inserting a picture into a dialog ist the same as inserting any other item. Details about you can find in the chapter Tabulator Scriptdialog of the documentation OfficeTalk Business-Process-Management.

All contained items of a worker are unfolded on clicking on the square beside the worker

In dialog Oranigrambowsers and Function-/Organigrambrowser clicking on the square beside a worker, all contained items (the subordinated workers and its aspects) are unfolded too, if possible. With this extension you must not scroll manually after unfolding a worker.

Disabling dialog items within Workbench

The expression <variable> = False for disabling dialog items with the button Disable was generated correct, when the macro was created with the button Create. Reading the macro with the workbench again, theese statements where interpreted vice versa (Disable if variable is True).

Groupboxes did not surround labels in script dialogs

In the script dialog, in oposite to the script dialog within the workbench, a groupbox did not surround given labels.

Terminating the evaluation version with portal Function-/Organigrambrowser

If OfficeTalk was running with the portal Function-/Organigrambrowser and process scheduling was done only, the message to store the changes into the internal database was skipped when exited with the window close button, and the internal database remained unchanged.

Toolbar was not drawn in the correct mode after changing

If OfficeTalk was opened with the portal Function-/Organigrambrowser and the toolbar labeling was changed in the general settings, the toolbar was not actualized after the changes where saved. The toolbar was drawn in the correct mode after restart of OfficeTalk only.

OfficeTalk was finished if hirarchybrowser or resposibility was closed

If OfficeTalk was opened with the portal Function-/Organigrambrowser and the window close button was touched while Hirarchybrowsers or Responsibility was displayed in the right portal part, OfficeTalk was finished without the default question.

Symbol in tabulators Workingoptions, Startactions, Useractions and Termactions

The list Symbol in the named tabulators preceeds the symbolname with its picture. Assigning a symbol is now easyer because "a picture says more than thousand words".

Insert a new action into a step with the contextmenu New of the step in the dialog Processgraph: <name of process>

With the new entries Startaction..., Useraction... and Termaction... in the contextmenu New you can insert Startactions, Useractions and Termactions into a step. If you want to insert actions only, this way is qicker than the usual one to open the step dialog.

Automaticly unlocking the locked worker on aborting OfficeTalk

If Microsoft-SQL-Servers or PostgreSQL-Servers was used and OfficeTalk was aborted, the logged in worker remained locked. Log in with the same worker again was not possible. The locked worker had to be unlocked first with the menu Unlock... in the Organigrambrowser dialog or with the database manager tool (PGAdmin-III for PostgreSQL, Enterprise Manager for Microsoft SQL-Server). If the logged in worker was the company, unlocking was possible with the database tool only. Now the logged in/locked worker is unlocked on aborting OfficeTalk automaticly and a second log in with the same worker is not denied.

Opening the inherited autorization in the tabulator Autorizes

In the portal Dialog the inherited rights could not be opened. Pressing the button Show all rights in the tabulator Autorizes resulted in an error message and OfficeTalk was terminated second.

Presetting the Environment for the first log in using the PostgreSQL database

Log in the first time into OfficeTalk when the schema is created, the input field Enviromnent is presetted with PostgreSQL because in the installation documentation this name is recommended for the ODBC entry using the PostgreSQL database.

Selecting Description in the listfield of the portal Function-/Organigambrowser with the right mouse button not possible

Selecting the entry Description in the left listfield of the Function-/Organigambrowser with the right mouse button was not possible. Instead of the preceeding worker was selected.

Im linken Listfeld des Portals konnte der Eintrag Beschreibung nicht mit der rechten Maustaste ausgewählt werden. Statt dessen wurde immer der darüber liegende Bearbeiter ausgewählt.

Creating a script macro within the Workbench using the portal Function-/Organigambrowser

If used the portal Function-/Organigambrowser the macro, created with the Workbench (opened with the context menu Workbench of the macro listfield in the Scritptbrowser) was not asigned to the script when the Workbench was closed.

Permanent display of the colors for steps and results in layout dialogs for processes

In the dialogs for setting the layout of processes, the buttons for the step and result colors show the current color setting permanent. You must not open the color dialog, to see the used color for a step or result type.

The options for layout orientation and step display type are identified by grafical symbols not by text anymore.

Changed names of the setting for the HTTP usage

In the environment all names of the HTTP-usage are changed. If you use HTTP in OfficeTalk, you must changes this names within the setting. On Windows platforms you changes the names of the keys in HKEY_LOCAL_MACHINE\SOFTWARE\JOOPS GmbH\OfficeTalk\Http from HTTPAccount to Account, HttpEmail to Email etc. On Linux platforms you change in the file OfficeTalk.ini this names in the same manner.

Problemes using PostgreSQL on a Windows-XP platform

If OfficeTalk was used on a Windows-XP platform with the database PostgreSQL version 8.0.1, after logon an error message appeared and OfficeTalk was terminated.

Version 2.60

New additional portal Function-/Organigrambrowser

For the most work within OfficeTalk you can use the new portal. It combines the working with functions and browsing the organigram for organizing the datas. In the general settings you can choose this portal in the select field Portal. Within this portal you can do most the task processing and organizing datas within a single dialog. This makes working with OfficeTalk faster and much easyer. Instead of the choosen portal Dialog, OfficeTalk is openened after the update with this new portal. If you want to use the portal Dialog again, you must set it in the General Settings and restart OfficeTalk. You may change the size of the dialog elements with the vertical resizers. For details please read documentation OfficeTalk Business-Process-Management.

Version 2.50

Import and control business processes from MO²GO © made by Fraunhofer Institut /IPK

With the context menu Import... in the template list field of the tabulator Processtemplates you can import a business process from the company modeling tool MO²GO made by the Fraunhofer Institut /IPK and second use the imported process as usual. With this import a company can model itself with MO²GO and control the resulted processes with the workflow functionality of OfficeTalk. To import a process select the filetype MO²GO Business process in the File Select dialog and second select a file with extension .shx. Details about importing business processes from MO²GO you find in the documentation OfficeTalk Import MO²GO Businessprocess.

New tabulator Processtemplates in dialog Settings

You can define in the tabulator the general settings for creating process templates. Settings, given in the dialog Processgraph: <name of process>,

are for the opened template only. For details please read the documentation OfficeTalk Business-Process-Management.

Choosing category names of visible processes, steps and actions

In the General settings you can select wether to get the category names of all visible processes, steps or action, when building new such artefacts. If you decide No, you get the categorys names of your own processes, steps or actions only. Choosing No, you make the opening of a few dialogs faster.

Displaying consumed resources within the history

The entry of an automaticly consumed resources (flag Use automaticly) in the dialog History for: <processname> was drawn with the wrong count, if the resource unit was not seconds.

Displaying the lifetime of an active process within the history

The dialog History for: <processname>, opened with the kontext menu History... for running processes has drawn sometimes a wrong lifetime.

Hint for assigned resources to an action in dialog Step: <stepname>

To see the fact of assigned resources quickly, the button Resources... in the tabulators Start-, User- and Endactions is colored blue, if any resource is assigned to the action. When a resource was assigned to the action, and this resource is removed allready, the buttons text is colored blue too. If you open the Assigning dialog, this resource is removed in the assigned resources too.

New menu item Quick step... in dialog Processgraph: <name of process>

The menu item inserts a step with default values (estimated time 1 hour, step is scheduled by the current worker, step is mandatory). A dialog to name the step is opened only. If an existing step is appended with a new step, the name of the new step is taken as the name of the step result (the blue connection line) too. With this item you can quickly build a process prototyp. and detail the steps and results later.

Displaying the sum of the runtimes and lifetimes and the consumed resources within the process history

Displaying the histories of finished processes, the lifetime and runtime and the consumed resources are displayed first. The values of the processes, choosen with the menu Filter tasks... are displayed only.

Displaying the history of an active process , the lifetime and runtime and the consumed resources are displayed first. The values of the steps, choosen with the menu Filter steps... are displayed only.

OfficeTalk is available in two variants now

OfficeTalk/MSP:Modeling-Simulating-Processing

This is the used (current) variant. You can model, simulate and execute processes.

OfficeTalk/MS: Modeling-Simulating

This is the new (additional) variant of OfficeTalk. You are able to model and simulate processes only. This variant is much

more cheaper than the MSP-variant. If you want to document or optimize your processes or you want to certify your

company ISO-9000, this MS-variant may fit to you. You can upgrade to the MSP-variant without loosing your modelled

processes !

Layout of the connections in dialog Processgraph: <name of process> optimized

If more connections (stepresults) ended at the same step, some connection labels where overlapped and not readable. Now, the labels of theese connections are shifted depending on theire connection direction and are readable again.

Spezial characters for Strepresult are allowed again

In the past spezial characters (+-,:...) for a step result name in tabulator xxxaction and Stepresults of the dialog Step - <step name> where not allowed. Because theese names are quoted with " within a script marco, spezial characters must not be forbidden.

Aborting dialog Settings after modifying some settings

Modifying some settings in tabulator General and second aborting the dialog with the window close button, the warning mesage Do you really want to close the dialog... was missing.

Settings for choosing the next step in tabulator Stepresults

In the combobox Next Step of the tabulator Stepresults the steps of all visible process templates are displayed. Using complex or many process templates, opening the dialog takes a long time. To make the working faster and because of most the steps of other process templates are not needed, the steps of the building process template are displayed by default only. If you want to use the previous behaviour, you must set the option All visible process templates - Coosing next step to Yes.

Adding results with same name

In the tabulator Stepresults of the step's dialog equal named results could be added. This is not allowed ! This was possible too using the menu New - Stepresult in the dialog Processgraph: <name of process>. Now adding equal named results in the same step is denied and answered with an appropriate message.

Removing a worker in the organigram

After a worker is removed in the organigram dialog or -browser, its superior worker is selected. This is not a big enhancement, but makes the working a little bit easyer and faster.

Dialog Assign Resource for Action: <actionname> displayed resources with same name

The dialog, opened with the button Resources... of the tabulator ...actions in dialog Step: <stepname>, displayed in listfield Available Resources all resources without ignoring duplicates (same name). Double cklicking such a resource moved it to the listfield Assigned Resources. But, closing and opening the dialog again, the duplicate resource was not assigned really.

Documentation Reference.pdf was splitted in Installation.pdf, BPM.pdf and Workflow.pdf

Because of the size of Reference.pdf was growing to much, it was splitted into Installation.pdf (all about installing OfficeTalk) BPM.pdf (maintenance of the base data) and Workflow.pdf (all about scheduling processes). The dialogs of the task lists got a new help menue. This menue open this Workflow.pdf only. The help menue of the main dialog open BPM.pdf.

New licence model Per-Usage

Starting with version 2.50 the licence Per-Usage defines the startable processes per month. This update allows unlimited processes to be started per month, because the Per-Client licence model was used only prior. Additionally to the licence model Per-Client (the licence prize is calculated depending on the number of used clients) you can buy OfficeTalk based to the licence model Per-Usage. This new licence model calculates the prize on base of the scheduled processes per month. The licence price can be calculated on base of both models, depending on the size and type of the company !

Version 2.40

Country setting for all other german speaking countries (Österreich, Liechtenstein etc.)

On the Windows-platforms the dialogs where displayed with english strings if the country setting in Windows was set to Austria, Swizzerland, Liechtenstein, etc. The directory messages\de had to be renamed to messages\C.

Removing a Resource

Removing a Resource with the context menu Remove in dialog Worker and Organigrambrowser removed the Resource without respect to the current using level. Now a security question is used, depending on the current using level.

New tabulator for documentation, first statements and last statements in the script macro workbench

In the new tabulaton Documentation you can describe the script maco. In the new tabulator First Statements you can define statements. Theese statements are executed before the dialog is opened. In the new tabulator End Statements cou can define statements. Theese statements are executed before a possible Return statement is executed. You must write the statement direct into the both tabulators. The known online help is available here too.

Filename of the diagram for HTML-Export of processes in dialog Processgraph: <name of process>

Exporting a process as HTML file within the dialog Processgraph: <name of process> the filename of the diagram (.png) was independent of the choosen filename built with the name of the selected process. If the same process was exported twize with a different layout, the diagram file (.png) of the first export was overwritten by the diagram file (.png) of the second export. Now, the name (.png) of the diagram file is built with the name of the choosen HTML file (.htm).

Error while scheduling a started process after restart of OfficeTalk and using PostgreSQL database

If a new process was started, OfficeTalk was ended and restarted, sometimes the new started process could not be scheduled. When double clicking the process or choosing the menu Schedule, you got an error message. This effect appeared only, using the PostgreSQL database !

Windowtitle in dialog Organigrambrowser and in dialog Organigram for: <Worker> not updated

If the name or the description of the worker was changed and die dialog was opened for this worker, the window's title did not reflect this changes. The dialog must be closed and reopened to display the correct value in the window's title.

OfficeTalk terminated when using the context menu Usings... in dialog scriptbrowser

Using the context menu Usings... in the listfield for script macros in the script browser dialog OfficeTalk noted an error message and terminated. Sorry, but we make mistakes too !

Open Source database PostgreSQL is useable for OfficeTalk

Using OfficeTalk you must have installed a database. Prior you had to install Oracle or Microsoft-SQL. Now you can use the Open Source database PostgreSQL (version 8 or higher) too. This database system if available free. You can download it from http://www.postgres.org. On Windows plattforms Windows 2000 or Windows XP or a higher version is required. For details please read documentation OfficeTalk Reference.

Path for directory Library can be configured for special purpose

Using OfficeTalk on Linux computers the location of the Library directory must be configured with the Environment LibraryDirectory, to avoid multiple installations of the directory.

Quick double clicking a process twize in the personal tasklist

When a process was double clicked twize in the personal tasklist, the next step was scheduled. After scheduling the history contained two entries for the scheduled step. The first entry contained a startdate only.

New directory for localized message files

The localized message files are moved from the directory OfficeTalk/Messages/C to OfficeTalk/Messages/OfficeTalk/C . The setup of the update does not delete the files (OT.lbl, OT.idx, GENERAL.lbk und GENERAL.idx) in the old directory (OfficeTalk/Messages/C). You must do this by hand.

Settings for Toolbarformat in dialog Setttings

In dialog Settings you can define the toolbar format for buttons with or without labels. You need not do this by hand

(on Windows platfoms in the registry with the systemprogram regedit.exe, on Linux platforms in the file OfficeTalk.ini) anymore. Closing the settings dialog all opened dialogs with toolbars are updated. For details please read documentation OfficeTalk Reference.

Path for licence file can be configured for special purpose

Using OfficeTalk on Linux computers the location of the licence file must be configured with the Environment LicenceDirectory, to avoid multiple installations of the file.

Path for internal database in evaluation version can be configured for special purpose

The path for the internal database OfficeTalk.bos can be configured with the environment DatabaseDirectory. This is required, if the standard location, the program directory, is read only.

Simulation engine for simulating a process template

With the integrated simulation engine you can simulate the possible effects of executing a process. The simulation calculates the consumed times and resources. Details about this big theme you find in the documentation OfficeTalk Reference chapter Making a tempate.

The labeling of all entities in dialog Processgraph: <name of process>, and for the labeled toolbar buttons changed

The labeling of all entities in all types processgraph dialogs is made smaller to look smother. The labeling of the toolbar button was adjusted to the standard size.

Sorting and display of consumed resources in history

The history dialog of the processes display the consumed resources and the totals on all level of the process entities. Yot can sort the history results by different criterias. Details about you find in the documentation OfficeTalk Reference chapter Tabulator Resources.

New service for notifying consumed resource within a script macro

With the service consumed(<resourcen name>, amount: <number>) of the system variable stepscheduler you are able to registrate consumed resources of an action. With this service you can register the cost of a step dynamically within a script macro. If you type into a macro the service name, the opening brace and a space, a dialog with all known resources is opened to select the requested one.

New services for using resources within a script macro

The service resourceNames() of the system variable stepscheduler answers the names of all useable resources as Array. The service resources() of the system variable stepscheduler answers all useable resources as Array. Only the resources, useable by the logged in worker, are answered.

General resource management for process execution

A general resource management for process execution is supported. Resources are defined (by time or any unit) and assigned to steps of a process template. Scheduling the step calculates the consumed resources for each step and put the results into the process history for later use. Within the process history you can see later, how many resources are consumed by the hole process and by each step. Details about this big theme you find in the documentation OfficeTalk Reference chapter Tabulator Resources.

New menu entry View - Toolbar of the Tasklists

With the new menu entry View - Toolbar within the Tasklists you are able to switch the toolbar on the top of the dialog on and off. This setting is stored in the environment ToDoGroupToolbar and ToDoToolbar for using after a new start of OfficeTalk.

Extending the database with new tables for the resource management

For the support of the resource management you must create two new tables. Before you install the new version 2.40 execute the following steps first:

Using Oracle database server:

Execute with the Oracle program SQLPlus-Worksheet the scripts

- OFFICETALK.RESOURCES.sql
- OFFICETALK.RESOURCES$SEQ.sql
- OFFICETALK.SCHEDULEDRESOURCES.sql
- OFFICETALK.SCHEDULEDRESOURCES$SEQ.sql

You must be logged in as the database owner.

Start the Oracle program DBA-Studio.

- Login as the database owner
- Open the group OFFICETALKUSER in Security - User - Roles
- Insert in the object permissions the rights ALTER, DELETE, INSERT, SELECT and UPDATE for the tables RESOURCES and SCHEDULEDRESOURCES.
- Insert in the sequences RESOURCES$SEQ and SCHEDULEDRESOURCES$SEQ the rights ALTER.
- Open the group Schema - Table - OFFICETALK.
- Extend both tables REESOURCES and SCHEDULEDRESOURCES with the new column RESOURCES and its properties varchar, size 2000, Null allowed.

Using Microsoft SQL database server:

Execute with the Microsoft program Query Analyzer the script

- Resources.sql

You must be logged in as the database owner.

You will find the needed files on the program CD in the root. The files are not installed by the setup. You must copy them by hand.

Version 2.30

Enhanced formatting of input of numbers and currencies in script dialogs

The service for automatic formatting of the input with the rule Number formats without decimal separator. The rule Decimal formats with decimal separator. In both cases the separator . for thousends is used. The format types "Fixedpoint" und "Real" are substituted by the new type Decimal. If you give a Null content using the service add...(...), you must second use the service format(<Elementname>, as: "Decimal") or format(<Elementname>, as: "Decimal", with: <Formatierung>) to do a propper formating. If you give a concrete value as content using the service add...(...), the standard format rule is used automaticly. For details please read documentation OfficeTalk Script.

Removing a script macro in the script browser with succeeding login with same shortcut

If in the right listfield of the script browser a macro is removed and second logged in as the same worker, the removed macro appeared again. You had to end and start OfficeTalk, to remove the macro at all. Sorry, but if a system becomes bigger, it's behaviour becomes sometimes curious too !

New Environmententry LabeledToolBar for toolbar buttons without label

If the entry is set to "0" or "No", the buttons of the toolbars are displayed without label. If it is set to "1" or "Yes", the buttons of the toolbars are displayed with label. The default is "Yes".

Service openProcessData of system variable stepscheduler

The service display the process data of the current or the given process in a list dialog. In general, this service is only for testing because the process data control the workflow and may not be understandable by the user. For details please read documentation OfficeTalk Script.

Menuitem Process data... in Tasklist, Personal Tasklist and Takeoverlist

The named menues support the new item Process data.... This menu item opens the dialog Data of process: <name of process>. The dialog shows you the data used be the process to execute some tasks. Process data is created by the service processdata.item(..., with:..., in:...) and handled by the other services of processdata.

Menuitem Previous execution... in Tasklist, Personal Tasklist and Takeoverlist

The named menues support the new item Previous execution.... This menu item open the dialog Processgraph: <name of process> directly. You must not go via the menuitem State for: <processname> and the button previous Execution.... in opened dialog State for: <processname> to open the execution path.

Dialog Processgraph: <name of process> displays the step's execution times and the consumed execution time

The step in the process graph displays the consumed execution time, if he is allready executed. The execution times is displayed in brackets after the execution time, if he is executed twice. In general only green steps are affected by this rule. If the current step is executed twice (orange), he displays the consumed time too.

Onlinehelp for typing in services with a requested dialog item name

Typing in a service, which requests an item name as argument (e.g. dialog.put(<name>, value: <value>) ), a selection dialog with the known item names is opened. Selecting a name puts this name into the argument list. The dialog is opened after typing in ( and two spaces.

The selection dialog for the service activeX(...) displays the known ActiveX copmponents only (see addComponent(...) ).

Background color for dialogs is selectable if logged out too

The background color can now be selected in logged-in and -out state. In past selecting was allowed only if logged in.

Additional process name was not requested starting a new process with the menu Start new process

Starting a new process in the tasklist with the menu Start new process, an additional name was not requested with the name dialog.

Renaming or creating a script, context menu in the name dialog was ever english

The context menu of the text field in the name dialog, creating a new or renaming a script, did not respect the countrys language. The menu entries were english named ever.

Usage of all Toolbars is enhanced

The toolbars of the dialogs OfficeTalk, Tasklist, Debugger and Processgraph are made larger and each button is named with a label. With this naming you can recognize faster the resposibility of each button.

Button for opening the previous execution path in dialog State for: <processname>

The butten was renamed from Process... to previous Execution.... This label is more usefull than the old label.

Statement For-Next in Scriptmacro language enhanced

The statement parts Start, End and Step can contain now complex expressions. In past, you could use only variables or literals, and the values had to be loaded first into variables before used in a For-Next statement.

New system variable typ Question for working with answers for process questions

With the new type you can work with answers for a process questions. With this type you can include the mail answer and its attachments into the process handling. For this task the system variable supports new services. For details please read documentation OfficeTalk Script.

Attachments of a process answer

The attachments of a mail answer for a process question, received and taken over automaticly, can be accessed. The attachments are stored automaticly in the Attachmend folder and can be accesses via the corresponding question/answer (the system typ Question). For this task the system variable supports new services. For details please read documentation OfficeTalk Script and OfficeTalk Reference.

New function UBound in the script language

The function UBound(<Variable>)answers the number of elements in the array <Variable>. For details please read documentation OfficeTalk Script.

Service names ot systemvariable WSDLClient changed

The service names valueNamed(...) und valueNamed(..., deep: ...) are changed for compatibility of semantic to other system variables into value(...) und value(..., deep: ...) geändert. For compatibility the old names exist up to the next maior version (3.00). For details please read documentation OfficeTalk Script.

Formatting values in Workbench optimized

Selecting the format type and the format pattern are depending values. Changing one modifies the other if usefull.

New service in system variable ScriptDialog

With the service format(..., as: ...) you can define the format pattern without putting a concrete value into the dialog item. For details please read documentation OfficeTalk Script.

Toolbars under Linux, Sparc, WindowsXP and Windows98 behaved not as usual

If OfficeTalk was installed on the named systems, the toolbar buttons of the main dialog, the script brower dialog, the process graph dialog and the debugger dialog behaved not as usual. When touched with the mouse, the button displayed not an extra border. This border is shown to notify the user, that the button can perform an action. The dialog's background color is used for the toolbar buttons too. This is important only, if you change the default color in the settings.

The layout of the HTML output of processtemplates is optimized

The HTML output, created with menu Process - Save as HTML in dialog Processgraph: <name of process> is optimized. Steps with more actions are readed easyer.

Some services in system variable ScriptDialog are renamed

For better semantic, some services in the system variable ScriptDialog are renamed. For compatibility the old names exist up to the next maior version (3.00). For details please read documentation OfficeTalk Script.

New dialog item for variable table in ScriptDialog

You can insert in a script dialog now a table item with variable column width. This item can best be used for dispaying and working with informations kind of table. You can sort the table by clicking on each colunmn label. For details please read OfficeTalk Reference and OfficeTalk Script.

The stetting Optional and Mandatory in the step

This option is defined automaticly by the type of the contained actions. You can change the option, if the step contains no action, only. For details please read documentation OfficeTalk Reference.

The extent of a groupbox was changed by sizing the canvas in the Workbench

If a item inside a groupbox was moves with the mouse, the groupbox extent was changed automaticly on next sizing the canvas. The extent of the groupbox where adjusted again, moving an item inside this groupbox.

Result of the script macro execution is displayed in test mode

If you run a script macro in the Scriptbrowser with the context menu Execute, the macro displays its result (the value of the Return statement) at the end. The gives you in the test state a better decision wether the logic of a macro runs in the right way.

Browser for process hirarchies

The context menu of the listfield in the tabulator Processtemplates of the worker dialog and the organigram browser contains the new item Hirarchybrowser.... The item opens a browser for the selected template. In the browser you can walk in the processes and subprocesses hirarchy. In the right side of the dialog you can work with the selected process template as usual.

Menuitem Subprocesses in step of the dialog Processgraph: <name of process>

The context menu has the new item Subprocesses. The item contains as subitems the processnames of the processes, startet insinde this step. Choosing a processname opens the dialog Processgraph: <name of process> for the process.

Version 2.20

Displaying the calculated execution time of a step

The calculated execution time is displayed with the execution time of the contained action only without /, if the step contains none or one action. With this enhancement you can see quickly, that a step contains only one action for his execution.

Displaying the processes to wait for in dialog State for: <Name of the process>

The processes in the list field waiting for: of the named dialog, opened with the menu item Actual State... in the task list, where shown with the wrong symbol for process templates. Because theese are active processes, they use the symbol for a running process (red, yellow, green, opened or closed folder).

Contextmenu of the processes in dialog State for: <Name of the process>

The contextmenu in the list field waiting for: of the named dialog, opened with the menu item Actual State... in the task list, offered wrong items. Choosing one of theese items resulted in no action, but why should we offer something, which is not avalable !

Onlinehelp for making expressions and statements in the Workbench

In the input field for an expression in the dialogs Dialogtitle, Contents, Result, Disable dialogitems and Return you can use all the online helps, known from the source input in the script browser. With this enhancements typing in expressions and statements is made more easier. For details please read documentation OfficeTalk Reference.

Selecting dependent items for Resizer and in Groupbox in Workbench is made more easier

Selecting an item in the property dialog of the two named items is made more easier. Selecting the same item twice in the elements field of the Groupbox's dialog is not possible anymore. Selection the same item as the below and above item is not possible anymore. The first change offers only more comfort. But the second change mades the selecting more saver, because selecting the same item as above and below item makes curious effects when using the dialog at process scheduling.

All elements can be inserted in dialog items without extra effort

All elements (workers, processes, times, e.g.) can be inserted in dialog items without effort, because each element knows its textual representation. A worker for example uses his name. The statement dialog.addComboBox( "", choices: worker.visibleWorkers( True ), named: "Workers", width: 234) adds all visible active workers into the combobox Workers. A worker can be selected with his name.

The system variable worker supports new service visibleWorkers(...)

The new service answers all visible active or passive workers. For details please read documentation OfficeTalk Script.

Skrinking a script macro under a 4000 border resulted in the message Macro can not be compiled

If a macro was shrinked below a 4000 border, the rest was not removed really and if the macro was executed on process scheduling, the message Error while compiling the macro appeared.

Compiling a script macro termed in rare times OfficeTalk

If the last line in a macro was a Call-Scriptmacro statement with a non existing macro, compiling this macro OfficeTalk exited with an error message, sorry.

Workbench recognize and build complex expression for the target of the dialog item result

Typing into the property dialog field Expression of an item more statements separated with CR, the Workbench builds the propper code for it. The typed in first statement must be an If statement with an expression with the service valueNamed(...) as one operand and containing a Return statement in the Then or Else clause.

An example:

If dialog.valueNamed("ZIP") = "2000"

Then result = True

Else result = False

EndIf

Workbench recognize and build complex Return statement

If you write into the text field Expression of the tabulator Return more lines separated with CR, the Workbench writes theese lines without an extra Return. Theese lines must be an IF-statement containing in the Then or Else part a Return statement.

An example:

If dialog.valueNamed("ZIP") = "2000"

Then Return True

Else Return = False

EndIf

Defaults in the Workbench for a dialog

Opening a Workbench to create a new dialog, dialog for the dialog's variable name and accepted for the result's variable name of the service open is predefined. Any way, you can change theese predefines.

Displaying tasks in Personal- and Grouptasklist

If theese task lists contained a scrollbar because of many tasks and any task was scheduled, the scrollbar went with the scheduled task (up or down) depending on the scheduling time. Now the scrollbar stays on the same position, and you must not move first the scrollbar to the previous tasks. This happen only, if a tasklist contain more task than it can display at one time.

Changes in Workbench were lost

If a workbench was modified and another tabulator in the worker or organigrambowser dialog was choosen, the workbench was closed without warning and the selected tabulator was opened. Now you get first a confirmation. You must answer Yes to abandom the changes in the workbench.

The first label was inserted in the dialog of the workbench without text

Inserting the first label in the dialog of the workbench inserted the label without text and the label was inivisible in the dialog. Selecting the item in the item's list made the label visible with it's selection corners only.

Self naming of dialog items in Workbench

If you insert an item with an existing name, the item is self named with an incremented number

Removing an item in Workbench removed sometimes the wrong item

Removing an item in the tabulator Dialog of the Workbench removed in rare conditions the wrong item.

Tabulator Return in Workbench contained all option fields

If the option Dialogitem is choosen, the combobox right side contained all option fields with their names and the wrong statement was build. Now the combobox contains only one entry for each option group with the group name.

Selecting an Action or Actionbutton for an action was possible

For an Action another Action or Actionbutton was selectable in For item: of the propery dialog of this Action. It makes no sense to choose an Action for another Action. So, theese items are not selectable anymore in the property dialog of an Action.

Workbench is extended for disabling one, more or all elements

The tabulator Dialog of the Workbench contains the new button Disabling. The button opens the dialog Disabling dialog elements. Within this dialog you can define one, more or all elements to be disabled depending on the content of a variable or the result of an expression. This feature is very usefull if the user may fill the dialog or may be allowed to see the contents only. The Workbench generates the needed statements for you.

New service in ScriptDialog for defining the online help for an element

With the new service named(..., helpText: ...) you can define the help text for a dialog element. This text is shown, if the user touches the element with the mouse. For details please read documentation OfficeTalk Script.

Extended services for defining field properties

The services for defining a field property (disableNamed(...), enableNamed(...), valueNamed(..., format: ..., with: ...), eg. ) can be used for more fields, using an array of fieldnames instead of a single name. For details please read documentation OfficeTalk Script.

Extended formatting for input fields in Scriptdialog

For formating an input in input fields you can use the new service valueNamed(..., format: ..., with: ...). With this service you need not to fill the input with a propper value. You can leave it empty. With this service you can define an alternative character for password input. For details please read documentation OfficeTalk Script.

Workbench supports macros with arguments

With the workbench you can generate now macros, having arguments. For this feature, the workbench contains the new tabulator Arguments. With this tabulator you can specify arguments, similar specifying variables with the tabulator Variables.

Database table scriptmethodsource is extended

The table was extended with the three columns source2, source3 and source4 having the same settings as column source. Wit this extension you can write script macros up to 16000 chartacters.

Attention: To use the version 2.20 you must add theese three columns to the tables scriptmethodsource !

You can do theese changes easy with Microsoft Enterprise Manager or with Oracle DBA Studio, depending on the used database. If you need help, our service will support you !

Dialog was modified if loaded again with Workbench

If an element's name was changes in the workbench, the changes where not made in corresponding groupboxes and resizers. Labels where put outside the groupbox, if the dialog was reloaded with the workbench.

Delegation to the substitution worker acts for the logged in worker too

If the logged in worker will be not reacheable at the start date (absent for tomorrow or later) of the next step, the process is delegated to his substitution worker.

Substituter selection did not distinct between process and step

Loooking for a substituter distincted not between process and step. If a process's name was equal to the step's name, the substituter for the process was used instead of the substituter for the same named step.

Substituter for category was used instead of substituter for a full name

If a substituter for the category was stored before a substituter for the full name, the substituter for the category was used without respect to the substituter for the full name. A full name substituter has higher priority than the substituter for the same named category !

Sorting of the substituted process templates and their steps

In the tabulator Substitutes of the workers dialog the contents of the list for is sorted in a better way. With this new sorting you can find a process or step out of many processes and steps easyer

Creating documents with tables with help of communication library Microsoft Word Small

With the small library Microsoft Word Small you can now fill tables in documents too. Filling tables with the lage library Microsoft Word is possible ever. But the small library has the advantage of a short loading time. For details please read the VisualBasic for Word documentation.

Internal processe for automatic scheduling and reading of answers disturbed scheduling of user processes

The internal processes for automatic scheduling and for reading process answers disturbed each other and disturbed the scheduling of user processes if they where scheduled at the same time.

Portal displays the OfficeTalk logo

The start dialog display after logging on the OfficeTalk logo with the many cheers.

Onlinehelp for servicenames answered wrong result

If a macro contained two Dim statements with similar variable names, the service dialog opened the servicenames for the wrong class. e.g.

Dim marks As SmallCOM.Word.Bookmarks and Dim mark As SmallCOM.Word.Bookmark. Typing in mark. opened the services for Bookmarks instead of Bookmark.

OfficeTalk is distributed with licence

Using OfficeTalk you need a valid licence. We must protect OfficeTalk against illegal copying ! Your setup contains the required licence. Starting OfficeTalk you get a notification if the licence is outdated or missing. On evaluation version the licence starts now at the day of the first programstart. In the past the licence started with the delivering of the program CD. The licence begins now when you start OfficeTalk the first time and is 30 days valid.

New dialog Settings for scheduling: <Processname>

The tabulator Processtemplate contains the button Options.... This opens a dialog to set the options for the process scheduling. Theese options are the priority, moved from the tabulator Processtemplate to here, and the two input fields Red Delay after and Yellow Delay after. With theese inputs you can specify the delay values for each process template separate. A started process takes the values from its template but can not be changed later !

Attention: To use the version 2.20 you must add the two columns yellowdelay and reddelay to the tables process and processtemplate ! Both columns are Integer, Null allowed.

You can do theese changes easy with Microsoft Enterprise Manager or with Oracle DBA Studio, depending on the used database. If you need help, our service will support you !

New input fields Red Delay and in the tabulator Processtemplates

The tabulator contains, as the Tasklist settings, the two input fields Red Delay and Yellow Delay. With this input you can define the delay values specific for each process template. A started process takes the values from its template and can not be changed later.

New step permission Start early

To start a step early (it has not reached it's start time), you must own the step permission Start early for this process.

Startime of step result extended

To start a step immediatly after ending it's predeeding step, the starttime option after without a delaytime must be given in the step result. To adopt existing processes to the new behaviour, you must change the step result option after value to zero.

Delaytime in dialog Setting - Tasklist removed

The dialog entry was removed. To start a step immediatly after it's preceeding step, you must set the step result's starttime to the option after without delay time.

Optimized handling of cascaded dialogs

If dialogs can be opened within other dialogs (e.g. Workload and Usings), theese cascaded dialogs are minimized and closed, if their parent dialog is minimized or closed. This is a small change but with great effect for the handling of OfficeTalk.

Estimated workload of a worker for steps in all processes

In the organigram and in the organigram browser you can see with the context menue Workload... the estimated workload of a worker for all processes. With this information you are able to distribute the process and step resposibilities in a better way. You can export the this information as HTML, to send it to a collegue. For details please read documentation OfficeTalk Reference.

Estimated workload of a process for all responsible workers

In the listfield of the process templates you can see with the context menue Workload... the distribution of the workload to workers in one process template. Optionaly can can change the step's association to the scheduling worker. With this menue you are able to plan the distribution of the responsibility for large process templates in an easier way. You can export the this information as HTML, to send it to a collegue. For details please read documentation OfficeTalk Reference.

Configurationmanager makes the using of OfficeTalk easier

The configurationmanager removes not needed menues und toolbar buttons in the main dialog and makes the using of OfficeTalk more easy.

Scriptdialog supports Resizer

In a script dialog you can insert a Resizer to modify the size or position of sourrounding items dynamicly. e.g. With a Resizer, the user can adopt the size of a Listbox to its content. For details please read documentation OfficeTalk Script.

Scriptmacro syntax supports operator Is

The syntax of a script macro supports now the operator Is. With this operator two object references can be tested for identity.

New workbench for defining a user defined dialog in a script macro

Defining the statements, needed for a user defined dialog, in a macro can be performed programaticly and now, supported by a workbench, in grafically mode too. Defining a user defined dialog for your Business Process is now OfficeTalk like (easy doing...). The context menue of the macro list in the ScriptBrowser contains the new entry Workbench.... Behind this many dialogs helps you building the macro for a user defined dialog. For details please read documentation OfficeTalk Reference, chapter Workbench....

Version 2.10

Menu Filter categories saves the selected categories in the environment

The menu View - Filter categories in all kind of task list saves the filter categories into the environment for using when next opened. With this modification the menu has not only category entries for the started processes but for the filter categories too.

F4-Key closes the dialog

The F4-Key close any dialog like in other applications. The symbol of the Close menues was removed and the aymbol of the Exit menu was changed, because the semaphore symbol was misinterpreted.

F1-Key opens the help contents

The F1 key opens, depending on the opened dialog, the help contents. This is not a big deal, but the F1 key us used in general for the help function now.

Stateline for all kind of tasklists

All kind of task lists have a state line on the bottom of the dialog. This field displays the current and active filter values whitch are taken to filter the processes in the lists. This field gives you a quick overview of the current filter state. Additionally the menu View was extended with the new entry Stateline. It hides and shows the stateline.

New menue entry Invert filter in all tasklists

With the new menue entry in the meue View you kan invert the task filter results. With this menue entry you can switch the task view to the filtered and to the oposite fast. This makes the working with a large amount of processes more easy. The setting is stored in the environment Invert.

New menue entry All processes in all tasklists

The new menue entry in the menue View clears all filter aspects (set in the dialog Filter processes, and in the menue Filter tasks by category). With this menue you can switch to an unfiltered view fast.

Tasklists show the number of folded in and folded out processes

Esspecially for working with a large number of processes all types of task list display in the window title the number of folded in and out tasks too.

Dialoge are opened with their last extent

If you change the extent of a dialog, it is opened the next time with this changed extent. The extents are remembered in the environment Opening. The environment UseLastExtent=No or UseLastExtent=0 ignores to open the dialog with the last extent. If the environment does not exist, Opening\UseLastExtent=Yes is assumed.

The position of the resizers in dialogs is archived

The position of the resizers (a thin line to organize the dialog parts, e.g. the splitting line between the listfield on the left and the dialog field on the right in the tabulator Processtemplates) is reused on the next opening. So you must not resize manually the dialog's parts on the next opening again. The environment UseLastResizer=No or UseLastResizer=0 disables the resetting of the lines. If the environment does not exist, Opening\UseLastResizer=Yes is assumed.

Userdefines startpage can be defined in the environment

In the environment Portal you can define your own startpage for the browser. For details please read documentation OfficeTalk Reference.

Optimized handling for pasting something from the clipboard

Pasting something with the context menue Paste from the clipboard into a list field selects the copied entry too. So you can work with the entry without any extra action after it is pasted . If the entry exist in the list filed allread you are notified about with a message.

Multiple copying an entry in a listfield into the clipboard

Copying an entry with the context menue Copy copied the entry more times into the clipboard. As the result you saw this entry more times in the clipboard's dialog using the context menue Paste.

OfficeTalk runs with Internet Explorer

Optionally you can start OfficeTalk with a startpage inside the Microsoft Internet Explorer. For users preffering browsers this is a very good news ! As a prerequisite any Windows platform (98/XP/ME/NT 4/2000/2003) and the Microsoft Internet Explorer is required. For details please read documentation OfficeTalk Reference.

New services in systemvariable stepscheduler

For automatic scheduling a process the new services automation() and isAutomation() are available in the systemvariable stepscheduler. For details read OfficeTalk Script chapter Systemvariable - stepscheduler.

Assigning a variable in scriptmacro resulted unexpected

Assigning an Array with a changed variable assigned the old value. e.g.

Dim myArray As Array

Dim line As String

line = "first line"

myArray(0) = zeile

line = "second line"

myArray(1) = line

Both Array elements contains "second line". A very rare situation, but...

Automatic scheduling of processes

A process can be automaticly scheduled if the required permission exist. Automaticly means, the next step is scheduled without user interaction if its starttime is reached. With this feature you can make undependent running processes (e.g. real machine processes, a process to notify if any other process is out of time). Therefore the settings for the Tasklist is extended. For details please read documentation OfficeTalk Reference.

New permission for automatic scheduling

For automatic scheduling the permissions are extended with the new right autom. schedule. A worker must have this permission to schedule the process automaticly. For details please read documentation OfficeTalk Reference.

Prepeared process for the scheduling escalation

The files System - Escalation.bos und Escalation - Setup.bos in Templates contains the same named processes. Theese processes can run automaticly and notify a person or can start another process if some avtive process is out of time. As a prerequisite you must run the current OfficeTalk Version 2.10. Details about the processes you find in Escalation.pdf.

New services in systemvariable stepscheduler and process

The system variables supports the new services visibleWorkers and executionColor for special purpose. For details read OfficeTalk Script chapter Systemvariable - stepscheduler and process.

Einige Dienste von Systemvariablen lieferten statt String als Ergebnis nichts

Einige Sonderdienste von Systemvariablen lieferten statt Sting als Ergebnis nichts. Das passierte, Gott sei Dank, nur bei einigen wenigen, selten benützten Diensten.

Newly inserted worker in organigram stays selected

If you insert a new worker into the organigram (Organigrambrowser or dialog Organigram for <workername>) the newly inserted worker stays selected, because OfficeTalk assumes that you want to work with this newly inserted worker next. This change allows a way of faster working.

Deleting all selected histories is made saver

If you start to delete with the menue Delete histories... all the selected histories, you get after the default question a second question, asking you to delete really the number of histories. You must answer the second question Yes to delete the histories really. With this change deleting histories is made a little bit saver.

Height for input fields in all dialogs

The height for input fields in all dialogs was changed fom 30 to 25 pixel. This change was reflected minor changes in the layout of some dialogs. The change is responsible for a finer design. With this change the design of some symbols was made three-dimensional..

Systemvariable processdata is displayed with its contents in the debugging dialog

Double clicking the variable processdata open its contents, the entries, and double clicking an entry displays the containing items. With this you can macros, using processdata, debug in a easyer way.

Global variables where not shown

Clicking Global in the variable list did not expand to the global variables.

The dialog for debugging contains menue and toolbar

The dialog contains for easier and faster using the menue Debug and a toolbar. Each can be used instead of the buttons in the dialog.

Differences are marked in dialog Importing existing macro:<name>

The dialog is opened, if a macro will be imported, but the same named macro exists allready. For better recognizing the differences, removed lines are colored red, added lines are colored blue and changed lines are colored orange. For details please read documentation OfficeTalk Reference.

Removing artefacts (e.g. Processtemplate, Permissions, ...)

The security question for deleting an artefact is suppressed only if OfficeTalk is running in expert mode. In all other modes you must answer a delete question Yes, to delete the artefact. This change is for security.

Importing of process templates and scripts

While importing one of the named artefact in tabulator Processtemplates and Scripts the overwrite dialog was opened on equal script macros too. Now equal macros are skipped automaticly.

Removing a middle step in dialog Processgraph: <name of process>

If a step from the middle of the graph was removed, in some cases succeeding steps could not be removed after. For theese situations the path was displayed wrong too.

Rights for removing and working a step in dialog Processgraph: <name of process>

To remove or work a step, only the logged in worker must have the permission the work the process.

Canceling dialog Tasklist columns adopted configured columns

Canceling the dialog, opened with the context menue Columns... in the task listfield of the tasklist dialog, with the window close button adopt modified column configurations. Now, changes are only adopted, if the dialog is closed with the Accept button. Anywhere changed column configurations are adopted permanent only, if the tasklist is closed with the Accept button too.

New context menue Columns... in listfields of the tasklist as table

With the context menue Columns... you can define for each listfield in the tasklist as table the columns to use and their sequence. Choosing the menue, the dialog Define the tasklist columns is opened for defining the columns. For details please read documentation OfficeTalk Reference.

User defined color for the step results

Up to now, the color for the step results was predefined as blue and could not be changed. With the dialog Settings (menu View - Settings of the dialog Processgraph: <name of process>) you are able to define the color by yourself now. For details please read documentation OfficeTalk Reference, chapter Create process temmplate menu View - Settings.

Button Reset in dialog Settings (menu View - Settings of the dialog Processgraph: <name of process>)

Clicking the Reset button twice without closing the dialog did not work. You had to open another process or restart OfficeTalk to use the original settings again.

New Onlinehelp for typing in the Library statement in Scriptmacro

If you type in the statement Library with " and a succeeding blank, you get the file selector dialog for choosing the communication library. Only files with the extension .pcl are accepted.

New service of the systemvariable stepscheduler

With the new services substitutes of the systemvariable stepscheduler you get all substitutes of the current process. You can use one worker of the list to delegate the process excecution. For details read OfficeTalk Script chapter Systemvariable StepScheduler.

Moving a step result with the mouse into a listfield

Moving a step result with the mouse from the dialog Processgraph: <name of process> to a listfield (e.g. process templates), OfficeTalk was terminated with an error message. Same happened, if you moved a listfield entry into the dialog Processgraph: <name of process>. Such an action make no sense, but OfficeTalk must not be ended on such actions.

Wenn Sie ein Arbeitsschrittergebnis (blaues Linienende) im Dialog Ablauf des Vorgangs: <Name des Vorgangs> mit der Maus in ein Listfeld (z.B. Vorgangsvorlagen) geschoben haben, beendete sich OfficeTalk mit einer Fehlermeldung. Gleiches geschah auch, wenn Sie umgekehrt einen Eintrag aus einem Listfeld (z.B. Vorgangsvorlagen) in den Dialog Ablauf des Vorgangs: <Name des Vorgangs> geschoben haben. Aktionen dieser Art sind zwar unsinnig, aber OfficeTalk sollte sich trotzdem dadurch nicht beeinträchtigen lassen.

Moving a step result from one step to another with the mouse in dialog Processgraph: <name of process>

To move the end of a step result from one step to another you can drag the requested end of the blue connection line (line start or arrow) to the next step. You must not drag the step result's label anymore.

Contextmenu Working options in dialog Processgraph: <name of process>

The menuitem Worker of the context menue Working options of the step contains the first item Current Worker. This item stands for the option Current Worker in the dialog Working Options.

Onlinehelp for Return statement writing a script macro

Writing the statement Return and two blanks openes a dialog for selection a return value. Depending on the context the results of the current step or the results of the steps of all visible process templates are displayed. Selecting a line and choosing the OK button writes the value after the Return statement in the script macro. For details please read the documentation OfficeTalk Reference.

Using user defined symbols from the gallery

Not all user defined symbols from the gallery where used (all worker types, process an its elements).

If a user defined symbol is to large or to small (between 16x16 and 24 x 24 points), a warning is displayed and the standard symbol is used for.

Sorting a rightmost column in dialog Tasklist for: <workername>

Sorting the tasks by a rightmost column with clicking the column header did nothing if the last task in the list was selected after the las sort.

Closing the tasklist Tasklist for: <workername> remained some opened dialogs open

An opened history- and state-dialog remained open, if the tasklist was closed. Now, if a process is scheduled in any way or the tasklist is closed, its state- and history-dialog are closed automaticly.

Double clicking the column header in the dialog Tasklist for: <workername> started the process scheduling

Double clicking the column header in the tasklist started the scheduling of the current selected task.

Sorting processes for working time in dialog Tasklist for: <workername> is done faster

Sorting the processes for working time of the next step was done with sorting the leaving runtime of the process. So sorting took a long time on complexe processes.

Importing a worker resulted in error messages

If in the dialog Organigram for: <workername> a previous exported workerfile <workername>.bos was imported, the error message Duplicate primary key... appeared if the imported worker contained a worker hirarchy.

Deleting a worker was aborted

If a worker or a subordinated worker was referenced in a pocesses step, in a visibility or in an authorize, deleting was canceled with an error message.You had first to remove the worker's references to delete it.

Extended messages if process is delegated because of a noted absent

The message notifying the delgation of a process because of an absent display the reason, if given too. The timespan of the absent was not given full in the messages.

Showing all templates in dialog Tasklist for: <workername> and Starting a new process

In the dialog only the templates of the worker where shown by default. Now all visible and startable templates are shown by default. With the menu View - All templates and the option Display all templates you can switch the display mode.

Onlinehelp for servicenames of a class is not opened

If a script macro started with comment lines and on line contained the string <Variable> As, the online help dialog with the possible services was not opened.

Evaluating And-expressions in script macro

The right expression part of the And expression was evaluated in any case. Now, the right part is evaluated only if the left part evaluates True. With this modification writing And expressions is more easy.

Communication library for Microsoft ADO Version 1.01

Using databases (from Access to Microsoft SQL) via ADO (Active Data Objects) in script macros, you must have installed Microsoft ADO. If it is not installed, you can use the system file msado10.dll from the CD. Copy msado10.dll from the CD to C:\Programs\Shared files\system\ado and run regsvr32 C:\Programs\Shared files\system\ado\msado10.dll. Substitue C with your system drive. JOOPS does not garantee the correct functionalitiy of msado10.dll on your system. In doubt, consult your system administrator.

Changed distribution

The file zlib.dll is not used anymore and not installed by this version in the directory Bin. If you have installed an older version previous, you can delete this file by hand.

Menu New - Step was not disabled

In the dialog Processgraph: <name of process> the menuentry of the menu Work and of the contextmenue was not disabled although the action was not possible.

Automatic type converting did not work sometimes is script macros

Automatic type convertion did not work with some types and OfficeTalk was terminated with an error message, sorry.

Scheduling an action with an unknown result

If the script of an action ended with an unknown result name (Return-statement used an unknown name), the dialog for correction this was not opened, but OfficeTalk was terminated with an error message, sorry.

Userdefined colors of scheduled, not scheduled and all other steps

Up to now, the colors for the steps where predefines and could not be changed (light green for scheduled, orange for the current and light gray for all other steps). With the dialog Settings (menu View - Settings of the dialog Processgraph: <name of process>) you are able to define the colors by yourself now. For details please read documentation OfficeTalk Reference, chapter Create process temmplate menu View - Settings.

The step's description is displayed in the tasklist

If the tasks in the tasklist are displayed as folder symbols, touching a task with the mouse shows the description of the next step too. Large descriptions can be truncated with the enviroments ProcessList\DescriptionSize, AdpotProcessList\DescriptionSize and GroupProcessList\DescriptionSize. Truncated descriptions are displayed with an ending .... If the value of this environment is missing, descriptions are truncated to 200 characters.

The dialog State for: <name of the process> shows the step's full description beside its start date With this information, you get a quicker overview of the tasks to be executed.

New column Runtime for the current step of a tasks

If the tasklist is displayed as table, the new column Runtime displays the estimated runtime of the task's next step. With this new column you get a quicker overview of the requested times executing the requires steps.

Login dialog of a HTTP connection for WebServices

If you have not given the complete login in the tabulator HTTP of the dialog Settings, using the service url(...)of the systemvariable WSDLClient, a HTTP login dialog is opened. Within you can complete the login data.

Blue connection line was positioned wrong with small column space in dialog Processgraph: <name of process>

If you set the column spacing to 50 or lower in the dialog View - Settings, the blue connection line (step result) of the middle step was positioned wrong in the process graph's dialog.

Dialog Processgraph: <name of process> fits the WfMC-Standard

The dialog Processgraph: <name of process> with the view setting Display Steps as circle (in dialog View Settings) fits most the WfMC-Standard. e.g. the stepresult name is appended with its sequence number, an noted in the WfMC-Standards. You see the sequence in the stepresult's listfield (dialog Step: <name of the step>, tabulator Stepresults) too.

Scheduling twite the same step of the same process was denied

Scheduling the same step a second time was denied with an error notification if the first scheduling was done with the dialog Scheduling step: <stepname>, sorry.

Login is required for modifying the settings in Dialog Settings

For modifying the settings, you must be logged in. The only exception is the field Database. Changing this field, you are not allowed to be logged in. This change makes the system more secure, because only allowed users are can change the settings.

Using Web-Services in Business Processes

You can use for business processes now web services of any host reacheable in the internet community and supporting web services. With this extension you can enhance your processes with services around the world. For this fearture the Settings dialog is extended with the setting for the HTTP. For details read documentation OfficeTalk Script, Chapter Systemvariables WSDLClient.

Version 2.01

Modified and enhanced dialog Settings

The dialog Settings, opened with the menue File - Settings in the main dialog OfficeTalk, contains now tabulators for the setting groups. Selecting one of the tabulator General, Tasklist or Mail you can set any param of the group.

New menues Activate filter and Deactivate filter in dialog History for: <processname>

With the both new menues you can switch fast and with one mouse click from a filtered to an unfiltered view of the process histories. Because working fast is an important aspect in OfficeTalk.

With theese items in the dialog's menue View you can activate and deactivate given selection criterias. You must not choose the menue item

Filter... and clear second the fields in the opened dialog Process history filtering by.

Background color of all opened dialog is changed

If you change the background color in the dialog Settings and close the dialog with the OK button, the background of all opened dialogs is set to the selected color.

New fields in dialog State for: <processname>

The dialog displays the fields for runtimes and working times in the two columns (Runtimes, Working times). For details please read documentation OfficeTalk Reference.

History dialog with new status line

The history dialog History for: <processname> has a status line. It displays the used selection criterias. This extension gives you a fast overview over the selection criterias and the results.

Scheduling the same step of a process twice

If the same step of a process was scheduled twize in the dialog Tasklist for: <workername>, the second scheduling was denied without any message.

Minor changes in dialog Process '<processname>' delegate/change und Question for '<processname>'

The elements in both dialogs had no help entry (text appearing when touching the field with the mouse).

Skript is automaticly selected after inserted or changed

If you insert a new script or change the name of an existing script in the tabulator Scripts of the worker's dialog, the script is automaticly selected because OfficeTalk assumes, that you want to work something in it second. This is a minor change, but working with it is more easyer.

Dialog Organigram and dialog History for: <processname> displays additional informations

In the dialog Organigram and in the history dialog the list entry of a step history displays in front of the step result the responsible worker.

Dialog Organigram with worker contents displays visibility, inheritance and estimated times

If you choose the menu View - Workers contents, for each visibility and right inheritance a line is displayed below the worker with its image. Additionally the estimated working time of a step and an action and the estimated start time in a step result is displayed with its image.

Showing the Working rights in dialog Rights inheritance for: <name of the worker> and Organigram for: <name of the worker>

In both dialogs (opened with button Rights in the worker's dialog and the menue View - Worker contents) you can open a right to see the containing working rights.

Database with waiting processes could not be loaded in Evaluation version

If OfficeTalk was finished with waiting processes (for an answer or for the end other processes), the next start was aborted with an error message. Only the evaluation version was affected by this problem. The production version was not affected by this error !

Dialog <workername/scriptname/scriptmacroname> is used in closes all opened and goes back to the start

The dialog contains the button Back. Using the button, this dialog and all dialogs opened from this are closed. The startpoint (the worker or the tabulator Scripts of the worker is activated/opened again. With this feature you can go back fast to the start point of your seaching.

Predefined colors for service valueNamed(..., formatWith:...) of system variable ScriptDialog in script macros

In the argument formatWith: you can use one color of many predefined colors. For details see documentation OfficeTalk Script, Chapter Setting and asking field propperties.

Critical error are displayed with a halt symbol

For better differencing the messages for critical errors contains an halt symbol now.

Compiling a macro with function Call(...) an error message occured

If the function Call(...) with an unknown script macro is used in an If statement with a boolean expression (e.g. If Call Script.Macro(...) = True Then ...), compiling the macro resulted in an error message and OfficeTalk was terminated, sorry.

New symbol for comunicating with an extern system in a step or action

In the tabulator Scheduling options and in the tabulator Actions the combobox Symbol contains a new symbol for communicating with an extern system.

Process path with link to itself were not hided in large processes

If the count of maximal displayed paths was exeeded (Environment MaxPath), the outcounted paths were not displayed in the dialog Paths of process: <name of the process>, opened with menue Statistic - Times/Paths in dialog Graph of process: <name of the process> and the self linked paths were not suppressed. In this case self linked paths are supressed to display the most important paths. The supressing of self linked paths is indicated in the last line of dialog Paths of process: <name of the process>.

Process paths with backward link could not be outlined

If a step had a backward link to his predecessor, the path was not displayed in the dialog Paths of process: <name of the process>, opened with menue Statistic - Times/Paths in dialog Graph of process: <name of the process> and could not be outlined.

The date is displayed in respect to the rules of the current country

Output and input of a date is conform with the country's rules. e.g. MM.DD.YYYY in aglo american areas and DD.MM.YYYY in german speaking areas.

The date is displayed in long form

The dates in all the dialogs are displayed with the month name instead of the month number. The date input can be done with the month number or month name.

The date in a script macro (system variable ScriptDialog) is displayed in short form with the month number. You can change this behavior with the sercive valueNamed(<fieldname>, formatWith: <format rule>), see documentation OfficeTalk Script.

Dialogs of the onlinehelp, while writing a script macro, did not use the background color

The dialogs of the onlinehelp, writing a script macro, did not use the background color of the Settings. The wrong icon was used as the window icon (top left).

Clicking the tabulator Stepresults in dialog <Name of the worker>

Sometimes OfficeTalk was ended with an error message when clicking the tabulator Stepresults on processtemplate with a special structure.

System variable was detached from database in scriptmacro

A system variable answered by a service of the system variable ScriptDialog was detached from the database on macro end.

e.g.: .... selected = dialog.valueNamed("processes") .....

valueNamed()moved the selected process from the listfield processes into the variable selected as user variable but not as system variable. On macro end the process was detached from database. As an effect opening the history of the process opened an empty dialog.

Abnormal end when creating a new process template

Creating a new process template in the dialog <Name of the worker>, tabulator Processtemplates OfficeTalk ended with an error message if the Button New was activated. This error was inserted at the last update 2.4.2004, sorry.

Double cklicking a process twize in the Tasklist

If a process was double clicked fast and twize and the called script macro was used the first time, the Dialog Schedule Step: <Name of the step> was opened twize. Because this is not allowed, the succeeding proceedings were wrong. Now double clicking a process is ignored, if the processes step is currently scheduling.

Filter values for running processes are stored in the environment group Filter

The dialog Selecting processes, started with the menue View - Filter tasks... in the Tasklist, stores the typed in values now in the environment group ProcessList\Filter and GroupProcessList\Filter, depending on the type of the task list, but not anymore in the environment group ProcessList and GroupProcessList. If you use filter values, you must type in them newly. Sorry for this, but the values are only a few.

Menue View - Filter tasks... remembered not all values

The filter values for Priority and Name where not remembered by the tasklist. After restarting OfficeTalk, you had to type in theese two values again, if needed, sorry.

Environment DisplayRuntime is used only for the tasklist with symbols and tasklist as browser

The environment is used only for this two types of tasklists, because for the tasklist as table you can define the used columns by yourself with the new context menue Columns.... For details please read documentation OfficeTalk Reference.

New context menue Columns... in listfields of the tasklist as table

With the context menue Columns... you can define for each listfield in the tasklist as table the columns to use and their sequence. Choosing the menue, the dialog Define the tasklist columns is opened for defining the columns. For details please read documentation OfficeTalk Reference.

Abnormal end if tasklist is sorted by start date and then actualized

If you sorted the tasklist by startdate (ascending or descending) and the choosed the menu View - Actualize, OfficeTalk ended with an error message, sorry.

Abnormal end if dialog of tasklist was maximized

If the tasklist, displaying the tasks as table, contained a task with complex structure, and the dialog was maximized, OfficeTalk ended with an error message, sorry.

Abnormal end while logoff and logon if tasklist as browser was opened

If the tasklist or group tasklist was opened as browser and you logged out and logged in, OfficeTalk was terminated with an error message, sorry.

Histories of finished processes can be filtered by the comment in the process, step and action

In the dialog History for: <process name> you can filter the histories of finished processes by the comment too. All histories of the processes, not containing the given comment (process, step or action) are suppressed. You get the history dialog for finished processes with the context menu in all template list fields.

Steps of an active process can be filered by given criterias

In the history dialog History for: <processname> for an active process you can filter the steps by different criterias. For this, the menu item filtering by... opend the dialog Filtering steps by. In this dialog you can give the criterias for filtering the steps in the given active the process.

No safety message when ending OfficeTalk with menu Exit

Ending OfficeTalk with the menue File - Exit in the dialog OfficeTalk is not secured anymore with an additional messagebox, because it is clear what you want, when you use the menue. This is only a minor change, but the additional messagebox was nerving.

Evaluation version could not be started again after executing processes

If you executed processes in the evaluation version, and ended OfficeTalk with the menu Term, OfficeTalk some times could not be started again. Only the evaluation version was affected by this problem. The production version was not affected by this error !

New service in system variable ScriptDialog for immediate refreshing opened dialogs

A service, which openes an closes an ActiveX dialog may leave OfficeTalk dialogs invalid. The obscured parts are not actualized. To avoid this, use the function Refresh after the call of the responsible service.

New service in system variable ScriptDialog for direct reacting on changes in input fieldes

To perform an action on every change in an input field, you can use the new service addAction(<command lines>, named: <name>, continuous: <bool-expression>). Adding an action with this service, every change in an input field, an editable spin-input field and an editable combobox field performs the given action. For details please read the documentation OfficeTalk Script chapter Systemvariable ScriptDialog service addAction(..., continuous: <bool-exprrssion>).

First start of OfficeTalk using MS-SQL-Server without installed client part of MS-SQL

If you start OfficeTalk on a client and the MS-SQL client was not installed, OfficeTall runned into enless loop. If you have not installed any parts of MS-SQL, you must create the environment variable Version with the current version nummer by hand. See documentation OfficeTalk Reference. Starting OfficeTalk with no database OfficeTalk, the ODBC driver and MS-SQL client must be installed as a minimum.

New services in system variable ScriptDialog for formating the contents of input fields

With the new services valueNamed(<fieldname>, formatWith: <rule>), valueNamed(<fieldname>, put: <vaiable>, formatWith: <rule>) and valueNamedFormatForPassword(<fieldname>) you can define format rules for input fields in many ways. The thirt service is for password like input. Each typed in character is displayed as an asterix. With the first and second service you can define format rules for all kind of variable types (string, number, date and time) including colors. For details please read the documentation OfficeTalk Script chapter Systemvariable ScriptDialog service valueNamed(<fieldname>, formatWith: <rule>), service valueNamed(<fieldname>, put: <variable>, formatWith: <rule>) and service valueNamedFormatForPassword(<fieldname>).

New services in system variable ScriptDialog for editing Combobox- and Spintext input

You can not only change the input with the buttons but edit the input text of theese fields with the new services too. For details please read the documentation OfficeTalk Script chapter Systemvariable ScriptDialog service addSpinInput(...) and service addComboBox(...).

Service openHistory of the systemvariable stepscheduler

The service displayed an entry for the current step in work. Now, this entry is not shown anymore, because its corresponding step is not finished.

Showing histories of finished processes

Histories of finished processes are shown only if the current worker or a subordinated worker is the owner of it's process template. This change is relevant for the dialogs Tasklist for: <workername>, Tasklist for workers from: <workername> and Starting process for: <workername>.

Die Historien abgeschlossener Vorgänge werden nur noch angezeigt, wenn entweder der aktuelle Bearbeiter, oder ein untergeordneter Bearbeiter Eigentümer der Vorgangsvorlage ist. Dies betrifft den Dialog Aufgaben für: <Name des Bearbeiters>, Aufgaben ab dem: <Name des Bearbeiters> und den Dialog Vorgang starten für: <Name des Bearbeiters>.

New service valueNamed(<Name des Eingabefeldes>, useSeconds: Boolean)

With the new service you can define wether a time inputfield is used with or without seconds. For details read OfficeTalk Script.

Displaying and typing in input fields for Time

Input fields and text fields with Time are typed in and displayed only on Machine related activities with seconds. On all other worker types (Desk, Office, e.g.) the time fields are handled without seconds. The times of the process history entries are displayed ever with seconds.

The Tasklist is opened with the previous used columns width

If in the Settings the option Tasklist as Table is set to Yes, your changes to the columns width are saved in the environment. Opening the Personal Tasklist or the Group-Tasklist the next time, these values are used. So, you must not change the columns every opening. The columns width are saved in the environment ProcessList, AdoptProcessList and GroupProcessList with the key ColumnsWidth.

Dialog Tasklist as Browser shows the average worktime

The dialog displays in the middle field not more the minimal and maximal worktime of the step but the average worktime (middle of minimal and maximal) and the runtime of the process (from start to now) in the field Runtime:. For details please read documentation OfficeTalk Reference, chapter Process-State.

Dialog Status of: <name of process> displays the total runtime of the process

The dialog displays additional to the worktime of the process the total runtime of the process in the field Runtime: too. For details please read documentation OfficeTalk Reference, chapter Process-State.

OfficeTalk can use .Net components for processes

Since this version you can integrate components in processes, using the new technologie Microsoft .Net. With this feature you can use in your processes this new and heavy technology. Using .Net components makes no difference to using other communication libraries.

New process permission ignore waitings

The tabulator Permissions in the worker's dialog contains the new permission ignore waitings. To schedule or terminate a process, whitch is waiting for the ending of another process or for the arrival of answers, you must have additional this permission.

New select criterias in dialog Selection processes (menue View - Select processes by... in dialog Tasklist for: <workername>) and in dialog Tasklist for workers from : <workername>

The options for the select criterias are moved into the combobox list Filter by:. Additional you have 3 new criterias (this Week, this Month and this Year). The new option select the proceses as named.

Communication library for Docuware 4.6

The communication library for Docuware version 4.6 is distributed. To integrate Docuware into a process workflow you must have installed Docuware 4.6 or higher.

Overflow on some input fields for description

In some input fields more characters, than allowed could be typed in. Description fields with more than 1000 character capacity where affected. Now, you can not type in more than allowed or the overflow amount is truncated without warning.

New service maxCharComment and maxCharString for adjusting text input size to database limitations

The system variable step has the new service maxCharComment and the system variable processdata the new service maxCharString. Theese services answer the allowed maximal number of characters for storing a text in database. You can limit in a ScriptDialog the input size of an input field <aName> with processdata.valueNamed(<aName>, maxChar: <aNumber>) to the maximal number of characters <aNumber>. For storing the text in a comment you must limit the input to step.maxCharComment. For storing the text in the processdata you must limit the input to processdata.maxCharString. If you do not limit the size and the user exeeds it, the text is cutted when stored into database without warning.

Wrong display of used database in dialog About OfficeTalk

When using the Microsoft-SQL-Server, the dialog displayed the using of the ODBC-database. But the functionality was not affected.

Sending a mail with vowel in subject or in text was denied

The systemvariable Mail did not send mails with vowels or ß in subject or in text. The service send returned False.

New service sendText in the systemvariable Mail

The systemvariable supports the new service sendText. Its an alias for the service send. For details read OfficeTalk Script.

Activating a template in the tasklist dialog begun the process starting procedure without permission

Activating a template in the template list of the task list dialog opened the dialog for typing in the private process name without having start permission. At least the new process was not started, but opening the private name dialog seemed to be started.

First dialog was opened in english if message directory C was installed

If a language directory and the english directory (named messages\C) for the texts was installed, the first dialog was displayed in english without respect to the language setting.

List of process paths is displayed in a new dialog

The menu Statistic - Process paths in the dialog Graph for process: <template name> displays the list of paths in the new dialog Paths of process: <name of the process>. Selecting a line in this dialog outlines the corresponding path in the process dialog. This strategy enables you the see all pathes and the process with the outlined path. On complex process structures the number of possible pathes and the wait time for opening this dialog explodes. So maximal 1000 paths are displayed. You can change this limit with the environment ProcessLayout\MaxPath.

Title in dialog Executing script macro '<name of macro>'

The title displayed sometime not the executed script macro.

Country language of the texts in dialog Executing script macro '<name of macro>'

The strings in the dialog where not nationalized but always english.

Displaying the steps with circles in dialog Graph for process: <template name>

The display option Steps as rectangle/circle in the dialog View Settings displays the steps of the process with small gray circles. This display type is a little more compact than displaying the steps with grayed rectangles. Choose your preferred display type !

Settings for Steps as rectangle/circle and Detailed or compact step for process displaying

The settings are stored in the environment in the group ProcessLayout (StepAsRectangle and SmallSymbols) and are remembered for the opening of the next process.

Pressing Enter key fast in dialog Tasklist for: <name> and Tasklist for workers from: <workers name>

If the Enter key was pressed in fast sequence before the next messagebox was opened, the system was hanging; sorry. This effect was not easyly reproductable.

Customize the users interface to the Cooperate Identity of your company

You can customize the dialogs, toolbars and menues of many dialogs and windows. This includes:

- Toolbar buttons of the main dialog
- Toolbar buttons of the organigram bowser dialog
- Toolbar buttons of the tasklist dialogs
- Menu symbols of all dialogs.
- Contextmenu of all list fields

In the directory OfficeTalk\Gallery you can place alternative symbols for the toolbar and menue items. The picture format may be any well known type (JPG, TIF, BMP, e.g.). Please read details in the documentation OfficeTalk Reference.

- The background color of the dialogs

In the dialog Settings you can set the background color of the dialogs to the requirements of your company's CI

Schedule or terminate process, waiting for process termination or an answer

On the userlevel Beginner canceling and scheduling a process that waits for ending another process or waits for an answer is not possible anymore. This is only allowed, if you have the reqired permissions and the userlevel Normal and Expert.

Activation of waiting pocesses did not work in evaluation version

When a process was finished, the waiting processes had not been not full aktivated.

New service in systemvariable stepscheduler for communication of dependent processes

With the service notify(..., with:..., inEntry: ...) a process gives to all his waiting processes processdata. With this service a process can give his initiator executing results.

Onlinehelp did not show services for classes with underscore in name while writing a script macro

If a classname contained an underscore (e.g. communication library for Docuware), the online help did not display the possible services after typing in point and scace after variable name.

New services of the systemvariable stepscheduler for delegating a process

With the new services workers, goTo() and goToPredecessor of the systemvariable stepscheduler you can delegate the process excecution to another worker as defined. For details read OfficeTalk Script chapter Systemvariable StepScheduler.

Changing the workers selection in the Organigram browser dialog

If you selected another worker, the current worker was changed, you answered the message for saving and abandom, and closed the dialog next, the system was hanging.

Removing workers elements in dialog Organigram for: <name of the worker> with the toolbar button

In the dialog dragging the sheras over a workers element (e.g. script) was allowed. But dropping it over did not remove the element.

FlyByHelp was missing in dialog State of process: <name of the process>

The FlyByHelp for the input fields, when touching with the mouse, was missing.

The shortcut Page Up and Page Down in the tasklist dialogs for faster work

With the keys Page Up and Page Down you scroll the symboled tasklists by page.

The shortcut Home and End in the tasklist dialogs for faster work

With the keys Home and End you select the first and last task in the tabeled tasklist.

The shortcut Del and Ctrl+CR in dialog Graph for process: <template name> for faster work

With the key Del you delete the selected step. With the key Ctrl+CR you open the selected step. For details please read OfficeTalk Reference.

Creating Scriptdialogs with automatic layouting

New services in ScriptDialog layout the elements in the dialog automaticly. Theese are new add-services and services to build the dialog. You must not calculate the element positions by hand anymore. For details read OfficeTalk Script chapter Systemvariable ScriptDialog.

Horizontal und vertical divider and groupbox in ScriptDialog

The script macro supports now services for inserting a divider and a groupbox into a ScriptDialog. For details read OfficeTalk Script chapter Systemvariable ScriptDialog.

Maindialog OfficeTalk can be closed with Alt-F4

The application can be closed with the shortcut Alt-F4 in the main dialog OfficeTalk (no tribute to Windows !). The shortcut ESC in the main dialog does not end the application anymore. This makes sense on parent dialogs but not on the main dialog !

Der Hauptdialog wird nun statt mit der Tastaturkürzel Alt-E mit Alt-F4 beendet (kein Tribut an Windows !). Auch kann er nicht mehr mit der ESC-Taste beendet werden. Bei Teilfenstern ist die ESC-Taste sinnvoll, nicht aber beim Hauptdialog der Awendung !

Creating and open a script dialog without positions

Now you need not calculate the position of the dialog elements by hand. You can insert elements (text fields, buttons, etc.) without position. For each kind of element a new service exist (for details read OfficeTalk Script). With the service build and buildWithColumns() you create the dialog in columns and open it as usual with open.

Traversing in dialog Graph for process: <template name>

With the direction keys Left, Right, Page up and Page down you can follow the execution pathes in the dialog. Traversing selects the next step in the path.

Deleting and opening entries in list fields and dialog Graph for process: <template name> with keyboard

For quicker working with OfficerTalk you can open an entry with the Ctrl+Enter key and delete an entry with the Del key.

Displaying the remaining runtime of a process

Because the remaining runtime must be calculated, to be displayed in the different task list dialogs, opening such a dialog may be delayed for complex process structures. To avoid this delay, you can supress displaying the remaining runtime. You must create the environment entry DisplayRuntime with the textvalue 0 or No.

- /ProcessList: personal tasklist
- /AdoptProcessList: Takeover tasklist
- /GroupProcessList: Group tasklist

On a Windows platform the environment is located in the registry HKEY_LOCAL_MACHINE\SOFTWARE\JOOPS GmbH\OfficeTalk. On a Linux platform the environment is located in the file OfficeTalk.ini. The dialog State for: <name of the process> shows the remaining runtime of a process in every case !

Menuitem Tasks - Open Processlist-Group... has been removed

The menuitem was removed. The menuitem Tasks - Open Tasklist... opens, similar the toolbar button, depending on the type of the logged in worker the process list or the group process list.

Modified communication library Microsoft Outlook

Because of technical reasons, the communication library for Microsoft Outlook (Mirosoft Outlook.pcl) was updated.

Endtime of history wait-entry is changed in dialog History for: <processname>

In the past, the end time for a history's wait entry (entry with semaphore symbol) for the ending of a process was set to the calculated process runtime. Now, the end time is set to the real end time of the process to wait for.

New services in system variable ScriptDialog for defaultbutton

Some new services for defining the default aspect of a button in system variable ScriptDialog are supported. With theese new services you can define wether a button acts as default (is activateable with the Enter key). For details please read OfficeTalk Script.

Logging access to the script macro cache

If you set in the Settings the option Logging auf Yes, information about the script macro cache access is written into the logfile protocol.txt.

Return activates the default button in the task list

If a process in the personal tasklist is selected, the Return key activates the Schedule button. If a process in the taskeover tasklist is selected , the Return key activates the Takeover button.

Process was selected in opened tasklist and all buttons were disabled

An existing process was selected after the tasklist or the group tasklist was opened, but all buttons were disabled like no process selected. First the process had to be reselected, to set the buttons into their right state.

Servicename of systemvariable stepscheduler has changed

The servicename stepResultNames in the systemvariable stepscheduler has been changed to resultNames. Change your script macros, if needed.

Scheduling steps without useraction (machine processes)

Scheduling the step of a machine process supports now steps without user actions. A machine process may have no user action. If a start- or end action answered a wrong step result (Return statement of the associated script macro), the process was finished. Now you get the finish dialog, to choose the propper result.

User action answers a bad step result

If a mandatory user action answered a wrong result (Return statement of the associated script macro), the process was finished. Now you get the step scheduling dialog, to choose the propper result.

Start script macro ends with no or unknown Return value

If a start script macro ends with a bad Return value (no or unknown) and the step has exact on step sucessor, the scheduling of the processes is automaticly proceeded with this only one next step.

Writing an argument in a script macro

Writing and modifying an argument inside a script macro is not allowed. Doing this has no consequence for the calling script macro, but it's not allowed. Now, if you try to write an argument, you get an error message when compiling the macro.

Importing a single script macro in tabulator Scripts did not enable the menu Save or Save and close

If single script macros were imported in the tabulator Scripts, but the macro's script was not selected, the menu items Save and Save and close were not enabled.

Logging mail activities

If you have activated in the Settings the option Protocol with Yes, mail activities are logged into the file protocol.txt.

Sending a process question in dialog Ask and wait for answer was denied

Sending a question with the dialog Ask and wait for answer was denied with a error message if a mailtext was given.

Password for receiving answers to process questins in Settings

In the Settings dialog you can set the password for mail receiving. If you typed the correct password, receiving mails is done automaticly without the login dialog.

Full overwiew of running processes

In the Tasklist-Group the worker Comany, Department, Office and Team can see now the active processes of all visible workers inside and outside his hirarchy. Processes in workers outside the hirarchy are displayed only, if the logged in worker has a permission with only read right.

Statement Input, Line Input, Print or Write with invalid file variable

OfficeTalk is ended, if the statement Input, Line Input, Print or Write is performed with an invalid file variable, sorry. E.g. you get an invalid file variable with opening a non existing file in Input mode and ignoring the error message.

Permission without any rights

Now, you can create a permission without any process- and step-right. With this, you can retract a permission, inherited from a superior worker.

Importing scripts

If a script macro allready exist, you get the difference dialog. With this dialog, you can inspect the contents of the existing and new script macro. Answering Yes or No overwrites the macro or skip it. Answering Yes to all or No to all proceeds with all subsequent macros in the same way.

Importing a processtemplate

If you import a process template, and a script macro or a permission or some other component is existing allready, you are asked how to proceed. Answering Yes or No overwrites the component or skip it. Answering Yes to all or No to all proceeds with all subsequent components in the same way.

Scriptdialogs must be enlarged

Because of moving to the new version of the system development platform, you may enlarge the height of script dialogs, containing elements at the bottom. Else the bottom part of this elements is cutted. You do this with the service height(). For details please read OfficeTalk Script - Systemvariable ScriptDialog.

Selection and deselection an entry in the script makro using list

If you selected and deselected an entry in the using list, you got an error message and OfficeTalk was terminated, sorry.

Using list for script macros displayed wrong references

The using list for script macros displayed a wrong reference, is there was a Call statement with a script macro beginning equal as the searched. e.g.:

Service.Construct2 was displayed searching references for Service.Construct too.

eMail answer of process questions were not stored in the history

A received answer to a process question was not visible in the semaphore entry of the process history.

Question and answer strings are limited to 4000 character

Sended and received mails are limited to 4000 characters. The text is shorted without warning if needed. In the past you got an errr message when saving the transaction with strings larger than 4000.

Scheduling a process with an empty step

In the past the process was ended if a step with no action (Start, User or Term) was scheduled. Now if the step has exact one direct successor (one stepresult with a step) the process steps to this step. If you need only a delegation without an extra action, you can use this.

Formating addAction(...) und addActionButton(...) in script macro in tabulator Scripts of the worker dialog

The menu Format formats the macro, written in the first argument of the services, like the other statements with line adjustment, case, a.s.o.

Login at the mail server for sending and receiving process questions

If you set in the dialog Settings the option Single-Sign-On to Yes and leave the textfield user empty, the login at the mail server is done with the login of the current worker. If the login is denied, you get the well known login dialog.

New service in system variable stepscheduler

The system variable supports the new services environment(..., in: ...) and environment(..., in: ..., put: ...). On Windows platforms, you can process inside a script macro the environment in the registry. For details please read OfficeTalk Script.

Export a worker with worker references

Exporting a worker, the worker references in the worker's components (steps, permission inheritance, ...) are exported too, if the reference describes a worker in his hirarchy. In past only the scheduling option Use current worker was exported instead of a scheduling worker.

Using an unknown variable in the source of the services addAction(...) and addActionButton(...)

If you use a not declared variable in the source (the first argument), an error text is displayed. The automatic variable declaration does not work here.

Wrong selection if syntax error in the source of services addAction(...) and addActionButton(...)

If a syntax error was detected in the first argument's source, the wrong source part was selected.

Compiling a script macro alerts an used but unknown script macro

Compiling a script maco you get a warning message if you use an unknown script macro name in a Call-statement. Answering Yes continues the compiling. The macro may exist only outside the visible workers hirarchy.

Cache for compiled script macros in the services addAction(...) and addActionButton(...)

The script macro, written as first argument, is cached when compiled and used. Doing the action twice is mutch faster, because the script macro must not be compiled again.

Formating a script macro in tabulator Skripts of worker's dialog

Formating a script macro writes the script macro names in the Call-command in the defined case.

In script macro opened dialogs are centered

Dialogs, opened in a script macro, are now opened at the mid of the screen. In past, they were opened at the current mouse position.

In all functions expressions as arguments are allowed

In some functions (InStr, IsDate, IsEmpty, IsNull, IsNumeric, Len und StrComp) only variables as arguments were allowed. Now, you can use expressions as arguments too. An expression can be a variable, a Call service, ein Call-Script service or a function. e.g.: IsEmpty(Call Customer.Adress) oder IsEmpty(dialog.valueNamed("field1")). For details please read OfficeTalk Script.

Formating a script macro in tabulator Scripts of worker's dioalog

Formating a script macro writes the servicenames and process template names in the Start-command in the case as defined.

Compiling a script macro alerts unknown process template names

If in a script macro a Start command with an unknown process template name is used, you get a warning message. Answering Yes continues the compiling. The template may exist only outside the visible workers hirarchy or the current worker has no permission to start the process.

The system variable action shows only possible service names

The online help (typing . and space) for the system variable action shows only the possible service names.

Most system variables are available at test time

If you test a script macro in the tabulator Scripts of the worker's dialog, the system variables worker, process, processdata, step und action are now available. worker holds a copy of the current worker. The other variables hold example data, and the messages System variable xxx does not exist... do not appear anymore when accessing a variable.

New service openHistory and openHistory(<category>, name: <name>, logicalName: <priv. name>)

With the new supported services by the systemvariable stepscheduler you can display in a script macro the history of the current process or the history of the named closed processes. For details please read OfficeTalk Script.

Script macro command process.logicalName set the name in the process history too

The command set the private process name not only in the process but in its history too.

Export and import a worker and his hirarchy

The contextmenu of the listfield in the dialog Organigramm- and Organigrammbrowser has the new entries Export... und Import.... With this menuentries you can export a worker and his hirarchy with all contained elements (processtemplates, permissions, scripts,...) and import it into another OfficeTalk system.

Wrong email adress in Incoming: in dialog Settings was not validated

An invalid email adress was used in Ask and wait for answer without validation and OfficeTalk terminated with an error message. The email adress must follow the RFC822 conventions. Now you can not store the stettings with an invalid Incoming, you get a message instead.

Invalid input in dialog Ask and wait for Answer

If you typed in an invalid receiver adress, not following the RFC822 conventions, OfficeTalk had been terminated with an error message.

New service processData of the system variable process

The service answers the processdata of a process and helps to give the processdata of the current process to a started process. For details please read OfficeTalk Script.

New service addEntry(<group>, from: <processdata>) of the system variable processdata

The service copies the entries, named <group>, from <processdata> into another processdata. For details please read OfficeTalk Script.

Updated communication library Docuware.pcl für using DocuWare in OfficeTalk

The directory Library contains the updated file Docuware.pcl. The library had to be actualized, because variables in script macro are not initialized anymore.

New services in systemvariable processdata

The systemvariable supports the new services item(<Name>, with: <Datum>, inEntry: <Gruppe>), removeItem(<Name>, inEntry: <Gruppe>) und removeEntry(<Gruppe>). For details please read OfficeTalk Script.

Services addItem(...) and item(...) are not case sensitive

Group- and entrynames within the service arguments are not case sensitive anymore.

Variable names in script macro are not case sensitive

Writing variable names in script macro is not case sensitive anymore. Please change your script macros, if you use same named variables with different case. e.g.: The two variables State and state where two different variables in the previous version, but means now the same variable.

Systemvariariable error is named Error

The systemvariable is written now with uppercase E. The script compiler knows the old style (lowercase e) too.

Variable declaration does not initialize the variable anymore

The declaration Dim <name> As <typ> does not initialize the variable with the default value (e.g. Integer: 0) anymore. Please change your script macros, if neccessary,

Filename in Library statement is not case sensitive anymore

In the statement, the filename of the communication library is not case sensitive anymore.

Call statement with wrong macroname inside an If statement

If a Call statement was written inside an If statement with wrong or unknown macro name, the script compiler did not recognize this mistake. The error was notified at execution time with the message Unknown script macro....

Call statement in service addAction(..,) and addAktionButton(...) was not checked

The Call statement, used in the named services of the system variable ScriptDialog, was not checked at compile time. A wrong macro name was notified only at execution time with the message Unknown script macro....

Saving of incomplete entries was possible

Saving an absent with missing start or end time and saving a step result with missing execution time was possible if an entry field in the dialog was cleared first and second another tabulator in the dialog was selected.

Debugging of a script macro using a dialog enhanced

Debugging a script macro, using a dialog, was not fully supported. Now you can see the execution of actions, defined in addActionButton(...), too.

New service addRadioButton(...) in script macro

In dialogs, created in a script macro, now you can place radiobutton. For details please read OfficeTalk Script.

Checkbox was positioned wrong in dialog of a script macro

The checkbox was positioned wrong with addCheckBox(..., leftFraction:...) in dialog. The box was not visible.

New menu Usings... in script macro listfield

The listfield of the script macros (right topmost in the tabulator Scripts of the worker's dialog) has the new context menu Usings.... The menu opens a list dialog displaying the script macros in which the selected macro is used. Double clicking a line opens the script macro and the using line is selected.

Not allowed menu in listfield Steps in register Processtemplates

In the step's listfield the menu New Step was enabled but not allowed, if no processtemplate was selected.

Readoly textfileds ar copyable

Textfields of readonly opened dialogs are not grayed anymore and can be copied into the clipboard with the contextmenu Copy or CTRL-C.

Some elements were not disabled in readonly opened dialogs

Some elements in the register Absents were not disabled, if the dialog was opened readonly.

Enddate in dialog History for: 'name of the process'

The field Enddate: is only filled, if the step or process is finished. In entries, waiting for the answer of a question, the enddate shows you, when you received the answer via email.

Wrong entry in end date and timespan in dialog History for: 'name of the process' of waiting entry

In the waiting entry (the semaphore), resulted by Ask and wait for answer the contents of the end-date and timespan fields were wrong.

OfficeTalk terminated after changes in history dialog

If the start- or end-date in the dialog History for: 'name of the process' was changed, OfficeTalk terminated with an error message, because histories are not allowed to be changed.

Incoming mail answers were not deleted if IMAP mailprotocol was used

If you used the mail protocol IMAP (in the settings), the incoming mail answers for processes where taken over, but not removed from the mailbox. So the mailbox increased and the mails had to be deleted by hand.

Question text for a process is written into the history

The text of a question, created with the menu Ask and wait for answer in the task list, is written into the history too. So you can see this text with the answer later in the history.

Service names and datatype names are not case sensitive anymore

Writing service names (e. g.: dialog.open) and datatype names (e.g.: d = New ScriptDialog) is not case sensitive. Formatting and compiling corrects the datatype names.

New service replyTo() of system variable Mail in script macro

The system variable knows the new service replyTo(). With this service you can specify the mail adress for the answer. For details please read OfficeTalk Script.

New option Incoming answers: in dialog Settings

The dialog supports the new option. If a concurrent mail system is running, you must specify an extra mailbox for incoming answers of process questions. If not, OfficeTalk does not see this answers. For details please read OfficeTalk Reference.

New service to insert a combobox into a ScriptDialog

The system variable ScriptDialog supports the service addComboBox(...) for inserting a combobox field into the dialog. For details please read OfficeTalk Script.

Import and Export scripts

In the tabulator Scripts you can export and import with the script list's contextmenu Export... and Import... a script with all containing script macros. The script is exported in a .bos-file. With this feature you can transport scripts from one OfficeTalk system to another.

The Call statement using in script macro

The Call statement can now be used in numeric and boolean expressions too. Up to the previous version you had to get the result of the Call statement first, and use the result in the expression second.

Disabled input fields in ScriptDialog dialogs can be copied

The contents of fields, disabled with disableNamed(<fieldname>), can now be copied with the context menu or the keyboard CTRL+c. This fields are not grayed anymore.

Missing script macro's content of actions in HTML output

If in the step of the action the option Current Worker was set (done in the dialog Scheduling Options), the content of its script macro was not printed into the HTML file. The HTML file is created with die menu Save as HTML... in the dialog Graph for process: <template name>.

Script macro was not formatted well in the HTML output

The script macro was formatted without indents and linefeeds. Now it is formatted like your dialog input with indents und linefeeds. The HTML file is created with die menu Save as HTML... in the dialog Graph for process: <template name>.

OfficeTalk was aborted if logging was not possible

If the option Logging was set to Yes in die dialog Settings, but the installations directory was Read-Only, OfficeTalk aborted with an error message. Now you get a propper warning, but the system works well.

Options Logging and Single-Sign-On in dialog Settings

Theese options are now changeable in any case. You must not be logged in as the Company anymore.

Message The worker <name of the worker> is logged in allready

If the logged in worker was modified and saved, using the Microsoft-SQL-Server, the named message appeared, if the login name of the worker and the login dialog was not equal in case. You could ignore this message, it was wrong.

Dialog Step '<name of the step>' is closed automaticly

After scheduling the last action of the step with the button Schedule and the scheduling worker has no permission to change the date or worker of the next step nor the next step itself, the dialog is closed automaticly. In the past the dialog must allways be closed with the button Finish. This modification makes process scheduling faster and smoother.

Step was noted more times in the HTML output

If a step was reachable by more step results (blue lines), he was noted more times in the HTML file.

Creating an OfficeTalk database user was incomplete

Creating inside the Organigram browser dialog a database user for the company with the context menu Create Database User did not create all needed elements.The missing elements had to be created by hand. If not, the creating of database users for other workers did work, but a later login was denied.

Error messages of Oracle library are given as text

The errors of Oracle functions in the communication library are given as text, not as a number anymore.

Better reading of script macro syntax

The syntax of Bool-expression was changed for better reading. e.g. Write If IsEmpty(<variable>) = True instead of If IsEmpty(<variable>) Then.

Compilie and save the relevant macros. If a wrong macro is used while step scheduling, you get the message Error while compiling the script macro <name> and the step is terminated.

Cache for compiled script macro

A compiled script macro is cached. So, executing twice is much more faster.

Used data type in Call-statement in script macro

In the Dim statement in a script macro of a Call-statement and in the arument line of a called macro the datatype had to be named identical. Now, you must not name them identical (e.g. ScriptDialog and Joops.Scripting.ScriptDialog).

Changing an username for mail

If the username for mail was changed in dialog Settings, the next receiving of mails was done with the old password. OfficeTalk had to be started new, to work with a new password. Now the new password is requested if the username was changed without OfficeTalk is restarted.

Default setting of host and username in systemvariable Mail in script macro

If in systemvariable Mail the services host() and user() were not used, now host and username of the dialog Settings Host and User were used to send the mail.

Color of semaphore in tasklist Tasklist for: <name> and Tasklist for workers from: <workers name>

The color of the semaphore for a process was not displayed correct, if the task was delayed only a few hours.

New functions in script macro

A script macro knowns new functions to insert in dialogs a list field with a horizontal scrollbar. For details please read OfficeTalk Script.

Program terminated when choosing the menu Path and selecting then the window close button in dialog Graph for process: <template name>

Choosing the menue Path on big processes and selection the window close button before the submenu was opened, OfficeTalk displayed an error message and terminated, sorry.

Combobox in Pemissions dialog displayed the same process category twice

The combobox for choosing the process template displayed a process category twice if two processes with the same category but different names were existing.

OfficeTalk was endede on a special script macro statement

Formating or compiling a scriptmacro with a statement with pattern <Variable> = Call <Scriptname>(<Expression>) ended OfficeTalk with an error message because of the missing script macro name in the Call statement..

New functions in scriptmacro

A script macro knows the new function MousePointer and the new service valueNamedSelectionIndex for the system variable ScriptDialog. For details please read OfficeTalk Script.

Listfields and labels in script macro with Courier font

Now you can display labels and the contents of list fields with the font Courier. This will help, if you want to display the contents of a list like a table. For details please read OfficeTalk Script.

New service for limiting the number of input characters in a script dialog's text field

The system variable ScriptDialog knows the new service valueNamed(<the fieldname> , maxChar: <count>). With the argument maxChar: you can limit the number of characters to type into a text field. This is usefull, if you want to store an input in a database table of your own, because a database must defined the maximum size of each column in a table.

New service column in communication library OracleForOfficeTalk

With the new service, you can access columns in the select result (a dynaset) by their position. Some select variants answer unnamed columns.

New functions Mid, Left und Right in scriptmacro

For better working with strings, you can use this new functions, well known in VisualBasic. For details please read OfficeTalk Script

Im- und export a process template

With the contextmenues Import... and Export... you can move process templates from one OfficeTalk system to another system. For details read the documentation OfficeTalk Reference.

Display of the used database in a evaluation version

The evaluation version shows in the Do About dialog the text Internal Database for used database.

Process rights inheriting is extended

If a worker inherits rights from a superior worker, he inherits the rights of the superior worker and the rights, the superior worker inherits itself too.

New function Delay in scriptmacro

In a script macro you can delay the statement's processing a given time. For details please read OfficeTalk Script

Termination a process in dialog Tasklist for: <name of worker>

If a process is selected in the personal tasklist and in the takeoverlist, you can terminate it with the keyboard key DEL. The shortcut of the corresponding menuitem is modified too.

Accept- and Cancel-Button named in scriptdialog

Both buttons are now named for enabling and disabling with enableNamed and disableNamed. For details please read OfficeTalk Script.

New services enableAccept, disableAccept, enableCancel and disableCancel in scriptmacro

With the new services you can disable and enable the close and abort functionality for the dialog. For details please read OfficeTalk Script.

New service enableNamed in scriptmacros

With the service you can again enable disabled dialog elements. For details please read OfficeTalk Script.

Returning comlex objects to calling scriptmacro

Returning with statement Return a complex object (e.g. a communication object) to the caller, the object was not useable by the caller scriptmacro.

Scriptmacro statement causes an abnormal termination

The statement <var> = <var2>(Date) caused an abnormal termination because the function Date returns no index for an array element access.

Extended function MsgBox in scriptmacro

Using the function MsgBox, you can predefine the answerbutton's number. If the userlevel fits, the message is suppressed and the function returns the predefined number. Read details in the documentation OfficeTalk Script in chapter Funktions MsgBox.

Using arithmetic operators in scriptmacro

The using of arithmetic operators is expanded. Read details in the documentation OfficeTalk Skript in chapter Makro Syntax.

Version 2.00

New option Do not substitute existing result of an useraction

In the register Useraktions of the dialog Step '<Name of the Step>' you can set the new option Do not substitute existing result. This option is only suitable for special situations. Read details about in the documentation OfficeTalk Reference.

Save or send a process template as HTML file

Selecting the menu Save as HTML... or Send... in the dialog Graph for process: <template name> you can choose between detailed and short output.

New menue Work and toolbar for all kind of tasklist dialogs

All kind of tasklist dialogs contain the new menue Work for scheduling, terminating, ... the processes. All kind of tasklist dialogs contain at the top a toolbar for the important commands. For details see Dokumentation OfficeTalk Reference.

Alle Formen der Aufgabenliste haben das Menü Bearbeiten neu und die Dialoge haben am oberen Dialogrand eine Toolbar für die wichtigsten Befehle aus der Menüleiste. Die genaue Beschreibung entnehmen Sie bitte der Dokumentation OfficeTalk Reference.

Installing the full version after having installed the evaluation

If you have installed an older evaluation version, you must first delete the registry key HKEY_LOCAL_MACHINE\SOFTWARE\JOOPS GmbH\OfficeTalk before you install the full version.

Installing OfficeTalk using an Oracle database

The automatic procedure of installing OfficeTalk with an Oracle database was a bit little buggy, and required manually work. Sorry !!!

Expressions with operator & in scriptmacro

Using expressions with the operator & is extended. Read details in the documentation OfficeTalk Script.

Service addAction() did not work in list entry

The service did not work in list entries as described in the documentation OfficeTalk Script.

Menu Save as HTML did not save the process diagram

In some cases, the diagram was not saved correct in the picture file (.png). As the result, you saw in the browser an empty rectangle instead of the process diagram.

Permission using is changed

Up to now, the permissions (register Permissions in worker dialog) were cumulated up the workers hirarchy, as the permission inheritance (register Authorize in worker dialog) was defined. e.g.: If worker Müller had the permission Schedule for the process Akquisition -Versicherung, inherited the permissions from his department, and the department had the permission To Work, worker Müller inherited this permission too. Now the first permission up the workers hirarchy matching the process name is used only.

Modifications in the rights management

Because of modifications in the internal rights management, you must set the right all Rights in the entries having had this right again.

Selecting the scheduling worker for a new step

In the tabulator sheed Scheduling Options of dialog Step: <name of the step> and in the tabulator sheed Step of the dialog Stepresult: <name of the stepresult> the combobox Scheduling worker was empty. For newly created steps, you had to select first the option Current worker. After saving and opening again, you could select a worker from the combobox entries. You get the dialogs with the step's contextmenu New - Step and New - Stepresult in the dialog Graph for process: <template name>.

New menuiten Refresh in Tasklist

The menu View contains the new menuitem Refresh. This menuitem initiates a refresh on both lists (the personal, and the takeover).

Toolbar for dialog Graph for process: <template name>

The dialog contains at the top a toolbar for the important commands. For details see Dokumentation OfficeTalk Reference.

New shortcut for menuitem Refresh

The menueitem View - Refresh in dialog Graph for process: <template name> and the tasklist dialoges is now reacheable with the shortcut F5.

Menueitem Start new process shows not startable processes too

The menueitem Process - Start new process in the tasklist showed not startable processes too. Selecting such a process did nothing, but not startable processes should not be shown.

New datentype Long in scriptmacro

Now, you can use the datatype Long too. The datatype Integer does the same, but for compleetenes...

New function Len and InStr in the scriptmacro

In the sriptmacro you can use the two new function. See documentation OfficeTalk Script for details.

Using othe datatypes than String in operator & in OfficeTalk Script

Now you can use other datatypes than String as operand in the operator. The operand is converted first to String, if needed.

Subsequently opening the dialog Graph for process: <template name>

Opening the dialog for the same process more than twice did not save modifications of the layout into the database.

Save or send a process template as HTML file

Now, you can use a process template outside of OfficeTalk. For this, the menu File in the dialog Graph for process: <template name> has two new items:

Save as HTML...

This menu item saves the process template, opened in the dialog, and its details as file in HTML format. With this feature, you can publish business processes or talk about with collegues, not having OfficeTalk.

Send...

With this menu item, you can send the process template, opened in the dialog, and its details via eMail to somebody else. With this feature you can talk about a business process with a collegue, not having OfficeTalk.

Special characters in process-, step- and script-name

In the past, you could use special characters (e.g. &, +, -), in this kind of name. But if you tried to use such a name in the script macro (Call script command or Start funktion), you got a compiler error. This version only accepts characters, digits and the underscore _ for names.

Dynamic interface for all Microsoft SQL-Server databases in script

With the library Microsoft ADODB.pcl you can now work with all userdefined Microsoft SQL-Server databases. Load first in a script macro the library (Library "..\liBRARY\Microsoft ADODB.pcl"). After loaded, you can use all services of the library. Read the documentation Communication library MSSQL for OfficeTalk. The filename of this documentation is Help\MSSQLForOfficeTalk.pdf.

Changing your own login or password and subsequent abandom changes

If you changed your own login or password and subsequent abandomed changes, you were logged out automaticly. If you selected a menue or clicked onto a toolbar button, you got the message For this action you must be logged in... but the title of the main dialog OfficeTalk continued displaying your name as the logged in worker.

Save-Abandom-Abort Message three times in Organigrammbrowser dialog

If you made changes in the register pages of the Organigrammbrowser dialog, you canceled the dialog with click into the window close button and you answered to the message with the button Abandom, you got the same message two times more.

Abandom changes and logged in with a not case sensitive password

If you were logged in with a not case sensitive password, and you abandomed changes, OfficeTalk logged you automaticly out. If you tried then to open the organigram with the corresponding toolbar button of the main dialog OfficeTalk, you got the message For this action you must be logged in.... Sorry, but nobody thought of this using combination.

Moving workers and inserting new workers in organigram is optimized

If you use the Oracle database server, many not necessary activities were performed, while moving a worker to annother superior worker or inserting a new worker into a superior worker. This actions where optimized and run now a little faster in the dialog Organigram for: <workers name> and in the Organigram browser dialog.

Inserting a new worker into the organigram in dialog Organigram for: <workers name>

Inserting a new worker with help of the toolbox, his superior worker was not expanded. Because of this, the inserted worker was not visible. Now, the superior worker is expanded and the inserted worker is selected.

Moving step results (blue connections) with the mouse in dialog Graph for process: <template name>

Now, you can move the endpoints of a step connection (the blue connectionline as a step result) no another step. To move the start point, select the named connection label and drag the top border of the label to the new step. To move the end point, select the named connection label and drag the bottom border of the label to the new step. Touching not allowed connection points the mouse is displayed as a crossed circle. Touching an allowed end point the mouse is displayed as a square.

Terminate a process in dialog Tasklist for: <name of worker>

If the tasklist displayed the processes as symbols and a process was terminated with the context menu's command, the task's picture was removed, but die selections were leaved.

Moving a worker into another superior worker in the organigram

Moving a worker into another worker was not allowed for referenced workers. e.g. A worker was the scheduling worker for a step in a process lying in another worker. Now, this action is allowed. But think of this fact: Moving a worker into another worker also moves the inherited aspects. e.g. Moving a worker with the aspect Inheriting rights from superior worker, the inheriting also moves to the new superior worker. The worker leaves selected and expanded after beeing moved.

User definable database connection name

In the database login, you can now specify the connection name for your database server. You must not use anymore the predefined name. If Oracle-SQL-Server is used, this is the service name. If MS-SQL-Server is used, this is the ODBC name from the system control. The connect name is labeled in the dialog with Environment:. The used connection name is stored in the environment DatabaseEnvironment.

Open onlinehelp with Book button

If the path to the online help file started with <x>:\, the file was not opened with click onto the book button. This happened on all book buttons. If the path was UNC compatible (<host>//<folder>\...), the onlinehelp was right opened.

Communication library Oracle for OfficeTalk with new services

The library supports for better handling of SQL errors the new services lastServerErr, lastServerErrText and lastServerErrReset. For description please read the documentation Communicationlibrary Oracle for OfficeTalk.

Indexfunction for an array in a scriptmacros

For dynamic creation of an array and accessing a defined element in an array the indexfunction is supported by a script macro. For further description see chapter Function in documentation OfficeTalk Skript.

Script supports the VB statement While-Wend

Now, Scripting supports the old format Do-While-Loop and the newer statement format While-Wend.

Dynamic interface for all Oracle-databases in script

With the library OracleForOfficeTalk.pcl you can now work with all userdefined Oracle databases. The component Bin\Oracle.dll must be fregistered in your system. The setup does this for you. Load first in a script macro the library (Library "..\liBRARY\OracleForOfficeTalk.pcl"). After loaded, you can use all services of the library. Read the documentation Communication library Oracle for OfficeTalk.

Optimized useability in login dialog

The cursor is now positioned into the probably first input field. Given a wrong password or logging in twice, this is the password field. So you must not do an extra mouse click.

Contextmenu (the right mouse button) in list fields and in the different kind of task lists

When an element in list fields or task lists is clicked with the right mouse button and the context menu is opened for this element, the previous selected element is selected again after the menu's action. The selection state of list fields and task lists is not modified anymore by clicking an element with the right mouse button.

More parallel opened steps in dialog Graph for process: <template name>

In the dialog Graph for process: <template name> you can open more than one step at the same time. This helps you to copy and paste informations from one step to another step. The menu Actualize and closing the dialog Graph for process: <template name> closes the opened step dialogs Step 'name of the step' first. The menu Save and close saves the modifications in the opened steps and closes their dialogs. If an opened step dialog can not be closed (because of missing information), you get a message and this dialog is topped.

Extended context menu for steps in dialog Graph for process: <template name>

The context menu is extended with the menu entry Schedulingoptions. With its submenues you can fast access and modify the most important step options.

Processtime Opens a dialog for changing the estimated process time.

Scheduling is With the submenu entries you can make the step execution optional or mandatory.

Current worker This entry makes the step to be executed by the currend worker

Worker The submenu list contains all selectable workers for assigning to the step.

Symbol The submenu list contains all symbols you can assign to the step.

Name Opens a dialog for changing step's name

Button Start Process in dialog Starting new process was selectable

If you where logged in as company, the button Start Process was selectable but no process in the list field was choosen. Nothing bad happened, but the display of the button reflected not the reality.

Onlinehelp for touching grayed dialog elements with the mouse

Grayed or not editable elements in a dialog did not show their description in a small text field. Now grayed and not editable elements show this description too. You can not use the element at the situation, but it my be of interest to know its reason.

Removing a Department, an Office or a Team

If you tried to remove such a worker and a subordinated worker was logged in, OfficeTalk's behaviour was, depending on the used database system, wrong. Using Oracle, OfficeTalk was waiting until the subordinated worker logged out. Using Microsoft SQL, the worker and all his subordinated workers were removed with bad results !!! Now, if you try to remove such a worker, but a subordinated worker is logged in, you get the error message The worker <name of the worker> could not be removed and all deleting operations are undone. You get the same message, if you try to remove a worker which is used anywhere else. Read the documentation OfficeTalk Reference too.

Some modifications for evaluation version

The menu Create database user is hided if you use the evaluation version. It makes no sense.

A worker could be removed but he was used anywhere else. Now its not possible to remove a worker if he is used by another element.

Unknown step result from a script macro

If in a script macro answered with Return an unknown result name, the step was mandatory and all the next possible steps had the option Use current worker, the process was ended with a normal message. Now you get an error message and the dialog Scheduling step <name of the step> for processing the step is opened with the details.

Dialog Settings modified

The selection list field Reading answers was removed. You switch on this function with the seconds value in the text field Reading answers:. All seconds greater than 0 switch this function on. Typing in 0 deactivates this feature.

Personal tasklist is periodically and automaticly syncronized

The processes in the personal task list are syncronized cyclic with the processes in the database. If a new process is added by another worker, you get a message and the list is actualized and the bell rings 5 times. This is the same like you manually use the context menue Actualize of the personal task list. You can define the periode to actualize in the dialog Settings in the textfield Updating tasklist: with typing in the seconds. If you type in 0 seconds, no syncronizing is made.

Closing Evaluation version

The previous version discarded all changes, if you closed OfficeTalk clicking on the window close button of the main dialog. Now, you get a last chance to save your modifications with the question Save all changes.

Onlinehelp for touching dialog elements with the mouse

All fields, buttons, options and list fields show now a short description in a small text field if you touch the element with the mouse. The description is closed after about 5 seconds or if you do a click with a mouse button. You can switch off this feature if you set the Using level: to Expert in the dialog Settings.

Testing and debugging script macros

While testing and debugging a macro in the Scriptbrowser dialog, the message Macro not found... was displayed if a Call statement was executed.

When testing and debugging a macro in the Scriptbrowser dialog, the variable worker is available now. The variable contains the worker, selected in the left upper list field in the Scriptbrowser dialog.

The terms Method and Macro are unified

In the documentation and in the program the terms Method and Macro are unified to the term Macro because a script contains macros not methods.

Sourcetext field in dialog Scriptbrowser was writable without selected script

The text field was writable but a script was not selected. So, the script macro was written without the assigned script. Now the source text field is only writable if a script is selected.

Context menu Rename... for script list in dialog Scriptbrowser

If selecting a script for an action, the context menu Rename.. was enabled. This action makes no sense and is disabled at this situation.

Online help for service namen of system data types variables

The online help for service names does not work anymore for system data type variables (Integer, Boolean, Double, e.g.) , because only statements and functions work with theese variable types.

New toolbar button for opening the script documentation

The toolbar in the scriptbrowser dialog has now the same button as the main dialog OfficeTalk. But clicking on this button opens the script documentation Scripting.pdf. If Adobe Acrobat Reader is installed, the file extension .pdf is associated with it. You can define your own reader within the OfficeTalk environment PDFReader. That one is taken, if defined, first.

Selecting a script in the script browser did not work

If the source of a displayed script macro was modified, but not compiled, selecting another script from the list field did not work without any message. No you get a notifyer, if you want to select another script without accepting changes.

Changed onlinehelp while writing a script macro

The list for selection a datatype from the namespace SmallCOM. has displayed not useable datatypes too.

Extended onlinehelp while writing a script macro

The onlinehelp for using datatypes in the argumentline is now working like writing a Dim line.

Formating and compiling a script macro

In general, syntactical errors are notified only if the macro is compiled. Formating a macro notifys only the errors affecting the format process.

Script macro without any commandline

If you compile a script macro without any commandline, you get a notification, that the Return is missing.

Case sensitive writing in the script macro

Typing in the namespace is not case sensitive anymore. Joops.OfficeTalk or joops.officetalk is equal. The cases are corrected automaticly at compile or format time.

Extended list dialog for selecting a system variable type while writing a script macro

The list contains now on the top of the system variable types the useable namespaces (Joops, Joops.OfficeTalk and SmallCOM).

Loading communication libraries while writing a scriptmacro

If you tried to load a library while formating or compiling the scriptmacro and the Library commandline contained the wrong filename, you was requested to select the file manualy and OfficeTalk terminated with an error message, sorry.

Extended online help while writing a script macro

In the dialog for writing a script macro the online help for system datatype is added. If you type the text Dim <variable name> As followed by 2 blanks, you get a selection dialog with all possible system variable names (String, Integer, e.g.). OfficeTalk datatypes you can write in the Dim line with the namespace Joops.OfficeTalk., Joops.Scripting. or SmallCOM.) or without qualifying (without namespace). If you type in the New statement followed by two blanks, a selection dialog with all possible namespace names is opened. If you select a name, the New statement is completed with this name and a closing point. If you type in again a blank, all datatype names containing in the namespace are displayed in a list.

Communication library for the Document-Management-System DocuWare

The distributrion contains now the communication library Docuware.pcl. With it, you can use complex document management functionality with DocuWare

by DocuWare AG in your business processes.

Communication libraries (pcl Files) with classnames containing underscore

Communication libraries with class names containing others than character or digits where not useable.

Abandom changes in the evaluation version

In the evaluation version changes can not be abandomed. Now you get a notifyer, if you want to abandom changes. In the evaluation version you can abandom changes only if you terminate OfficeTalk by closing the main window OfficeTalk with the window close button. But if you end OfficeTalk in this way, you loose all changes made since the last program start !

Wrong displaying if path in dialog Graph for process: <template name>

If a steps dialog was opened, starting from the graph's dialog, and the step was modified, but the changes where abandomed, (message: Do you want the changes to Save Abandom Abort) the step results (the blue connections) of this step where displayed double.

Logo in main dialog OfficeTalk

This change is for the marketing only. The main dialog OfficeTalk shows now the centered the logo of OfficeTalk.

New button Details in Dialog Step 'name of the step' processing

The dialog shows, when opened, the action list and the most important buttons only. With the button Details >> you enlarge the dialog to show the details of the step processing. The button << Details hides the details.

New menue entry View - Description in tasklist

The dialog Tasklist for: <name of the worker> has the new menu View - Description. With this menu you can hide or display the description textfield of the selected process. If you hide this field and the process templates list, the list fields for the personal- and takeover tasks are enlarged to the dialogs width. The setting for the description field is stored in the environment ProcessDescription.

Automatic login if necessary

If you choose a menu entry or its button in the toolbar whitch requires a logged in state and you are not logged in, you get a notifyer and second the well known dialog for logging in.

Customized directory for the help documentation

The help files normaly are found in the directory Help. If you want to store theese files anywhere else, you can name the new location (a directory), where OfficeTalk can find the help files, with the environment variable helpDirectory.

Toolbar in main dialog OfficeTalk has been extended

The toolbar has been extended with the buttons for Help, collaps all windows and restore all collapsed windows.

Program abort when selecting the menu Filter tasks... in Group-Tasklist dialog

If the named menu entry was selected, OfficeTalk terminated with an error message, sorry.

Extended dialog Processhistory filter

The rules for selecting terminated process histories was extended with filtering histories by the logical process name. The dialog Processhistory filter, opened with the menu filtering... in die dialog Processhistory for: <name of the process>, is extended by the field Name:. In this textfield you can type in the logical name of the process for whitch histories you are looking for. Use the wildcard * for any string and ? for any single character.

Wrong message and substitute entry in evaluation version

In the evaluation version the tabulator Substitutes in the worker dialog did not show the substitute worker. Leaving the tabulator, the message text #incompleteDomainMessage was displayed.

Used fonts

The used font in dialog fields and list fields was unified, and made a little smaller. So, more inforamtion is visible in a single field.

Used colors in dialog Graph for process: <name of the process>

Executed steps are drawn green. The next step to execute is drawn orange. The selected path (menu Statistic) is drawn orange.

Repeated execution of a step

If a step is executed a second time, because a succeeding steps successor is a predeceeding step, its user actions were not executed more.

Category names can be selected too

In the dialogs, using a category field (e.g. processtemplate, step and action), now you can select an existing category name or typing in a new one.

Step with personalized symbol

In the dialog Step: <name of the step> you can select from the list field Symbol:, similar to the actions, a symbol of your own. The step is shown with this symbol in the dialog Graph for process: <name of the template or process> and in the list field Steps of the register Processtemplate in the workers dialog.

State colors for the steps of a process

If you open the dialog Graph for process: <name of the process> with the context menu State... in any task list, executed steps are displayed green. The current step is displayed in red.

Variable column width and sort order in any task list

You can change the column width and the sort order of the tasks in any task list at runtime. Microsoft Windows users know this feature from using the Explorer. The list fields in the task list have a title line with elements like buttons for each column. Clicking with the left mouse button on one of this element sorts the tasks in ascending or desceding column value order. Drag and drop the mouse between two column title elements changes the width of the column on the left side of the mouse.

Changing a Todo- or processlist option in dialog Settings

Selecting a Todo- or processlist option in the dialog, all task- and process-lists must be closed first.

Selectlist Worker in dialog Selecting processes

The selection Worker was empty, if the processlist Processlist for worker starting at: <name of the worker> was opened in browser mode.

Optionlist Database in dialog Settings

The optionlist is only useable, if no login is executed. If you are logged in, this optionlist is grayed.

New menu entry Contents... in menu Help

The new menu entry opens the OfficeTalk reference documentation Reference.pdf. If Adobe Acrobat Reader is installed, the file extension .pdf is associated with it. You can define your own reader within the OfficeTalk environment PDFReader. That one is taken, if defined, first.

New options in dialog Selecting processes

The dialog, started with the menu View - Selecting processes... in the tasklist or group-tasklist has two new options. up to Today selects all processes with a startdate of today and in the past. from Today selects all processes with a startdate of today and in the future.

Outdated timestamp of program file OfficeTalk.exe

The timestamp of the program file was without respect to the creation date 08.13.2002. No the timestamp of the program file corresponds to the creation time of the version.

OfficeTalk is now available for evaluation as Single-User system

OfficeTalk is available now as a Single-User system (working in Stand-Alone mode) too. The Microsoft SQL- or Oracle-Server is not needed, the internal database OfficeTalk.bos is used instead. This variant is not useable for a multi user scenario ! But for evaluation its the fastest way to get information about OfficeTalk, because it contains many examples. Order this evaluation version or perform the following steps to get OfficeTalk into the Stand-Alone mode:

1. Start OfficeTalk

2. Close the logon dialog with the window close button

3. Set the selection list Database in the dialog Settings (Menu File - Settings...) to No

4. Close OfficeTalk.

Starting OfficeTalk again, it works in Stand-Alone mode. Read more about this mode in the documentation readme.doc. Installing the evaluation version performs theese steps automaticly.

Display of optional list fields in tasklist dialog corrected

The functionality of the menu entries Takeoverlist and Processtemplates, menu View, in the dialog ToDo-List for: <workers name> has been corrected. If a menu entry hided it's list field, the dialog was enlarged and the list field was unhided, the separator and the list field was positioned wrong.

Menu item Filter tasks... in dialog History for: <name of the process>

If the dialg Processhistory filtering is opened with the menu item, but the filter is not modified, the task is expanded or contracted anywhere.

If you have changed the filter values, the menu item is checked to indicate the changed filter.

Symbol for the process in the history dialog

As the symbol for an ended process the gray folder symbol is used in the dialog History for: <name of the process>. As the symbol for a running process the colored symbol (red, yellow, green) is used in the dialog History for: <name of the process>.

Red- and Yellow-Delay in Takeover- and Group-Tasklist

The delay settings in the dialog Settings where not used for the two named tasklist types. For this two types, the default values 24 Hour and 6 Hour where used.

Personalized action symbol in the history

In the dialog History for: <name of the process> you will see, instead of the default action symbol, the symbol choosen in action page of the step's template.

New menü item Delete histories... in main dialog

The menu Processes of the main dialog OfficeTalk contains the named menu item. With it, you can delete outdated histories. Histories are located in the process template from whitch the process has been created. A selection dialog is opened. In this dialog you can define the date range and selection criterias. Clicking on the OK button starts the deleting action. But you must be the owner of the process template to be able to delete a processes history. You are the owner of a process template, if the template is located in your worker's registry Processtemplates.

New context menu entry Delete histories... in dialog Tasklist and Start new process

The listfields with process templates in the named dialoges contains the context menu entry Delete histories.... With it, you can delete the outdated histories of the selected process. Histories are located in the process template from whitch the process has been created. A selection dialog is opened. In this dialog you can define the date range and selection criterias. Clicking on the OK button starts the deleting action. But you must be the owner of the process template to be able to delete a processes history. You are the owner of a process template, if the template is located in your worker's registry Processtemplates.

Additional display modes in the dialog Graph for process: <template name>

In the dialog Settings, opened with the menu View - Settings, you can choose two new display modes.

- Small symbols: Displays the steps with smaller rectangles. Some informations, as category name for the step and action, the workers first name and the minimal estimated execution time is supressed. If the process is opened the first time, this option is switched off.
- Steps with border: Displays the steps without its border . Decide whitch kind of display you like ! This option is switched on, if you open the process the first time.

New service for systemvariable stepscheduler

The systemvariable knows the new services stepResultNames and nextStepWorkerFor(<name of the stepresult>). With theese you can read inside the skript the names of the next possible results. Read further in the documentation OfficeTalk Script.

New services for systemvariable ScriptDialog

The systemvariable knows the new services cancel and accept. These services are useable in the services addActionButton and addAction as first argument and closes the dialog. cancel sets the dialog result to FALSE. accept sets the dialog result to TRUE.

Signaling received answers for eMail questions

The receiving of an answer for an eMail question is signaled with 3 pings.

Tabelle Action and ActionTemplate extended

The named tables are extended with the column symbolname. If you have an existing database, please contact the OfficeTalk-Support under 089-6006920, before installing this version.

Display of process templates in dialog Graph for process: <template name> corrected

Sorry, we make errors too. After changing the step name the step's block was adjusted right, but the connection lines (step results) where adjusted wrong. After inserting or removing a step the process graph was corrupted. After inserting or removing an action in a the step the step's block was adjusted right, but the connection lines (step results) where adjusted wrong.

The described problems occurred only if the scrollbar was moved before.

Adjusted display of process templates in dialog Graph for process: <template name>

The leftmost and rightmost steps of big process templates where only shown half. To show theese steps full, the window had to be maximized.

New service close for system variable ScriptDialog

The system variable ScriptDialog has the new service close. With this service you can close a dialog with an Action button. If you must first validate input data, you can use an Action button instead of an Accept button and close, if the input is valid.

Dialog ToDo-List for workers starting at: <workers name> as browser

If you switch the option ToDo-Lists as browser in the dialog Settings on, the Group-ToDo-List is displayed as a browser, similar to the file browser. Each worker is displayed with a gray folder. If you double click the folder, its contents, the current processes, is opened. The functionality is the same as in other Group-ToDo-List.

Messages display the full processname

The messages related to the process executing display the additional process name too. With this, you see the same full name in the message as in the tasklist.

Password input while login

The password input for the OfficeTalk login is not case sensitive anymore.

Dialog ToDo-List for: <workers name> as browser

If you switch the option ToDo-Lists as browser in the dialog Settings on, the ToDo-List is displayed as a browser, similar to the file browser. The functionality is the same as in other ToDo-List.

'Fly by Help' for the process symbols inside the tasklist

The folder symbol of a process in the dialog Tasklist for: <name> and Tasklist for workers from: <workers name> shows its details, if you touch it with the mouse. The details are the process name, the starttime and the estimated runtime. To see the processes as symbols, switch the option ToDo as text in the dialog Settings to off.

'Fly by Help' for the list fields inside the tasklist

The elements (list fields and buttons) inside the dialog Tasks for: <name> and Tasklist for workers from: <workers name> show a short description if you touch it with the mouse.

Windowtitle with full proces name

The title of the process related dialogs show the full process name (including the additional name).

Delegation a step increased

Now you can delegate a step or process only to a worker, who owns the right for executing or terminating the process. In the dialog Process <process name> delegating/modifying you can select only a worker how owns the right to adopt the process.

Changing the additional processname

In the dialog Process: <process name> delegating/modifying you can modify or define the additional processname if you have the privileg to start the process.

Drag and Drop in tasklists with symbols

Drag and drop in tasklists with symbols work in the same way as in tasklists with tables now.

Display process template graph with actions of steps

The dialog View - Settings, opened with the menu View - Settings in dialog Graph for process: <process name>, has the new option Show Actions. Setting this option, the process diagram shows inside the step its actions with its assigned image. First the startactions, second the useractions and last the termactions are listed. The symbols for the start-, term- and mandatory useractions contain an exclamation mark.

Symbol for action can be assigned

In the dialog Step: <name of the step> you can assign in the action tabulators an image for each action from the list Symbol:. The list contains the most useable symbols. An action without an assigned symbol is displayed with a default symbol.

New menu in dialog Organigram

The dialog Orgranigram for: <Name of the worker>, opened with the menu Work - Organigram from the main dialog, has the new menu View - Workercontents. This menu shows in the listfield all the contents of the workers. With +, and - you can navigate yourself in the workers structure .

Selectable display type in the different task lists

In the Tasklist and Group-Tasklist you can select a table based display (as now) or a symbol based display of the processes. If you choose a symbol based display:

Started processes are displayed with a closed folder. Started and begun processed are displayed with an opened folder. If the estimated processtime is in limit, the process is displayed with a green folder. If the estimated processtime is over the limit, the process is displayed with a yellow folder. If the estimated processtime is much over the limit, the process is displayed with a red folder. You select the displaytype in the dialog Settings, opened with the menu Settings, in the main dialog OfficeTalk . The symbols are labeled with:

1. Line: The name of the next step

2. Line: Your additional processname, if given.

The symbols of the group tasklist's are labeled with:

1. Line: The name of the next step

2. Line: Your additional processname, if given.

4. Line: The name of the current worker owner in brackets

If the process is waiting for the answer of an email or for the end of another process, its lines are displayed cursive.

New ScriptDialog service addAction()

With this service you can define an action, whitch is performed, when the contents of a field has changed. Read for further documentation OfficeTalk-Skript.

New ScriptDialog service addImage()

With this service and his variants you can position an image in the dialog. Read for further documentation OfficeTalk-Skript. The images format must be BMP, GIF, JPEG or XMB. Into the directory Vorlagen the image OfficeTalk.jpg is installed, and used by some dialogs from the example database.

Check for step steptime duration overlapping when delegating

If the next or first step of the process should be delegated to a worker, his absents are tested against the estimated processtime of the step. The processtime (date and time) is the start time and the end time (start time plus the sum of all action processtimes).

Modified installation structure

The directories OfficeTalk and Joops and subdirectories are not created anymore. Instead of the directory Messages is installed.

Dialog Selecting processes extended

The dialog, opened with menu View - Selecting processes from dialog Tasklist, was extended by the textfield Name. With this you can filter the processes by the additional name. The input may contain wildcards. ? is for a single character, * is for any combination of characters.

Additional name for a process

Starting a new process, the dialog Additional processname is opened. With this dialog you can name the process with a definition of your own. This name may be more accurate than the standard process name and is displayed in front of the standard process name.

Typing into Date and Time fields

Typing into Date and Time fields was to difficult and was modified. (Changing the month or day, typing in 4 digits year, changing the minutes, etc.)

Online-Completing of the Start statement in the scriptmethod dialogfield

If you want to type in a Start statement, but you have forgotten the process name, the online completion of OfficeTalk can help you. In the dialogfield of the source type in Start " followed by a space. A list dialog with all startable process names is opened. Select the wanted and accept with the OK-button. The Start statement is completed with the selected process.

Online-Completing of the Call statement in the scriptmethod dialogfield

If you want to type in a Call statement, but you have forgotten the script method name, the online completion of OfficeTalk can help you. In the dialogfield of the source type in Call followed by two spaces. A list dialog with all useable script method names is opened. Select the wanted and accept with the OK-button. The Call statement is completed with the selected script method. Substitude the argument templates (including '<' and '>') with the concrete arguments.

New Symbols for some worker types

The worker types Desk, Team and Department have new symbols. The new symbols are better, we beleave, than the old one.

New menuentry 'Create database user'

The contextmenu in dialog 'Organigram for: <name>', the menu 'Worker' in the dialog 'Organigram browser' and the menu 'Extra' in the workers dialog contains the new menu entry 'Create databaseuser'. This command creates for the 'Single-Sign-On' in the database an user corresponding to the used worker. If the Oracle database is used and the command is used for a company, only the role OFFICETALKUSER with the rights for the tables is created. For all other worker types the database user with same login and password is created. You can activate the 'Single-Sign-On' in the dialog 'Settings' opened with the menue 'File - Settings' in the main dialog 'OfficeTalk'. You must know the system administrator's login and password, to perform this job. Prerequisites for the 'Single-Sign-On' are:

· 1. On Oracle Create databaseuser for worker Company is done first

2. The worker is stored allready

3. The worker has a login and a password

4. The search path for the Oracle tool sqlplus.exe or the MS-SQL tool isqlw.exe is set

5. You know the login and password for the database system administrator. (For Oracle login is preset to System. For MS-SQL the login is preset to sa.)

Starting OfficeTalk the next time you can direct login with the workers login and password without first login to OfficeTalk. For the 'Single-Sign-On' you must set login and password of the worker and corresponding database user equal.

Automatic creating the OfficeTalk tables

If you start OfficeTalk the first time, the main user and all tables are created by OfficeTalk. This job must be done by the system administrator, because you must know his login and password. Prerequisites are:

1. The search path for the Oracle tool sqlplus.exe or the MS-SQL tool isqlw.exe is set

2. You know the login and password for the database system administrator. (For Oracle login is preset to System. For MS-SQL the login is preset to sa.)

You must not create by hand the main user and tables anymore. The database user is created with the login OfficeTalk and the password OfficeTalk. If you want to switch later to the 'Single-Sign-On' you must use for the database user and the worker the same login and password.

Method is compiled automaticly before executed in ScriptBrowser dialog

If you want to run or debug a modified, but not compiled method, you get a message. Answering 'Yes' compiles the method first.

Database role for Oracle example database

The example database contains now the role 'OFFICETALKUSER' with all rights needed for working with the OfficeTalk tables. Creating a database user in Oracle for the Single-Sign-On, you must only assign this role to the user to give this user all rights for all OfficeTalk tables.

New context menue 'Test with Debugger' in scipt browser

The listfield of the methods (right upper listfield) in the script browser has the new context menue 'Test with Debugger'. Choosing this menue for a selected method opens the debugger's dialog. You can execute the method under the control of the debugger (description see next).

Debugger for executing script methods

A debugger for executing script methods was integrated. If an error occures while executing a script method of performing a process, you get an error message. Answering 'Yes', you can proceed the method from the error line under the control of the debugger and its dialog is opened. With the Button 'Step' you execute the method step by step. With the Button 'Abort' you abort the method. With the Button 'Proceed' you end the debugger and proceed the method. In the upper right listfield you see the contents of the variables. Double clicking on the variable group (Global, Local or Temporary) you see the contents of the variables in this group. The contents display of the variables is actualized after executing each command. In the upper left listfield you see the method's hierarcy. In the textfield at the bottom you see the method's source. The command which is executed next, is displayed reverse.

Online-Completing of methodname in script

If you want to type in the methodname of a variable, but you have forgotten its name, the online completion of OfficeTalk can help you. In the dialogfield of the source type in the variable followed by a '.' and a space. A list dialog with all available methodnames is opened. Select the wanted and accept with the OK-button. The selected methodname is filled into the source after the points position. You must only complete the arguments, if any requested. Requested arguments are displayed with the string '<arg>'. Replace the arguments string including the '<' and '>' with the real arguments value. If you type in into the declaration line (Dim) after the 'As' the classname prefix 'Joops.' or 'Joops.OfficeTalk.' followed by a space, a dialog with all possibles classnames opens. After selecting a name and accepting with 'OK', the declartation is completed with the selected classname.

New compact library for Microsoft Word

For Microsoft Word you can use the compact library Microsoft Word Small.pcl instead of the full library Microsoft Word.pcl. This library is much smaller and loaded much faster. But it contains only restricted services for filling out and printing templates.

SmallCOM.Word.Application

documents

quit(<True/False>)

quit( , originalFormat: )

quit( , originalFormat: , routeDocument: )

visible

visible(<True/False>)

SmallCOM.Word.Documents

open(<filename>) and all variants

SmallCOM.Word.Document

bookmarks

printOut and all variants

close

save

saveAs(<filename>) and all variants

SmallCOM.Word.Bookmarks

item(<bookmarkname>)

SmallCOM.Word.Bookmark

range

SmallCOM.Word.Range

insertAfter(<a string>)

For further description see the library documentation.

Version 1.99

New menuentry 'Start Process' in dialog 'Todolist for: <Name>'

The menu 'Processes' of the dialog has the new entry 'Start Process' without the ending '...'. This entry contains for each category a submenu. Each submenue has menu entries for the startable processes in this category. Choosing such an entry starts the named process direct. The function of this menu entry is identical to the right listbox of the process templates.

New menu 'Group-Tasklist' in dialog 'Todolist for: <Name>'

The menu 'View' of the dialog has the new entry 'Group-Tasklist'. Selecting or deselecting the entry displays or hides the listbox with the active tasks in the visible workers on the bottom. If this list is hided, the listfield with the tasks of your own (upper listbox) is maximized. Per default the entry is selected. The selecting state is remembered in the environment. The string '0' says hide and the String '1' says display listbox.

On windows platforms this is written into the registry entry ‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\DoToListGroup'.

New menu 'Processtemplates' in dialog 'Todolist for: <Name>'

The menu 'View' of the dialog has the new entry 'Processtemplates'. Selecting or deselecting the entry displays or hides the listbox with the processtemplates on the right side. If the templates listbox is hided, the textfield for the description and history is enlarged to the dialog's height. Per default the entry is selected. The selecting state is remembered in the environment. The string '0' says hide and the String '1' says display listbox.

On windows platforms this is written into the registry entry ‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\ProcessTemplates'.

Toolbar in tabsheed 'Scripts' of the workers dialog

The textfield of the method now has a toolbar für the most used functions 'Format method', 'Compile method', 'Test method with debugger' and 'Cut', 'Copy', 'Paste'.

New menu in dialog 'Tasklist'

The dialog has the new menu 'View - Processtemplates'. Deselecting this menu disapears or the right side the listfiled processtemplates and the textfield for the description. The listfield for the tasks left side are enlarged up to the full dialog whith.

Creating scripts in actions from the dialog 'Step: <name>'

In the tabsheed User-, Start- and Termactions clicking the Button '>>' opens the script browser with the scripts of the current worker and the visible workers. If the current workers scripts are displayed, you can write new scripts and methods for this worker. So, when defining a process, you can write the needed scripts for the actions too. You must not do a extra jump to the 'Scripts' tabsheet in the worker dialog.

The password input in the logon dialog

For savety, the password textfield does not have a contextmenu (Cut, Copy, Paste, e.g.) anymore.

Startmethod in script without arguments

A startmethod in a script (checkbox 'Startmethod' in tabsheet 'Scripts' inside worker dialog) must not have arguments. When creating an method, OfficeTalk checks this rule. If you write a method with arguments and mark the 'Startmethod' checkbox, OfficeTalk unmarks the checkbox while accepting the method. For an action (listbox 'Script' in tabsheet 'Startactions', 'Useractions' and 'Endactions' inside worker dialog) only scripts with a start method or a method without arguments are presented for selection.

New menu 'Save and close'

The dialogs Organigram browser, Organigram and Worker contain the new menu entry 'Save and close'. This menu saves the changes and closes the dialog. The menu entry 'Save' performs only a save of the modifications, the dialog remains open.

Right 'View' for processes

To see a process in the dialog 'Tasklist for: <name>', the worker must have the right 'View process'. The right may also be inherited from an upper ordinated worker. The right list (startable processes) and the list at the bottom (started processes in visible workers) are affected by theese rules. The dialog 'Group tasklist' is also affected by theese rules.

New menu 'Ask and wait for answer...' in dialog 'Tasklist'

The context menu for processes in the upper list of the dialog 'Tasklist for: <workername>' contains now the entry 'Ask and wait for answer...'. The entry opens the dialog 'Question for process'. Within this dialog you can send any person an email. The functionality is the same as described in the next point (Process waits for answered aMail question). The input fields of the dialog:

- Worker: If the receiver is a worker, you can select his email adress from this list. This puts the email adress into the input field

'eMail:'.

- eMail: Type in the email adress of the receiver if he is not a known worker.
- Subject: The subject of the email.
- Question: The email text.

Process waits for answered eMail questions

In a script you can send an eMail as a question to one or more persons. The process is queued into a waitinglist and waits for the answers. This is shown with a cursive processname in the tasklist. In the dialog 'State for: <processname>' you can see the receivers of the question and the subject of the question. Within the history, if activated, the question is shown as a semaphore with the receiver and subject noted in the coment field. OfficeTalk reads in a given interval the answers and removes the corresponding processes from the waitinglist. To recognize an eMail as an answer, the subject must be the sames as of the original mail but with the prefix 'AW:' or 'RE:' and the original reveiver as the sender ! A recognized answer is removed from the inbox when it is taken over from the process. If a waiting process will be scheduled with the Button 'Schedule' or its context menu, you get a confirmation witch shows you the waiting for receivers. You must answer 'Yes' to proceed. With theese funktion in scripts you can send a question:

- process.ask("<email adress of receiver>", subject: "<Subject>", question: "<Text>")
- process.askWorker(<Worker>, subject: "<Subject>", question: "<Text>")

On Windows platforms (other platforms see description 'Environment') you can setup the reading answer options:

‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\Mail\Protocol'

'IMAP': The IMAP protokol is used (default)

'POP3': The POP3 protokol is used

‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\Mail\Host'

The hostname of the mailserver

‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\Mail\User'

Your username for the login to the mailserver

‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\Mail\ReadAnswersInterval'

The reading interval in seconds (default is 180)

‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\Mail\ReadAnswers'

'0': no reading of answers

'1': answers are readed in interval (default)

The dialog, opened with menu 'Settings...', contains on the bottom new entries for the permanent setting of this values.

Loginpath in dialog ‚Login and password' when logging into OfficeTalk

The input field ‚Login:' can now contain a loginpath name. The path contains the worker names down the organigram hirarchy. So, the login name of all workers in all hirarchies must not be different anymore. The login name as path describes the concrete logging in worker. Name parts must be separated with ‚/'or ‚\'. An example of the fictive comany ‚Master Consult' and its hirarchy:

Workertype Company/Term/Name Login Password

Company Master Consult OfficeTalk OfficeTalk

Department Aquisition aquire

- Desk Marta Heyns heyns 123qwe

Department Sales sales

· Desk John Heyns heyns 456asd

In this example ‚Marta Heyns' logs in with ‚heyns' and ‚123qwe'. But ‚John Heyns' must log in with ‚/master consult/sales/heyns' (or ‚sales/heyns') and ‚456asd' because ‚heyns' is found in ‚Marta Heyns' too, but the password would not match. Using a department, office or team as login part, you must use the adress entry ‚Term:'. Using the company as a name part (the first part with a leading ‚/'), you must use the adress entry ‚Company:'. The difference between a relativ and an absolute login path are:

Es wird zwischen relativen und absoluten Loginpfaden unterschieden:

- Absolute The login path starts with ‚/'. The first name part is the companys name followed by the worker names down the organigram hirarchy up to the wanted worker.
- Relative The login path starts not with ‚/'. The first name part can start anywhere in the organigram hirarchy, but must be unique.

For the database login the last part of a loginpath is used as the database username.

Attention: Some tables are modified

The tables ‚processtemplate', ‚process', ‚steptemplate' und ‚step' are extended. If you use an older Version, you must newly create theese tables first. Contact please the user support for this action !

Definition of login and password in worker dialog

Login und password must be defined now in a seperate dialog. Clicking the button ‚Login and Password' in the workers dialog opens an input dialog for typing in theese values. The password must be typed in a second time for recognizing a misspelled input.

Delaycolors in dialog ‚Tasklist'

The delay colors (red, yellow, green) for the processtime of the next step are not displayed with the colored time column anymore. A new first column shows the semaphore as a colored point.

Layout settings for dialog ‚Graph for process: <name>'

Each process has now its own layout setting for the graph diagram (margins, spacings, etc.). So, each process can be displayed with an individual layout. Up to now, for all processes was use the same layout setting. New processes are starting with the layout from the environment. On Windows platforms the entries are:

‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\ProcessLayout\ColumnSpacing'

· The column spacing in pixel as text.

‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\ProcessLayout\RowSpacing'

· The row spacing in pixel as text.

‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\ProcessLayout\Margin'

· The margin in pixel as text.

‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\ProcessLayout\Orientation'

· The diagram's orientation (‚vertical' or ‚horizontal')

‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\ProcessLayout\LabelOrientation'

· The adjustment of the labels (‚vertical' or ‚horizontal')

On all other platforms theese entries are located in the environment file ‚OfficeTalk.ini' beginning with the name part ‚ProcessLayout\'.

Inputfields of primary keys not changeable

The fields, used for the primary key in the database, are not changeable after storing the element. This depends on technical reasons. Not changeable are:

- Process: Name
- Right: Name
- Substitute: all values
- Action: Name

If a field must be changed, delete the hole entry and store is new.

Spinbuttons for time without seconds

The input fields do not show and handle the seconds anymore.

Option ‚Current Worker' in dialog ‚'Step - Options'

The tabsheed uses now the named option. If you select this option, the list box for the worker is disabled. After scheduling the preceeding step, the current worker is used to process this step.

Sequence order of toolbar buttons

The toolbar buttons ‚Open tasklist' and ‚Start process' where placed leftside.

Initial open size of main window

The main window is only used for the toolbar and the menues, so its initial size is made smaller.

Displaying backward links in dialog ‚Graph for process: <name>'

Backward links (blue arrows) are drawn beside their forward link for better visibility.

Abort when activating an entry in the dialog ‚Rights hirarchy'

When an entry was activated (double click) in the dialog, the system was terminated with an error message.

Displaying of available process names in dialog ‚Rights'

In the dialog the names of all existing processes where shown. Now the names of only the visible processes (see visibility rules) are shown.

New button for delaying a step in dialog ‚Scheduling step <name>'

Pressing the button ‚Delay' delays, if the rules allowes this action, the step for later scheduling like the window close button and closes the dialog.

New filename for OE.exe

‚OE.exe' doe not longer exist. The replacing file is ‚OfficeTalk.exe'. The link-properties of a desktop icon are changed too.

Display of a step in dialog ‚ Graph for process: <name>'

For a steps the minimal und maximal calculated process time is displayed. The minimal process time contains only the mandatory actions of the step. The maximal process time contains all actions.

New menu ‚Statistics' in dialog ‚Graph for process: <name>'

The menu contains the entry ‚Processtimes/Path '. The entry contains a submenu entry for each process path with the calculated minimal and maximal process time. Selecting an entry displays the corresponding path (the blue lines) with red lines. Selecting the menu entry ‚do not display path' draws the red lines blue again. The menu entries for the pathes are sorted from lower to higher maximal process time.

New menu ‚ Settings...' in main menu ‚File'

The new menu ‚Settings...' opens a dialog for defining the environment settings. So, the settings must not be done manualy anymore by a text editor or the program regedit.exe on Windows platforms.

The contents of the dialog:

- Using level (a ‚Yes/No' select list): Defines the using level.
- Logging (a ‚Yes/No' select list): Process activities are logged into the file ‚protocol.txt'.
- Database (a ‚Yes/No' select list): ‚No' uses no database. The stored artefacts are deleted on terminating OfficeTalk.
- DB-Login (a ‚Yes/No' select list): ‚No' uses a Single-Sign-On for logging in.
- autom. login (a ‚Yes/No' select list): ‚Yes' starts the login process automaticly after starting OfficeTalk.
- Process history (a ‚Yes/No' select list): ‚Yes' creates the history for process activities.
- autom. ToDo-List (a ‚Yes/No' select list): ‚Yes ' opens the ToDo-list after starting OfficeTalk automaticly.
- last logins: Number of remembered login names in the login name field of the login dialog.
- Schedule reached: Timespan in minutes for increasing the schedule time of a step.
- Red delay: Timespan in hours for warning about a delayed process scheduling.
- Yellow delay: Timespan in hours for warning about a possible delayed process scheduling.

Security message when deleting an entry

Deleting an entry with the context menu or a ‚Remove' button, a security message appers. After answering ‚Yes', the deleting process is continued. If the using level is ‚Expert' or higher, this security messages is skipped.

Displaying a step reaching from more results in dialog ‚Steptemplate for <name>'

If a step is reached from more than one result (incoming blue arrow), it was displayed for each reaching result. To show, that the same step is used by more results, it is displayed only once but with more incoming results (incoming blue arrows).

Toolbar displaying on Windows-2000 platform

On Windows-2000 platform the toolbar lines where not hided when the toolbar itself was hided.

Environment setting for the type of user

In the registry key ‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\UsingLevel' you can define the type of using OfficeTalk.

- 'Expert' oder ‚E' defines an expert. Only most important messages and questions are displayed.
- ‚Normal' oder ‚N' defines a normal user. The minor important messages and questions are displayed too.
- ‚Beginner', ‚Begin' oder ‚B' defines a learning user. All questions and messages are displayed, also the informative messages.

Method argument variables in script debugger

The script debugger shows now the arguments of a method in the ‚Arguments' group too.

Automatic start of the next step

If you close the dialog ‚Scheduling step <name>' with the button ‚Finish', the next step, if it is in time, is started. If the next step contains only mandatory user actions, the step is scheduled without opening the dialog ‚Scheduling step <name>'. The registry key ‚scheduleTimeReached' is taken to calculate the schedule time too.

Display the assigned script of an action

In the tabbed sheed ‚xxx-action' of the dialog ‚Step <name>' the button ‚>>' opened the wrong script, if inside all visible workers a script with the same name existed more times.

Support for ActiveX Controls

On a scipt's dialog, you can use now an ActiveX Control too. As a prerequisite, the corresponding library must have been loaded, the ActiveX Control can be placed on the ScriptDialog. For details read the documentation ‚OfficeTalk Script' chapter ‚Systemvariable ScriptDialog'.

No parallel process scheduling

While scheduling a process, the menu items for waiting scheduling, or adopting a process are not allowed. Selecting such a menu item opens a message box and tops, after clicking ‚OK', the dialog ‚Scheduling step <name>'.

Adapt a process with ‚drag/drop'

If you have the permissions for adopting a process from the taskpool (bottom list in dialog ‚Tasklist'), you can move him by selecting the process and dragging it to the upper list (the tasks) with the left mouse button.

Putting a process into wait state

A process can be put into waiting state within the dialog ‚Tasklist'. Move the process whitch will wait with the righ mouse button and pressed ‚Alt'-key over the process waiting for finishing. The dialog ‚<name> will wait' is opened. You can comment the waiting state. The process is really set into waiting state if you close the dialog with the ‚OK'-button. If you abort the dialog with the window close button, the process is not set into waiting state.

Additional question to terminate a process

If you want to terminate an active process in the dialog ‚Tasklist' (button ‚Terminate' or context menu ‚Terminate'), you must answer ‚Yes' to the security question to terminate the process really.

Important modifications in table structure

The table ‚protocol' is not needed anymore. Within this change the table ‚process' is extended by the column ‚lastprocessed'. This modification is incompatible to the previous version. You must delete all tables before starting OfficeTalk. OfficeTalk generates the tables new while first started. If you will loose important data, contact the support to recover the data first.

Changed menu name in dialog ‚Tasklist'

The context menue ‚Protocol...' is named now ‚History...' The semantic is the same.

Optional history for ended processes

The context menu of a process template (template list fields in dialog ‚Tasklist', ‚Starting process' and the tabulator ‚Processtemplates' in the workers dialog) has the new menue item ‚History...'. This item opens the dialog ‚Process history for <name>'. The dialog shows in the left list the history of all ended processes as a tree. A process line is displayed only with the start- and end-time because the dialog shows all processes with the same name. This name is displaed in the dialog's title. At the end of a step line its result is displayed in brackets. By expanding or contracting (double clicking the entry or clicking the preceeding ‚+'-sign) the structure, you can inspect the history parts of a process. In the right dialog you see the history details of the left selected element. The menue item ‚ Expand/contract all processes' expands or contracts the performed steps of all processes. Aborted processes are displayed in the left list in red color. Active processes are shown not here but with the context menue ‚History...' in the dialog ‚Tasklist' only ! In the registry key ‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\ProcessHistory' you can activate the history for closed processes with the string ‚1', ‚Yes', or ‚On'.

Automatic Datebase Update

Wher the database ‚OfficeTalk' is empty or some tables are missing, they are generated at start time.

In the MSSQL version you need the following script files in the directory ‚Library':

OfficeTalkForMSSQL.sql Skriptfile for the database creation

SerialNumbersForODBC.sql Skriptfile for the database creation

The Oracle Version of OfficeTalk does not need these files for the update of the database.

Right mouse button in dialog ‚Organigram Browser'

If a worker is clicked with the right mouse button (context menue) and another worker is allready selected and modified, the message ‚Do you want the changes...' appears. Answering ‚Save' or ‚Abandom' saves or abandoms the changes, the clicked worker is selected and his context menue appears. Answering ‚Abort' does not select the clicked worker. The selected worker remains selected and the appearing context menue references him.

Right mouse button in dialog 'Graph for process: <name>'

Selecting a process element with the right mouse button deselects all other possible selected process elements. The appearing context menu is for the ‚right button clicked' element.

New icons for Login, Exit, Inspect and Browser

In the toolbar of the main dialog ‚OfficeTalk' and the context menue of the list dialogs, the named icons are changed.

Changed functionality for menu ‚View' in dialog ‚Organigram (-Browser)'

The menues ‚All levels' und ‚Next level' work now like a Flip/Flop.

New context menu ‚Current state...' for the process list in the dialog ‚Tasks(-group)'

The menu opens for the selected process a dialog whitch shows the runtime times for the next step and the overall runtime times of the process. On the bottom of the dialog, the processes for their termination he is waiting, are shown. The times are estimated because the step performing is variable. Steps whitch should be performed on a weekday or monthday are not respected, because their time span is relative and depends on the performing day of the preceeded step. To display the ‚Runtime' of a process the history must be activated for active and ended processes. To do this, in a Windows environment the registry entry ‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\ProcessHistory' must exist and contain the string ‚1', ‚Yes', or ‚On'.

New context menu ‚Delegate...' for the process list in the dialog ‚Tasks(-group)'

The menu delegates the selected process to a next worker. A dialog with the visible workers having the scheduling right for this process and the visible passive workers (e.g. Department, Office, ...) is opened. Selecting the checkbox ‚Only substitutes' shows only the substitutes of the next worker for this process. Choosing a worker and pressing the ‚Delegate' button delegates the process to the selected worker. Only the workers having the scheduling right for the process are shown. To delegate you must have the right ‚Change next worker' (see tabulator ‚Rights' in the workers dialog) for the processes with the same name. Delegating a process to a passive worker (e.g. Department, Office, ...) makes it available for all other workers, seeing this passive worker. You can also change the startdate and priority of the next step, if you have the right ‚Change step' for equal named processes assigned (see tabulator ‚Rights' in the workers dialog). For a delegation and if the process history is activated, you can type in a comment into the text field below. Inside the delegation entry of the process history you will see this comment later.

Yes/No settings in boolean environment variables

Instead of ‚1' you can write in environment variables ‚Yes', ‚On' or ‚True' too. Instead of ‚0' you can write in environment variables ‚No', ‚Not', ‚Off' or ‚False' too. Upper- or lowercase writing is not relevant.

Linesize in list- and combobox dialogs for Linux

The size of lines in list dialogs was corrected for the Linux version. The leading icons was cutted.

Only the first ‚System' process was scheduled

If more than one ‚System' processes existed, only the first of them was scheduled.

Automatic scheduling of ‚System' - ‚Start' process

When first time logging into OfficeTalk, the process named ‚System' - ‚Start' is started. The process must be visible and the neccesary rights (Start, ...) must exist. You can define such a process for performing general things for OfficeTalk (e.g. loading libraries).

New menue for scriptlist in dialog ‚Script Browser'

The script list in the dialog ‚Script Browser' contains the new context menue (right mouse button) ‚Usings...'. This menue opens the dialog ‚Usings' for the selected script. It shows all the actions using this script. Double clicking an entry opens the worker, containing the ‚process container', the process template page, the step and its action page using this script.

New menue ‚View' in the main dialog ‚OfficeTalk'

The main dialog has been extended with the menu ‚View'. With its entries (‚Hide toolbox' and ‚Show toolbox') you can make the toolbox invisible or visible. This current state is recorded in the registry entry ‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\Toolbox'. The string ‚0' is used for invisibility. The string ‚1' is used for visibility. If the registry entry is missing, the toolbox is shown.

Parameter handling on Unix systems

On Unix Systems the OfficeTalk parameters are stored into the file ‚OfficeTalk.ini'. The environment variable ‚OFFICETALKHOME' defines its directory. If the variable is not set, the variable ‚HOME' is used. When this variable does not exist too, the file is stored into the directory of the file ‚OfficeTalk.im'. The file is structured like ‚ini' files in Windows. General parameters are stored in the section ‚[OfficeTalk]'. The key value pair is formed from registry entry without all up to ‚OfficeTalk' and the last part. The parts from ‚OfficeTalk' up to the last part are used for the key. An example: The registry entry ‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\ProcessList\FilterDate\' is used in the ‚OfficeTalk.ini' file for:

Chapter: ‚[ProcessList]'

Key-Value: ‚FilterDate=<nnn>' (<nnn> stands for the concrete value)

Parameters in Unix Systems

In Unix systems the OfficeTalk Parameters are stored in the file ‚OfficeTalk.ini'. The environment variable ‚OFFICETALKHOME' defines the directory of the file. If the variable does not exist, the variable ‚HOME' is used. If this variable is missing too, the directory of the file ‚OfficeTalk.im' is used.

Changed menu entry in main dialog ‚OfficeTalk'

The menue entry ‚Work -- Inspect worker...' contains now the icon associated to the logged in worker. If no worker is logged in, a question mark is displayed.

No toolbar in dialog ‚Organigram' for ‚Desk' and ‚Machine'

When the logged in worker is of type ‚Desk' or ‚Machine', the toolbar in the dialog ‚Organigram' is hided, because the actions, initiated by the toolbar, are all restricted in theese both cases. The menue items for the toolbar are all disabled too.

New toolbar button

The new toolbar button ‚Open/inspect processlist... ' (the opened folder, the right most) opens the process list when an active worker is logged in, otherwise the group process list is opened.

Changed symbol for process

The symbol for a process has minimal changed.

Abort when using some toolbar buttons without login

Some toolbar buttons aborted OfficeTalk, when used without being logged in.

Additional message when closing OfficeTalk

When using menue ‚Close' or when closing the main dialog ‚OfficeTalk' an additional message 'Do you really want to close OfficeTalk' appears. Answering ‚Yes', and if no other facts contratict, OfficeTalk ends.

Pending wait state for a process

The wate state of a process was not fully removed if the process to be wait for was removed. The message 'The process is waiting for finishing...' appeared when scheduling or terminating this process.

New buttons in main window toolbar

The toolbar in main window ‚OfficeTalk' contains now a button for finishing OfficeTalk (die Door) and a button to start a new process (the folder symbol)

Message when a modified worker will be leaved in dialog ‚Organigram browser'

When a selected and modified worker should be leaved by selecting another worker, the message ‚Do you want the changes...' appears. Responding ‚Save' stores the changes, and the next worker is selected. Responding ‚Abandom' abandoms the changes and the next worker is selected. Responding ‚Abort' does not store the changes and the selection remains untouched. This can happen only if the ‚Oracle'-database is used.

Modified text field must not be leaved anymore to accept changes

Text fields had to be leaved to accept the changes. To enable a ‚Save' menu, the modified text field had to be leaved first too. Now, modifying text field contents does accept too and an existing ‚Save' menu is enabled automaticly.

Increased performance for selecting elements in list dialogs

Selecting elements in list dialogs with mouse is performed faster.

Display of a single history was not synchron with the history list

In dialog ‚History for <name>' the display of a single history was not synchron with the selected history when the expanded structure of a selected history was contracted. When contracted, another entry of the list was selected, but the display right side showed not the same history.

Worker leaved locked for subsequent processing

When in dialog ‚Organigram browser' the structure was changed by ‚Copy/Paste' a worker, the original worker leaved locked. If the original was subsequent selected in the list, you got the message ‚The worker <name> is in use. He is opened read only'.

Message ‚... Save Abandom Abort ' in dialog ‚Organigram browser'

When the structure of an organigram was modified by deleting or adding a worker, second another worker inside the structure was selected and thirth the dialog was closed, the named warn message appeared but the modifications where allready stored into the database. This happened only in combination with the database ‚Oracle'.

Message when dialog ‚Starting a new process' was closed with window close button

When the dialog was closed with the window close button, and second the OfficeTalk main window was closed, the message ‚There are uncommited transactions...'. appeared.

Processdescription in dialogs ‚Starting new process' and ‚Tasklist'

These both dialogs contain below the process template list a read only text field. Selecting a process template, you can see it's description in this text field. The list and the text field are splitter windows. By moving the line between, you can change the hight of both elements.

No warn message when aborting the ‚Organigram browser' dialog with window close button

When the dialog ‚Organigram browser' is cancelled but not saved, no warn message ‚...Save Abandom Abort' appears after changing the organigram or a worker inside. The modifications were not stored into the database. An important issue:

When OfficeTalk is working with the database ‚Oracle', changing the worker's selection inside the organigram list left side performs a commit. So, changes of the organigram or of a worker are stored into the database. Because of this automatism, the menu entry ‚Save' is grayed after selecting another worker inside the organigram list left side.

Skript debugger performance and visualizing inside debugger dialog optimized

The script debugger performance was optimized and the evaluation of variables is visualized inside the debugger dialog by selecting the variable when evaluating.

Message when dialog ‚Tasklist' was closed with window close button

When the dialog ‚Tasklist' was closed with the window close button, and second the OfficeTalk main window was closed, the message ‚There are uncommited transactions...'. appeared. Answering ‚Yes' or ‚No' was not relevant.

Opening automaticly the task list after login

After an active worker (desk or machine) has logged in successfully, OfficeTalk opens the task list and minimizes the main window. On Windows versions this automatic can be supressed with the string ‚0' in the registry entry ‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\ AutoToDo'.

Automatic login when starting OfficeTalk

OfficeTalk opens at start time the login dialog for the login procedure. On Windows versions this automatic can be supressed with the string ‚0' in the registry entry ‚HKEY_LOCAL_MACHINE\Software\JOOPS GmbH\OfficeTalk\AutoLogin'.

Missing ‚Fly by Help' for organigram browser icon in main dialog

The ‚Fly by Help' (touching the icon with the mouse) for the organigram browser icon in the toolbar of the main dialog was missing.

Contract worker structure or deselect the worker in dialog ‚Script Browser'

Contracting the structure of the selected worker has selected two workers simultaneosly. Now, nothing is selected in this situation and the dialog on the right side shows the question mark. It shows the question mark too, if you deselect the selected worker on the left side.

Putting a process into wait state

In a script the current process can be put to wait for termination of other started processes. you can do this with method ‚waitFor()' of the systemvariable ‚process'. Details read in ‚Scripting.doc', chapter ‚'Systemvariable process'. Waiting processes are displayed with italic process name in the task list. If you want to schedule or terminate such a waiting process, you get a message, listing all the processes for whitch the scheduled process is waiting for. If you answer ‚Yes', you are able to proceed.

For this functionality the return type of the function ‚Start' was changed from Boolean to Process. If you use the return value in your scripts, you must adapt theese scripts.

For this functionality the database table ‚waiting' was added. Starting this version the first time, the table is added automaticly.

Version 1.98

Modifying the organigram structure inside dialog ‚Organigram for: <workername>'

If a worker is moved with the mouse to another parent inside the dialog ‚Organigramm for <workername>', this change was not made persistent at some conditions. So. after OfficeTalk was restarted, these modifications where lost. Some other effects would apear too after structure modification.

Selecting menue ‚New' - ‚Machine' in dialog ‚Organigramm for <workername>' terminated OfficeTalk

Selecting the named menue terminated OfficeTalk with an error message.

JOOPS Informationstechnik GmbH

Orlando-di-Lasso Str. 2
85640 Putzbrunn
Germany

+49 89 6006920
http://www.joops.com
OfficeTalk@joops.com