Best Of
Re: Cireson Portal fields mandatory based on other fields value
@Bart_Leving - Great! Glad to hear it!
Re: Cireson Portal fields mandatory based on other fields value
@Justin_Workman Thank you, that works for me.
In my case with License management, I had to change SoftwareAsset into License, but then adding the loadScript to custom.js makes everything work like a charm.
Re: Cireson Portal fields mandatory based on other fields value
@Justin_Workman How about a "Definitive Cireson JavaScript " Course, like Adam's powershell one 😁
Re: Cireson Portal fields mandatory based on other fields value
@Simon_Zeinhofer @Bart_Leving - you guys are correct! The Asset Management forms go through some additional backend validation that the work items don't go through and therefore can't have js statements determine the requirement on the controls. I built a custom task to get around this. It's available here:
https://github.com/justinkwork/SWARequired/blob/main/SWARequired.js
This has the added benefit of listening for changes to the viewModel and therefore the requirement on the contingentProps updates according to the current value of the boolProp.
Re: Is it not possible to hide a page from navigation menu but still have acces to it?
Ahh okay I am totally understanding what you are trying to achieve now, apologies for my ignorance!
So the behaviour you are seeing is correct and functioning how it should.. however! The way you stop the navigation node showing for all users is by unticking public, and not adding any security groups.
There is an exception to this.. the user that created the navigation node will always see it! Which is what you are seeing here.
But in answer to your question there is not a way for this to be done out of the box, it seems like an edge case because why do you want to hide something from the nav but still view it?
Re: End of Support for Cireson running on older version of SCSM and Windows Server
Hello David,
If the versions you are running are still supported by Microsoft, we will provide support for them.
Listed below are the versions of SCSM and Windows Server and the EOS dates provided by Microsoft:
SCSM 2012 / 2012 R2 | 12 July 2022
Server 2012 / 2012 R2 | 10 Oct 2023
Server 2016 | 12 Jan 2027
SCSM 2016 | 11 Jan 2027
Server 2019 | 9 Jan 2029
SCSM 2019 | 9 April 2029
Kind regards,
James Nuamah
Re: Migrating Runbook Activity Templates
I've configured RB connectors in our dev & prod SCSM environments to point to the same folder structure in SCO (therefore the RB guid is the same in both SCSM environments). Basically the only logic in this runbook is to determine the environment and then invoke the business logic for the appropriate environment.
I also wrote a separate function runbook that determines the environment. This basically takes the RBA's guid as input, and then uses SQL Query activity to first check the dev environment's BaseManagedEntity table for the guid, if not found, then check the prod environment.
At runtime, the RBA (in either prod or dev) will invoke the same runbook, which checks the environment, and then invoke a separate runbook for the business logic that targets either dev or prod SCSM.
Re: License Expiration Dashboard
Hi Peter,
For the relative date you would need to use a SQL Query and a SQL widget.
Geoff
Re: What is the PowerShell command you run to find the enumID for an extended property?
It is working now. Thanks for your help.
Re: 2024 Roadmap
A few things here:
- Yes its still a thing 😁
- With the release of Archiver, and no less Global Search being able to query the Archive several roadmap items were pushed back
- Those roadmap items such as viewing Activity History within/alongside a Parent Work Item's History, bulk edit, updates to Power Automate/Cloud Connector, etc. are all things we are still committed to delivering