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.
I came accross this issue today and wanted to see if anyone else has encountered this problem.
Maximo 7.5.0
I've created a series of classificaitons for assets, created attributes for these classifications. All the orgs and sites match so no issues there. There is one parent and 18 different children under this parent classificaiton. There are 7 attributes at the parent level that are 'applied down hierarchy' to all classifications below.
The problem I am seeing is that for certain attributes the 'use description' and 'sequence' fields are read only. What is very strange about this - for other classifications within the same area of the hierarchy these field are modifable. Even when adding additional attributes to these child classifications, same issue (some are modifiable and others are not). I'll give you an example - I created a SUPPLY FAN and an EXHAUST FAN classification - both of which have the same exact attributes. For EXHAUST FAN some of the fields are unable to be modified that are modifiable in SUPPLY FAN.
There is no rationale as to why one classifications attributes are modifable and others are not - they are the same exact attributes.
Any thoughts?
Is it out of the box consistent & repeatable ? if so I'd report it
Rgds Ian
From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of john_gould14
Sent: 07 September 2012 13:50
To: MAXIMO@yahoogroups.com
Subject: [MAXIMO List] Classifications For Assets - Issues with 'Use Description' on Attributes
I came accross this issue today and wanted to see if anyone else has encountered this problem.
Maximo 7.5.0
I've created a series of classificaitons for assets, created attributes for these classifications. All the orgs and sites match so no issues there. There is one parent and 18 different children under this parent classificaiton. There are 7 attributes at the parent level that are 'applied down hierarchy' to all classifications below.
The problem I am seeing is that for certain attributes the 'use description' and 'sequence' fields are read only. What is very strange about this - for other classifications within the same area of the hierarchy these field are modifable. Even when adding additional attributes to these child classifications, same issue (some are modifiable and others are not). I'll give you an example - I created a SUPPLY FAN and an EXHAUST FAN classification - both of which have the same exact attributes. For EXHAUST FAN some of the fields are unable to be modified that are modifiable in SUPPLY FAN.
There is no rationale as to why one classifications attributes are modifable and others are not - they are the same exact attributes.
Any thoughts?
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.
**************************************************************************************************************
Out of the box to some extent. We did create some crossover functionality for use with work orders but for this particular example - the 'Use With' is for ASSETS. The problem is really that's it's completely inconsistent in terms of what attributes are modifiable and which are not. I've submitted a PMR as it really appears to be some sort of bug.
--- In MAXIMO@yahoogroups.com, Ian Wright <ian.wright@...> wrote:
>
> Is it out of the box consistent & repeatable ? if so I'd report it
>
> Rgds Ian
>
> From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of john_gould14
> Sent: 07 September 2012 13:50
> To: MAXIMO@yahoogroups.com
> Subject: [MAXIMO List] Classifications For Assets - Issues with 'Use Description' on Attributes
>
>
>
> I came accross this issue today and wanted to see if anyone else has encountered this problem.
>
> Maximo 7.5.0
>
> I've created a series of classificaitons for assets, created attributes for these classifications. All the orgs and sites match so no issues there. There is one parent and 18 different children under this parent classificaiton. There are 7 attributes at the parent level that are 'applied down hierarchy' to all classifications below.
>
> The problem I am seeing is that for certain attributes the 'use description' and 'sequence' fields are read only. What is very strange about this - for other classifications within the same area of the hierarchy these field are modifable. Even when adding additional attributes to these child classifications, same issue (some are modifiable and others are not). I'll give you an example - I created a SUPPLY FAN and an EXHAUST FAN classification - both of which have the same exact attributes. For EXHAUST FAN some of the fields are unable to be modified that are modifiable in SUPPLY FAN.
>
> There is no rationale as to why one classifications attributes are modifable and others are not - they are the same exact attributes.
>
> Any thoughts?
>
>
> 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.
> **************************************************************************************************************
>
>
>
>
>
Silly as it may sound, down here on v. 6.2.x, I've had issues where a few fields in ITEM would become read-only if the item description exceeded a certain length. I believe it was that I had extended the length of the field, and if the # of characters in an item description exceeded what had been the out-of-the-box length for the field, some behavior changed. Also, I think it mattered if the record had been created when we were on version 6.0 or on a later version (something somewhere in an upgrade from 6.0 onward made it go wacky).
Anyway, what I'd do if I were you is take a couple of records that you know work incorrectly and a couple of records that you know work correctly, and compare them side-by-side.
Are you using any Conditional UI statements?
Are you applying your classification to newly-created assets, or to assets that have been in the database for a while under a different classification or no classification at all? If the latter, try re-creating an existing asset, just to try it out. See if it misbehaves.
Travis Herron
--- In MAXIMO@yahoogroups.com, "john_gould14" <john_gould14@...> wrote:
>
> Out of the box to some extent. We did create some crossover functionality for use with work orders but for this particular example - the 'Use With' is for ASSETS. The problem is really that's it's completely inconsistent in terms of what attributes are modifiable and which are not. I've submitted a PMR as it really appears to be some sort of bug.
>
> --- In MAXIMO@yahoogroups.com, Ian Wright <ian.wright@> wrote:
> >
> > Is it out of the box consistent & repeatable ? if so I'd report it
> >
> > Rgds Ian
> >
> > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of john_gould14
> > Sent: 07 September 2012 13:50
> > To: MAXIMO@yahoogroups.com
> > Subject: [MAXIMO List] Classifications For Assets - Issues with 'Use Description' on Attributes
> >
> >
> >
> > I came accross this issue today and wanted to see if anyone else has encountered this problem.
> >
> > Maximo 7.5.0
> >
> > I've created a series of classificaitons for assets, created attributes for these classifications. All the orgs and sites match so no issues there. There is one parent and 18 different children under this parent classificaiton. There are 7 attributes at the parent level that are 'applied down hierarchy' to all classifications below.
> >
> > The problem I am seeing is that for certain attributes the 'use description' and 'sequence' fields are read only. What is very strange about this - for other classifications within the same area of the hierarchy these field are modifable. Even when adding additional attributes to these child classifications, same issue (some are modifiable and others are not). I'll give you an example - I created a SUPPLY FAN and an EXHAUST FAN classification - both of which have the same exact attributes. For EXHAUST FAN some of the fields are unable to be modified that are modifiable in SUPPLY FAN.
> >
> > There is no rationale as to why one classifications attributes are modifable and others are not - they are the same exact attributes.
> >
> > Any thoughts?
> >
> >
> > 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.
> > **************************************************************************************************************
> >
> >
> >
> >
> >
>
Travis,
Thanks for the note. These newly created classifications have not been applied to any assets yet - I'm only still within the classification application. I am not utilizing any conditional UI statments. These are very vanilla classificaitons. As I said, the issue really centers around the attributes not having similar behavior between different classificaitons of the same type (i.e. classifications for use with ASSET).
-John
--- In MAXIMO@yahoogroups.com, "Travis Herron" <therron@...> wrote:
>
> Silly as it may sound, down here on v. 6.2.x, I've had issues where a few fields in ITEM would become read-only if the item description exceeded a certain length. I believe it was that I had extended the length of the field, and if the # of characters in an item description exceeded what had been the out-of-the-box length for the field, some behavior changed. Also, I think it mattered if the record had been created when we were on version 6.0 or on a later version (something somewhere in an upgrade from 6.0 onward made it go wacky).
>
> Anyway, what I'd do if I were you is take a couple of records that you know work incorrectly and a couple of records that you know work correctly, and compare them side-by-side.
>
> Are you using any Conditional UI statements?
>
> Are you applying your classification to newly-created assets, or to assets that have been in the database for a while under a different classification or no classification at all? If the latter, try re-creating an existing asset, just to try it out. See if it misbehaves.
>
>
> Travis Herron
>
> --- In MAXIMO@yahoogroups.com, "john_gould14" <john_gould14@> wrote:
> >
> > Out of the box to some extent. We did create some crossover functionality for use with work orders but for this particular example - the 'Use With' is for ASSETS. The problem is really that's it's completely inconsistent in terms of what attributes are modifiable and which are not. I've submitted a PMR as it really appears to be some sort of bug.
> >
> > --- In MAXIMO@yahoogroups.com, Ian Wright <ian.wright@> wrote:
> > >
> > > Is it out of the box consistent & repeatable ? if so I'd report it
> > >
> > > Rgds Ian
> > >
> > > From: MAXIMO@yahoogroups.com [mailto:MAXIMO@yahoogroups.com] On Behalf Of john_gould14
> > > Sent: 07 September 2012 13:50
> > > To: MAXIMO@yahoogroups.com
> > > Subject: [MAXIMO List] Classifications For Assets - Issues with 'Use Description' on Attributes
> > >
> > >
> > >
> > > I came accross this issue today and wanted to see if anyone else has encountered this problem.
> > >
> > > Maximo 7.5.0
> > >
> > > I've created a series of classificaitons for assets, created attributes for these classifications. All the orgs and sites match so no issues there. There is one parent and 18 different children under this parent classificaiton. There are 7 attributes at the parent level that are 'applied down hierarchy' to all classifications below.
> > >
> > > The problem I am seeing is that for certain attributes the 'use description' and 'sequence' fields are read only. What is very strange about this - for other classifications within the same area of the hierarchy these field are modifable. Even when adding additional attributes to these child classifications, same issue (some are modifiable and others are not). I'll give you an example - I created a SUPPLY FAN and an EXHAUST FAN classification - both of which have the same exact attributes. For EXHAUST FAN some of the fields are unable to be modified that are modifiable in SUPPLY FAN.
> > >
> > > There is no rationale as to why one classifications attributes are modifable and others are not - they are the same exact attributes.
> > >
> > > Any thoughts?
> > >
> > >
> > > 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.
> > > **************************************************************************************************************
> > >
> > >
> > >
> > >
> > >
> >
>