27 results found
-
Map Advanced Data Tables - Static Sections
When a static section is required in an advanced data table, clients still want to be able to query the data across records. While technically they can in a report, the only way to make this more user friendly at the moment is to create hidden fields that are populated with template formulas or try to make the section dynamic and map to L2s.
It would be much more user friendly and make configuration easier if you could just map each applicable cell to a field on the same record level. This would reduce template formulas that have to run…
6 votes -
Advanced Data Table - Total Row Validation on dynamic advanced data table sections
Often times clients want to enforce a minimum or maximum amounts on certain columns such as request amount or match amount on an advanced data table total row. This currently isn't possible without passing the data to a static section. This makes validation tedious and time consuming to configure, but also more complicated for a client to edit and update later.
One should be able to use validation in the amounts in the total row only such as:
-Comparing the amount in one column to a field on the grant or linked cycle
-Comparing the amount in one total column…6 votes -
Enhance Auto Assignment Feature
It would be nice to be able to use the auto assignment feature as follows instead of having to use workflows and enable this to be used with the contacts tab instead of assigned sf:
1) When a new user is added in a particular role to the contacts tab of an L1, automatically assign them to the L2s in the contacts tab as a particular role
2) When a new L2 is created and users from the L1 are set to auto assign to the L2, the assignment is passed upon activity creation
3) When a user is removed…5 votesMonitoring Interest ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
There are multiple parts to this idea. One is that we will ensure the auto-assignment works for single users, this ticket will represent the request to support multiple contacts. We may also consider supporting deletions, but that will be after we deliver this first step of supporting multiple contacts.
-
Revamp the Person to Person relationship menu
I have a couple of clients that are using the person to person relationship in SmartSimple. This is an older feature that hasn't gotten a lot of love/updates and it would be nice if we could update the UI to match the UI we have for Associations. Right now the UI is pretty out dated and it feels clunky to navigate.
4 votes -
Need to be able to attach an organization to L2 payment records
We need to be able to attach a payee organization on an L2 payment record that can be different from the org listed on the L1. We've had to create a number of inelegant workarounds in the record and in reporting to get payments to work for our business processes. If it worked like the standard organization field on the L1, that would be the functionality we need.
4 votes -
Expanding Auto Archive Settings
It would be helpful for the Auto Archive feature to be configured per status that triggers it, so that there is more granular control over how records get archived.
For example, despite multiple statuses being able to trigger the archival process, if they must be unarchived, they all get the same status.
Additionally, it would be helpful to also be able to define when the auto archival process happens. For example, perhaps after a day, week, or month. Being able to define that per status add more flexibility.
2 votes -
Enable the copy profile option workflow task to work without the copy button being visible
Currently in order to use the copy profile option in a workflow, the user that triggers the workflow must have access to the copy button under the new menu in the record. This creates extra menus for external users who don't need to see the copy button when the workflow is being run in the background. This should not have to be visible on the record for the user triggering the workflow in order for the workflow to trigger. This is something for all FHLBs.
2 votesPlanned ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We agree this condition should be removed as the work around adds more risk to maintain going forward.
- Don't see your idea?