kday
My feedback
173 results found
-
229 voteskday supported this idea ·
-
2 voteskday supported this idea ·
-
114 voteskday supported this idea ·
-
15 votes
This is a CALPADS bug on their end. They DO intend to allow these special characters again, so we will not be changing our process at this time. If the
SINF update is needed, the customer either needs to make it manually in OM, or remove the offending characters from Aeries, but ALSO delete the CALPADS log entries for that change (the ones that contain the offending characters) so they won't be extracted also.
kday supported this idea · -
1 votekday shared this idea ·
-
7 voteskday supported this idea ·
-
35 voteskday supported this idea ·
-
31 voteskday supported this idea ·
-
95 voteskday supported this idea ·
-
132 voteskday supported this idea ·
-
162 voteskday supported this idea ·
-
7 voteskday supported this idea ·
-
7 voteskday supported this idea ·
-
2 voteskday supported this idea ·
-
16 votesConsidered for feature modernization · AdminMinott Opdyke (Quality Control, Aeries Software) responded
Hello! Thank you for this idea. We are making plans to include it in the Aeries NextGen system. Stay tuned!
kday supported this idea · -
4 voteskday supported this idea ·
-
8 voteskday supported this idea ·
-
5 voteskday supported this idea ·
-
2 voteskday supported this idea ·
-
3 voteskday supported this idea ·