Change status using Integration Framework ---->>> Integration Framework : Application Import and Export
Integration Framework : Application Import and Export & Change status
This feature supports the import and export of data directly from applications, such as PO orWork Orders. This allows users to perform import and export of data without having to having access to the I-F External System application
User can just export the application and do the required modification in the application without approaching I-f external system
New functionality allows the user to export the data to a formatted file that can be maintained in an Excel spreadsheet. The user can apply changes across one or more rows of data in the spreadsheet and when completed, the data can be imported back into Maximo.
The application-based import and export functionality relies on the object structure component of the integration framework to define the data content and any processing classes (Java) that are needed to facilitate the exporting and importing of data. No other integration framework components (such as publish channels, JMS queues & end points) need to be configured. Administrator will enable the integration for an application using a provided object structure or by creating a new object structure.
Use the following steps to duplicate the MXPO object structure:
1 . From the Maximo Admin Console select ‘Go To’ -> ‘Integration’ > Object Structures’
2 . Click on the ‘Object Structure’ tab
3 . Type ‘MXPO’ in the ‘Find’ dialog.
4 . Press Return. The MXPO Object Structure will be displayed.
5 . In the ‘Select Action’ drop down box, choose ‘Duplicate Object Structure’.
6 . Assuming you duplicated MXPO and created NEWMXPO, based on your user’s requirements, you could delete all the objects except PO
7 . Once that is done your user may also want to limit the number of Po fields that are available. PO , by default has over 80 fields in the object and having a spreadsheet with that many columns can be difficult to maintain.Your user may only want/need to use up to 20 fields.
8 . To support this, the object structure application has a Select Action, Include/Exclude Fields, that allows the administrator to define which persistent and non-persistent fields are to be included in the data that is exported and imported.
9 . If you are exporting in flatfiles file formate the go for Add/Modify Alias of select action , to assign unique field name where there are currently duplicates..
10 . From Select Action, click on Add/Modify Application Export Support, that allows you to enable exporting to an application
11 . In the dialog (above), select New Row and the application will default to an application that has a main object that is the same as PO . The Default File Type can be set so that your user will not have to select this object structure each time.
12 . Select Action, Add/Modify Application Import Support, that allows you to enable importing to an application (save the object structure before using this Select Action).
13 . In the dialog (above), select New Row and the application will default to an application that has a main object that is the same as PO . The Default File Type can be set so that your user will not have to select this object structure each time. So if your users will primarily use the data in a spreadsheet you should select Flat File.
Use the following steps to Grant Security access:
1. From the Maximo Admin console select ‘Go To’ -> ‘Security Groups’
2. Select ‘Application’ tag
3. Select ‘Asset’ Application
4. Select ‘Application Import’ and application export
5. Check the ‘Grant Access’ box
6. Select the ‘Save’ icon
7. logout and login
8. you can see import and export icons in your applications
Steps to follow while exporting :
1 . Select new record and fill all the required values
2 . Save the record
3 . Now click export application icon to export the data and fill the details .such as name of object structure which we have created and configuration format
4 . Save the downloaded xml file
5 . Open the downloaded xml file in edit++ Let us change the status of record to approve and any other updates let it be description
Steps to follow while importing :
6 .Now we need to import the xml modified by us
7 . Open po and click on application import .select the object structure and import configuration
8 . Click ok to start importing
9 . You can see th changes by opening the po 1009 status as appr and description as purchase order for my organization
ALL the best
Customizing Headers with corporate colors and logo in maximo
To
Steps to follow:
1 .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
applications\maximo\maximouiweb\webmodule\webclient\skins\mobile\images
applications\maximo\maximouiweb\webmodule\webclient\skins\tivoli09\images
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.
3 .Locate and backup the images. Navigate to the folder for the skin you are using and backup the images shown below:
tivoli09 - banner_bkg.png --> size 205 bytes resolution 1*45
banner_swoosh.png size --> 15kb resolution 557*45
banner_swoosh_applink.png --> size 15kb resolution 557*45
banner_bkg_applink.png --> size 195bytes resolution 557*45
4 .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.
5 .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.
6.Rebuild your ear file and re-deploy
clear the history and cookies ,cache
Mbo Constants in maximo
Function | Value | Explanation |
All rows | 10000000 | Constant used to fetch all rows from a MboSet |
Change by user | 16L | Used to indicate that the user has changed a field from the user interface. |
Count addition | 2 | Count Constant used to count records recently added to the MboSet. Counts new Mbos whether or not they have been deleted. |
Count after save | 16 | Count Constant used to count records that would be left if a save was done now. |
Count data base | 1 | Count Constant used to count records in the database only. |
Count deleted | 4 | Count Constant used to count records deleted from the MboSet. Counts Mbos deleted from the database and Mbos recently added and then deleted. |
Count existing | 8 | Count Constant used to count the number of potential Mbos in the set. Includes number of records in the database plus additions. |
Delay validation | 4L | Delay validation |
Discardable | 39L | Bit for discardable mbos. Discardable mbos are always read-only. If a Mbo set is marked as DISCARDABLE, then the mbo set does not cache the mbos as it fetches from the database. |
No related mbos of owners children fetch | 16L | Internal bit for allowing only one level of related mbos of owner children access. |
No access check | 2L | Suppress access control checks |
No action | 8L | Used to suppress action of a field |
No add | 1L | Bit for add access |
No commit | 2L | Constant to indicate whether to commit to the database as part of the save or not. |
No delete | 4L | Bit for delete access |
Non | 0L | General value used to denote no value |
No save | 8L | Bit for no-save access |
No set value | 32L | Similar to the READONLY, except that no exception is thrown and the setValue() calls are suppressed. Used as an internal flag to prevent setValue() calls on field values set with DELAYVALIDATION flag |
No update | 2L | Can the object be changed. This is the same as the READONLY flag. |
No validation | 1L | Used to suppress validation of a field |
No validation and no action | 9L | Used to suppress validation and action |
Read only | 7L | Is read only ! |
Rebuild | 1L | Constant used to indicate whether to rebuild a MboSet after commit. |
Required | 8L | Bit for setting the field required |
Same value validation | 16L | Bit for Same value validation. setValue() call with the same value causes validation to occur, if this flag is set. |
User | 256L | Bits upwards from this value can be used for user defined purposes |
Subscribe to:
Posts (Atom)