Maximo Open Forum

One of our users asked about this this morning.  To provide the capability, did the following:

In Application Designer > Job Plans:

• add a signature option JP_DUP with the "UI action" flag set.
• update Select Action menu to replace the DUPLICATE option with JP_DUP

In Security Groups:

• Locate an appropriate security group (for testing, EVERYONE works usually) and grant the JP_DUP signature option for Job Plans

In Automation Scripts:

• Create an Action launch point JP_DUP and associate with a script JP_DUP
• Set the script code as follows:

from psdi.mbo import MboConstants;

## get context
session = service.webclientsession(); ## we need the session so we can get the app bean
appbean = session.getCurrentApp().getAppBean(); ## get the app bean

appbean.DUPLICATE(); ## call the DUPLICATE function as if the user would have

## after DUPLICATE, the screen is displaying the "new" job plan
mbo = appbean.getMbo(); ## pull that into 'mbo'
mbo.setFieldFlag("SITEID", MboConstants.READONLY, False); ## undo read-only
mbo.setFieldFlag("SITEID", MboConstants.REQUIRED, True);  ## make sure required is shown

Finally:

• Sign off / sign on (new security grants take effect)
• Test

Nice solution Jade!

There's also a way to do this without having to modify the menu options. If you create your automation script with the OBJECT.DUPLICATE name (in your case JOBPLAN.DUPLICATE), Maximo will automatically fire the script whenever a Job Plan is duplicated. Within the script there will be two implicit variables: 1) mbo, which represents the record being copied, and 2) dupmbo, which represents the newly copied record. You should then be able to trim the script down to something like:

from psdi.mbo import MboConstants## after DUPLICATE, dupmbo represents new recorddupmbo.setFieldFlag("SITEID", MboConstants.READONLY, False)  ## undo read-onlydupmbo.setFieldFlag("SITEID", MboConstants.REQUIRED, True)   ## make required

Hope this helps,

One of our users asked about this this morning.  To provide the capability, did the following:

In Application Designer > Job Plans:

• add a signature option JP_DUP with the "UI action" flag set.
• update Select Action menu to replace the DUPLICATE option with JP_DUP

In Security Groups:

• Locate an appropriate security group (for testing, EVERYONE works usually) and grant the JP_DUP signature option for Job Plans

In Automation Scripts:

• Create an Action launch point JP_DUP and associate with a script JP_DUP
• Set the script code as follows:

from psdi.mbo import MboConstants;

## get context
session = service.webclientsession(); ## we need the session so we can get the app bean
appbean = session.getCurrentApp().getAppBean(); ## get the app bean

appbean.DUPLICATE(); ## call the DUPLICATE function as if the user would have

## after DUPLICATE, the screen is displaying the "new" job plan
mbo = appbean.getMbo(); ## pull that into 'mbo'
mbo.setFieldFlag("SITEID", MboConstants.READONLY, False); ## undo read-only
mbo.setFieldFlag("SITEID", MboConstants.REQUIRED, True);  ## make sure required is shown

Finally:

• Sign off / sign on (new security grants take effect)
• Test

Hi Alex!

I did try the JOBPLAN.DUPLICATE approach first because it is far more elegant--but for reasons unknown to me, the screen did NOT refresh (i.e. the Site field remained read-only).

:o) Jade

Nice solution Jade!

There's also a way to do this without having to modify the menu options. If you create your automation script with the OBJECT.DUPLICATE name (in your case JOBPLAN.DUPLICATE), Maximo will automatically fire the script whenever a Job Plan is duplicated. Within the script there will be two implicit variables: 1) mbo, which represents the record being copied, and 2) dupmbo, which represents the newly copied record. You should then be able to trim the script down to something like:

from psdi.mbo import MboConstants## after DUPLICATE, dupmbo represents new recorddupmbo.setFieldFlag("SITEID", MboConstants.READONLY, False)  ## undo read-onlydupmbo.setFieldFlag("SITEID", MboConstants.REQUIRED, True)   ## make required

Hope this helps,

One of our users asked about this this morning.  To provide the capability, did the following:

In Application Designer > Job Plans:

• add a signature option JP_DUP with the "UI action" flag set.
• update Select Action menu to replace the DUPLICATE option with JP_DUP

In Security Groups:

• Locate an appropriate security group (for testing, EVERYONE works usually) and grant the JP_DUP signature option for Job Plans

In Automation Scripts:

• Create an Action launch point JP_DUP and associate with a script JP_DUP
• Set the script code as follows:

from psdi.mbo import MboConstants;

## get context
session = service.webclientsession(); ## we need the session so we can get the app bean
appbean = session.getCurrentApp().getAppBean(); ## get the app bean

appbean.DUPLICATE(); ## call the DUPLICATE function as if the user would have

## after DUPLICATE, the screen is displaying the "new" job plan
mbo = appbean.getMbo(); ## pull that into 'mbo'
mbo.setFieldFlag("SITEID", MboConstants.READONLY, False); ## undo read-only
mbo.setFieldFlag("SITEID", MboConstants.REQUIRED, True);  ## make sure required is shown

Finally:

• Sign off / sign on (new security grants take effect)
• Test

One of our users asked about this this morning.  To provide the capability, did the following:

In Application Designer > Job Plans:

• add a signature option JP_DUP with the "UI action" flag set.
• update Select Action menu to replace the DUPLICATE option with JP_DUP

In Security Groups:

• Locate an appropriate security group (for testing, EVERYONE works usually) and grant the JP_DUP signature option for Job Plans

In Automation Scripts:

• Create an Action launch point JP_DUP and associate with a script JP_DUP
• Set the script code as follows:

from psdi.mbo import MboConstants;

## get context
session = service.webclientsession(); ## we need the session so we can get the app bean
appbean = session.getCurrentApp().getAppBean(); ## get the app bean

appbean.DUPLICATE(); ## call the DUPLICATE function as if the user would have

## after DUPLICATE, the screen is displaying the "new" job plan
mbo = appbean.getMbo(); ## pull that into 'mbo'
mbo.setFieldFlag("SITEID", MboConstants.READONLY, False); ## undo read-only
mbo.setFieldFlag("SITEID", MboConstants.REQUIRED, True);  ## make sure required is shown

Finally:

• Sign off / sign on (new security grants take effect)
• Test