9 results found
-
Ability to use "objemail" variable in BCC line
We often include the "objemail" variable (copied from an application record) in the To or CC line when we generate an email to a grantee from Outlook. By including the "objemail" variable in the To or CC line, the email will then be attached automatically to the application record. However, the functionality does not work if we include the "objemail" variable in the BCC line. Since the "objemail" variable is a long string of characters, we would find value in using it in the BCC line so that it is hidden from recipients to avoid any confusion on their end.
3 votes -
The ability to choose to wrap text or not for list views (functionality like excel)
Some of our fields can have long values. I want to include them in listviews, but the text automatically wraps so that you can see everything. That sometimes makes a single record take up an entire page.
I'd like the ability to opt out of text wrapping for some columns- completely understand that that means I may not be able to see all the text in the column. Sometimes it's enough to see that it is filled out, or the first few words.
This would be similar to excel or google sheets, where you can determine how wide each column…
1 vote -
Give the option (when configuring) to define whether a custom field should be allowed to be reported on
Over time our system has become cluttered with custom fields (for ex. multiple fields called something similar) which makes it difficult for end-users to determine which fields are relevant, unless they have access to configuration mode to identify the ID of the field.
It could be useful to have the option to mark a field whether it should be reportable or not, minimizing the list of available fields that can be used.
1 voteThank you for the suggestion—while the idea does have merit, it's not something we plan to pursue at this time. However, within the Report Builder, you can use the custom field search to filter the list of custom fields by caption, field name, or ID, which may help achieve a similar outcome.
-
Make Submit button redirects dynamic based on user role
We have two different roles doing reviews - external reviewers with the "Reviewer" role, and staff with the "System Administrator" role. Right now the review "Submit" button redirects to the Reviewer Portal accessible to external reviewers, and throws a permission error to the internal reviewer. It would be nice to be able to redirect to the internal reviewer's Staff Home portal and the Pending Reviews listview there from the same submit button. Let's not proliferate too many buttons!
1 voteNot Planned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
Two different buttons are required in this scenario. We do not have plans at this time to support dynamic redirection.
-
Introduce merge conflict feature for features accessed in config mode, report builder, workflow creation
Sys admins can override one another's changes without knowing it simply because each is editing the same field, workflow, or report at the same time. If sys admin saves config, report, or workflow task/connector and it has changed since they accessed it, show merge conflicts so they can resolve
1 voteNot Planned ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
Due to the low risk, we do not intend to address this, but if it comes up more often, we will reconsider
-
Save L1 unsaved contents when L2 web page view opened
We use custom web page views to perform CRUD operations on L2 records. We also have an HTML grid that shows those L2 records on the L1. There's a platform limitation with this approach.
Suppose I have three fields on my L1:
1: Title
2: WPV (allowing edit access to my L2s)
3: HTML display of L2s for everyone else who isn't clicking on the WPV and for PDF outputIf user enters title, clicks on WPV, enters L2s, saves L2s wpv, then submits, the HTML display doesn't show the grid (because a save draft didn't occur to refresh that…
1 vote -
'Save and Close' button for modals
For modals, users have to click save and then close out of the window. A "Save and Close" button would be nice so that users do not have to worry about closing out of the window after saving. This would also prevent instances of users having the modal open in multiple different windows.
1 vote -
1 vote
-
1 vote
- Don't see your idea?