5 results found
-
Type Specific Captions for a Custom Field
The platform was enhanced in recent years to support different display order numbers on a single custom field by Application Type. This allowed us to finally be able position a single field in different positions on different forms. It would be great if we could also support different captions for that one field by Application Type. The only way to do this today is to create multiple fields for the same purpose and then use the value storage setting to store each discrete field to a master field for reporting purposes.
43 votes -
We would like to propose a feature that enables bulk (batch) translation of applicant-entered content in custom fields using SmartSimple’s e
We would like to propose a feature that enables bulk (batch) translation of applicant-entered content in custom fields using SmartSimple’s existing in-tool translation functionality. Currently, translations must be performed manually field by field by clicking the translation button, selecting a target language, and choosing the destination field for storing the translated content. We are not referring to translating field captions/labels, but rather the actual responses submitted by applicants.
1 voteIt sounds like you are currently using the Enable Field Translation Service to translate applicant‑entered content and store the translated text in separate custom fields by manually clicking the Translate button on each field.
If your goal is to translate multiple applicant‑entered fields in a single action, you may want to consider using a workflow with the task type Translate Field Values. This approach may allow you to execute the translations in batch. You could then expose this workflow through a single button on the application form, enabling on‑demand translation of all relevant fields without needing to translate each field individually.
While this is not a native bulk‑translate action within the SmartField interface itself, it might effectively achieve the desired outcome with less manual effort. I suggest escalating to Support if you’d like assistance with configuring the workflow or validating the setup.
If you are still interested in a native…
-
Native integration with OpenAlex (Publication Search)
In our Grants and Fellowships programmes, we require our candidates to link their application to publicly available publications, papers, etc. as to build the State of Art, Methodology, etc. of their project.
Currently SmartSimple supports some Publication search engines natively (Scopus, Web of Science and PubMed as far as we are aware). These are all good resources, but there is a new source which is becoming more popular - OpenAlex -. As it stands, we are building a custom integration with their API for the Fellowships instance, but we would like to suggest that SmartSimple builds a native integration with…
1 vote -
SmartFolder Direct Access Hyperlink
The SmartFolder Link custom field allowed users to add a clickable folder link directly within a record. When clicked, it opened the associated SmartFolder in a modal window, providing quick access to documents without leaving the page.
Use Cases:
Quickly access client or project folders directly from the record.
Enable workflow participants to view or manage related documents during task completion.
Streamline processes such as document review, onboarding, or audits by embedding direct folder links into forms or workflows.
Restoring the SmartFolder Link field would improve efficiency by providing seamless, in-context access to folders where related documents are stored.
7 votes -
1 voteFeedback Needed ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
@Hevedar - can you provide more details on your use case? Thanks
- Don't see your idea?