BPM at Clock Out

Austin,



Grab the EmpID in a pre-process routine, and assign it to one of the call
context variables. Then, enable post-processing directives.



Then, in your post-processing directive, you've got the value of the EmpID
in the call context variable, so you can process there.



Kevin Simon



From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com] On Behalf Of
Austin Skrepak
Sent: Tuesday, November 13, 2012 12:44 PM
To: vantage@yahoogroups.com
Subject: [Vantage] BPM at Clock Out





I am trying to create a BPM that assigns all idle time records for an
employee to their home department (LaborDtl.Character01) at the time they
clock out. The issue am I running into is that the empID parameter is
cleared after the base process, so I can't specify the employee. Also, it
does not appear that the idle time records are created until after the clock
out, so grabbing the empID as a pre-process won't help. I wrote some 4GL to
update all idle time records within a certain date frame, but that slowed
the clocking out process down so much that it isn't feasible.

Does anyone have any good ideas for this? I have to be missing something
here.

Thanks!

Austin Skrepak
Data Specialist / Developer
[EMAIL] askrepak@... <mailto:askrepak%40rosenboom.com>
<mailto:askrepak@... <mailto:askrepak%40rosenboom.com> >

"Without ambition one starts nothing. Without work one finishes nothing. The
prize will not be sent to you. You have to win it."
Ralph Waldo Emerson

[Non-text portions of this message have been removed]





[Non-text portions of this message have been removed]
I am trying to create a BPM that assigns all idle time records for an employee to their home department (LaborDtl.Character01) at the time they clock out. The issue am I running into is that the empID parameter is cleared after the base process, so I can't specify the employee. Also, it does not appear that the idle time records are created until after the clock out, so grabbing the empID as a pre-process won't help. I wrote some 4GL to update all idle time records within a certain date frame, but that slowed the clocking out process down so much that it isn't feasible.

Does anyone have any good ideas for this? I have to be missing something here.

Thanks!

Austin Skrepak
Data Specialist / Developer
[EMAIL] askrepak@...<mailto:askrepak@...>

"Without ambition one starts nothing. Without work one finishes nothing. The prize will not be sent to you. You have to win it."
Ralph Waldo Emerson



[Non-text portions of this message have been removed]