Please share any images or screenshots, if relevant.
No Screenshot needed
Please share any other relevant files that may be required (for example, logs).
N/A
Share all details about your problem, including any error messages you may have received.
We are working on an upgrade from IdentityIQ 8.3P3 to 8.4P2 and have discovered an issue with the forms framework. Basically we have a validation script which is in addition to performing validation updating the current value of the field itself if validation was to pass. We’ve noticed that with 8.4P2 that the update to the field does not “stick” when it’s made. Additionally though addition testing I’ve found that if a validationScript attempts to update any other form field which is visible and Read/Write the update does not stick, however if the form field is Read-Only the change made via the validation script does “stick”. Anyone else run into these issues?
I ran into an issue on 8.4p1 where validation scripts were firing twice causes a lot of issues with existing forms. I was told the fix was targeted for 8.4p2, but maybe it was not fixed and is related to your issue. I found this similar post at the time as well: Field validation happens twice in form(s)
I would add some logging to your scripts and see if you are seeing something similar because you should be able to get an e-fix. I was given one for 8.4p1.
Thanks for the response Patrick. We’ve definitely added the logging, the script is only being fired one time. We have a work-around, but it’s just that a work around. In the same spot in the validation script where the form field is being set, we are setting a temporary value in the identity model to hold the calculated value. From there we are then adding an afterScript to the form step in the workflow to extract that temporary value for further use in the workflow. It’s not pretty, but it works. The eFix would be a good idea, however we are on an extremely tight timeline and need to get this working in the next couple of weeks.
A little tangent but somewhat related on forms, I’ve had inconsistencies with the identityModel since running on 8.4. I’ll gather values from a form into an identityModel and do some manipulations to it in a post step. Then I’ll use the identityModel to create a plan to send into LCM Provisioning, but when the workflow resumes my identityModel will be reverted to it’s original key/values almost as if a rollback occurred somewhere.
It’s strange and the worst part is I can’t consistently reproduce it. I’ve had to resort to creating a cloned map and then replacing it if I detect a change.