Click HERE to see how Saviynt Intelligence is transforming the industry. |
04/12/2022 01:24 PM
Hide on Create config on the dynamic attribute definition hides the attribute on create request forms.
Hide on Update config on the dynamic attribute definition hides the attribute on update request forms.
Yes, hidden dynamic attribute’s default value can be used in provisioning connections to pass important account information to connected target applications such as user employeetype (FTE, contract hire, intern)
You can configure to show/hide one dynamic attribute based on another dynamic attribute value in “Action String” parameter in dynamic attribute definition
Sample:
Dynamic Attribute 1 - EmployeeType which can take value Employee or Contractor
Dynamic Attribute 2 - ReservedParking
Dynamic Attribute 3 - LunchID
Dynamic Attribute 4 - ParkingValidation
Dynamic Attribute 5 - LunchCoupon
Action String on EmployeeType dynamic attribute to be defined as
'SHOW###ReservedParking###Employee___HIDE###ReservedParking###Contractor___SHOW###LunchID###Employee___HIDE###LunchID###Contractor___SHOW###ParkingValidation###Contractor___HIDE###ParkingValidation###Employee___SHOW###LunchCoupon###Contractor___HIDE###LunchCoupon###Employee'
Above sample shows ReservedParking, LunchID when EmployeeType=Employee and hides ReservedParking, LunchID only for EmployeeType=Contractor. Shows ParkingValidation, LunchCoupon for EmployeeType=Contractor and hides ParkingValidation, LunchCoupon for EmployeeType=Employee
Required config on the dynamic attribute definition when checked makes the dynamic attribute mandatory in request forms
You can configure to make one dynamic attribute required or not required based on another dynamic attribute value in “Action String” parameter in dynamic attribute definition
Sample:
Dynamic Attribute 1 - EmployeeType which can take value Employee or Contractor
Dynamic Attribute 2 - Employee1
Dynamic Attribute 3 - Employee2
Dynamic Attribute 4 - Contractor1
Dynamic Attribute 5 - Contractor2
Action String on EmployeeType dynamic attribute to be defined as
REQ###Employee1###Employee___NREQ###Employee1###Contractor___REQ###Employee2###Employee___NREQ###Employee2###Contractor___REQ###Contractor1###Contractor___NREQ###Contractor1###Employee___REQ###Contractor2###Contractor___NREQ###Contractor2###Employee
Above sample makes Employee1, Employee2 mandatory when EmployeeType=Employee and makes Employee1, Employee2 non mandatory only for EmployeeType=Contractor. Marks Contractor1, Contractor2 mandatory for EmployeeType=Contractor and makes Contractor1, Contractor2 non mandatory for EmployeeType=Employee
04/12/2022 03:14 PM
Hi Aarthi,
Few of questions
1. Can we have both point 3 and 5 together?
2. Can we default child attribute to a default value?
3. If Parent attribute is read only, can child attribute value can be set depending on the parent attribute?
Thanks,
Minesh Shah.
04/12/2022 03:14 PM
Minesh, did you try with both 3 and 5 together? Is that worked ?
04/12/2022 03:14 PM
No, Tuhin.
I havent tried it.
04/12/2022 03:14 PM
I've tested and 3 and 5 combined does seem to work.
04/12/2022 03:14 PM
Thanks Adam,
04/12/2022 03:14 PM
Can someone please provide me a screenshot for 3 & 5.
I have a requirement where I need to show other dynamic attribute based on previous selection
04/12/2022 03:14 PM
We have tried combination of 3 and 5 and it does not work for us either. Can anyone provide any working example of SHOW and REQ together on action string?
Thanks,
Rituparna Das
04/12/2022 03:14 PM
Hi, was anyone able to get this working?
04/12/2022 03:14 PM
I have 3 fields:
iga_company,
iga_createcompany (boolean),
iga_companyString.
In the field iga_createcompany (boolean) I have an action string:
SHOW###iga_companyString###TRUE___HIDE###iga_companyString###FALSE___REQ###iga_company###FALSE___NREQ###iga_company###TRUE___REQ###iga_companyString###TRUE___NREQ###iga_companyString###FALSE
it works for show/hide and for requiring the attribute as mandatory.