Configuring invitee form in invitation-based user onboarding

[Community_User]

Originally posted on October 14 2020 at 19:20 UTC

Hello,

Configuring invitation-based user onboarding in https://saviynt.freshdesk.com/support/solutions/articles/43000553743-invitation-based-user-onboardin... talks about inviter and invitee forms.

AFAIK inviter form is the form that is displayed with Create User Request and invitee form is the form available via tokenised hyperlink. Invitee form seems to follow Update User Request.

Is it supported to configure invitee form that hides some fields that would be otherwise visible in Update User Request? Lets say for example "enddate" would be editable in Update User Request, but "enddate" would be not editable and hidden in invitee form.

Thanks,

Juha

[Community_User]

Originally posted on November 4 2020 at 07:30 UTC

Yes, you should be able to hide/unhide certain attributes based on other dynamic attributes in the form. e.g. you can have attributes meant for invitation only show up when an attribute "Creation Type" is marked as "Invitation" while other attributes show up when "Creation Type" is "Create Directly".

Regards,

Aditya

[Community_User]

Originally posted on November 4 2020 at 16:52 UTC

Thanks for responding, however my use case is slightly more complicated.

So, what I am looking for is something like this:

- Hide "enddate" field from Request form when Contractor is accessing the form via external token link (via invitation)

- Show "enddate" field in Request form when Employee is accessing the form via ARS / Update User Request

If I set to hide "enddate" field when "Creation Type" is "Invitation", then the same action string applied to everyone having access to the form and it wont be visible to anyone.

Thanks,

Juha

[Community_User]

Originally posted on November 5 2020 at 06:26 UTC

I understand. A workaround to this would be to have two end date fields, one show only on Create Request (controlled by the Invitation Type) and the other which shows up only on Update Request. Hopefully this solves your problem.

[Community_User]

Originally posted on November 5 2020 at 06:47 UTC

I made a feature request about this.

The issue is not when creating users, but when updating users afterwards.

Since the same "Hide On Update" flag on register user attribute controls the visibility when responding to the invitation and when using "Update User Request", the problem remains even when using two fields.

Thanks,

Juha

[Community_User · Accepted solution]

Originally posted on November 17 2020 at 12:57 UTC

Fair enough. I will add the feature request to our product backlog.

Regards,

Aditya