Its ok i found the parameter in the settings
This is perfect thanks for your help
looks like an issue with the timing of the event. it runs when the company person lu has a new entry but the org name is coming from the company_pers_assign. so when firing the data is not there for it to be collected. might be worth breaking your attribute down a little to see if it pulls the data of just the org name first try this IFSAPP.COMPANY_ORG_API.GET_ORG_NAME(&NEW:COMPANY_ID, &NEW:ORG_CODE). i have the same issue with employee job titles when the employee is a future starter
looks like you have a access attribute set up for that area. if you have a access attribute set up then that will need to be attached to an access role and the assigned to the employee/person via the organisation position. this should let you use the employee wizard. Make sure you give access to the structure that the employee/person will be creating new employees on
Hi, You will need to ensure that the ‘ChangeReqState’ is granted in the ‘AbsenceEmployeeHandling’ Projection. screenshot below. this will then let you change the state of the absence request Thanks Wayne
Hi Wayne, If the problem is still exist, I think you can try with a minimum configuration first (only with the mandatory steps ) and see if you can create an employee. If that is possible, you can then add next steps gradually to see which step is causing the error. That’s a great idea Lasanthi. I will try this today Thanks Wayne So I created a new wizard and it seems to get stuck on the schedules. The thing that is strange is that I can change a schedule on an existing employee using the wizard so I must have the correct access. Wondering if this could be a bug?
Hi Wayne, If the problem is still exist, I think you can try with a minimum configuration first (only with the mandatory steps ) and see if you can create an employee. If that is possible, you can then add next steps gradually to see which step is causing the error. That’s a great idea Lasanthi. I will try this today Thanks Wayne
Hi Wayne, Would you be able to get back regarding the below questions please? Is the start date in the future and does the user have access to that date as well? you mentioned that the user is able to create an employee manually. Is the same user able to enter position assignment, schedules, etc to the newly created employee? Hi The start date is today (these are test employees). yes they can enter position assignments schedules etc as you would normally do
Thank you i will try this as you described
Thanks Lénaïc Do you know what columns would need to be included in the attribute? Thanks
Hi, As a rule you are not meant to remove used organisation positions. These will have transactional data in them that is held in the database. You will have to make them obsolete buy entering a valid to date. if you don't want to see them in the org chart you can select the ‘exclude form organization chart’ box. Hope this helps Wayne
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
