You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The current code does not allow for update of the InSite attribute of the AFAS user. Only whenever the account has been correlated.
See line 140 in the update.ps1.
The following code is present: if (($account.PSObject.Properties.Name -Contains 'InSi') -and ($actionContext.AccountCorrelated -eq $true)) { $updateAccountFields += "InSi" }
The same goes for the OutSite attribute (Site)
The second part should not be present if you want to actually update that attribute in a regular update event.
The text was updated successfully, but these errors were encountered:
@mouki9 What would be the use case for updating these settings during an update, aside from a bulk update? Is it when the decision to enable or disable is based on HR data to support department or profession changes? For example, should it be enabled for the IT department and disabled for the Administration department? And should it automatically update if an employee switches between these departments?
Exactly that use case, but also possible with use cases where you take into account other information of the contracts.
Met vriendelijke groet,
KaHo Man
IAM Consultant
Kaho Man
Consultant
Contact on Teams
View LinkedIn Profile
Amalialaan 126C | 3743 KJ Baarn
Tel: 035 548 3255
***@***.***
SelfServiceDesk
Contact | Certificeringen | Disclaimer
________________________________
From: rschouten97 ***@***.***>
Sent: Thursday, October 3, 2024 5:37:48 PM
To: Tools4everBV/HelloID-Conn-Prov-Target-AFAS-Profit-Users ***@***.***>
Cc: Kaho Man ***@***.***>; Mention ***@***.***>
Subject: Re: [Tools4everBV/HelloID-Conn-Prov-Target-AFAS-Profit-Users] update insite / outsite in update event (Issue #19)
@mouki9<https://github.com/mouki9> What would be the use case for updating these settings during an update, aside from a bulk update? Is it when the decision to enable or disable is based on HR data to support department or profession changes? For example, should it be enabled for the IT department and disabled for the Administration department? And should it automatically update if an employee switches between these departments?
—
Reply to this email directly, view it on GitHub<#19 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/AQHY2NXEC5525IIF2I363I3ZZVQEZAVCNFSM6AAAAABONS77JOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOJRG4ZTKMBWHA>.
You are receiving this because you were mentioned.Message ID: ***@***.***>
The current code does not allow for update of the InSite attribute of the AFAS user. Only whenever the account has been correlated.
See line 140 in the update.ps1.
The following code is present:
if (($account.PSObject.Properties.Name -Contains 'InSi') -and ($actionContext.AccountCorrelated -eq $true)) { $updateAccountFields += "InSi" }
The same goes for the OutSite attribute (Site)
The second part should not be present if you want to actually update that attribute in a regular update event.
The text was updated successfully, but these errors were encountered: