If a client uses UXBuilder over a private link setup, then SS&C (Project/Support Team) can't access it at the same time. As the private link url would be different than the internet url- devpl.{clientname}.awdcloud.co.uk awddev.{clientname}.awdcloud.co.uk The URL needs to be amended in WSUXBUILDER  resource parameter to get the access.  The issue that makes this one complex to solve is with the variety of UXB setups you can have (not just with CPC), e.g. (non-exhaustive): - A pure over the internet/whitelisted setup where Chorus and UXB sit behind the same URL - A mixed setup (as in this case) where users might reach Chorus and UXB via a number of different endpoints (internet/VPN/Private Link) - A setup where UXB is behind a different address to Chorus entirely (e.g. a 'devuxb.oldmutual' address). The last option is what product have assumed is in play but is not currently something supported by CPC, and even if it was it could still end up with a split access scenario if the customer wishes to use a private connection i.e. you end up with 4 addresses: Chorus over the web, Chorus over VPN, UXB over the web, UXB over VPN. Which would lead to the same problem. Unfortunately because the redirections happen at the browser/user desktop side there is little CPC can do directly to override this. The suggestions given as a solution when discussed were: - Use a browser plugin https://modheader.com/ as a workaround to redirect one address to another locally. (No product release required but of course not ideal) - Update product to allow a map of endpoints for UXB to use which would vary depending on the current Chorus URL (e.g. map awddev.oldmutual to uxbdev.oldmutual and devpl.oldmutual to uxbpl.oldmutual etc), this was seen as quite complex to implement and may still cause gaps in future. - Update the way UXB endpoints are handled within Chorus so that if no specific UXB URL is given in config then the current Chorus URL is used, this was my preferred option but it was recognised there may be edge-cases where this wouldn't work. ServiceNow Ticket Ref - INC2280374 CPC Client: Old Mutual   ... View more

Radio button controls in UX Builder currently require static value lists to be defined manually. If field value definitions (FVDs) already exist in the Admin workspace, these cannot be leveraged — resulting in redundant maintenance and inconsistency risks. The proposed idea is to enable radio button controls to dynamically reference FVDs from the Admin workspace. This enhancement will help in simplifying ongoing maintenance and reduce redundant data entry. ... View more

Currently, only the ROS templates that are defined using file path can be launched from UXB forms. UXB forms cannot trigger ROS templates based on a folder path as defined in the server console. The idea is to enable UXB forms to launch ROS templates based on folder paths (not just file paths) as configured in the server console and also facilitate automated copying of LOB fields from the current work item to the corresponding ROS object similar to classic forms behavior. This enhancement will help us provide a consistent user experience without having to deviate to use classic forms for launching ROS. ... View more

Currently, it is not possible to overwrite an existing UXB form with another form. Attempting to save a form (e.g., UXBFORM1) as an existing form (UXBFORM2) results in an error. The proposed idea is to allow the user to overwrite an existing UXB form intentionally — e.g., saving UXBFORM1 as UXBFORM2 when required. ... View more

There is currently no ability to create reusable templates in UX Builder (UXB). When multiple UXB forms share common field groups, changes must be made manually in every instance. The proposed enhancement is to introduce the ability to create and manage reusable UXB templates, similar to Classic templates i.e., to allow inclusion of a UXB template into a form using an Area control (or similar), where updates to the template automatically reflect wherever it is used. This enhancement will reduce maintenance effort when changes are required and provide better management of common sections/groups. ... View more

Users have mentioned that instead of X icon, if Remove word can be displayed, next to the uploaded document. They mentioned that X confuses user into thinking that that particular document didn't get uploaded. Screenshot attached: ... View more

Currently the file upload on the UXB portal is handled by a multipart/form-data POST (to /downstream/chorus/createWorkObject), subsequently the file is sent to AFT and a source object is created in Chorus. We are facing a couple of issues in this: 1) with a sizeable file (say 40MB) and some level of network latency (say workstation is based in India and the AWS region is in Europe), the user may face a request timeout due to the Cloudfront 3-min hard limit (e.g. see https://repost.aws/questions/QUcE5aWJNuR_6Tb3iL4mOx_A/how-to-increase-the-origin-response-timeout-quota) 2) With the current implementation, the file is sent to Chorus/AFT directly, there doesn't seem to be a 'quarantine zone' to perform a virus scan before the file upload. With these in mind, I'm wondering if the UXB Portal File Upload can send the file to S3 first, so that the file can be staged and virus scanned there before the final file upload to Chorus/AFT. This way, it would also remove the Cloudfront 3-min hard limit? ... View more

Currently the 'table' component in UX Builder does not allow you to configure 'pagination'. Use case: Data is retrieved from an API which contains 000's or 0000's of records the user only has the ability to either filter or scroll. Scrolling to the bottom could take a very long time ... View more

As the number of UXB project grows, the UXB landing page is slow to load.  Having a default filter or pagination could increase the UXB Landing page load time.  Also, is there any enhancement to make certain UXB projects private or public to limit who can access you UXB projects?   Thank you. ... View more

Could you add the ability to Drop UX Builder Projects.  We do projects in dev environments that are no longer needed.   Could you add the ability to delete/clear data rows from UX Builder Project Source Tables? The delete/drop validation could be done by forcing the user to type the name of the project as part of the delete/drop process. Both purging actions can reduce data bloat in UX Builder tables. ... View more

Description: Currently, the UX Builder only allows users to drag and move one text input field at a time. This becomes inefficient when working with multiple input fields that need to be repositioned together, especially when organizing complex forms. Requested Enhancement: Add functionality to allow users to select and drag multiple text input fields at once. This would greatly improve productivity and usability for users building forms or layouts with several input elements. Current Behavior: Users must individually move each text input field. Expected Behavior: Users can multi-select input fields (via Shift+Click, Ctrl+Click,) and drag them as a group to a new position within the layout. ... View more

Currently, there are a variety of Chorus-specific button options in UX Builder, including Save, Cancel, and Submit. We really need a Clear option.  Clear should empty any data collected on the associated Form Project. Why is this important?  If we have a multi-Form Project experience built in Chorus Design Studio and we allow the user to go back, so they can take a different path, we don't want the previous, unwanted data to be saved.  If saved, that unwanted data can appear in the UI or resulting images/objects in Chorus BPM. ... View more

I would like to request an enhancement to the UXBuilder form behavior. Specifically, when a form element or section is conditionally marked as hidden, any data a user has entered into that section should be automatically cleared as soon as they click out of it or when the section becomes hidden. Currently, I am encountering an issue where data entered into hidden sections persists, even after the section is no longer visible. This behavior is causing forms to freeze or retain outdated input, especially in production environments, and affects the stability of dynamic forms with conditional visibility. Implementing this enhancement would help ensure data integrity, prevent form freezing, and improve the user experience by avoiding unintended data retention in hidden elements. ... View more

It would be helpful to publish the version of UX Builder along with Chorus Server Version in the Help-About of Chorus.  See screen shot. ... View more

This is a list so please bear with me if this is a lot. Also correct me if the feature is already available but I've missed to notice it. 1.) Have a direct link to the session logs of the work queue item in web based control room. So it would be similar experience like you are in the BP client where you can view the session logs directly from the work queue item view. 2.) A button to create a schedule from scratch in Schedule Manager. Currently we are just cloning a schedule then editing it to our needs. As per the documentation we can create a new schedule but the add a new schedule button is nowhere to be found. 3.) Can we have a filter in work queue items via the Tags column 4.) Can we have the filter to locate the text wherever it is. Apparently if you are looking for the word "Completed" if you search for "ompl" it will not have the wanted result. Users are forced to know the start of the word they are looking for if they want to filter. 5.) Going forward or back from links resets the users view to the starting page instead of where you left. If you are scrolled down in a long list, if you move or go temporarily in a different page, when you get back, you will be back on page 1. 6.) Headers text are too big. maybe you can have the option to customize the size of the texts on screen. They are too big and the most important contents are too small, the contents in the scrollable tables are too small, make it expandable. You need to scroll down a bunch in order to see the details you are looking for. Browser view is normal 100% no zoom. 7.) Text are cut off even if there are enough spaces. Kindly fix orientation and focus on full readability. Users are forced to hover the text just for the tooltip to come out 8.) In Interact, you cannot have a rule to a field in a page that will affect other fields from a different page in the same form. It would be useful if you can. 9.) Send an email notification to the interact team approver that there is a pending interact form entry that requires approval. It would be easier to the approver to be notified via email that there is a pending item in Interact forms waiting for the approval.   Thanks, Marc ... 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

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

No log out option. User is unable to switch accounts for testing and unable to log out and enter other email address. ... 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