Settings and activity
26 results found
-
4 votes
Victor de la Fuente
supported this idea
·
An error occurred while saving the comment -
9 votesVictor de la Fuente
supported this idea
·
-
4 votesVictor de la Fuente
supported this idea
·
-
8 votesVictor de la Fuente
supported this idea
·
-
1 voteFeedback Needed ·
AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We support a number of e-signature vendors. Can you provide more details on which vendor you are looking at and the reason why you can't leverage any of the existing e-signature vendors we support?
An error occurred while saving the comment Victor de la Fuente
commented
Hi John, la Caixa currently works with Signaturit, although they have been acquired by Namirial and I think by end-of-year we will transition to their product. However, we do not connect directly to their services, as we use a middleware to ensure that even if we change vendor (as it will happen), all la Caixa platform integrated with eSign services do not see a disruption to their service (only the middleware needs to adjust). This is necessary as la Caixa has quite a few products connecting with the eSign platform (at least 15), so it is the most efficient way to handle this in our case.
In any case, we believe this option would benefit all SmartSimple clients, as they would be able to retrieve documentation from other platforms into their SmartSimple instance via a WF Type Task Web Service - RESTful Request GET operation. For example, it could allow clients that integrate with their Finance system to retrieve a document into an project indicating that the payment transfer has been completed.
Victor de la Fuente
shared this idea
·
-
23 votesVictor de la Fuente
supported this idea
·
-
40 votesMonitoring Interest ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We see this as a usability improvement opportunity and will monitor interest to determine if the priority becomes higher.
Victor de la Fuente
supported this idea
·
-
21 votesVictor de la Fuente
supported this idea
·
-
52 votesUnder Consideration ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We are looking at a number of user experience improvements with list views and will include this idea too
Victor de la Fuente
supported this idea
·
-
4 votesVictor de la Fuente
supported this idea
·
-
6 votesVictor de la Fuente
shared this idea
·
-
9 votesVictor de la Fuente
supported this idea
·
-
59 votesMonitoring Interest ·AdminJohn Fulton
(Director of Product Management, SmartSimple, Foundant Technologies)
responded
We will consider a way to differentiate and enable/disable the user. We will monitor interest for future consideration.
Victor de la Fuente
supported this idea
·
-
4 votesVictor de la Fuente
supported this idea
·
-
4 votesVictor de la Fuente
supported this idea
·
-
42 votesVictor de la Fuente
supported this idea
·
-
9 votes
We plan to review pagination, search, and filtering capabilities within the T2P tool. If versioning is not being promoted, it should be reported as a defect to support.
Victor de la Fuente
shared this idea
·
-
42 votesVictor de la Fuente
supported this idea
·
-
93 votesVictor de la Fuente
supported this idea
·
-
15 votesVictor de la Fuente
shared this idea
·
To add more context to this request, what we have observed is:
1. If the user is logged in using a language that is not supported by the type he is trying to access, the system loads the form with the default language defined for the type - which is OK -.
2. If the user is logged in using a language that is supported by the type and IS NOT the default language for the type, it still loads the form attached to that type in the type's default language.
In the case showcased by Oscar, that would be a user who uses the platform in Catalan, and once they access the type, they will see the form loads in Spanish - even though Catalan is an available language and they can switch to it once the form loads -.
It would also be great if the selection is persistent. Essentially, if the user access the form and selects a language different from the default, it would be great if the next time they access the form SmartSimple remembers what language they selected the last time they looked into that form. Right now it always loads the default, so if you want to see the form in another language you have to change the option in the dropdown every time you access that form.