Emerson Exchange 365

• Not Answered

Who answered a Batch Prompt?

Hi,

I need to store the user name of the Operator who answers a Batch Prompt.

I want to store Operator Name as a Batch Report parameter so I can pass it forward to another phase which will be executed later.

We need to confirm Operator does not complete both steps of process.

When I look at Batch Journal Files I can see 'Confirmer Name' when I create prompt that needs to be confirmed.

Is there any parameter in phase\unit\batch exec that stores this information?

Thanks

• prompt

FDKelly

• 21 Apr 2021 4:03 PM
• Cancel

11 Replies

• Jordi ter Meulen

  

  • 17 Aug 2021 2:26 PM

  Hi FDKelly,
  
  I have a similar issue. In my case acknowledger and verifier cannot be the same person. So i need to make sure the user IDs are not the same for acknowledger and verifier. Currently a supervisor can sign as acknowledger and verifier. Did you find a solution?

  • Cancel
• Andre Dicaire

  

  • 17 Aug 2021 3:52 PM

  If I understand this, you have an SOP that says the same operator can not complete two steps. Yet, you have operators that are doing that, and you know this because the Batch Journal File has recorded the operator doing just that.
  
  If your operator is not willing to follow the SOP, why wouldn't they find a way around this added check you want to implement? Assuming you can pass the Operator name who answered the first prompt, what will prevent your operators from sharing their password so that they can use each other's account to answer prompts? Humans are machines of ingenuity, and if there is a will, there is a way.
  
  Sometimes, it is better to enforce the standard operating procedure and avoid complicating the code. Some one once said "You can't make it fool proof, because fools are so smart."

  Andre Dicaire

  • Cancel
• Matt Stoner

  

  • 17 Aug 2021 5:57 PM

  There is no parameter that stores the Username that can be used for this. You could on the second prompt use a confirm and verify with the option that the Confirmer and Verifier NOT be the same person. This is a global selection for everything so if you want different cases you will have to come up with a different design.
  
  The Allow Confirmer and Verifier to be the same person selection is on the properties of the ElectronicSignatures that is under Setup/Security. If you do not see ElectronicSignatures then you need to Enable Signature Policies under the system preference on the ProPlus.

  • Cancel
• Jordi ter Meulen

  

  • 18 Aug 2021 5:37 AM

  In reply to Andre Dicaire:

  This answer does not help Andre. FDKelly and me as well are looking for a technical solution. That's why we ask in this forum. If you can help on the topic i really appreciate, else there are other forums to comment on procedures and fools.

  • Cancel
• Jordi ter Meulen

  

  • 18 Aug 2021 5:37 AM

  In reply to Andre Dicaire:

  [deleted]

  • Cancel
• LaurentB

  

  • 18 Aug 2021 5:56 AM

  In reply to Jordi ter Meulen:

  The Andre’s answer is the most valuable answer to this topic. Going back to process university can help you to find efficient solution.

  • Cancel
• IntuitiveNeil

  

  • 18 Aug 2021 7:40 AM

  In reply to Jordi ter Meulen:

  Matt and Andre know their onions.
  
  I concur with both.
  
  I conclude from this, there is no simple technical solution in the product. (Matts response)
  
  And from that Andre is suggesting an alternate non technical solution. And also suggesting why a technical solution may also not provide the silver bullet you require to solve your problem, even if you did implement a technical solution.
  
  Both valuable inputs to this discussion in my opinion.

  • Cancel
• FDKelly

  

  • 18 Aug 2021 11:19 AM

  In reply to IntuitiveNeil:

  Hi ,
  
  I opened a Ticket with Emerson Support about this issue and they confirmed the information I needed was not available from Batch Exce\Unit\Phase parameters. In the end we had to included an extra signoff on Batch Record - It works but it is not a great solution.
  
  I think Emerson should consider adding the ability to store who answered or confirmed a batch prompt so we can access within a phase and publish to a report parameter if needed. I think more site's will look for features like this as we try to eliminate or minimize Paper Batch Records.
  
  Regards
  Finbarr

  • Cancel
• gamella

  

  • 18 Aug 2021 11:57 AM

  Using SoftPhases may help but not sure if fully feasible (will need to spent time to test....).
  After PHASE who originated the prompt a SoftPhase may be launched to access Batch Journal (text files) or Batch Historian (SQL server).
  This softphase may generate a report value with user name, obtained from Journal o Batch historian, that can be consumed by next phases.
  
  Just a quick idea.

  • Cancel
• Matt Stoner

  

  • 18 Aug 2021 12:41 PM

  In reply to FDKelly:

  You can submit ideas like this at https://userideas-emerson.com/

  • Cancel
• Andre Dicaire

  

  • 18 Aug 2021 3:18 PM

  In reply to Jordi ter Meulen:

  My response was not only for your Jordi, and was offered as a point of reflection before diving into what could be a complex solution with diminishing returns. Only you can decide on what your solution requires.
  
  As for the fools part, I'm sorry you don't appreciate a bit of levity, but no, I'll be staying here on this forum thank-you. But feel free to not read any of my posts in the future as I am likely to make a joke or two along the way.

  Andre Dicaire

  • Cancel