John Jameson
My feedback
36 results found
-
17 votesJohn Jameson
supported this idea
·
-
3 votes
An error occurred while saving the comment -
10 votes
We plan to make this update in 2022.
Thank you!
John Jameson
supported this idea
·
-
6 votesJohn Jameson
supported this idea
·
-
8 votesJohn Jameson
supported this idea
·
-
2 votesJohn Jameson
supported this idea
·
-
8 votesJohn Jameson
supported this idea
·
-
1 voteJohn Jameson
shared this idea
·
-
49 votes
Thanks for the feedback! After thorough research and team analysis we’ve decided to not pursue this idea in the near future because of the scope.
This idea will remain on the ideas portal for continued voting and comments.
Thank you!
John Jameson
shared this idea
·
-
5 votesJohn Jameson
supported this idea
·
-
105 votes
Thank you for submitting and voting on this Idea. We’ve spent some time here at Skyward doing research for this request and have determined after a thorough analysis that we will not be pursing this development.
We discovered, that if we add multiple buildings to the employee profile, this change would create large ramifications. Building is found in many places throughout the system and the effort, impact and risk to update is not something we will be able to address at this time.
We recommend using Employee Management Data Mining to report on Employees and all their Assigned Buildings.
In Data Mining use Assignment as the Driver Table, In Field Areas select Position, and under Position select Position Building Code, Position Building state, and Position Building Desc. To report on all buildings associated with an Employee.
Thank you!
John Jameson
supported this idea
·
-
75 votes
Thank you for submitting this Product Idea.
We've reviewed it and are not considering it for immediate development.
This idea will remain open for continued voting, and commenting. Thank you!
John Jameson
supported this idea
·
-
57 votes
Thank you for submitting and voting on this idea. We’ve researching implementing this enhancement and have determined we will not pursue it at this time.
There are several limitations to updating the font so that it is bolder. The biggest impact is that by making the font bolder it will shift the font and take up more room. Every report in the system would need to be reviewed and most likely updated as data would get pushed off the report rendering them unusable.
Thank you,
Ashley Prinsen
Product OwnerAn error occurred while saving the comment John Jameson
commented
I received a lot of the same feedback from my staff when we first started using Skyward. The thing that I found was that users were using Firefox which by default uses a Mozilla built-in PDF viewer instead of an actual PDF program. The Firefox PDF viewer does a poor job displaying text. I had some staff stop using Firefox and some just switch Firefox to use an Adobe to view PDFs instead and this stopped the negative feedback. (This is useful. I post it on my Skyward login screen: https://support.mozilla.org/en-US/kb/disable-built-pdf-viewer-and-use-another-viewer)
-
34 votes
Thank you for submitting this idea. We’ve reviewed it and conducted internal analysis. At this time it is not under consideration for future development. The required scope of this request does not align with our road map priorities.
Thank you.
John Jameson
supported this idea
·
-
20 votes
Thank you for submitting this idea. We recommend using Skycoder to reposition the “add from Online Catalog” button under the “Add” button when completing a requisition.
Thank you
An error occurred while saving the comment John Jameson
commented
If you have an IT person with SkyCoder access, they can move it for you without Skyward making a change for all clients: $('#bAdd').after($('#bAdd2'));
-
83 votes
Thank you for this idea request and participating in voting.
We suggest using the “Force Widget Suggestions” This process will re-suggest the widget to all users that are currently not using the widget.
While this option will not force widgets on users, there are technical difficulties that would delay this enhancement. We are taking this request into consideration and working on a Qmlativ solution. At this time we will no longer be considering this enhancement for SMS 2.0.
Thank you!
John Jameson
supported this idea
·
Here's an interesting twist on discipline records. I don't know if the practice is widespread. Some contracts have clauses that state after a set number of years (varied by contract), the discipline record can no longer be used against an employee (reviews, rifs, etc). If this is a widespread practice it would be good to be able to set the number of years as a configuration for different assignments so that if there are integrations with other modules "aged out" transactions won't be pulled in to other modules.
Additionally, some contracts state that after a set number of years, employees can petition to have a discipline record expunged from their employee record.