Settings and activity
96 results found
-
17 votes
Greg Smith supported this idea ·
-
54 votes
Greg Smith supported this idea ·
-
11 votes
Greg Smith supported this idea ·
-
10 votes
Greg Smith supported this idea ·
-
2 votes
Greg Smith supported this idea ·
-
5 votes
An error occurred while saving the comment Greg Smith supported this idea ·
-
5 votes
An error occurred while saving the comment Greg Smith commented
Revisiting this idea, as our ticklers were failing again due to an instance of invalid data. If tickler dates were validated or selected from a calendar date picker pop-up (as suggested by Khaled Mohammad Alsarairah) then this could be avoided.
Greg Smith shared this idea ·
-
5 votes
This idea will be reviewed for consideration as an enhancement in an upcoming release.
Greg Smith supported this idea ·
-
5 votes
Greg Smith supported this idea ·
-
4 votes
Greg Smith supported this idea ·
-
4 votes
Greg Smith supported this idea ·
-
7 votes
Greg Smith supported this idea ·
An error occurred while saving the comment Greg Smith commented
I have to agree. Even though it's slightly inconvenient and despite the fact that "security through obscurity" isn't a valid security control in and of itself, keeping the Sierra API documentation public could still make it easier to exploit any vulnerabilities that affect it.
-
2 votes
Greg Smith supported this idea ·
-
4 votes
Greg Smith supported this idea ·
-
8 votes
Greg Smith supported this idea ·
-
6 votes
Greg Smith supported this idea ·
-
26 votes
An error occurred while saving the comment Greg Smith commented
And while we're discussing this... surely in 2024 it's possible to have more review files?
Greg Smith supported this idea ·
-
3 votes
Greg Smith supported this idea ·
-
6 votes
Greg Smith supported this idea ·
-
18 votes
Greg Smith supported this idea ·
An error occurred while saving the comment Greg Smith commented
Innovative is going to have to switch to 64-bit dates to fix this problem. The case highlighted here is probably the one that is hitting the wall first; I wonder if they plan to EOL Sierra before this problem begins to affect core system functions rather than resolve the issue across the board.
Additional sophistication of this nature would be much appreciated. As it is, we use multiple types of suppression and it is necessary for staff to recognize their meaning (and it's not possible to use this approach to "hide" records from staff for whatever reason).