The developerWorks Connections platform will be sunset on January 2, 2020. This blog will no longer be available unless an extension has been requested. More details available on our FAQ.
with Tags:
maximo+7.1
X
X
Tracking Ticket Status by Taking Calendar and Shift into Account
Ticket records, i.e. service requests (SR), incidents, problems, have historical status data stored in TKSTATUS table. The duration between status change dates is calculated on STATUSTRACKING field of TKSTATUS table. This calculation is a simple subtraction of two dates which ignores the Calendar and Working Time (Shift) of the person changing the status of ticket. Below, you can see the original dialog which is opened via View History option from Select Actions of ticket applications (sr, incident, problem applications). < dialog id =... [More]
Tags: maximo+7.6 calendar problem sr sla incident shift maximo+7.1 maximo+7.5 controldesk maximo status servicerequest ticket statustracking |
Configuration for Filtering with Application ID and Sigoption ID within Applications Tab of Security Groups
By default, Maximo (or Control Desk) Security Groups application has a tab named Applications, which is used in order to grant Signature Options per application. We filter the applications and their signature options by their descriptions in this tab. But, we usually tend to memorize applications and the signature options by their IDs, i.e. App ID for Work Order Tracking application is wotrack . There are also many default or custom signature options defined for Work Order Tracking application such as READ , DUPLICATE , REPFACILITY , WMLINEAR... [More]
Tags: sccd application+designer controldesk+7.5 security maximo+7.5 maximo+7.1 controldesk+7.6 filter maximo controldesk sigoption securgroup maximo+7.6 application tablecolumn |
Object Level Configurative Action and Exception Structure similar to Automation Scripts (v7.1)
Maximo/Control Desk product introduced Automation Scripts instead of Java customizations on version 7.5 and enhanced the scripting functionality on version 7.6. Yet, there are many customer environments which have not been upgraded to latest versions. The following customization had been created for a customer environment which was in version 7.1. The aim of this development is to present a generic and configurative structure to replace and prevent continuous Java customization. 1. Adding the custom business objects to hold restriction... [More]
Tags: customization configuration maximo+7.1 action mbo tsrm java maximo exception object |
Personalizing Default and Visible Start Center Tabs on Maximo v7.1
Personalizing Start Center tabs for visible and default tabs is an improvement presented on version 7.5. Yet, with a simple xml customization same result can be achieved on version 7.1. Start Center Tabs are based on security groups, so it is an issue to personalize them for different users in same or different security groups in v7.1. System admins try to overcome this issue by duplicating security groups and start center templates and assigning different templates as default. The pop-up following the path Profile -> Personal Information... [More]
Tags: startcenter maximo+7.1 visible tab default maximo tsrm personalize primary |
