Settings and activity
128 results found
-
23 votes
The product team will review this idea for consideration for a future release.
Greg Smith
supported this idea
·
An error occurred while saving the comment -
18 votes
The product team will review this idea for consideration for a future release.
Greg Smith
supported this idea
·
-
6 votes
The product team will review this idea for consideration for a future release.
Greg Smith
supported this idea
·
-
8 votes
The product team will review this idea for consideration for a future release.
Greg Smith
supported this idea
·
-
25 votes
The product team will review this idea for consideration for a future release.
Greg Smith
supported this idea
·
-
20 votes
The product team will review this idea for consideration for a future release.
An error occurred while saving the comment
Greg Smith
commented
One thing I would recommend in this regard is a clear indication in the GUI when applying changes that also require contacting Innovative (e.g., service commitment to update request rules).
Greg Smith
supported this idea
·
-
4 votes
The product team will review this idea for consideration for a future release.
Greg Smith
shared this idea
·
-
36 votes
The product team will review this idea for consideration for a future release.
Greg Smith
supported this idea
·
An error occurred while saving the comment
Greg Smith
commented
We have an administrative protocol for staff-placed holds (staff append initials to the hold note to distinguish holds we have facilitated from those placed directly by clients) to approximate part of this functionality, but it would be vastly preferable for Sierra to provide this information.
-
13 votes
The product team will review this idea for consideration for a future release.
Greg Smith
shared this idea
·
-
5 votes
The product team will review this idea for consideration for a future release.
Greg Smith
shared this idea
·
-
13 votes
Greg Smith
supported this idea
·
-
14 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Greg Smith
supported this idea
·
-
6 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Greg Smith
supported this idea
·
-
9 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Greg Smith
supported this idea
·
-
13 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Greg Smith
supported this idea
·
-
8 votes
This idea will be reviewed by the product management team for possible inclusion in a future release.
Greg Smith
supported this idea
·
-
10 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Greg Smith
supported this idea
·
-
46 votes
This idea will be reviewed by the Innovative product team for consideration in planning the upcoming product roadmap.
An error occurred while saving the comment
Greg Smith
commented
As Kimberly mentioned, organizations with rigorous IT compliance policies will not permit use of long-outdated software like the Sierra-compatible version of JasperSoft Studio. Obtaining permission for this has proven impossible, and for good reason. I appears that 6.21.3 is the most current 6.x version, but that a 7.x version now exists which may be even less compatible since "the new JRXML 7 model is not compatible with currently existing JasperReports Server versions" as per the information at the following URL:
https://community.jaspersoft.com/download-jaspersoft/community-edition/jaspersoft-studio_7.0.0
Greg Smith
supported this idea
·
-
24 votes
An error occurred while saving the comment
Greg Smith
commented
This, along with a variety of other audit trail functions, would be a considerable benefit.
Greg Smith
supported this idea
·
-
12 votes
Greg Smith
supported this idea
·
Having a more obvious, built-in feature for this kind of search would probably be more user-friendly than the method that is currently required.