This document provides instructions and code snippets for common administrative tasks in Ivanti, such as: 1) Publishing service requests via roles, creating link fields, and associating roles with requests. 2) Useful global constants for email addresses and a query to list employees and their roles. 3) How to make fields only visible to administrators and add business objects to the application landing page.

1. Ivanti Cheat Sheet v1.0 (2017.1)
www.traversys.io
Ivanti Cheat Sheet Version 1.0 http://www.traversys.io
Publish Service Request via Roles
Create a Link Field in the ServiceReqTemplateEntityAccess Object
Create Relationship between Control System and
(Frs_def_role) Role Object
Zero or Many
Link Field created
Associates With
Zero or One
RecId (Primary Key)
Navigate to: Self Service > Configure Access > Add Filtering Property
Title:
 Role
Relationship:
 ServiceReqTemplateEntityAccessAssocFrs_def_role
Validation List:
 RoleList
Employee Relationship:
 RoleAssignedUsers
Request Publish Action Access, will now allow you to select “Role” as a filter
option.
Note: if a User is related to a Role (even if not logged in), and that Role has a SR
published too it, this will mean the User will have visibility of that Service Request.
Useful OOTB Global Constants
Email:
 Listener: $(GetGlobal("ListenerEmailAddress"))
 Default: $(GetGlobal(“DefaultFromAdress”)
 Owner: $(OwnerEmail)
 Team: $(OwnerTeamEmail)
Query to List Employees and Reprective Roles
SELECT
Employee.DisplayName,
STUFF((SELECT
', ' + Frs_def_role.DisplayName
FROM Frs_def_role
JOIN Frs_def_role_assignment
ON Frs_def_role_assignment.SourceID = Em-
ployee.RecId
WHERE Frs_def_role_assignment.TargetID =
Frs_def_role.RecId
AND Frs_def_role_assignment.SourceID = Em-
ployee.RecId
FOR xml PATH (''), TYPE)
.value('.', 'varchar(max)'), 1, 2, ''
) AS Roles
FROM Employee
ORDER BY DisplayName
Common Business Objects
How to add a business object to the "Business Objects" landing page in the Config-
ure Application > Business Objects
 Navigate to Configure Application
 Select and click into any Business Objects
 Click on the "Commonly Used" check box on the "Details" page
Field Visible for Administrator Role
On your chosen form/list, use the expression below on a field that you would
like only to be visible by 'Admin' role.
 $(if (CurrentUserRole() == "Admin") then true else false)
Reversing the true/false statement allows you to apply this logic to the Hidden
Expression in a BO layout view, as below.
 $(if (CurrentUserRole() == "Admin") then false else true)
Add link field to Exported Report
In Configure Application, navigate to a chosen Business Object and Select the
"Quick Actions" tab.
Select and click Edit on the ‘Export to Excel" Action
Add a new line and enter a ‘Header Name‘ in first column.
The third column ‘Value Expression’ allows you to select the related objects
link fields to display.
Clicking the ‘Fx’ icon will enable a tree view for easier
selection.
Automatic Timeout
In Configure Application, navigate to Security Controls
Select ‘Security and Session’
Scroll down to ‘Session Timeout’ this allows you to define in minutes the ses-
sion inactivity timeout for current tenant.
Capture incoming ‘From’ Email Address
Create Text field: i.e. ‘From_Email_Address’
Create workflow with following conditions:
 Run on Created
 AND Source = ‘Email’
Use an update block to include expression:
$(ChildFold("Incident#", RecId, "Jour-
nal#Email", "FromAddr", "+", "$(Category
='Incoming Email')"))
Allow other roles to Edit Risk Level
 Navigate to Users and Permissions > Roles and Permissions
 Open chosen role
 Open Object permissions.
Grant all permissions (Add, View, Edit, Delete) to both the "RiskLevel" and
"FRS_RiskQuestionAnswer" objects:
Wait Block
In order to force a wait block to wait for it’s given timeout period, set the condi-
tions as below:
Select ‘AND’
Field RecId Is Empty ‘leaving the value field empty.