Maximo Open Forum

I am currently working on a project with work orders (wotrack application), in the workorder database object there is a non-persistent attribute called jpclass (WO Class) which is used to look up job plans.

For some reason when I am creating a work order using wotrack, the WOCLASS is being set to WORKORDER which is what I would expect, but the jpclass does not contain the same value in fact it is NULL  The problem this causes is that the selection to add a job plan does not work.

The strange thing is this is working for the PLUSWOTR application (Work Order Tracking (Nuclear)).

This is only happening in the client's DEV environment and not in their test environment.  

What are the possible causes of a non-persistent attribute not being populated when a new record is being created, and could this be an application specific issue.

Hi @Stephen Hume!

In the application editor (WOTRACK), you can edit the WOCLASS field. You can put it read-only, default, required (I've seen it in all 3 ways). You can put a default value or not. So, if you define a default value, every time you create a new WO record, it will appear. If you do not define any default value and the field is released (defined as default), it will not load anything and will leave it released.

So, the difference is in the default value. You can modify this either by editing the wotrack xml or in the application designer on WOTRACK, by pressing "Toggle show conditional UI Control" (it will show you all the conditional controls with a black icon).

Regards!

I am currently working on a project with work orders (wotrack application), in the workorder database object there is a non-persistent attribute called jpclass (WO Class) which is used to look up job plans.

For some reason when I am creating a work order using wotrack, the WOCLASS is being set to WORKORDER which is what I would expect, but the jpclass does not contain the same value in fact it is NULL  The problem this causes is that the selection to add a job plan does not work.

The strange thing is this is working for the PLUSWOTR application (Work Order Tracking (Nuclear)).

This is only happening in the client's DEV environment and not in their test environment.  

What are the possible causes of a non-persistent attribute not being populated when a new record is being created, and could this be an application specific issue.

I am currently working on a project with work orders (wotrack application), in the workorder database object there is a non-persistent attribute called jpclass (WO Class) which is used to look up job plans.

For some reason when I am creating a work order using wotrack, the WOCLASS is being set to WORKORDER which is what I would expect, but the jpclass does not contain the same value in fact it is NULL  The problem this causes is that the selection to add a job plan does not work.

The strange thing is this is working for the PLUSWOTR application (Work Order Tracking (Nuclear)).

This is only happening in the client's DEV environment and not in their test environment.  

What are the possible causes of a non-persistent attribute not being populated when a new record is being created, and could this be an application specific issue.

I am currently working on a project with work orders (wotrack application), in the workorder database object there is a non-persistent attribute called jpclass (WO Class) which is used to look up job plans.

For some reason when I am creating a work order using wotrack, the WOCLASS is being set to WORKORDER which is what I would expect, but the jpclass does not contain the same value in fact it is NULL  The problem this causes is that the selection to add a job plan does not work.

The strange thing is this is working for the PLUSWOTR application (Work Order Tracking (Nuclear)).

This is only happening in the client's DEV environment and not in their test environment.  

What are the possible causes of a non-persistent attribute not being populated when a new record is being created, and could this be an application specific issue.

It's unlikely this class has any customisation. And since it only occurs in the DEV environment, I rule out it is a Maximo bug. I would try refreshing the DEV environment from Production first. If it doesn't help, two options I can think of are:

• Develop the feature in TEST
• Connect an IDE with Maximo DEV to do a live debug

I am currently working on a project with work orders (wotrack application), in the workorder database object there is a non-persistent attribute called jpclass (WO Class) which is used to look up job plans.

For some reason when I am creating a work order using wotrack, the WOCLASS is being set to WORKORDER which is what I would expect, but the jpclass does not contain the same value in fact it is NULL  The problem this causes is that the selection to add a job plan does not work.

The strange thing is this is working for the PLUSWOTR application (Work Order Tracking (Nuclear)).

This is only happening in the client's DEV environment and not in their test environment.  

What are the possible causes of a non-persistent attribute not being populated when a new record is being created, and could this be an application specific issue.