Resource Provisioning by JobCode

Legacy Contributor

Hello All,

 

I wondering if anyone has tried to develop a flow that provisions new and existing resources in Lawson based on their JobCode in HR11 and what tools they used to make it happen. At my organization just like many others, we have unique jobcodes, and we have specific role(s), groups(s) and portalRole to grant each jobcode. It makes sense to develop a flow that will crosscheck an employee's jobcode against a table of sorts and determine what roles, groups and portal role the resource should have.

 

I built a proof-of-concept flow for a federated Lawson V10 system that provisions a resource across LSF and LMRK based on their job code. I picked about 8 jobcodes in HR11, defined them at start in a flow and within same flow, crosscheck an employee's jobcode from a lawson query node against those 8 jobcodes using if-else statements. if true, the flow picks an array of roles for that jobcode (also defined at start), and grants it to the employee. the same logic is applied for an array of groups, and the portalRole.

 

The issue is - all of it had to be hard-coded at start, and if you have thousands of job codes, that becomes unfeasible to hardcode every job code and their respective arrays of roles and groups. not to mention building a long list of if-else statements for each jobcode. More so, if new job codes are ever created, flow would have to be constantly updated which is a redundant.

 

Is their a mechanism within IPA (perhaps Rich Client), that can used to get this accomplished?? Someone clued me into maybe leveraging the Cross Reference Codes table in Rich Client to make it work, but i'm running into limitations with that? I would rather steer clear of a crossreference table file if possible and have it all done in IPA if possible. Input appreciated. Thanks

Legacy Contributor

Based on the Cross Reference Codes being mentioned you could try something like the below:



In theory you could have, say, HR update a .csv file with Job codes and security listed and then loop through the file to provision users. You could also use a new database table and connect IPA to it. Others could update the table via Access or other means. This would allow end users to manage the security received by new hires.



I suppose it might be possible to do everything within IPA, but likely you would need the data stored somewhere to avoid hard-coding the flow. Hopefully these ideas provide some help!