Maximo Open Forum

 View Only
  • 1.  Workflow Options and Actions for Condition nodes

    Posted 12-21-2021 19:03
    Hi folks

    I have a workflow condition that checks that the Supervisor field (in work orders) is not null, workflow message prompts user to add a value when the condition resolves to false and workflow stops.  What the user is requesting is that Maximo automatically opens the person lookup associated with the Supervisor field, and ideally as a function of workflow rather than exiting workflow.

    Does anybody have any suggestion/example of how this can be facilitated

    Thanks in advance

    Cheers
    #EverythingMaximo

    ------------------------------
    Peter McDonald
    Prima58
    ------------------------------


  • 2.  RE: Workflow Options and Actions for Condition nodes

    Posted 12-28-2021 10:53
    Not sure that there's a way (OOTB) to automatically open the lookup, but for starters this is what I'd do:

    • leave your condition node as-is
    • when it resolves to false, connect that to an Interaction node instructing the User to fill in the Supervisor field (make sure to select the "Display One?" option)
    • then have a Task node for the USER role (at least that sounds like what's needed, from what you wrote)
    • have just one positive line exiting the Task node, and connect it back to your condition node -- this time it would resolve to TRUE and proceed through the Workflow (assuming USER followed your instructions -- but if not, it's right back to USER until the instructions are followed correctly)

    Now on that Interaction Node's exiting line, I feel like maybe there would be a way to have an Action that calls an Automation Script that would open the dialog.  I'm using How to create an automation script to retrive a lookup list (ibm.com) as a reference, but that uses an Attribute Launchpoint where we have the Retrieve List option, but we need an Action Launchpoint Script.  Is there a way to create a (Action Launchpoint) Script that runs a (Attribute Launchpoint) Script?  Probably, but I've not done that before.

    If that doesn't work, a much-less-elegant option might be to put a Set Value Action on that Interaction Node's connecting line.  Set the value of the Supervisor field to something ludicrous.  That should at least force an error when it does the field validation, and the user won't be able to Save until it's corrected.

    Completely alternatively, maybe you could use a Conditional Expression to make sure the Supervisor field is not null, especially if the next "thing" in the Workflow is a Status Change.

    ------------------------------
    Travis Herron
    Pensacola Christian College
    ------------------------------



  • 3.  RE: Workflow Options and Actions for Condition nodes

    Posted 12-30-2021 03:11
    Hi Travis

    Thanks for your feedback, automation scripting is not my forte but I get where you're coming from.  I'm curious about your suggestion to add a bogus entry as a set value action though, I tried it and it throws a Maximo error (BMXAA3097E) and thought that perhaps I could trigger the lookup as a System Action on the error message, again, something I'm not familiar with but could be a good option.  If you have any thoughts on that approach, happy to hear them, thanks

    Cheers
    Peter

    ------------------------------
    Peter McDonald
    Prima58
    ------------------------------