We are enriching BizzStream with more and more functionality. Because we want you to participate in building the best possible platform, we give you the opportunity to add feature requests and vote for the best ones. We will prioritize the features and plan them on our roadmap.

+3

Logo visable in BizzStream App

Onno de Boer 3 weeks ago 0

Making the header of the BizzStream App flexible like the desktop version


Current layout of the BizzStream App

Would be nice tot have






+3

Permission editor: keep the header with statusses visible when scrolling down

Onno de Haan 1 month ago 0

Permission editor: keep the header with statusses visible when scrolling down


Now the header with all the status-codes is scrolled out of screen. This makes setting permission very very hard when working on large scale processess.


See the clip below that shows the difficulty with the current implementation of the editor


OosterhofHolman - difficult to set the right permissions.mp4

+3

Use attachment field in outgoing REST-call

Onno de Haan 3 months ago • updated by anonymous 1 month ago 1

At the moment Its not possible to send out a rest-call that contains the content of

An attachment field.


If the platform Could be extended to send out the content of attachment, we Could send attachment off for storage in external systems like Corsa and sharepoint. Or Metacom DMS.


We would need support in scripted and modelled REST-calls.

+3

Add Print Document rule

Peter van Meijel 3 months ago • updated by pvdlageweg 2 months ago 1

As a user, I would like to print directly from my document.


[WHY] To be able to print directly from a document

[WHO] Admin

[WHAT] Add a Print rule to a user action in the workflow. This rule makes an API call to a Google Cloud Print with a template that has been rendered.


Current Situation

Users cannot print directly from a document.


Acceptance Criteria

As an admin I can add a print rule to a user action in the workflow:

  1. Go the the Workflow of a document definition

  2. Add a user action and open the user action

  3. In the rules dropdown insert the Print rule

  4. The print rule has the following fields:

    1. Label

    2. Description

    3. Template (with the same source DD)*

    4. Execute only if

    5. Google Cloud Print API* (perhaps some additional fields are required to add parameters)

*Mandatory fields


As a user I can click a button that executes the print rule action in a document:

  1. Click the button

  2. A confirmation dialog is shown with the text: ‘Are you sure you want to print the document?’

  3. I click OK, the template is sent to the printer.

  4. (if possible)If the Google Cloud Print responds, a dialog with a success notification will be shown

    1. If the printer doesn’t respond within x ms, an error notification will be shown

For every time the print rule is executed a log needs to be written.

+3
Staged for Release

Return to same position in document after leaving a reference / autocomplete field on mobile

pvdlageweg 4 months ago • updated by Jira user 4 weeks ago 8

As a mobile user I would like that, after I have selected a value in a reference / autocomplete field and return to the document, I return to the same position in the document as before entering the reference field. This would improve my User Experience, especially in large documents.


[WHY] To improve the user experience on mobile devices.

[WHO] Mobile user

[WHAT] Make sure that after leaving the reference / autocomplete field on mobile, the user returns to the same position in the document as before.


Current Situation

After leaving the reference / autocomplete field, the user’s position is atop the document.


Acceptance Criteria

  • After leaving the reference / autocomplete field on mobile, the user should return to the same position in the document as before entering the reference field.

  • Any field that has one level deeper should have the same behaviour, so that in case we are adding new fields with the same behaviour it should work for these fields as well.

+3
Under review

Add a field type "URL"

Hans van Lith 6 months ago • updated 4 months ago 2

As an administrator, I want to be able to show a link in layout so I can link to another document in BizzStream or to external websites.


Why: This gives the possibility to switch to a related document without having to search again (This adds another layer to the menu structure in BizzStream). This also gives the possibility to link to video's for workinstructions  on Youtube or to workinstructions on the suppliers website a.s.o.. 

Who: administrator

What: add a field type "URL" + property "Open in new tab".


Current situation: you cannot add a document related URL in a specific document (only in a user action but that URL then relates to all documents in the document system).


Acceptance criteria: you can add fields with field type URL to a document. You can choose wether the URL will open in a new tab or stays within the same. The entered URL is validated. If you click or tab on the URL, the webpage is opened.

+3
Staged for Release

Restrict size of signature field

Peter van Meijel 11 months ago • updated by Peter Van de Lageweg 11 months ago 7

As an administrator, I want to restrict the size of a signature field so that I don't have to deal with signatures that have various sizes.


(WHY) The size of the signature field depends on the user's device. As a result, signatures may have different sizes, which makes it difficult to deal with.

(WHO) Administrator

(WHAT) Restrict size of signature field


Current Situation

The size of the signature field depends on the user's device. As a result, signatures may have different sizes, which makes it difficult to deal with.


When a signature field is very wide, users tend to put the signature in one part of the field (see screenshot 1).


When the signature field is rendered on another device, it is resized in such a way that its aspect ratio got lost. This is undesirable. 


Acceptance Criterea

We try to store images in the same aspect ratio, so that it is relatively easy to resize those signatures.


We use an aspect ratio of 1/6. For each pixel that the signature field is width, it is 1/6px height. So when a reference field is 600px width, it is 360px height)


UI/UX Design


Screenshot 1: A signature in a very wide signature field



Screenshot 2: The signature rendered on a mobile device




Sprint 21 August 2017 - 15 September 2017
+3
Done

Add confirmation functionality to guard rules in user actions

Peter van Meijel 11 months ago • updated 5 months ago 10

As an administrator, I want that the guard rule terminates a user action if a user does not confirm so that accidental mistakes are avoided.


(WHY) Some user/bulk actions may have consequences that are hard to revert. In this case, is is desirable to be able to ask the user to confirm that he wants to start an action.

(WHO) Administrator

(WHAT) Add confirmation functionality to guard rules in user actions


Current Situation

When a Delete Document rule is part of a user action, a confirmation is shown. Apart form that, no confirmations are shown to the user when an action starts.


Acceptance Criterea

This story consists to two parts:

  • Adding the rule
  • Asking a confirmation when the rule starts


Add the Guard rule

To add a rule, the administrator completes these steps:

  1. Open a document definition
  2. Go to the workflow section
  3. Opens an user action
  4. Click on insert and then on Guard
  5. Enters the confirmation text in the Confirmation box (see mockup 1).
  6. Clicks on Update to remember the changes
  7. Close the action dialog
  8. Click on Save to persist the document definition.
Note: Please note that the Confirmation property is only visible for Guard rules in user actions.

Ask confirmation

BizzStream determines as follows up to what point rules are executed:

1. BizzStream will show a confirmation dialog (see mockup 2) for each of the Guard rules with a confirmation question.

2. If a confirmation dialog is cancelled, no further confirmation dialogs are presented to the user. BizzStream will ask the server to execute the rules up to the Guard rule that was not confirmed.

3. On the server the rules up to the Guard rule that was not confirmed are executed. If one of these rules throws an error or a Guard rule is triggered via the Execute Only If functionality, the user action is interrupted at that point.


Note: A guard rule with a confirmation dialog can thus interrupt the user action if the Execute Only If condition resolves to true, even though the user clicked Ok in the confirmation dialog.


UI/UX Design



Mockup 1: The confirmation properties in the Guard rule



Mockup 3: The confirmation dialog

+3
Staged for Release

Add support for QR codes to mobile reference and autocomplete field

Peter van Meijel 1 year ago • updated by Hans van Lith 6 months ago 4

As an administrator, I want to enable users to fill out reference fields by scanning a QR code so that the risk of typing errors is reduced.


(WHY) In some cases, reference fields may point to documents that have reference labels that are very similar (say a 10 digit identification code). If users enter this code manually, there is a high risk of typing errors. This can be reduced by completing reference fields by scanning a QR code.

(WHO) Administrator

(WHAT) Add support for QR codes to mobile reference field


Current Situation

Mobile reference and autocomplete fields do not have support for QR codes.


Acceptance Criterea

This story consists of two parts:

  • Enabling QR code support in the layout
  • Scanning the QR code

Enabling QR code support

To enable QR code support, the administrator

  1. Opens a document page layout
  2. Clicks on the pencil icon of a reference/autocomplete field
  3. Checks the box Enable QR Code Scanner on Mobile Devices (see mockup 1)
  4. Clicks on Save to persist the layout

Scanning a QR code
To complete a reference/autocomplete field using a QR code, the user

  1. Opens a document using the mobile app
  2. Clicks on the QR code button of the reference/autocomplete field (see mockup 2)
  3. The QR code scanner now opens (see mockup 3)
  4. The users scans the QR code
  5. If one document is found
    1. If we have a 1-1 autocomplete/reference field, the new value is used and the user returns to the document (see mockup 2).
    2. If we have a 1-N autocomplete/reference field, the new value is added and the user returns to the document (see mockup 2).
  6. If multiple documents are found, the user returns to the reference field helper. The search box contains the value of the QR code that was scanned.

The QR code scanner acts as a way to find references. So BizzStream tries to find documents for which the reference label matches with the content of the QR code. It uses the same search method and respects the reference filter. In other words, the QR code scanner is a way to circumvent manually typing search criteria. Apart from that, there is no real difference between manually entering a search string or using the QR code scanner.



UI/UX Design


Mockup 1: The Enable QR Code Scanner on Mobile Devices checkbox



Mockup 2: The QR code button in the mobile document



Mockup 3: The QR code scanner



Mockup 4: The reference field helper where the search box is filled with a value provided by the QR code scanner

Sprint 24 May 2017 - 23 June 2017
+3
Done

Filter scripts on name/label

Peter van Meijel 2 years ago • updated 2 years ago 9

As an administrator, I would like to filter scripts on name and label so that it is easier to find a relevant script.


(WHY) Making it easier to find a script in the list

(WHO) As an administrator

(WHAT) Adding filter fields for name and label


Current Situation

Currently, it is not possible to filter scripts.


Acceptance Criterea

When the administrator goes to to Setup > Scripts, he can filter on name and label.


UI/UX Design

The overview with filter fields for name and label

Sprint 21 December 2016 - 18 January 2017