cancel
Showing results for 
Search instead for 
Did you mean: 
Status: New

Current Behavior
When creating attachments in UX Builder using the “Create Work Object” action on a button, the configuration only allows specifying a fixed number of attachments. This approach can become highly complex and inefficient when dealing with a large number of source or document types - for example, 100 different types

.SimonChatfield1_0-1765867883343.png

Proposed Enhancement
Consider introducing a mechanism to parameterize the attachment source type. Instead of selecting a specific source type from a predefined dropdown, UX Builder could allow passing a variable (e.g., a data source) that determines the document type dynamically based on the user’s selection. UX Builder would then create the corresponding attachment accordingly.

This enhancement would be particularly valuable for clients with extensive document type libraries, which is common in banking and financial institutions.

Error Handling
If the specified document type does not exist in Chorus, the system should display an appropriate error message.

1 Comment
John.Aitken
Level 1

For the bank to be able to develop and use UXBuilder successfully going forward, beyond an initial (internal use case) POC, and to satisfy its business need to deploy self-service customer facing portal solutions, this will be a required enhancement.