An often overlooked best practice is that for file naming conventions.
Files should always be renamed with a prefix of the last modified date in YYYY-MM-DD format, for sorting purposes, and contain a meaningful name and version number.
Descriptions such as “final” and “complete” should also be discouraged as 99% of the time there will be revisions. This best practice ensures files are easily found, sorted, and clearly indicate the last modified date, version, and file contents.
Note that the file saved date/time often changes as files are sent via email, download again, or saved by mistake.
For example, Task #8043 has two attachments:
Copy of 2020-09-11 – Sample UAT Test Scripts Complete.xls should be 2020-09-11 – UAT Test Scripts v2
2020-09-11 – Sample UAT Test Scripts Complete.xls should be 2020-09-14 – UAT Test Scripts v3
Blackout, is a point in time in the development process when a system becomes unavailable (off-line) by design. The term comes from Electricity “blackouts”when there is a complete electric shut down.
A best practice is to take the UAT system off-line when UAT is undergoing maintenance or configuration in preparation for End User Acceptance testing. This is to prevent any unauthorized access by end users that might want to start testing the system before it’s ready, which is never a good idea. After all, you don’t call the building inspector until you’re up to code, right? Leaving UAT available during configuration can be disastrous. Don’t make this rookie ISM mistake, you will thank me later!
One of the most crucial steps in System Development Life Cycle (SDLC)is User Acceptance Testing (UAT), a type of system and business objective validation, performed by the end users, and business objective sign off by the project owner; not to be confused with System Testing which is performed by the Ivanti Developer and/or ISM Administrator
Many Ivanti Service Manager implementations fall short when it comes to proper UAT Testing, be it due to a lack of resources, time, or budget, but more often than not due to a shortcoming of proper UAT Action Plan andUAT Test Cases and Scripts.
Today we will focus on a sample high level UAT Action plan:
Refresh UAT with PROD (ISM Administrator)
Push Asset Scanner Packages to UAT (ISM Consultant)
Create UAT Test Cases/Scripts (ISM Administrator/Knowledge Manager; with assistance from ISM Consultant)
Create Documentation for ISM Users (ISM Administrator/Knowledge Manager with assistance from ISM Consultant)
Test Data Preparation (ISM Administrator)
Test Run (ISM Administrator)
UAT Run (ISM Administrator+ Storage Managers)
Remediation (ISM Consultant)*
UAT Run (ISM Administrator+ Storage Managers)*
Including Validation of Documentation and Knowledge Article Creation (ISM Administrator/Knowledge Manager)
Confirm Business Objectives – Sign Off (Project Owner)
Schedule Push to PROD (ISM Consultant)
Communication Plan (Core Team)
ISM Change Control Announcement
ISM Change Control Email with Documentation
Before – for example 3 days before
At PROD Push
After – optional – follow up
PROD Push (ISM Consultant)
Validate PROD Push (Core Team)
PROD Emergency Support – 1 to 2 hours after push – (ISM Consultant)
If you want to add an image to a business object then you can use the Binary/Max field type which is a good way of displaying a screenshot or picture that you can open with a single click, opposed to attachments that you need to save locally first.
HTML text fields with Base 64 Code
Another way is to use an HTML field, first select Text as the field type you want to add and then change it to HTML. Now you can paste images which which will be converted to Base 64. To view the base 64 code click source edit to copy it and voila!
Now you can copy and paste the base 64 code OR entire HTML code to Global Constants such as a “generic” Email Footer for example for ALL outgoing email notifications.
Tip: If you do not have any HTML fields, then you can create an Email with Ivanti Service Manager and use the email body (it’s HTML)
and then click source edit to reveal the base 64 code
and then copy the code into the Global Constant.
Calling Global Constants
In your email notification body, or anywhere else in ISM you can call the Global with the function GetGlobal()
Ivanti Service Manager (HEAT) has two options for sending mobile notifications.
Send Mobile Notification Quick Action – is very limited, only works with Apple Devices and requires push notifications to be working and enabled.
Email Notification Quick Action – the better way is to set a Quick Action to send straight, small text emails to the user’s mobile device. Most all Cellular Providers have this option.Some of the email addresses to use are below:
Zapier is a web-based service that allows you to integrate web applications.
With Ivanti Service Manager2017.3.1 onward you can now trigger the creation of an Incident, Change, Request, Service Request, or Incident note from other supported Zapier integrations such as a Google Sheet, Excel Spreadsheet, Google Calendar, Twitter, Chatbot, etc.
You can also trigger an integration when a new Incident, Change Request, or Service Request is created, for example, trigger the creation of a Google Calendar Entry when a Change Request is created or a Service Request is created (Computer Loaner Service Request for example).
The Zapier Pricing model is by # of Zaps (Integrations) and Tasks, starting at $25 USD per month.
Ivanti Service Manager 2017.1 onward uses a new “model” for relevancy searching.
For example if you search Incidents for a customer with the keyword Consultant your search may NOT be in the order of your list view however if you use double quotes for specific phrases such as “Consultant” then your search will be in the correct order.
The solution is to add a Global Constant as outlined here:
Defining a New Global Constant for Full Text Search Relevancy
Customers who want to roll back the Full Text Search Relevancy to the older model used for releases prior to Ivanti Service manager 2017.1, must define a new Global Constant. Changing the settings for the global constant will either enable or disable the feature. For information about how to create a global constant see Creating a Global Constant.
Enter the name for the constant exactly as shown.
False disables the new model and reverts the search relevancy to 2016.x functionality. Set the Value to True to enable the newer functionalityThe value for the global constant.