This is an archive of the Maximo Yahoo Community. The content of this pages may be a sometimes obsolete so please check post dates.
Thanks to the community owner Christopher Wanko for providing the content.
All,
I need to get some expert Maximo opinions on an issue that we have recently run into. We have several custom attributes added to the LOCATIONS object. Many of these custom attributes are only conditionally applicable to any given location record based on the value of another custom attribute (essentially a category). So we have custom code in place that sets these attributes to read only and null based on the value of the category. This works perfectly for us. However recently we started updating locations records through the MIF and then we ran into a problem. What is happening is that for the attributes that we are conditionally setting to read only based on the category, the MIF is allowing values to be entered into the attributes that we have set to read only through the custom code. While it is easy to correct the data, I'm concerned about things like this occurring again in the future.
We've opened a PMR with IBM and their response is not exactly to our liking. What they have told us is that the MIF basically ignores the read only property on an attribute and allows data to be entered. They gave us several justifications for this behavior, including that it would have been impossible in the early days of the MEA when it was PL/SQL. My understanding has always been that the reason to use the MIF rather than just pumping crap in through the back end was that it filtered through your business logic. Basically their bottom line is that if we want this changed we are going to have to put in an enhancement request, which I am considering.
I'm wondering if anyone else has ever run into similar situations or if anyone has any thoughts on the subject. I'm also looking for honest opinions on whether my line of reason is correct in general, that I should be able to rely on the MIF to apply my business logic to incoming data.
Thanks!
Chris A Hanna, CTR
Application Programmer
Digital Management Inc.
US Coast Guard Operations Systems Center
christopher.a.hanna@uscg.mil
(304)433-3234
Chris,
How about having a 'Processing Rule' for the Enterprise Service that 'sets' the 2nd attribute based on Integration Control values for the first. You can even null out the second value for conditions in which you are making it readonly on the screen. Let me know if you need more clarification.
Dinesh
--- In MAXIMO@yahoogroups.com, "Hanna, Christopher CTR" <christopher.a.hanna@...> wrote:
>
> All,
> I need to get some expert Maximo opinions on an issue that we have recently run into. We have several custom attributes added to the LOCATIONS object. Many of these custom attributes are only conditionally applicable to any given location record based on the value of another custom attribute (essentially a category). So we have custom code in place that sets these attributes to read only and null based on the value of the category. This works perfectly for us. However recently we started updating locations records through the MIF and then we ran into a problem. What is happening is that for the attributes that we are conditionally setting to read only based on the category, the MIF is allowing values to be entered into the attributes that we have set to read only through the custom code. While it is easy to correct the data, I'm concerned about things like this occurring again in the future.
>
> We've opened a PMR with IBM and their response is not exactly to our liking. What they have told us is that the MIF basically ignores the read only property on an attribute and allows data to be entered. They gave us several justifications for this behavior, including that it would have been impossible in the early days of the MEA when it was PL/SQL. My understanding has always been that the reason to use the MIF rather than just pumping crap in through the back end was that it filtered through your business logic. Basically their bottom line is that if we want this changed we are going to have to put in an enhancement request, which I am considering.
>
> I'm wondering if anyone else has ever run into similar situations or if anyone has any thoughts on the subject. I'm also looking for honest opinions on whether my line of reason is correct in general, that I should be able to rely on the MIF to apply my business logic to incoming data.
>
> Thanks!
>
> Chris A Hanna, CTR
> Application Programmer
> Digital Management Inc.
> US Coast Guard Operations Systems Center
> christopher.a.hanna@...
> (304)433-3234
>
Yes, that may be a viable workaround temporarily and was suggested by IBM. However what I want to avoid if I can is needing to have multiple pieces of code in order to implement the same business rule because that just creates a maintenance nightmare.
Thanks!
-Chris H
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of dinesh_t_shenoy
Sent: Wednesday, August 01, 2012 11:25 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Re: Read only attributes in the MIF
Chris,
How about having a 'Processing Rule' for the Enterprise Service that 'sets' the 2nd attribute based on Integration Control values for the first. You can even null out the second value for conditions in which you are making it readonly on the screen. Let me know if you need more clarification.
Dinesh
--- In MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> , "Hanna, Christopher CTR" <christopher.a.hanna@...> wrote:
>
> All,
> I need to get some expert Maximo opinions on an issue that we have recently run into. We have several custom attributes added to the LOCATIONS object. Many of these custom attributes are only conditionally applicable to any given location record based on the value of another custom attribute (essentially a category). So we have custom code in place that sets these attributes to read only and null based on the value of the category. This works perfectly for us. However recently we started updating locations records through the MIF and then we ran into a problem. What is happening is that for the attributes that we are conditionally setting to read only based on the category, the MIF is allowing values to be entered into the attributes that we have set to read only through the custom code. While it is easy to correct the data, I'm concerned about things like this occurring again in the future.
>
> We've opened a PMR with IBM and their response is not exactly to our liking. What they have told us is that the MIF basically ignores the read only property on an attribute and allows data to be entered. They gave us several justifications for this behavior, including that it would have been impossible in the early days of the MEA when it was PL/SQL. My understanding has always been that the reason to use the MIF rather than just pumping crap in through the back end was that it filtered through your business logic. Basically their bottom line is that if we want this changed we are going to have to put in an enhancement request, which I am considering.
>
> I'm wondering if anyone else has ever run into similar situations or if anyone has any thoughts on the subject. I'm also looking for honest opinions on whether my line of reason is correct in general, that I should be able to rely on the MIF to apply my business logic to incoming data.
>
> Thanks!
>
> Chris A Hanna, CTR
> Application Programmer
> Digital Management Inc.
> US Coast Guard Operations Systems Center christopher.a.hanna@...
> (304)433-3234
>
MIF can't be expected to know what the user interface is doing
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Hanna, Christopher CTR
Sent: 01 August 2012 14:28
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Read only attributes in the MIF
All,
I need to get some expert Maximo opinions on an issue that we have recently run into. We have several custom attributes added to the LOCATIONS object. Many of these custom attributes are only conditionally applicable to any given location record based on the value of another custom attribute (essentially a category). So we have custom code in place that sets these attributes to read only and null based on the value of the category. This works perfectly for us. However recently we started updating locations records through the MIF and then we ran into a problem. What is happening is that for the attributes that we are conditionally setting to read only based on the category, the MIF is allowing values to be entered into the attributes that we have set to read only through the custom code. While it is easy to correct the data, I'm concerned about things like this occurring again in the future.
We've opened a PMR with IBM and their response is not exactly to our liking. What they have told us is that the MIF basically ignores the read only property on an attribute and allows data to be entered. They gave us several justifications for this behavior, including that it would have been impossible in the early days of the MEA when it was PL/SQL. My understanding has always been that the reason to use the MIF rather than just pumping crap in through the back end was that it filtered through your business logic. Basically their bottom line is that if we want this changed we are going to have to put in an enhancement request, which I am considering.
I'm wondering if anyone else has ever run into similar situations or if anyone has any thoughts on the subject. I'm also looking for honest opinions on whether my line of reason is correct in general, that I should be able to rely on the MIF to apply my business logic to incoming data.
Thanks!
Chris A Hanna, CTR
Application Programmer
Digital Management Inc.
US Coast Guard Operations Systems Center
christopher.a.hanna@uscg.mil<mailto:christopher.a.hanna%40uscg.mil>
(304)433-3234
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
**************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.
**************************************************************************************************************
Just to clarify, this has nothing to do with the user interface, these are conditionally set at the MBO layer, NOT the UI layer.
Thanks!
-Chris H
-----Original Message-----
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Ian Wright
Sent: Thursday, August 02, 2012 3:57 AM
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] RE: Read only attributes in the MIF
MIF can't be expected to know what the user interface is doing
From: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com> ] On Behalf Of Hanna, Christopher CTR
Sent: 01 August 2012 14:28
To: MAXIMO@yahoogroups.com <mailto:MAXIMO%40yahoogroups.com>
Subject: [MAXIMO List] Read only attributes in the MIF
All,
I need to get some expert Maximo opinions on an issue that we have recently run into. We have several custom attributes added to the LOCATIONS object. Many of these custom attributes are only conditionally applicable to any given location record based on the value of another custom attribute (essentially a category). So we have custom code in place that sets these attributes to read only and null based on the value of the category. This works perfectly for us. However recently we started updating locations records through the MIF and then we ran into a problem. What is happening is that for the attributes that we are conditionally setting to read only based on the category, the MIF is allowing values to be entered into the attributes that we have set to read only through the custom code. While it is easy to correct the data, I'm concerned about things like this occurring again in the future.
We've opened a PMR with IBM and their response is not exactly to our liking. What they have told us is that the MIF basically ignores the read only property on an attribute and allows data to be entered. They gave us several justifications for this behavior, including that it would have been impossible in the early days of the MEA when it was PL/SQL. My understanding has always been that the reason to use the MIF rather than just pumping crap in through the back end was that it filtered through your business logic. Basically their bottom line is that if we want this changed we are going to have to put in an enhancement request, which I am considering.
I'm wondering if anyone else has ever run into similar situations or if anyone has any thoughts on the subject. I'm also looking for honest opinions on whether my line of reason is correct in general, that I should be able to rely on the MIF to apply my business logic to incoming data.
Thanks!
Chris A Hanna, CTR
Application Programmer
Digital Management Inc.
US Coast Guard Operations Systems Center christopher.a.hanna@uscg.mil <mailto:christopher.a.hanna%40uscg.mil> <mailto:christopher.a.hanna%40uscg.mil>
(304)433-3234
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
**************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.
**************************************************************************************************************
So let me get this clear
You have field A & B, field B is read only if you select for arguments sake the value 'TRUE'
So I presume if you enter a value in field B and then set field A to 'TRUE' it will also set field B to Null
If this is the case I would expect the MBO to behave the same through the MIF if it doesn't then I think you have a case
It depends on your stance in my opinion for what is worth when you set a field to read-only its interacting with the user interface
Rgds Ian
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of Hanna, Christopher CTR
Sent: 02 August 2012 12:10
To: MAXIMO@yahoogroups.com
Subject: RE: [MAXIMO List] RE: Read only attributes in the MIF
Just to clarify, this has nothing to do with the user interface, these are conditionally set at the MBO layer, NOT the UI layer.
Thanks!
-Chris H
-----Original Message-----
From: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>] On Behalf Of Ian Wright
Sent: Thursday, August 02, 2012 3:57 AM
To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com>
Subject: [MAXIMO List] RE: Read only attributes in the MIF
MIF can't be expected to know what the user interface is doing
From: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com> <mailto:MAXIMO%40yahoogroups.com> [mailto:MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com> <mailto:MAXIMO%40yahoogroups.com> ] On Behalf Of Hanna, Christopher CTR
Sent: 01 August 2012 14:28
To: MAXIMO@yahoogroups.com<mailto:MAXIMO%40yahoogroups.com> <mailto:MAXIMO%40yahoogroups.com>
Subject: [MAXIMO List] Read only attributes in the MIF
All,
I need to get some expert Maximo opinions on an issue that we have recently run into. We have several custom attributes added to the LOCATIONS object. Many of these custom attributes are only conditionally applicable to any given location record based on the value of another custom attribute (essentially a category). So we have custom code in place that sets these attributes to read only and null based on the value of the category. This works perfectly for us. However recently we started updating locations records through the MIF and then we ran into a problem. What is happening is that for the attributes that we are conditionally setting to read only based on the category, the MIF is allowing values to be entered into the attributes that we have set to read only through the custom code. While it is easy to correct the data, I'm concerned about things like this occurring again in the future.
We've opened a PMR with IBM and their response is not exactly to our liking. What they have told us is that the MIF basically ignores the read only property on an attribute and allows data to be entered. They gave us several justifications for this behavior, including that it would have been impossible in the early days of the MEA when it was PL/SQL. My understanding has always been that the reason to use the MIF rather than just pumping crap in through the back end was that it filtered through your business logic. Basically their bottom line is that if we want this changed we are going to have to put in an enhancement request, which I am considering.
I'm wondering if anyone else has ever run into similar situations or if anyone has any thoughts on the subject. I'm also looking for honest opinions on whether my line of reason is correct in general, that I should be able to rely on the MIF to apply my business logic to incoming data.
Thanks!
Chris A Hanna, CTR
Application Programmer
Digital Management Inc.
US Coast Guard Operations Systems Center christopher.a.hanna@uscg.mil<mailto:christopher.a.hanna%40uscg.mil> <mailto:christopher.a.hanna%40uscg.mil> <mailto:christopher.a.hanna%40uscg.mil>
(304)433-3234
GDF SUEZ E&P UK Ltd (Company Number 3386464), registered in England and Wales with a registered office address at: 40 Holborn Viaduct, London, EC1N 2PB.
**************************************************************************************************************
This email and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed.
If you have received this email in error please notify the system manager.
This footnote also confirms that this email message has been swept by MIMEsweeper for the presence of computer viruses.
**************************************************************************************************************