Automating adding user security for Landmark Applications

I have the automation built to add employees and security to LSF and Landmark, but now that we are adding our first Landmark application, I need to add the employees to an HROrganization and to an Agent so that they can use Employee Space. I know that you need to pass a number for Context Property and Employee but can't remember where to find the number to pass for the "Employee =" when adding the Agent. Can anyone point me in the right direction

Find more posts tagged with

Process Automation (IPA) - General Discussions

Comments

suryaprakash-mallareddy

For us, the agent number is HROrganization, Employee# from the Employee Table / Resources. The Agent ties the actor to the employee #.

Example: HROrganization = 1, Employee # = 1, Agent = 1,1 and is tied to actor jsmith01

jreese

That I understand. There are unique ID's assigned to the HROrganization, which you can find by searching on ContextProperty and need to pass in the flow to add the employee to the Organization. There is also a unique ID that translates to Employee that you need to pass when adding the agent. This plus adding the login id creates a unique Id for the employee that is actually behind the Agent = 1,1.

suryaprakash-mallareddy

Oh, okay. We used a filter to get the Context Property Unique ID on the query. We used a filter to do the same for Agent. Multiple record query with a filter to find the agent ID and then assign it to the actor in another node of the IPA once we have the agent.

Example:

_dataArea="<!appProdline>" & _module="person" & _objectName="Agent" & _actionName="Find" & _actionOperator="NONE" & _actionType="MultipleRecordQuery" & _runAsUser="" & _authenticatedUser="" & _pageSize="30" & _filterString=KeyText="<!EmployeeAgentKey>" and BusinessObjectRef.BusinessClassName="Employee" & _relationName="" & _setName="" & _asOfDate="" & _effectiveDate="" & Agent

The Employee Agent Key is a variable of "1, 1"

Does that help?

Legacy Contributor

Short Story is: it is the AGENT from the AGENT table.

I create the LSF USERS, ACTORS, Identities and Roles and Context with one query of data. Then I use a separate query that was pulled at the same time as the first query to link Actors to Agents. I look for those that don't have CONTEXT yet.

So I gather up all the id's and agents to link to actors with this query that puts the data in a file with a SQLCMD.

(I've added returns for clarity but your SQLCMD can have no returns. S is your database url, d is DataBase identifier, U is userid, P is Passord, if you're not familiar with SQLCMD.

I wasn't and had to learn the hard way.

SQLCMD -S xxxxx.xxxxxx.com-d LMLTMPRD_FTC -U xxxxxxxxxx -P xxxxxxxxxx -s, -W -Q

"SELECT b.AGENT, a.EMPLOYEE

FROM lmhcm.EMPLOYEE a

JOIN lmhcm.AGENT b ON ((RTRIM(CONVERT(VARCHAR(10),a.EMPLOYEE)) = SUBSTRING(b.KEYTEXT,6,6) OR CONVERT(VARCHAR(10),CANDIDATENUMBER) = SUBSTRING(KEYTEXT,6,6)) and b.DELETEFLAG = 0)

WHERE not exists

(select 'x'

from lmhcm.ACTORCONTEXT d

where ('CPS0' + convert(nvarchar(10),a.EMPLOYEE) = d.ACTOR or convert(nvarchar(10),a.EMPLOYEE)= d.ACTOR ) and d.DELETEFLAG = 0)

and (RELATIONSHIPTOORGANIZATION in ('EMPLOYEE','SUBSTITUTE' )

or (RELATIONSHIPTOORGANIZATION = 'VOLUNTEER' and WORKTYPE = 'ATHLETIC COACH'))

and HRORGANIZATION = '100'

and RELATIONSHIPSTATUS in( 'ACTIVE','MILITARY LEAVE UNPD')

and b.BORBUSINESSCLASSNAME <> 'Instructor' ORDER BY 2 desc;

" | findstr /V /C:"-" /B > H:Sulk_dat1.txt

Then i parse the file (comma delimited)with the parser and assign a variable AGENT_STRING this value:

substring(DI_2_outputData1, 2,10) + "-" +

substring(DI_2_outputData1,10,14) + "-" +

substring(DI_2_outputData1,14,18) + "-" +

substring(DI_2_outputData1,18,22) + "-" +

substring(DI_2_outputData1,22,38)

Then my Lanmark node looks like this:

_dataArea="<!appProdline>" & _module="person" & _objectName="Agent" & _actionName="LinkToActor" & _actionOperator="NONE" & _actionType="CreateUpdateDelete" & _pageSize="30" & Agent="<!AGENT_STRING>" & Actor="<!cps_empid>"

I leave to you how to create an Actor name for a given employee.

Wichtige Lösungen in der Wissensdatenbank Februar 2012.pdf

Copyright © 2025 Infor. All rights reserved.