I migrated my IDM 4.8 workflow and JSON forms to IDM 4.9 by just exporting and importing them. All seems to work fine BUT the buttons like approve,deny,cancel do not fire any event and do not close the form. Any experiences from somybody else?
Cybersecurity
DevOps Cloud (ADM)
IT Operations Cloud
I migrated my IDM 4.8 workflow and JSON forms to IDM 4.9 by just exporting and importing them. All seems to work fine BUT the buttons like approve,deny,cancel do not fire any event and do not close the form. Any experiences from somybody else?
I think this is mentioned in the Known Issues Area: https://www.netiq.com/documentation/identity-manager-49/release-notes-identity-manager-49/data/release-notes-identity-manager-49.html#identity-manager-49-known-issues
Issue: After upgrading to Designer 4.9, the Button component in JSON forms is not working for approve and request actions. [Issue: OCTCR56A604329]
Workaround: Perform the following steps:
Go to the Button component’s Display tab.
Copy the logic specified in the Button Request Logic or Button Approve Logic fields.
Change the Action to custom.
Specify the logic copied from Step 2.
Click Save.
Best regards, Katharina
Hi Katharina
thanks a lot, this is working. But a strange behavior to have to make all buttons custom buttons and not being able to use the standard actions types.
regards
Andreas
Hi Katharina
next issue. If you use "custom" on the action type the buttons are working but mandatory fields are neglected. The error message pops up but nevertheless the form is closed and sent.
Any ideas on that issue?
regards, Andreas
Hi Andreas,
actually I've never had any issues with that. Is the checkbox "Disable on form Invalid" activated at the bottom? (In the "Display" tab)
Usually the button is not working as long as the form is not valid when this is checked.
br, Katharina
Hi Katharina
I'm not user to this behavior. In prior version if I clicked on deny or approve and a required field was not filled the appropriate error message appeared and the form was not sent. With your procedure the buttons are disabled until I enter a value in the fields. This way the user receives absolutely no hint why he can't press the button. It's working but I'm not happy with it.
thx for your help I appreciate very much, Andreas