1) Mapping of TEM Legacy KB's to DCF's
2) Troubleshooting documentation for Tivoli Application Dependency Discovery Manager
Thursday, April 17, 2014
Monday, April 7, 2014
Use Email Interaction Setup to Change Status
Below are the steps to setup Email Interaction:
1. Create a new record in the Email Interaction Setup application:For example, call the new configuration MFWO
Setup Object Status Change configurations:
Case 1: If the work order status is APPR , mobile user can reply with 1 to set status to INPRG or 2 to set status to COMP
Case 2: If the work order status is INPRG, mobile user can reply with 1 to set status to COMP or 2 to set status to CLOSE:
Attach a communication template (MFMAILSENDWO) to send to the owner of the work order (WOWNER):
2. Setup email listener:
Create a email listener address mx4mail:
Go to select action menu, select security settings.
Add a row for workorder object:
Tick the Active checkbox and save the record:
3. Create an Escalation:
Create an escalation called MFMAILSENDWOM with the condition below:
exists (select 1 from mfmailst where mboname='WORKORDER' and origin=1 and workorder.status=status) and parent is null and owner is not null
Attach an out of the box action to send email for the work order:
Below is the definition of the MFMAILSENDWOM action from Actions application:
Steps to test Email Interaction:
1. Create a new work order 1273.
2. Click Set Owner icon on the toolbar. Assign the work order to Wilson:
3. Approve the work order:
4. Email arrives in Wilson's inbox:
5. Wilson reply with 2 to complete the work order:
6. Wait 1 minute. Wilson receives another email that says work order 1273 has been changed to complete status:
7. Log in to Maximo to confirm that work order 1273 has been changed to complete:
Email Interaction Setup Using Workflow
Steps to setup Email Interaction:
1. Create an Email Listener record mx4mail
Workflow Process = MFMAILRCV
Cron Task Name = LSNRCRON
Cron Task Instance = LSNR3
email interaction setup WFWO
Crontask instance LSNR3 is active in the Cron Task Setup application:
2. Build a workflow process in Workflow Designer to reinforce a business process:
For example: Create a workflow process called MFMAILWF
Newly created work order record will go to Financial Approval 1
If the estimated labor cost is greater than $500, then it will go to Financial approver 2
Then someone will perform some safety check:
3. Create a record in the Email Interaction Setup application:
Attach a communication template
For example, MFMAILRESCOMPWF:
Testing:
1. create a new work order in Work Order Tracking application
Route the record to workflow via the Route Workflow icon:
2. Wilson receives email in his in-box since he is the originator of the work order
option 1 - I approve this work order. Route to next step in workflow.
option 2 - Cancel this work order
3. Reply with 1:
4. Wilson receives some email that says the workflow assignment has been approved
Wilson receives another email with
option 1 - Initiate work - in progress
option 2 - Cancel this WO
5. Reply with 1 in the body:
i.e. Get Safety and Permit Approval
6. Wilson receives some email that says the workflow assignment has been approved:
7. Reply with 1:
8. Work Order 1275 has been changed to INPRG status
Go to select action menu > workflow > view workflow history:
This work order record has gone through the entire workflow without having a user logged into Maximo.
Workflow Process = MFMAILRCV
Cron Task Name = LSNRCRON
Cron Task Instance = LSNR3
email interaction setup WFWO
Crontask instance LSNR3 is active in the Cron Task Setup application:
2. Build a workflow process in Workflow Designer to reinforce a business process:
For example: Create a workflow process called MFMAILWF
Newly created work order record will go to Financial Approval 1
If the estimated labor cost is greater than $500, then it will go to Financial approver 2
Then someone will perform some safety check:
3. Create a record in the Email Interaction Setup application:
Attach a communication template
For example, MFMAILRESCOMPWF:
Testing:
1. create a new work order in Work Order Tracking application
Route the record to workflow via the Route Workflow icon:
2. Wilson receives email in his in-box since he is the originator of the work order
option 1 - I approve this work order. Route to next step in workflow.
option 2 - Cancel this work order
3. Reply with 1:
4. Wilson receives some email that says the workflow assignment has been approved
Wilson receives another email with
option 1 - Initiate work - in progress
option 2 - Cancel this WO
5. Reply with 1 in the body:
i.e. Get Safety and Permit Approval
6. Wilson receives some email that says the workflow assignment has been approved:
7. Reply with 1:
8. Work Order 1275 has been changed to INPRG status
Go to select action menu > workflow > view workflow history:
This work order record has gone through the entire workflow without having a user logged into Maximo.
New videos for Maximo Asset Management!
Check out the full library of Maxi
-
Syst
em i nsta llat ion and depl oyme nt V 7. 1- four presentations including: - NEW! Clone a Maximo 7.1.1 administrative workstation
- Building and deploying the maximo.ear
-
Syst
em i nsta llat ion and depl oyme nt V 7. 5 - five videos including - NEW! Clone a Maximo 7.5 administrative workstation
- NEW! Maximo 6.2 to 7.5 database upgrade process overview
-
Syst
em a nd a ppli cati on m anag emen t V7 . 1 - 19 videos including: - NEW! Using the report list portlet
-
Syst
em a nd a ppli cati on m anag emen t V7 . 5 - 12 videos including: - NEW! Using the report list portlet
- Understanding Maximo Asset Management inventory reorder calculations
-
Manual reorder process
-
Work
ord er m anag emen t V7 . 5 - two videos including: - NEW! How to use HARD and SOFT reservations in work order tracking
-
Work
ord er m anag emen t V7 . 1- four videos including: - Configuring work order status changes with the Automated Flow Control feature
Maximo 7.5 Performance Technotes links
SCCD 7.5.1 Performance Education Session
Correcting Slow User Queries
Maximo Performance Best Practices
Best Practices for System Performance 7.5
JVM Separation Process
Out Of Memory errors on the systemout.log
Database Connection leak
Using System Instance Properties to Control Cron Tasks
Parameters to improve Maximo performance using WebSphere
Stopping Data from Auto-populating List Tab
Configuring Autofill Properties
WebSphere 7.0 fixpack 27 or higher with Java SDK 1.6.0 SR12 Cumulative Fix
Understanding Memory Requirements For 32 And 64 Bit Systems
Understanding Search Methodologies
SQL SPECIFIC Technotes:
Maximo Performance on SQL Server - Turning off Page Locking
Maximo 7.5 on SQL Server out of memory and performance problems
httpThursday, March 27, 2014
UI framework event handling in Maximo
Application Event Model
Overview
Events are sent to the user interface framework whenever an end user
clicks a toolbar button in the application toolbar, selects an action
listed in the Select Action menu, clicks a push button within the user
interface, or selects an option from a menu next to a field. Many other
types of user interactions also send events to the user interface
framework, but those widgets previously listed are the ones that
application developers are mostly likely to configure.
This article explains what events are sent to the user Interface
framework when your end users interact with those types of widgets. We
will also explain how the user interface event handling framework
handles those events. This article should allow you adjust your user
interface to use a wide variety of widgets to fire and handle events to
best meet your end users usability needs.
Toolbar Button Events
Example "Save" Toolbar Button
Find the Signature Option that corresponds to the Save button
Select Action Menu Events
Example Menu Action “Duplicate Action”
Choosing a Select Action menu item causes the user Interface framework
to receive an event that matches the Signature Option id associated with
this Select Action menu item. In the example above, the user
Interface framework would receive an event called “DUPLICATE” based on
the details of the configured Signature Option as shown below.
Translating a Select Action to the Underlying Event
Configuring Push Button Events
Example Select Members Push Button
You can associate a push button with an event using the “Event” field
in Application Designer or using the “mxevent” attribute in the
presentation xml. You can optionally specify the ID of a control that
processes the event using the “Target ID” field in Application Designer
or “targetid” in the presentation xml.
When an end user clicks the button, the event ID specified in that
panel above “selectmembers” is received by the user interface event
handling framework.
Popup Menu Events
Each field-level popup menu has underlying mxevents associated with each of the menu choices.
Example Popup Menu
Configuration of Popup Menu for this Field
Actual Popup Menu for this Field (from Menus.xml)
Notice the events listed for each of the choices shown. That event
string is the event that gets sent to the underlying user Interface
framework when this menu choice is clicked.
User Interface Framework Event Handling
The user interface framework processes the event received in this order:
-
First the framework checks to see if the event matches a signature option (sigoption) ID.
- If the event does match, the user interface framework checks to see if the user has privileges for that signature option.
- If they do have security privileges, the framework checks to see if there is a special flag set to handle the Signature option in an Advanced way. If the Signature option does have a flag the user interface handles that flag accordingly. So if the Signature Option is flagged as an Action then the User Interface invokes that action. Here is an example of a menu option that would start a System Configuration->Platform Configuration->Action called “INSERT” for the Action object instead of firing the default INSERT event.
Setting Advanced Options to point a Signature option to an Action
The Underlying Action that would get called by the Advanced Sigoption Metadata Above
- If there is not an “Advanced” Flag for this sigoption then the framework checks the target control/component to see if it handles such an event (by implementing a method that matches the event name.) Events sent from Select Action and Toolbar buttons will rarely match this check as the target control/component for the Select Action and Toolbar buttons is the Application Toolbar, and it rarely handles the event directly.
- If the control or component doesn’t have a method that matches then the framework will check to see if the DataBean or ApplicationBean associated with the target component/control has such a method; if it does then that method will be called. The Select Action or Toolbar buttons are bound to the ApplicationBean, so will check there for a method that matches. Buttons and Button groups can be bound to other Databeans based on where they are placed within the application.
- If a targetid is not configured in the Application Designer for the events, the framework will check the Application Bean for the application to find a matching method.
Example Application Bean method to handle the INSERT signature option event
- If the Application Bean doesn’t contain a matching method, the Mbo and MboSet of the DataBean will be checked for a matching method as well.
- If no such method exists or the method returns the integer constant for EVENT_CONTINUE, the framework will then check to see if there is a dialog in the current application with a dialog id that matches the event name. If such a dialog exists then that dialog will be displayed.
- Finally the framework will check to see if there is a dialog in the System Libraries that has a dialog ID that matches the event, and it will display the dialog in that case.
If all of these checks fail, NOTHING will happen when the event is received by the user Interface framework.
Example
So putting all this information together, let’s go through the use case
where an Application Developer may want to add a button to the user
interface that would expose a functionality that is also exposed in the
Select Action menu. For example, in the Inventory application, let’s
add a button on the main Inventory tab that would trigger the 'Adjust
Current Balance' that is typically available only from the Select Action
menu.
First we’ll look at the Sigoptions defined in the Inventory application in Application Designer to find the right event:
Event is CURBALADJ
Drag and drop a button group and push button onto the main Inventory
tab and set the event to CURBALADJ to match the signature option above.
Configuring the Pushbutton Event and Label
Save the Application.
Now from within the Available Balance section, your end users can click
the Adjust Current Balance button and pop up that dialog.
Current Balance Adjustment window
With all the information you learned above, you could even put a
field-level menu next to the current balance that let you fire this
event (rather than a push button.)
Hopefully this explanation of the event model will help you enhance your user interfaces to meet your end user requirements.
More Detailed Information
Technically when the end user interacts with each of those widgets
above, a click event is sent to the component, and the component
translates that click event into a queued event that matches the
description given above. Sometimes to help debug issues in the field,
the user interface team might turn on javascript event tracking and you
might see these click events being sent from the client.
Customizing Headers with corporate colors and logo in Maximo
Steps
-
Locate your images in the folder structure - Within the
folder structure there may be multiple image locations that are used for
different skins and screen mirroring in bi-directional language
scenarios.
We have 3 general locations for left to right images. They are:
applications\maximo\maximouiweb\webmodule\webclient\images
applications\maximo\maximouiweb\webmodule\webclient\skins\mobile\images
applications\maximo\maximouiweb\webmodule\webclient\skins\tivoli09\images
Each of these folders also contains an rtl folder which holds the right-to-left version of the images for bi-directionality.
The mobile folder is used for mobile implementations and can be treated the same as the others. - Determine the skin your system is using - In 7.x, prior to 7.5 the default skin uses the css and images in the folders directly under the webclient folder. From 7.5 the tivoli09 skin is used and the corresponding folder will contain the images and css. If you are not sure which skin you are using see the skin images above to help you identify.
-
Locate and backup the images. Navigate to the folder for the
skin you are using and backup the two images discussed earlier as well
as applink images depending on skin:
tivoli09 - banner_bkg.png and banner_swoosh.png. banner_swoosh_applink.png and banner_bkg_applink.png
classic - bg_navbar.jpg and bg_navbar_applink.jpg -
Modify the images to have the coloring and look you desire -
Open the images in the image editor of your choice and edit them as
desired. Maintain the size of the images so that the layout will work
correctly. (for classic, you should also modify the 'bgnb' class and
change the background color to match with your new image)
-
Modify css classes to change text color if desired - Locate the appropriate css file within the same path as your used skin. Find maximo.css and look for the following classes:
powerwhite, goto, txtappname.
Change the color of these classes to the text color you desire. For classic skin, the application images can also be hidden by adding css:#appimage { display: none; }
and link images can be removed by adding
pwimg { display:none;} - Rebuild your ear file and re-deploy.
Subscribe to:
Posts (Atom)
-
Queues The IBM Maximo uses these queues for data integration purposes: Inbound sequential (sqin) - Maximo sequential queue used for...
-
Application Event Model Overview Events are sent to the user interface framework whenever an end user clicks a toolbar button in th...
-
Here is the sample code. ? 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23...
