Update Action Request Parameter

Hello all,

I am attempting to update a user field in an action request form via IPA. This user field will be hidden on the form to trigger a flag for a part of the process that is used in a constraint. While FindHireApplied allows me to get the parameters from the form, I have been unable to determine a way to update this parameter on the form via IPA. Has anyone else had success in this area? I have attempted changing the actionType to CreateUpdateDelete, changing the actionName to UpdateHireApplied, UpdateInProgressHireApplied, and various combinations of these. I have also attempted many updates from the objectName ActionRequest, etc... We are on Landmark 10.1.1.55. The form constraint works well at least, so this is my last hurdle.

v10 Cust Day - 10.1.0 User Experience.pdf

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

unknown

Hi Robert,

I think I've fiddled with this, but it's challenging. From the application's perspective, the userfield is part of the business class it is associated with, so you have to update it from that business class.

Is your userfield configured on the JobApplication business class or the ActionRequest business class? It sounds like it's on ActionRequest, so you'd need to use an Update against ActionRequest using the UniqueID (ActionRequest) as the key.

If it's on JobApplication, then you should be able to use the UpdateHireApplied or UpdateInProgressHireApplied to update the record because the application should "see" it as part of the JobApplication business class.

Good Luck

Kelly

rmbell

Thanks Kelly. I made the user field part of the JobApplication business class so it is recognized by the configured Hire form in configuration console, but the UpdateHireApplied and UpdateInProgressHireApplied do not work in changing the field to true on the form. It will inquire per example below, but not change the value of the user field.

I have tried some various other methods from using Find with CreateUpdateDelete, adding the ActionRequest to the string, and even trying the actionName="HireApplied"(creates a new blank request without the action request, blanks out the current request if ActionRequest is included, both not recommended).

Example:

_dataArea="lmghr" & _module="Recruiting" & _objectName="JobApplication" & _actionName="UpdateHireApplied" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & HROrganization="1000" & Candidate="123456" & JobRequisition="35" & JobApplication="1" & GCSHRAdmin="true"

complete: true

response message: Inquire Completed

record count: 1

has next: false

has previous: false

Results header string: HROrganization,Candidate,JobRequisition,JobApplication,GCSHRAdmin

Results string: 1000,123456,35,1,false

Communications trace

null

unknown

Ahh - I think I see the problem.

When you are trying to update fields within an Action Request, you need to pass the ActionRequest value (from the flow/service) as the key rather than the HROrg/Candidate/JobReq/JobApp.

So, rather than your example, you need to do something like this:

Example:

_dataArea="lmghr" & _module="Recruiting" & _objectName="JobApplication" & _actionName="UpdateHireApplied" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & ActionRequest="<!ActionRequest>" & GCSHRAdmin="true"

This ensures that the field that is being updated is the ActionRequest Parameter field for this instance of the HireApplied action, which is what I think you want.

I hope this helps.

Kelly

rmbell

Thanks for the help on this, the documentation on these processes(non-buildable actionNames) is non-existent.

I tried the action request instead of the user info prior, and it gives the does not exist exception. I am running this with the hard coded action request and other variables for testing purposes.

_dataArea="lmghr" & _module="Recruiting" & _objectName="JobApplication" & _actionName="UpdateHireApplied" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & ActionRequest="015efa8e-aa79-0000-0002-a1b7538f85a8" & GCSHRAdmin="true"

Exception: com.lawson.bpm.landmark.LandmarkApplicationException: com.lawson.rdtech.type.DoesNotExistException: Job Application does not exist.

at...

This is one of those process functions that seems like it should be pretty straight forward, but is nowhere near, unfortunately.

unknown

I've never been successful in hard-coding the ActionRequestID, probably because it's a hex field, but I'm not sure.

Instead, you should be able to put this in a test flow (just this update node) in designer, and point to a workunit that references the ActionRequest you are trying to work with. It's a pain, but that way it should work exactly how the flow would work in real life.

unknown

I just re-read what I wrote, and it wasn't very clear. Sorry about that.

To clarify...run the flow in Designer and in the "Run Process" dialog select the "Use data from Workunit:" radio button and enter the workunit number of the TA Hire (HireApplied) workunit you are testing against.

rmbell

No problem, I have never thought to approach that way, but seeing that now I am kicking myself for all the copy/pastes I have done in the past, thanks!

It still gave that error about job application does not exist:

Activity started: LMTxn7120 (Run Id: 5)

Landmark:LMTxn7120 Executing transaction_dataArea="lmghr" & _module="Recruiting" & _objectName="JobApplication" & _actionName="UpdateHireApplied" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & ActionRequest="<!ActionRequest>" & GCSHRAdmin="true"

Landmark:LMTxn7120 Executing transaction_dataArea="lmghr" & _module="Recruiting" & _objectName="JobApplication" & _actionName="UpdateHireApplied" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & ActionRequest="015efa8e-aa79-0000-0002-a1b7538f85a8" & GCSHRAdmin="true"

Landmark:LMTxn7120 Retrieving page 1 started @ 10/09/2017 01:46:03.776 PM

Landmark:LMTxn7120 Application Error com.lawson.rdtech.type.DoesNotExistException: Job Application does not exist.

at com.lawson...

I tried adding the variables for the HROrg, JR, JA, and Candidate, and while that doesn't fail, it treats the process as an inquire:

_dataArea="lmghr" & _module="Recruiting" & _objectName="JobApplication" & _actionName="UpdateHireApplied" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & HROrganization="<!HROrganization>" & JobRequisition="<!JobRequisition>" & Candidate="<!Candidate>" & JobApplication="<!JobApplication>" & ActionRequest="<!ActionRequest>" & GCSHRAdmin="true"

Activity started: LMTxn7120 (Run Id: 7)

Landmark:LMTxn7120 Executing transaction_dataArea="lmghr" & _module="Recruiting" & _objectName="JobApplication" & _actionName="UpdateHireApplied" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & HROrganization="<!HROrganization>" & JobRequisition="<!JobRequisition>" & Candidate="<!Candidate>" & JobApplication="<!JobApplication>" & ActionRequest="<!ActionRequest>" & GCSHRAdmin="true"

Landmark:LMTxn7120 Executing transaction_dataArea="lmghr" & _module="Recruiting" & _objectName="JobApplication" & _actionName="UpdateHireApplied" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & HROrganization="1000" & JobRequisition="35" & Candidate="123456" & JobApplication="1" & ActionRequest="015efa8e-aa79-0000-0002-a1b7538f85a8" & GCSHRAdmin="true"

Landmark:LMTxn7120 Retrieving page 1 started @ 10/09/2017 01:54:48.731 PM

Landmark:LMTxn7120 Retrieving page 1 completed @ 10/09/2017 01:54:52.041 PM

Landmark:LMTxn7120 transaction complete:true,

response message:Inquire Completed,

record count:1,

results header string: HROrganization,JobRequisition,Candidate,JobApplication,ActionRequest,GCSHRAdmin,

results string:1000,35,123456,1,null,false,

has next:false,

has prev:false

LMTxn7120_complete = true

LMTxn7120_recordCount = 1

LMTxn7120_hasNext = false

LMTxn7120_hasPrevious = false

LMTxn7120_resultsHeader = HROrganization,JobRequisition,Candidate,JobApplication,ActionRequest,GCSHRAdmin

LMTxn7120_currentPage = 1

LMTxn7120_recordCount = 1

LMTxn7120_currentPage = 1

Activity completed: LMTxn7120

LMTxn7120_errorCode = 0

LMTxn7120_informationCode = 0

LMTxn7120_returnMessage = Inquire Completed

LMTxn7120_outputData = 1000,35,123456,1,null,false

LandmarkLMTxn7120: Executing loop 1 of 1 (Page 1)

unknown

Th Landmark node is extremely finicky. Just to be sure, did you create the source workunit AFTER you created the new UserField? The ActionRequest fields are set when the action is created, so if you added the UserField later, old actions would not know anything about it - and this would cause an error like you mentioned above.

The Landmark node will error if it doesn't like anything about the input - but it won't be obvious what the problem is. A good practice is to update something you know should update and make sure that works, then add the "new" field.

FYI - this is a little late in this conversation, but It just occurred to me that I have never figured out the "trick" to updating ActionRequest parameters this way - though the Infor developers claim it is possible. The only way I've been able to get it to work is to query the ActionRequest directly to pull out the ParameterView value (which is xml), parse the xml using the xml node in IPA (so it can been referenced via javascript), update the xml using javascript, then update the ActionRequest using the "UpdateParametersInProcess" action and passing in the modified ParameterView xml string. This pretty much sucks, but that's how I had to do it. I hope you can figure out how to do it the other way. Sorry I didn't remember this before - it's been a long time since I've fiddled with this.

Kelly

rmbell

The request was post UF creation, and I was able to change the actual User field value, just not the form value in this case. I will explore your method below, that may be the approach I have to take. I am also looking into the ActionRequest UF method as well, but it may require some sort of custom relation. I will post what I come up with, but thanks for this! At least I know there is a way to accomplish this!

rmbell

Ok, so I approached this from a different angle. I created a user field on the ActionRequest Business class, and update that data(instead of form parameters) in my process. Before the HR Administrator node, I use this:

_dataArea="lmghr" & _module="la" & _objectName="ActionRequest" & _actionName="UpdateInProcess" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & ActionRequest="<!ActionRequest>" & GCSNode="HRADMIN"

to update the user field GCSNode with the value of the UA node it will be at next. In config console, I use this constraint:

Birthdate

constraint (Birthdate entered

and last PendingActionRequestRel.GCSNode = "HRADMIN"

or last PendingActionRequestRel.GCSNode != "HRADMIN")

"BirthdateRequired"

to require this field at this node. After this node, I clear the value in case of return.

unknown

Hi! This is an older post but I am hoping it will reach you and you will be able to help me. We use a flow similar to the approach in this thread. It is looking to find the initiator of the request and then it drops in that users email as the "Requester". With that, it also picks up the Requester's Email. We have one user who it isn't picking up. I ensured they're setup is identical to those not having the problem but still cannot seem to make the flow pick him up. Maybe it isn't within the flow I need to be searching still but more so in GHR, but I feel I have looked every where possible. Any help would be greatly appreciated!

0911060553270289.pdf

unknown

Hi Deana,

I moved away from Infor/IPA support over a year ago, so I'm pretty rusty.

I'm guessing, but I'd recommend that you re-check the Actor record to be sure that the email address is populated, and also check the PfiUserTask business class to ensure that the users Actor has a record, and that it is marked as "valid".

I hope this helps. Good Luck!

Kelly

Copyright © 2025 Infor. All rights reserved.