7 results found

1. Allow for copy text capability in document preview

   The new ability to preview uploaded documents is great. However, is there a way to make it so that the user has the ability to copy text from the document while in preview mode?

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Proposed Idea  ·  0 comments  ·  Documentation  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

2. Data Extraction API - Metadata endpoint that returns the schema definition of each entity type

   Provide a schema discovery endpoint that allows clients to programmatically retrieve resource metadata, enabling automated data pipelines without requiring manual field mapping.

   At minimum:

   • Field id
   • Field name
   • Display label
   • Field type
   • Description
   • List of possible values when Enum
   • Created date
   • Last modified date

   In the iterated version of this, it would be good to have metadata on the UTA types (L1, L2, L3) and relationships between entities.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Proposed Idea  ·  0 comments  ·  Reporting and Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

3. Data Extraction API - Inclusion of data from all field types (and particularly data tables)

   Currently data captured through fields such as Basic and Advanced Data Tables is not included in the responses returned by the Data Extraction API.
   It would be ideal to have them included and formatted as a json or xml.
   In general, I think it would make sense that all collected data is made accessible through the Data Extraction API.

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Proposed Idea  ·  0 comments  ·  Reporting and Analytics  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

4. Annotation Mode Data Integrity Issue

   Currently, when a role has the "Edit Field" permission enabled for annotation mode, they are able to edit fields on an otherwise Status Locked record by adding an annotation alongside the change they make. This is great for the revisions process as it creates a clear record of where an external user has made an update to a record they already submitted; they are not able to make changes to fields unless they also include an annotation.

   However, there is a delete button on individual annotations that is only accessible to the user who added that specific annotation. When testing deleting annotations, we discovered that an external user is able to change a field via annotation mode, then delete the annotation associated with this field level change, and while the annotation is deleted, the field level change is retained. This creates a data integrity issue as it means users could make changes to fields and then delete the associated annotation, thus removing the clear record of what changes were made during the resubmit.

   This feels counterintuitive to how annotation mode was designed, as to save an edit made to a field while in annotation mode, a user must add a message; this makes sense based on what I previously described before with how annotation mode allows for override of the status lock. Without anyway to toggle the availability of the delete button or have the field level change revert, the intended use of annotation mode to enhance revisions while maintaining security is lost.

   There is the ability to see field level changes via annotation mode with the Track History toggle; however, the field history button shows up on a specific annotation once a field level change has been made with it, so if that annotation is then deleted, there is still no clear flag that a specific field was changed. Additionally, while the Track History feature can be used for individual fields to see if they were changed, this defeats the ease of review that annotation mode is supposed to create, as it means our staff would have to manually click through the field history button for each individual field they suspect was changed, instead of seeing a clear indication of that via an annotation.

   To address this issue, there should either be the ability to toggle the delete button on or off for various roles (similar to the other permissions for Annotation Mode in a specific status) or there should be a workflow or validation in place that causes the field value to revert back if its associated annotation is deleted.

   Currently, when a role has the "Edit Field" permission enabled for annotation mode, they are able to edit fields on an otherwise Status Locked record by adding an annotation alongside the change they make. This is great for the revisions process as it creates a clear record of where an external user has made an update to a record they already submitted; they are not able to make changes to fields unless they also include an annotation.

   However, there is a delete button on individual annotations that is only accessible to the user who added that specific annotation. When testing… more

   2 votes

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Proposed Idea  ·  0 comments  ·  Security and Compliance  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

5. New SmarConnect API Session Refresh Method

   I fully understand that the RESTful API is stateless and under most circumstances having the ability that I am requesting doesn't make sense. However, due to the nature of our usage and reliance on the SmartConnect API, having such a feature is somewhat important. We have users that are "active" in an SPA for a long period of time but the platform does not recognize that they are active at all and times them out. Alerts regarding the session timeout are not particularly useful either as the user still needs to perform some native platform action in order to "refresh" the session timeout. The ability to tie specific actions within the SPA to trigger a refresh would allow us to identify to the platform that the user is active.

   I completely understand if there are security implications to implementing such that would prevent such a feature to exist, but I am hoping that this is not the case and it is within the platforms capability to support something like this.

   What I am ultimately looking for is a way for our SPA's using the SmartConnect API to identify to the platform that the user is still active. How that manifests it totally up to you.

   I fully understand that the RESTful API is stateless and under most circumstances having the ability that I am requesting doesn't make sense. However, due to the nature of our usage and reliance on the SmartConnect API, having such a feature is somewhat important. We have users that are "active" in an SPA for a long period of time but the platform does not recognize that they are active at all and times them out. Alerts regarding the session timeout are not particularly useful either as the user still needs to perform some native platform action in order to "refresh"… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Proposed Idea  ·  0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

6. New SmartConnect Trigger Workflow Method

   The old Pandora API had a method that allowed us to trigger workflows by passing the workflow id along a few other parameters. This functionality was never passed onto the SmartConnect API. Currently the only way to "trigger" a workflow via the SmartConnect API is to create a redundant record and set a status. This is obviously not an efficient workflow for us as it creates unnecessary records that we now have to clean up at some point. It would greatly appreciated if a "Trigger Workflow" method could be added to the API that could be triggered against any Level One, Two or Three, Contact, Company and Transaction in the same manner as the Pandora API allowed.

   The old Pandora API had a method that allowed us to trigger workflows by passing the workflow id along a few other parameters. This functionality was never passed onto the SmartConnect API. Currently the only way to "trigger" a workflow via the SmartConnect API is to create a redundant record and set a status. This is obviously not an efficient workflow for us as it creates unnecessary records that we now have to clean up at some point. It would greatly appreciated if a "Trigger Workflow" method could be added to the API that could be triggered against any Level… more

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Proposed Idea  ·  0 comments  ·  Other  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating

7. Built-in spell check in text fields

   It would be great if the platform included built-in spell checking in text fields across all applications and activities.

   Most browsers have their own spell checker, but not everyone has it enabled and the experience isn't always consistent. Having spell checking built into the platform would make it easier to catch typos and spelling mistakes wherever you're typing, without relying on browser settings.

   It’s a small feature that could make any text more polished.

   1 vote

   Vote Vote Vote Vote

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Vote

   We’ll send you updates on this idea

   Proposed Idea  ·  0 comments  ·  Edit…  ·  Delete…  ·  Admin →
   How important is this to you?

   Not at all You must login first! Important You must login first! Critical You must login first!

   We're glad you're here

   Please sign in to leave feedback

   Signed in as (Sign out)

   Close

   Close

   Submit Rating