Jason Bryan and Steve Alba

Speaker
12/19/2012Name, Title
DD Month 2010

TTEC: Conditional UI in Maximo 7

Jason Bryan and Steve Alba
12/19/2012

not for distribution

Jason Bryan and Steve Alba

Speaker
12/19/2012 Name, Title
DD Month 2010

Conditional UI in Maximo 7

not for distribution

Introduction
Conditional UI in Maximo
Conditional UI allows more flexibility for security access at a
database or application level as well as the ability to control
object properties and functionality conditionally.
Objectives: Gaining a basic understanding of Conditions and
how they can be used in Maximo 7
After attending the TTEC students should be:
Familiar with creating a condition
Aware of the way conditions are applied to Maximo
Able to set up conditonal UI multiple places in Maximo

not for distribution

Condition Expression Manager

The Conditional Expression Manager application is
where conditions are created.

not for distribution

Conditional Expression Manager

Select New Row button to create new condition

not for distribution

Conditonal Expression Manager

After selecting New Row, the condition will autonumber but can be
changed to something more memorable.

Type can be EXPRESSION for a user defined condition or CLASS to

use a class file.
Expression is where you enter the expression to create the
condition.
Always Evaluate? when checked will evaluate the condition after
every change, unchecked will only validate on save
6

not for distribution

Conditional Expression Manager

Create an expression for Site = BEDFORD

Changed condition name to BEDFORD, set expression to take

current SITEID and compare to BEDFORD and checked off
always evaluate
7

not for distribution

Conditional Expression Manager

Conditional Expression Manager is launched with the icon to the right

of the Expression text area and can help you to create a condition as
well as validate the condition you have built against an object you
select from a drop down.

not for distribution

Conditional Expression Manager

Select Asset object to test against and scroll down to bottom of

screen to see the Test Expression button

not for distribution

Conditional Expression Manager

After selecting Test Expression, get Validation Successful message

10

not for distribution

Using Conditions
There are many places in Maximo that allow the use of Conditions:
Domains:
ALN Domain values can be conditional.
Crossover Domains allow for a condition on the source and
destination fields.
Application Designer:
Rights to any object can be conditional including tabs, fields and
sections.
In addition, properties on the objects can be conditional (inputmode,
lookup etc.)
Security Groups:
Data Restrictions at an Object or Attribute level can be set to be
conditional.
not for distribution
11

Creating Conditional ALN Domain Values

Allows for normal use of values without a condition associated
to them.
Better way to set up site level values.
Values can be associated to multiple conditions.

12

not for distribution

Creating Conditional ALN Domain Values

Select View/Modify Conditions with row highlighted

13

not for distribution

Creating Conditional ALN Domain Values

Select BEDFORD condition from previous example. BLACK value
should only appear if site=BEDFORD. Could also set an Object Name
so that the condition would only apply to that object.

14

not for distribution

Check out valuelist in Assets with condition associated

Asset 1004 with site=BEDFORD shows BLACK value when Color valuelist
is launched.

15

not for distribution

Color Valuelist in Assets when site is not equal to BEDFORD

With an Asset with site NASHUA, BLACK does not appear in list

16

not for distribution

Adding a second condition to a value

Create new Condition for when Status is OPERATING

17

not for distribution

Associate New Condition To ALN Domain Values

Associate CONDOP condition to BLUE value. If Status on Asset is
Operating then BLUE value will display.

18

not for distribution

Add two Conditions to a Value in an ALN Domain

Both Conditions associated to BROWN Value. When Status is
OPERATING or site is BEDFORD, BROWN value will display

19

not for distribution

Testing conditions in Assets

With Site as BEDFORD and status NOT READY, BLUE value does
not appear because it's condition of status OPERATING is not met.
BROWN appears because one of it's conditions of site= BEDFORD is
met. This allows values to appear in two sites or under two conditions.

20

not for distribution

Testing Conditions on Assets

With Status=OPERATING BLUE Value appears because
condition is met.

21

not for distribution

Crossover Domains and Conditions

In Crossover Domain can associate Condition to Source and/or Destination fields

22

not for distribution

Using Conditions in Application Designer

Any object (tab, field, section,etc.) in Application Designer can have
a Signature Security Option associated to it.
By giving rights to the Signature Option associated to the object, the
object will appear, without rights the object will not appear.
This functionality replaces Field Level Security and allows for tab
and section security.
Conditions can then be associated to the Signature Options to give
rights conditionally and therefore display the object or not, based on
whether the condition is met.
Another way conditions can be used is in the field properties.
Any property like inputmode or lookup can be set conditionally.

23

not for distribution

Creating Signature Security Option in App Designer

From the Select Action menu, Add/Modify Signature Options, select New Row

24

not for distribution

Creating Signature Security Option in App Designer

Create New Sig Option, be sure to set description so you can see it in
Security Groups, can be named anything unique.

25

not for distribution

Associating Sig Option to a tab in App Designer

Right click Actuals tab and select Properties

26

not for distribution

Associating a Sig Option to a tab in App Designer

Select Advanced tab to see options for Signature Option and
Conditions and select newly created sig option.
Set Sig Option Data Source ID to MAINRECORD

27

not for distribution

Testing Tab Security

Without rights to the sig option associated to the Actuals tab, it will not
appear.

28

not for distribution

Granting Rights to new Sig Option

From the Security Groups application, select Work Order Tracking
application and find the new option. Check off Grant Access and save.
Sign Out and back in to Maximo and test.

29

not for distribution

Testing Rights to Sig Option

With rights to the Sig Option associated to the Actuals tab,
tab now appears.

30

not for distribution

Adding Condition to Sig Option associated to Actuals tab

31

not for distribution

Adding Condition to Sig Option associated to Actuals tab

In Security Groups, select the WOTRACK application, find the Sig Option
associated to the tab and associate a condition to the option.
The users belonging to the security group will only have access to any object the
sig option is associated to when the condition is met.

Now with site set to Nashua tab is not available.

32

not for distribution

Adding Conditions to field properties in Application Designer

Launch App Designer, select Asset application and create new Sig Option.

33

not for distribution

Adding Conditions to field properties in Application Designer

Select Properties for user defined contact field. This field had a lookup
associated to it previously. We will remove that property and add it
conditionally.

After removing lookup value of PERSON, select Advanced tab and

associate Sig Option of TEST55
34

not for distribution

Adding Conditions to field properties in Application Designer

Associate Signature Option of TEST55 and select Configure
Conditional Properties button. Need to give rights to TEST55 in
Security Groups for the following steps to work.

35

not for distribution

Adding Conditions to field properties in Application Designer

In Configure Conditional Properties, select Security Group this will
affect, in the next section select the condition(s)

36

not for distribution

Adding Conditions to field properties in Application Designer

Add properties and values for when the condition of status = OPERATING is
true

37

not for distribution

Testing properties in Asset when condition is true

With Condition of status=OPERATING true, the field color is changed to
orange, the lookup is available and the field is required denoted by the asterik

38

not for distribution

Setting properties for when condition is false in App Designer

When condition is false, inputmode is set to readonly and no lookup is
associated to the field.

39

not for distribution

Testing properties for when condition is false in Assets

Status is NOT READY so condition is not met.
Contact field is now readonly with no lookup property associated to it.

40

not for distribution

Toggle/Show Conditional UI Controls in App Designer

From the Select Action menu select Toggle/Show Conditional UI Controls to see what
conditional UI controls have been added to the application.

41

not for distribution

Toggle Show Conditional UI Controls in App Designer

After selecting Toggle Show Conditional UI Controls, any tab with conditional UI
controls will appear marked as with the Actuals tab below

42

not for distribution

Toggle Show Conditional UI Controls in App Designer

Another example of Toggle/Show Conditional UI Controls

43

not for distribution

Setting Data Restricitons in Security Groups

In Security Groups Data Restrictions tab, you can create a data
restriction at the Object or Attribute level that can be made conditional.
You can specify an object or have it restrict everywhere the object is
accessed.

44

not for distribution

Setting Data Restricitons in Security Groups

Object level restriction types are:
Hidden when the condition is true, data will be masked
Read Only when the condition is true no modifications will be allowed
Qualified only records that meet the condition will be fetched from the
database.
New in version 7.5 an Allow Qualified property can be specified to allow the UI to
use a Qualified data restriction for objects that are not main records

Attribute level restriction types are:

Hidden when the condition is true, the field data will not be displayed
Read Only when the condition is true no modifications will be allowed
Required when the condition is true, the attribute is required

Collection Restrictions

If there are no collection restrictions all CIs, Assets and Locations are allowed
If there are collection restrictions, only CIs, Assets and Locations in the
collections are allowed

Highest access wins in the case of combined restrictions

45

not for distribution

Setting Data Restricitons in Security Groups

Create READONLY object restriction on ASSET object.
Reevaluate checkbox is similar to Always Evaluate in Conditional
Expression Manager and will reevaluate after every change instead of at
save.
These settings should be tested and only used if necessary to avoid
potential unwanted performance issues

46

not for distribution

Testing Data Restricitons in Assets

After saving Data Restriction, Sign Out and back in to Maximo,
launch Assets and all records appear readonly as they should.
Add a new record and receive the message below.

47

not for distribution

Setting Conditions on Data Restricitons in Security Groups

Take the Data Restriction for making the Asset object readonly and add a
condition with Expression :STATUS = 'OPERATING'
When Asset records have the status of OPERATING access to the ASSET
object is readonly.
All other records should have full access.

48

not for distribution

Testing Conditions on Data Restricitons in Assets

Create new Asset record with status of NOT READY and
access is normal.

49

not for distribution

Testing Conditions on Data Restricitons in Assets

Change status to OPERATING and get the message in the screen shot.
This occurs because Reevaluate is checked in the data restriction.

50

not for distribution

Testing Conditions on Data Restricitons in Assets

Select existing record with Status set to OPERATING and record
appears readonly

51

not for distribution

Conditions on Data Restricitons in Security Groups

Uncheck Reevaluate? checkbox to eliminate condition message and allow status
change or a change on a record that satisfies the condition to occur.

52

not for distribution

Testing Conditions on Data Restricitons in Assets

Now the status for an asset record can be changed to OPERATING and
when the condition is met the record turns readonly as the data
restriction should.

53

not for distribution

Data Restricitons at an attribute level

With a new condition for site = Nashua here are examples of
data restrictions at the attribute level

54

not for distribution

Data Restricitons at an attribute level

In Security Groups, select a group and select the Data Restrictions tab.
Select the Attribute Restrictions sub tab

55

not for distribution

Data Restricitons at an attribute level

When site in Work Order Tracking is set to Bedford work type is normal

56

not for distribution

Data Restricitons at an attribute level

When site in Work Order Tracking is set to Nashua work type is hidden
meaning value is not displayed and work type lookup is not accessable.

57

not for distribution

Data Restricitons Object Level Type Hidden

Create Object Level Restriction of type Hidden

58

not for distribution

Data Restricitons Object Level Type Hidden

Save restriction, Sign Out and test in Work Order Tracking

Note that all data is masked in an object level HIDDEN restriction

59

not for distribution

Setting Mask Character for Type Hidden

In System Properties set character for masking

60

not for distribution

Data Restricitons Child Objects

Setting a restriction on a child object in an application:
Data restrictions allow you to specify an object and an application.
This allows you to restrict against an object that's not the main object
For that application and only restrict within that application.
In the following example we will restrict the Actual / Labor tab of
Work Order Tracking

61

not for distribution

Data Restricitons Child Objects

Prior to restriction, Labor rows are editable:

62

not for distribution

Data Restricitons Child Objects

In Security Groups, set object restriction against LABTRANS object
For Work Order Tracking application only:

63

not for distribution

Data Restricitons Child Objects

Save, Sign Out and test in Wotrack, Actual, Labor:

64

not for distribution

Data Restricitons Child Objects

Labor records are no longer displayed due to qualified restriction:

65

not for distribution

Global Data Restrictions

In Security Groups, from Select Action menu, Global Data Restrictions
Object Level restriction types are HIDDEN, QUALIFIED, and READONLY

66

not for distribution

Global Data Restrictions

In Security Groups, from Select Action menu, Global Data Restrictions
Attribute Level restriction types are HIDDEN, READONLY, and REQUIRED

67

not for distribution

Questions

68

not for distribution