The developerWorks Connections platform will be sunset on December 31, 2019. On January 1, 2020, this blog will no longer be available. More details available on our FAQ.
Are there performance recommendations for turning Admin Mode ON ?
This is a common question from administrators and points to some recommendations. For best results, you should be aware of the long running crontasks on your system and avoid starting Database Configuration operations when they are running. When you start Admin Mode, Maximo prevents your crontasks from firing but we have to wait the running ones to end their job otherwise there will be data corruption on your database. You can either: 1. Change schedule of your crontasks making them to run during the dawn. 2. Run admin mode when your... [More]
Tags: ibm-blog |
Unable to add Domain to attribute in Database Configuration app
So, you are trying to change the domain on an attribute from a specific object, however the domain that you created in the Domains app is not in the select value list. You try to create a new domain, but it also doesn't show up. What could be happening ? A common cause for this kind of behavior is if for example you are trying to add an ALN data type domain to an attribute where the data type in not ALN (for example, the attribute type is set to UPPER instead). Once you change the attribute data type to ALN, you should able to see... [More]
Tags: ibm-blog |
Is this a System, Set, Organization or Site level record?
Sometimes you are working with records in Maximo and you are not aware whether Maximo requires to associate a SITEID information or ORGID information, thus you get confused and would like to know what records in Maximo are considered to be level specific. For example, you have in a work order an asset record associated, which is a site-level record, and at the same time there is a job plan associated, which is a system-level record. Finally the work order record is a site-level record. So... how do you get a list or information about the... [More]
Tags: ibm-blog |
What is the logic behind PONUM autonumber for both Site and Organization levels?
The autonumber PONUM exists at both the system level and organization level in Maximo system. Do you believe there is some explanation of why it exists at both? The Autonumbering is controlled by the Autonumber Setup within the Organizations application. Autonumbering can be setup at system, org, and/or site levels in any combination desired. A PO is a SITE Level record and when you create a new PO, Maximo takes in consideration the User Default Insert Site to fill the PO SiteID and OrgID. This way if a PO Header is specified in the ORG1... [More]
Tags: ibm-blog |
Blogging the Support Handbook:Introduction
As promised this is the first entry in the Blogging the Support Handbook Series Here is a link to the Support Handbook (henceforth referred to as SH) in browser format, on this first page, on the right-hand side you can also find a link to a downloadable pdf format http://www14.software.ibm.com/webapp/set2/sas/f/handbook/home.html So we start with an overview of IBM Support which covers IBM's Commitment and a broad overview of the Support Organization. IBM's... [More]
Tags: #supmax handbook support |
Changing the Welcome messages on the Maximo login screen
By default the Welcome message on the login screen in Maximo displays as: "Welcome to Maximo". This message and other text on the login screen is controlled by values in the MAXMESSAGES table. In order to change the values in your MAXMESSAGES table there is a Messages application under Select Action in the Database Configuration application. Go to System Configuration-> Platform Configuration-> Database... [More]
|
MIF object structure Child object key attributes not displayed
Question: I created a Maximo Integration Framework Object Structure with main object as WORKORDER and child object as WOACTIVITY. The WOACTIVITY has the key attributes SITEID and WONUM. When generating this object structure Schema/View XML file, why these two fields are not included in the WOACTIVITY section? Answer: By default, the child object Key Attributes are automatically removed if the parent object has the same keys. However, you can change this behavior. In the Maximo Object Structures application - Select Action - Advanced... [More]
|
New Features in Maximo for Service Providers 7.6.2
The latest version of Maximo for Service providers offers new features, such as labor-based price books, customer agreement templates, and updates to customer billing. Efficiently manage labor prices for multiple customers by using price books You can create a price list for labor resources in a price book. This list of labor prices can be shared with multiple customers, and you can update the labor prices without revising the customer agreement. Use templates to create customer agreements for new customers You can define customer... [More]
Tags: serviceproviders 7.6.2 service-provider maximo_for_service_provid... |
Does Maximo Support characters greater than U+10000 ?
You might want to or not want to use a characters such as pictogram/emoji and wonder if it's supported with maximo. So here is the answer for you on how characters with maximo supported. Currently this is not supported and characters greater than $FFFF is filtered out. Java uses UTF-16 which handles unicode greater than $FFFF by escaping these into two characters. Due to the copmplexity of handling escaped UTF-16 code we currently filter out these characters.
Tags: utf-16 #sup_max emoji |
New system property "mxe.crontask.runonschedule" is added
Have you used the new system property "mxe.crontask.runonschedule" ? The system property mxe.crontask.runonschedule has been introduced from 7602. We can make missed scheduled crontasks run immediately or not run until the next scheduled time. In other words, when the property is set to 0, missed scheduled cron tasks are run immediately and then at the next scheduled time. When the property is set to 1, missed scheduled cron tasks are not run until the next scheduled time. For example, ... [More]
Tags: #supmax mxe.crontask.runonschedul... runschedule crontask |
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
