We have commissioned a client-facing portal which is being built using the UX Builder and it has been noted that there is no option for a user to log out of the system. We would like to have the option to add a "Logout" button or link to every page in the system so that users can terminate their session as required. ... View more

We have commissioned a client-facing portal which is being built using the UX Builder and we require more complex client-side validation than is currently possible. For example, if the user were to enter a policy inception date (PID), a policy expiry date (PED), a claim event date (CED) and an insured date of birth (IDB) then we would want to validate that the IDB was prior to the PID, that the PID was prior to the CED, that the CED was prior to the PED. We would also want to check that the IDB did not make the insured person impossibly old or too young to have a policy. These dates are just one example of client-side validation that exceeds simple data typing - we would like to see configurable complex validation rules in the UXB, some of which will depend on mixed data types (e.g. if _this_ dropdown have value "A" then _this_ amount must not be zero). ... View more

UX builder should have an ability to throw a validation error when user attempt to upload a file of size exceeding maximum permitted limit. Currently it creates a work object and discards attachment creation in chorus without an indication to the user of attachment creation failure. Ideally a validation error should be displayed to the user upfront and should not create work object until validation is corrected.  ... View more

Users should have the ability to clear the value selected from a dropdown field especially from non-mandatory dropdowns if user selects a value accidentally, currently it forces user to select a value from dropdown instead leaving it as blank. Usually, dropdowns add a blank value to the list of values which gives the user the ability to set the dropdown to blank. ... View more

When the 'Edit/Delete Rows' functionality is selected in the Table Operations for a UX Builder table, we would like to have the option of being able to perform specific actions, such as executing a service for example, when the user edits a row and then clicks the Update button: Since this functionality does not currently exist, it is not possible to update a row of information on a table directly from UX Builder into a custom table on the database.  ... View more

We would like to have the ability to configure custom tabbing orders on UX Builder forms to enable UX and navigation through the forms as per specific requirements.. This functionality currently exists in Dynamic and Classic Forms, and should therefore be present in UXB as well. ... View more

We would like to have the ability to not choose to display the Filter and Sort options on a table in UX Builder. Currently, these options are shown on all tables by default at runtime, and we would like it so that they can be toggled on or off, depending on the requirement. This would make it so that certain table elements can be used purely for displaying data without the need to take any action on said table. If any actions are required by the use case (for example row select, delete, sort, etc.), they can be configured specifically.  ... View more

It is difficult to tell which service is configured to which step on an action. In previous versions of UX Builder, the name of the service configured behind an action was visible, but it isn’t any more. If there are multiple services configured to a button press, for example, it becomes difficult to track which service is configured where. In the example below, all three are different services: The only way to tell which service corresponds to which action is to open them manually to check. ... View more

We would like to have the ability to limit characters on the multiline element in UX Builder. This element is often used as a 'Comments' entry element, and a lot of the times, clients want to limit the number of characters a user can enter in such fields. See screenshot for reference.   ... View more

No log out option. User is unable to switch accounts for testing and unable to log out and enter other email address. ... View more

The order of actions cannot be changed without deleting them all and reconfiguring each one again. It would be very useful if the action configurations could be dragged over or under each other to rearrange the order in which they are executed. Currently, if the top one needs to be configured to a different action, all existing ones need to be deleted and reconfigured anew. This gets onerous if service configurations are multiple in number and complicated to configure. ... View more

Allow a background image to be assigned to a page or section in UX Builder. This would allow for text to overlay the images like a number of websites. ... View more

We would like to have the ability to direct a section to a new page/section.  This would enable a dynamic way of viewing information on the form based on certain conditions/buttons. For example,          ... View more

We have commissioned a client-facing portal to give our clients the ability to log cases in our Chorus system and a requirement has been raised by a client who has seen the suggested solution demonstrated: they require that when they have created or updated a case in the portal they can then generate a summary of all the details they have entered and the documents they have uploaded. They would like the summary to be in the form of a PDF that they could then download and store in their own system. Ideally the summary would be generated on user request. ... View more

We would like to request the ability to perform an action on multiple selected rows on a table. At the moment, actions, such as executing a service, are only available for a single selected row, but we would like for it to be enhanced to include performing an action for multiple selected rows. The following use cases would greatly benefit from such functionality: Selecting multiple rows on a table and marking a flag on them (invalidating, or validating, or simply marking the rows) Selecting multiple rows and deleting them Both of these become cumbersome when the user has to individual action each row. For example in the following form, when it is converted into a UXB form, we would like to be able to perform the highlighted actions on multiple rows, rather than sequentially one after the other for a better user experience: In this instance, the Delete Turns button would mark multiple selected rows as deleted. There could be an instance where the rows may need to be removed from the table altogether. And the Reinstate Turns  button would update certain fields on the selected rows.  ... View more