We maken BizzStream steeds beter om uw bedrijfsprocessen te kunnen automatiseren. Omdat we u een stem willen geven in de ontwikkeling van BizzStream kunt u hier Feature request plaatsten. Iedere gebruiker kan stemmen op een feature, de feature met de meeste stemmen zal op de roadmap van BizzStream komen.


Sort in reference fields

Peter van Meijel 1 year ago • updated 11 months ago 11

As an administrator, I want to sort reference fields so that I see the most relevant options in an order that makes sense to me.

(WHY) In many cases, master data elements such as resources have a unique number. This number contains information about the resource. When working with reference fields that refer to such master data elements, it is important that the documents that can be chosen by a user are sorted in a way that makes sense to them.

(WHO) Administrator

(WHAT) Enable the administrator to set the order of the references

Current Situation

Currently, when a user wants to select a document in a reference field, the documents are not sorted in any order.

For instance, when the user selects a cost type, the cost types are not sorted on number (see screenshot 1). Typically, cost types that start with a 1 represent machines, and cost types that start with an 8 represent subcontracting. That's why it is confusing for users to see the documents not sorted.

Acceptance Criterea

Setting the sort field

In a document definition page, the administrator can set the field on whcih the documents can be sorted:

  1. Open a reference field
  2. In the Sort Field field, select the field on which the documents should be sorted:
    1. The field is a combobox that contains fields of the target document definition.
    2. Only the fields of the type text, e-mail, number, date, time, picklist, and autocomplete can be selected.
  3. The Sort Order field determines how the documents should be sorted:
    1. This is a combobox that contains the values Ascending and Descendin
  4. Click on Save to remember the update
  5. Click on Save to update the document definition

Using the sort field

When a user opens the reference field (both 1-1 and 1-N references), the suggestions should be displayed base on the sort order and the sort field.

For instance, if the field Gekoppelde Kostensoorten is sorted ascending on code, the order is:

  • 12120 - Vrachtauto met kraan
  • 26331 - Coniferen
  • 83900 - Onderaanneming diversen rioolwerk

UI/UX Design

Screenshot 1: The documents presented in an unsorted way

Mockup 1: The Sort Field and Sort Order fields in the definition of a reference field

Sprint 29 March 2017 - 25 April 2017

Get Geolocation in App

Peter van Meijel 1 year ago • updated 11 months ago 5

As a user, I want to set a geolocation field on my mobile phone so that I don't have to use the desktop interface.

(WHY) Currently it is not possible to set geolocation fields on a mobile phone. This should be possible

(WHO) A user

(WHAT) Set location field on mobile phone

Current Situation

Currently it is possible to set a geolocation field on the desktop. When the user clicks on the magnifier button (see screenshot 1), the current location of the user is put in the field.

On mobile, the user can also click on an icon, but the phone displays the error "There is no geolocation data available".

Acceptance Criterea

When the user clicks on the retrieve geolocation button in the mobile interface, the geolocation should be retrieved. This geolocation may be based on Global Positioning System (GPS) and location inferred from network signals such as IP address, RFID, WiFi and Bluetooth MAC addresses, and GSM/CDMA cell IDs.

UI/UX Design

Screenshot 1: The magnifier glass button in of a geolocation field

Screenshot 2: The error text that a user sees when retrieving the geolocation on a mobile phone.

Sprint 29 March 2017 - 25 April 2017

Make MomentJS available in script environment

Peter van Meijel 1 year ago • updated 1 year ago 7

As an administrator, I would like to use the MomentJS functions in my scripts so that it is easier for me to manipulate dates in scripts.

(WHY) Documents in the construction industry contain often dates and times. BizzStream scrips are regularly used to make calculations using this information. However, date/time manipulation in JavaScript can be quite complex. We want to make this easier.

(WHO) Administrators.

(WHAT) Give access to the MomentJS library in scripts.

Current Situation

Administrators do not have access to any date/time manipulation library in the script environment. They could create a separate script with some date/time manipulation methods, and include this script in another script. However, this is not very practical.

Acceptance Criterea

The administrator has access to the MomentJS functions in a script. The default locale is US English. If the administrator would like to use another locale, he can set this by calling:


Two locales should be available: US English (as mentioned, this is the default) and Dutch.

The administrator can execute Moment functions by calling:

moment().format('MMMM Do YYYY, h:mm:ss a'); // January 2nd 2017, 11:43:26 AM
Sprint 18 January 2016 - 31 January 2017

Show notifications when finishing synchronous REST call in user action

Peter van Meijel 1 year ago • updated 1 year ago 5

As a user, I want to see the response of a synchronous REST call in a user action so that I can act upon this response.

(WHY) Currently, synchronous REST calls in a user action cannot give direct feedback to the user. However, there are use cases in which it is desirable to give such feedback. For instance, if a user wants to send an invoice to an ERP system, the ERP system may want to inform the user why it couldn't process the invoice.

(WHO) User

(WHAT) Show a notification when the REST call contains information.

Current Situation

Responses from REST calls (whether synchronous or not) are stored into the logs, but not directly displayed as notification to the user.

Acceptance Criterea

Imagine we have a user action with a synchronous REST call* (see Screenshot 1).

A notification is displayed for each of the following elements that is present in the response of the REST call:

Respons Element Field Name Displayed as
Header errorText Error
Header successText Success
Header infoText Info
Body _errorText Error
Body _successText Success
Body _infoText Info


Imagine that the REST call responds with the following header

     errorText: "Oops, something went wrong"

and this footer

    _errorText: "We could not process this stuff.",
    _infoText: "But the call was processed."

Then BizzStream displays 3 notifications:

  • Error: "Oops, something went wrong."
  • Error: "We could not process this stuff."
  • Info: "But the call was processed."

UI/UX Design

Screenshot 1: The User Action of the example mentioned in the Acceptance Criteria. The REST call is synchronous because the "Save Response" checkbox is selected. See http://support.bizzstream.com/topics/369-workflow-action-rest-calls/ for more information.

Sprint 21 December 2016 - 18 January 2017
Staged for Release

Sort list of scripts in alphabetical order

Peter van Meijel 1 year ago • updated by Bram Nieuwenhuize 1 year ago 4

As a administrator, I want to see the list of scripts in the setup section in alphabetical order so that it is easier to find a script.

Current Situation

Currently, the list of scripts in the setup section is not sorted.

Acceptance Criterea

When the administrator goes to Setup > Scripts, the list of scripts is presented in alphabetical order based on the name. Administrators can override this default sorting by clicking on a column header.


Edit document line text fields in popup on desktop

Peter van Meijel 1 year ago • updated 1 year ago 5

As a administrator, I want to edit document line text fields on desktop in a separate popup so that the width of the column can be reduced.

Setting the layout

To do so, the administrator has to edit the layout first. In the layout, text fields in lines have an additional option, namely the Edit in Popup on Desktop checkbox. (Text fields that are not part of a line don't have this property.)

Editing the document

When the user now opens the document, he sees paperclip icon when the text field has a value. Otherwise the cell is empty:

When the user clicks on the cell, a button appears (just as witch attachment fields):

By clicking on the button, a popup opens. This popup let the user edit the text:

Sprint 26 October 2016 - 22 November 2016

Let the REST API for documents recognize lines by external ID

Peter van Meijel 2 years ago • updated 1 year ago 5

As a user, I want that the REST API recognizes lines by external ID so that lines are not removed if an external system does not know the BizzStream ID of lines.

Currently, the BizzStream REST API for documents removes lines when an empty query is passed. In the case of Maxedy Pizza, we have a document that contains orderLines. When an order is updated and we pass an empty array:

orderLines: [ ]

all the orderLines are removed.

When we pass an array with line IDs, only the orderLines that have an _id are retained. So, when the following document is passed, one existing line is retained and one new line is inserted:

        "quantity": 5,
        "_id": "1234567890"
        "quantity": 10

In some cases the external system does not know the _id field. In that case, it is impossible to update a document and to retained all lines at the same time.

This can be solved if we would let BizzStream look at the _id field first. If that field is not available, it looks at the externalId field. In that case, it is possible to update a document via the REST call with the following orderLines array

        "quantity": 5,
        "externalId": "1234567890"
        "quantity": 10,

and retain both lines.

See for a concrete case where this happens the topic that has been merged.

Sprint 28 September 2016 - 25 October 2016

Export Documents (.xls, .xlsx, .csv)

Peter van Meijel 2 years ago • updated by Bram Nieuwenhuize 2 years ago 7

As a user, I want to export the documents in my overview to an Excel readable format so that I can analyse the data outside BizzStream.

To enable users to do this, the administrator does:

  1. Add a bulk action (see http://support.bizzstream.com/topics/537-/)
  2. Add the Export Documents rule to the bulk action
  3. Save the document definition

Now, the user can export by:

  1. Clicking on the user action button
  2. Choosing the export options.

Supported file formats

This feature supports currently only CSV and XLSX exports. This implies that only normal fields (in contrast with fields that are part of lines) can be exported.

Adding the bulk action

When the administrator added a bulk action, he can click on Insert and than select Export Documents. The settings for this rule now appear:

There is one checkbox. By selecting this checkbox, the administrator gives the user the possibility to export fields that are not included in the layout (but to which the user has permission).

Interface for the user

In the overview, the bulk action button is displayed.

When the user clicks on this button, the following dialog is opened:

The field Export Fields that are not in the Layout is only visible if the field Allow Export of Fields that are not Part of the Layout are set to true.

When the user clicks on Ok, the export starts and a notification is shown: "The export started and may take a while to complete...".

On Mobile

The export functionality is not available on mobile. If the user clicks on a Bulk Action button that contains a Export rule, a notification appears: "Export of Documents is not Supported on Mobile".

How the bulk export works

The server generates the export as follows:

  1. Query the documents:
    1. That pass the filter criteria of the overview
    2. Using the sort settings of the overview
    3. (If the user action has an incoming status arrow): That have the status required by workflow.
  2. For each document, check whether the user has read permissions.
  3. If the user has read permissions, show for each of the columns in the layout the value of the document if the user has view permissions on the field.
  4. If the user also selected to "Export Fields that are not in the Layout", add columns for each of the fields that is not part of the layout. For each document, fill these columns if the user has access to the associated field.

The bulk export works asynchronously. When the export is completed, the file is sent to the webbrowser.

Sprint June 6 2016 - July 1 2016

Default values

Bram Nieuwenhuize 2 years ago • updated 2 years ago 10

Being an administrator, it should be possible to define conditions on fields of a Document Definition in order to accomplish (default) value calculation of a document instance.


The following situations have been identified:

  • Absolute values that should be set when a document is being created (from now on mentioned as 'Initial Value') (i.e. 2015-01-01 in case of a date field)
  • Relative values that will be computed when the document instance is being created (from now on mentioned as 'Initial Placeholder') (i.e. {!system.today!} which will evaluate to the date the instance is being created)
  • Relative values that will be computed when a dependant* value has been changed (from now on mentioned as 'Placeholder') (i.e. {!source.company{"fieldName": "defaultStartTime"}!} which will evaluate to the value of the defaultStartTime field of the selected company instance)

* dependant values can be reference fields but also fields like {!system.today!}. Setting the latter kind of value may imply recalculation when opening the document.


To determine the actual value of a field the following order will be maintained:

  1. Placeholder
  2. Initial Placeholder (only in case of creating a new document / line)
  3. Initial Value (only if the Initial Placeholder evaluation did not resolve to a value


  • The field permissions will be honoured to decide if a field can be set / updated. By default, only visible fields (in the current layout) will be evaluated, but it will be possible to override this functionality, so invisible field can be set / altered as well.
  • This functionality has no impact on the current REST implementation


This functionality won't have any impact on the REST interface.

Supported field types

  • Text
  • Email
  • Number
  • Picklist
  • Date
  • Time
  • Checkbox
  • Reference

Out of scope

  • This feature does not include functionality that enables setting values through user- or scheduled actions.

Sprint April 11 2016 - May 6 2016

(Target) Document based on source document, data

Edward Jousma 2 years ago • updated 2 years ago 2

In the case of a purchase order in BizzStream would you like to create one of more receive documents. These receives you want to create on the basis of data from a source document. In this case the purchase order.

At this moment you can create through script target documents but now you want to create a document based on a source document. Either with all data or just a portion. This option, function, button should be available in the feature.