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.
As a BizzStream customer / partner I want to know what features are (going to be) released and what bug are (going to be) fixed throughout the BizzStream DTAP street.
[WHY] To have more insight in when important functionality and fixes are released.
[WHO] Customers / Partners
[WHAT] Create a new public webpage were releases on test-, acc- and app.bizzstream.com are shown.
Currently we have roadmap.bizzstream.com that shows what features are expected and what features are finished. However this needs a lot of manual updating and is not precise enough on the exact location of a feature/bug fix in the DTAP street.
A new webpage will be created on http://release.bizzstream.com
The page contains 3 sections: test.bizzstream.com, acc.bizzstream.com and app.bizzstream.com.
A header will be added with the BizzStream orange color and the text BizzStream Releases. A BizzStream logo would be nice.
All finished stories and bug fixes are shown in a list grouped by a sprint.
The first sprint group will show on top of the list.
A list item shows 2 things:
The type: either a Story or Bug.
The link to the Story or Bug (the bug link will be only accessible for partners). Click opens in a new tab.
When the list is longer than the container, a scroll bar appears.
As an administrator, I want to be able to set columns in a document layout for tablets devices.
(WHY) Tablet screens are wide enough to show multiple columns, this way more information can be shown in a screen without to much scrolling.
(WHAT) Be able to set 'show columns on tablets'
Currently when there is set more than 1 column in a document layout, these columns only get rendered on desktop. On mobile phones and tablet these columns are rendered as a long list.
- Be able to set the property 'show columns on tablets' in the layout editor. (false by default)
- Render columns on tablets, respecting the field properties (margin, in between space, height)
- Scrolling is set on the window, not the columns independently.
Setting the show column property
The property 'Show columns on tablets' needs to be added to header fields. This is a checkbox type field.
Rendering column on tablets
If the show column on tablets has been set to true, columns need to be rendered according to the bootstrap grid. If values don't fit inside the field, they are concatenated (...).
At this moment scrolling is bound to the listview, enabling smooth scrolling. To have the same experience, the window as a whole.
For example a 2 column view, columns are separated by a grey space.
For example 2 and 3 columns in one view.
Make it possible to select documents from a dialogbox based on the document.
Currenlty users can select values from a selector. See the sceenshot below.
Sometimes users don't know the exact code and want to select values based on other fields.
It would be great if we could open a dialog that contains a (definable) grid. with koloms and headers in which we can search records.This will enable users to find records based on other criteria.
We see this request at a lot of customers. Defining a "dialog-box-like screen" would be very helpfull.
As an administrator, I want to know the name of the action that triggered a script so that I can modify the behavior or scripts depending on the action.
(WHY) Sometimes the behavior of one script should differ based on the action that triggered it. This allows us to keep scripts more generic.
(WHAT) Add the name of the action that triggered a script to actionInfo object
We write generic scripts, that need to behave slightly different based on the button that was pressed. It would be very helpful if we could see the name of the button inside the script.
Add the name of the action that triggered a script to actionInfo object so that we can retrieve it via:
As a administrator, I want to assign multiple menus to a single user so that I can create menus for individual business processes.
(WHY) Currently only one menu can be assigned to a user. As a result, there is a menu is necessary for each combination of business processes that is used in the environment. This is difficult to maintain.
(WHAT) Assign multiple menus to a single user
Typically menus contain the items for one or more business processes. Because only one menu can be assigned to a user, there needs to be a menu for each combination of business processes that is used in an environment. This is difficult to maintain, especially if more and more business processes are added.
It should be possible to add multiple menus to a user, so that there can be a single menu for each business process in the system. In other words: we change the menu assignment from a single menu to an array of menus.
This story consists of two parts:
- Setting the menu for a user
- Assigning the menu to users
The story http://support.bizzstream.com/topics/1998-render-multiple-menus-for-a-user/ deals with the rendering of multiple menus.
Setting the Menu for a User
The administrator should be able to set the menus to which a user has access as follows:
- Go to Setup
- Click on Users
- Select a user and click on Edit
- In the Menus field, select the menus to which the user needs access. The menus field is a multiselect field.
- Click on Save to update the user
- Go to Setup
- Click on Menus
- Select a menu and click on Edit
- In the Users field, select the users that have access to the menu
- Click on Save to persist the menu and update the assignment of the menu to users
- Currently, the menu that is assigned to a user changes when a user is added to an existing menu. When opening the previously assigned menu, the user is no longer listed in the Users field.
- This should change so that when a user is added to a menu, we add the menu to a menus array. When opening the previously assigned menu, the user remains assigned to that menu as well. Likewise, if the user is removed from the Users field, we remove the menu from the menus array.
Mockup 1: The Menus field in a user's environment settings
Screenshot 1: The Users field in the menu page
Zuurmond: we set a boolean value via SetFieldValue in a workflow.
When we look at the doc. definition, with DD.findOne(), we see that the Rule is saved als a string value
Gabry already analysed this and asked me to create this bug report.
Currently we can supress error messags with the option "Do not show success message".
We would also like an "don not display error message".
@DenOuden we have created a few "validation"-scripts. Those scripts calculate some values and when those values exceed a limit; an error is thrown.
It also checks the values of some fields; that are mandatory under certain conditions.
We than display error(s) with: notification.error('fout', 'dit is een fout');
We always used a "Throw "" in order quickly abord the workflow; but the customer indicated that this extra message was confusing to users and an extra mouse click.
In order to avoid the confusing "Something went wrong while executing REST-action" message, we let the "validation"-scripts set a field to "Error" and removed the "throw".
We then implemented a guard rule that checks on that field, for the value Error.
But this requires extra fields, extra save actions in scripts, extra rules (guard rule).
It would be very helpfull if we could supress the error message; so that we don't have to use the workaround construction with extra field and guard rule
As a user, I want open a document in a new tab by pressing Ctrl and clicking in overview on desktop so that I do not have to open a new tab in advance.
(WHY) It is not possible to open a document listed in an overview on desktop directly in a new tab. As a workaround, users first open a new tab and then navigate to the overview to open the document. This workflow can be optimized.
(WHO) A user
(WHAT) Open a document in a new tab by pressing Ctrl and clicking in overview on desktop
On desktop, a user can open a document by:
- Clicking on the document to select it
- Clicking a second time to open the selected document
- Clicking on the document to select it
- Click on the View button
It is not possible to open a document listed in an overview grid on desktop directly from an overview grid.
A document opens directly when a user clicks on a marker.
A document opens by double clicking on
The selected document should open in a new tab if:
- The user presses Ctrl and clicks for the second time on a document
- The user presses Ctrl and clicks on the View button
The selected document should open in a new tab if the user clicks on a marker and presses Ctrl.
The selected document should open in a new tab if the user double clicks on a document and presses Ctrl.
As an administrator, I want to be able to catch errors that are caused by a call to a BizzStream method so that I can do my own exception handling.
(WHY) In scripts, it is possible to handle most exceptions using a try/catch block. However, when a BizzStream method (e.g. persistent.saveDocument) causes an error, the script terminates.
(WHAT) Make it possible to catch errors caused by a call to a BizzStream method
Currently it is possible to write a script like this:
throw "This is an error.";
console.log("The script continues...");
The error that has been thrown is handled by the try/catch block.
However, when the try/catch block contains a call to a BizzStream method such as persistent.saveDocument, no error handling is possible:
console.log("The script continues...");
In this example, the log of the error and the text The script continues... is written to the log.
It should be possible to catch errors caused by BizzStream methods in a try/catch block.
As a user, I want to click on a a line in a mobile overview so that I do not have to aim for the > button.
(WHY) Users can open a document in the mobile app by clicking on the > button. They have to aim for that button specifically. It would be easier if the user could click anywhere in the line to open the document.
(WHO) A user
(WHAT) Make the whole line clickable
A user can only open a document by clicking on the > button of the line (see screenshot 1). This is needlessly cumbersome.
The user can open a line by:
- Opening an Overview Grid layout
- Click anywhere in the line to open a document.
Ensure that the click is really a deliberate touch/click. The user must be able to scroll up/down by clicking anywhere in a line and move his finger up/down. Such a scroll action must not trigger a line to be opened.
The long press action will be used to select a document (this is currently the click).
Screenshot 1: The button where the user must click to open a document.
Customer support service by UserEcho