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.
Our customer GP Groot has asked us to provide more insight into the usage of the system.
At the moment it only possible to see the usage per month. A view suggestions to make thing better from GP Groot, VanWerven (where I'm on location at the moment) and myself:
- stack the monthly / daily bar with documents per document system. So that the monthly-bar contains the docdef (or 10 most used) and show that part of the bar in a different color. Like this:
AND / OR (less work?))
- make it possible to "filter" on document system, in order to see how much each "functional process" is used
- when clicking on a month bar, "zoom" in to an overview per day
- make it possible to filter on values (like companyId) , in order to see how much documents are created per business unit. This will allow the customer to charge to usage of the bizzstream to the correct business unit. This one is tricky; but I'm thinking that we might want to filter on "master data" doc-def Id's
Perhaps an export option to send detailled information is already sufficient to achieve this thirth point.
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.
(WHAT) Add support for QR codes to mobile reference field
Mobile reference and autocomplete fields do not have support for QR codes.
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
- Opens a document page layout
- Clicks on the pencil icon of a reference/autocomplete field
- Checks the box Enable QR Code Scanner on Mobile Devices (see mockup 1)
- Clicks on Save to persist the layout
Scanning a QR code
To complete a reference/autocomplete field using a QR code, the user
- Opens a document using the mobile app
- Clicks on the QR code button of the reference/autocomplete field (see mockup 2)
- The QR code scanner now opens (see mockup 3)
- The users scans the QR code
- If one document is found
- If we have a 1-1 autocomplete/reference field, the new value is used and the user returns to the document (see mockup 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).
- 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.
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
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
Currently, it is not possible to filter scripts.
When the administrator goes to to Setup > Scripts, he can filter on name and label.
The overview with filter fields for name and label
Use reference to script in REST-header URL edit box.
We now have to enter the URL, for example:
It would be great if we could use a script reference, for example
Where restURL is a variable in the script named "settings".
Now we are able to export from the documentoverview screen. This export may including the headfield within the documents. But as many information is stored within the lines, this information is excluded from the export. So can this functionality be expanded so these grid are expotered as well (maybe to different tabs?)
As so, it would be great is the user can determine/select which grids within the document are to be exporterd.
As an administrator, I would like to be able to define an autocomplete field so that I can help users entering data based on documents in a collection.
Currently, we only have a reference field, which stores references to documents. The autocomplete field behaves very much like a 1-1 reference field, but stores the label of the selected document rather than a reference.
To implement this feature, a couple of changes have to be made.
- Add a new field to the document definition
- Implement a field renderer for desktop
- Implement a field renderer for mobile
New field in document definition
We add a new field type, called Autocomplete to the document definition page:
There are two differences with the reference field:
- When a Related Document is Deleted: This field is not available because the Autocomplete fields stores a label and not a reference.
- Value should be in list of suggestions: This setting enforces that there is at least one document in the collection that has a filter that corresponds to the value entered in the field. In other word, the field will not validate when the user entered a text that does not correspond to one of the suggestions.
It is possible to have a 1-N autocomplete field. In this case, several values will be separated by comma's. For instance, we could have the values "Pizza Restaurant Duit, Pizza Restaurant Amsterdam West".
Implement a field renderer for the desktop
In this case, we can use the Kendo UI Autocomplete.
Implement field renderer for mobile
On mobile, we can use a basic text field for the document:
When the user clicks on the > button, the list of suggestions appears:
Support for "common data", for example: generic PostalCode document, CountryCode document or Currency Code. That way we can model solutions for customers that require the use of Address-data.
Would be very helpfull with Freesmij, VanWerven, etc. Almost every integrations needs this data.
It would be nice that you can influence the behavior of filters. Sometimes you want the filters directly show. In some cases not.
Reason. Filters not directly open means that you have more space for data in the grid.
Now, always open.
As an end user I would like to see picklist content in my own language. Currently, employees who have a different native language cannot understand the values displayed in the picklist.
(WHY) There isn't an option to fill in a translation key.
(WHAT) Add a translation key.
Customer support service by UserEcho