LTM Hire Processflow

Hi Dave Lis,

I haven't done this, but it certainly should be possible.  You would need to use a Landmark Transaction node (or several of them).  Basically, you'll need to note carefully how the recruiter does the process manually, and then mimic that in the flow.  If the recruiter can do it via Canvas, then you should be able to do it using the Transaction node in Pflow - though there may be some things that aren't as obvious. 

One thing to consider is that in some places (like ours) the same requisition could be used for multiple hires, so you'd need to be sure that all the positions were filled before dispositioning everyone.  You'll also have to figure out what do do if they decide not to fill one of the openings.

Here are the steps I would use:

• Query the "ActionRequest" bc using the "Find" action and the "ActionRequest" value as the key.  Return the BusinessAction (which will be RehireApproval" or "HireApproval", I think.)
• Save a variable that prepends "Find" to the beginning of the BusinessAction (i.e. FindHireApproval)
• Query the "JobApplication" bc using the "FindHireResource" (the variable you defined above - note that this will NOT be in the action list) and the "ActionRequest" value as the key.  Return the fields you need from the ActionRequest form (Primarily the "JobRequisition" value.)
• Query the "JobRequsition" bc using the "Find" action and "HR Org" and "JobRequisition" as the keys.  Return the fields you need from this bc (primarily AvailableOpenings and HireCount - just my guess)
• Query the "JobApplication" bc using a "Find" action and "MultipleRecordQuery" action type, and the "HR Org" and filtering by "JobRequisition" (I'm guessing on this one, you may need to play with it) and return Employee and Disposed.
• Update each "JobApplication" using the appropriate action

Like I said, we haven't done this, so I'm not positive this is correct, but it should give you a place to start.

Is there something specific you haven't been able to figure out?

Kelly

This is a great place to start.  I'll follow your advice and see what I come up with.

What's tricking me is in S3 I can call PA31, or any other transaction but I never tried it in LTM.  I'm looking throught the business classess but havent seen anything yet.

Thanks for you help.

Dave.

Yep, you can do the same thing in LTM. You just have to know what business class you are looking for. Generally, you can use CTRL-SHIFT-O on form fields to get an idea of what BC and field you are looking for. Generally the actions on the form are included in the list of actions in the Landmark node. Good Luck.

I just looked and, on the Recruiting>>JobApplication business class, in the Action dropdown in the Landmark node, there is an action named "DispositionCandidateApplied".  I'm guessing this is what the "Disposition Candidate" action on the form in Canvas uses.  It takes Candidate, HROrg, JobApp, and JobReq as keys, and includes DispositionReason field and SendAutomatedEmail (boolean).  I'm guessing you would call this as an Update action.

In Recruiter Space, if you select the "Disposition Candidate" action, it prompts you to select one of the predefined Reason Codes.  In the source for this action (in $LASRCDIR/{prodline}/modules/Recruiting/bl/JobApplication.busclass - see attached) it looks like the email flag is pulled from the Recruiting Setup.  I think you'd need to either look this up or manually populate the value.

 Note that this is from our 9.2.5 environment, so it may be somewhat different if you are on LM10.

Kelly

Hi Kellly,

I tried the DispositionCandidateApplied action and it worked.
Good job!!!!

Thank you.
Dave.

Yay! I'm glad to hear it.

Kelly