In this week's release, we are bringing the following additions and changes to our SaaS customers. As every Wednesday, we push the updates to all environments tonight after 5pm.
What have we added?
- The portal has the option to show news items where you can also add attachments (currently only embedded in the message).
- It has become possible to close (if set) or reopen (seperate settings) a ticket from the portal.
- Also, you can now set a status that can be triggered automatically when responding or changing a status of a ticket, from within the portal (see also previous point).
- It is possible to authorise individuals to view/edit all their organisation's tickets from the portal.
- Even without 'edit rights', you can now be authorised to add timeline items to an object (if enabled for that object).
- BIjj Administration > User management you can now also change the table's columns.
- The fields to be displayed for tickets on the portal are configurable. For example, you can choose to hide urgency from your end users.
- Fields within datasets can now be bordered at the top and/or bottom.
What have we changed?
- The [Delete] and [Archive] buttons are now hidden on a smartphone on tickets by default.
- The user interface of the system log has been updated (colour of statuses)
- The portal is now displayed in a 'container' so there is always a fixed width.
- For organisations, we have added the 'Supplier number' field. To complete this, the 'Client number' field is now 'Client number'. For both fields, they are only shown once 'Supplier' and/or 'Client' is checked.
- Log items (Administration > System log) can now contain (drop-down) details and minor changes have been made to the user interface of that page.
- Tickets, organisations, people and processes now also have a page bar at the bottom of the page when viewed from the 'Linked' tab and the (still under development) global search page.
- When creating a ticket, it is now no longer possible to choose an end date before the start date (in the calendar).
Which bugs have we fixed?
- No text was displayed, when viewing a ticket on the portal. This was because there were only invisible responses in this particular example.
- Spaces were still visible despite not having authorisations for them.
- Popovers (the pop-ups showing the contents of a ticket) remained visible once you had clicked on a ticket.
- Confidential tickets of all submitters were visible to a submitter authorised to view all tickets of his/her organisation.
- Tables are now properly designed in all formatting fields.
API changes
Please note; as also indicated last time, in this release the use of a api_key in the URL removed. You should now always using a bearer token for authorisation.
