Cireson Partners, Customers and Community members share your customizations and examples here to help benefit the community as a whole to earn Kudos and badges.
DISCLAIMER
All files and projects located here are provided and come "as-is" and without any warranty or support. Use at your own risk. Your use of Community Uploads is subject to our Terms of Use.
Cireson does not and will not support or maintain these enhancements, extensions, and scripts.
For Team Cireson uploads click here.
Add Active / Inactive Buttons to Team Request page
Mikkel_Madsen
Customer Advanced IT Monkey ✭✭✭
Warning: It works but it’s an ugly solution 😀
Our users wish to see inactive team requests so with my limited programming skills I have made this solution to add the Active / Inactive buttons the team request page.
A specials thanks to @Ryan_Lane and his post https://community.cireson.com/discussion/4366/sql-queries-to-simulate-analyst-views which gave me the idea to solve this.
This solution contains several steps you must go through before it works.
1. Make at new Navigation Node and a new custom page under this. We don’t want it to be visible in the navigation menu, so we are going to hide this node in the javascript. Make both visible and public to work (https://community.cireson.com/discussion/5016/is-it-not-possible-to-hide-a-page-from-navigation-menu-but-still-have-acces-to-it#latest )
TIP: Place the node last in the navigation menu – it will be visible for a short time before script is loaded.
2. On the custom page add a new sql table widget – Name it “Team Requests” to match the original team request best – but you can use what ever name you want. Query the ServiceManagent database with sql query attached to this post.
3. Fill out the variables in the custom_AddInactiveWorkItemsLinkToTeamRequests.js to match your environment.
4. Load file in custom.js
Comments
Hello @Mikkel_Madsen while I hate necro-ing this thread and bringing it back to life from the dead, we've received exactly a request for this in our company. I've tried you suggestions and the guide and the Javascript itself works, but the query seems to be off and is not returning any results for us. Could you validate to see if the query is still applicable after 5 years of posting this? :) Thanks.
Hi @Gabriel_Lences
Sadly we are not using Cireson anylonger so I'm not able to test it.
You have have du dive in to it yourself 😁
/mikkel
Thank you very much for the prompt response, I'll look into it :)
So the trick for us was to modify the query a bit by adding the ",AffectedUserEmail nvarchar(256)" line 104 in the adjusted SQL query since in the original query it was returning an error. After adding the line, the query works like a charm. Might have been something related to specifically our environment :)