Topic
IC4NOTICE: developerWorks Community will be offline May 29-30, 2015 while we upgrade to the latest version of IBM Connections. For more information, read our upgrade FAQ.
2 replies Latest Post - ‏2012-10-11T12:17:29Z by maxmix
SystemAdmin
SystemAdmin
5842 Posts
ACCEPTED ANSWER

Pinned topic Restrict user from canceling desktop requisition when any PR on MRLINEs

‏2012-10-08T15:55:09Z |
Hi
I need help on applying a condition on desktop requisitions to prevent any user from changing its status to CAN(cancel) for any purchase requisitions have been created on the desktop requisitions(DR's) on it's MRLINES.

I am using Maximo 7.1.1.6 with redhat linux server.

Your help will be greatly appreciated.
Updated on 2012-10-11T12:17:29Z at 2012-10-11T12:17:29Z by maxmix
  • SystemAdmin
    SystemAdmin
    5842 Posts
    ACCEPTED ANSWER

    Re: Restrict user from canceling desktop requisition when any PR on MRLINEs

    ‏2012-10-10T11:41:22Z  in response to SystemAdmin
    Can any one help me in creating condition to restricting a user from cancelling DR as mentioned above?
    • maxmix
      maxmix
      83 Posts
      ACCEPTED ANSWER

      Re: Restrict user from canceling desktop requisition when any PR on MRLINEs

      ‏2012-10-11T12:17:29Z  in response to SystemAdmin
      Well as I have no matching MX in reach, I had hoped someone more familiar w/your setup would go first.
      So here some generic troubleshooting:
      Identify the Domain that feeds the status field of your DR.
      The recent MX releases have a "view modifiy Condition" that allows attaching a "conditional expression manager"'s condition to each domain value.
      While I have not done so quite yet, I suspect the logic for the condition would be similar to the conditions attachable at workflow action arrows: specify the conditions for which this status is a valid option.
      Be as specific as possible, as this domain may also be reused for other objects.

      Other than that, please keep an eye out on "status changes via a nonperistent MBO". This will require you to adapt your condition statement accordingly, as a ":prnum" might not be present in such a reduced nonp. MBO.

      Hope it inspired you where to stroll around next...