Hi i'm designing an infopath form which uses a web service and load some combo boxes, this service needs the username of the user as parameter.
I need the form to load data in formload method
How do i set the username as the default parameter in infopath?
InfoPath has a built-in function called userName() you can use to get the currently logged in user. You can use this function in rules such as Form Load, etc.
Related
Is it possible to direct a user to a user flow along with a value that we want to set on a custom attribute? We dont want the user to be able to edit this field, it is ok if they see it.
I would like to have a custom app where the user will fill out some info, the app will validate their info against an internal database and return a value we would like to store in a custom attribute (an internal username).
I would then like to send the user off to a sign up user flow where they can either create a local account or create an account with an external IDP and the custom attribute would be pre populated for them and not editable.
To pre-populate the claim, set it as an input field on the form.
To make it non-editable, copy it to a readonly claim and display the readonly claim as an output.
To pass the data, make the whole flow a sign-up flow.
You can call a REST API in the flow to validate the data. Store the return value in an extension attribute.
Then ask the user if they want to federate with an external IDP.
If so, do the federation and add the value to the social account.
If not, create a local account and add the value.
You would have to create an external account beforehand.
I figured out you can send back custom errors from a rest API. What I am ending up doing is gathering the data from the user, sending it to a custom API for validation, then if it validates properly, the API returns the custom attribute.
If the validation fails I can return errors to the B2C that will be shown on the sign up page.
I have a requirement where i want to validate a template using Access Code, but i want to bypass the access code validation by passing the Access code programatically(similar to how we can bypass the Initiator landing page https://docs.docusign.com/supportdocs/ndse-help/Content/populate-custom-fields.htm#pnz1578456644088).
There is a value you can enter to bypass the access code validation. If you append the parameter ActivateOnly=1 at the end of your Email PowerForm URL, the recipient will not have to enter an Access Code
A Sample PowerForm URL would look like this:
https://www.docusign.net/Member/PowerFormSigning.aspx?PowerFormId=ad01e352-158a-4380-96c9-9cbc4366028t&ActivateOnly=1
It is explained in more detail here:
https://support.docusign.com/en/articles/Email-PowerForms-How-to-remove-system-generated-Access-Code-requirement
The problem with this option is that it requires users to access the powerform from their email
If you need the template to be both available to your internal sending users as well as your Powerform, then split them up.
Duplicate your template by using "Create a Copy" from the drop-down menu. Rename the one being used by your PowerForm and unshare it with your users. Remove the Access Code requirement from the template role.
Edit the duplicate template. Ensure this one is shared with your users.
If a person has previously filled out a contact us form on our website, the next time they visit that form I would like their information pre-populated. Using Kentico EMS and the form builder, how can I make that happen?
you can access the contact informant via macros or custom macro methods and place it in the contact form default values (I would use an alternative form), but often you do not know if the user already exists unless they are logged in or enter the same email (which you would then need to add a client side trigger to Ajax an api once the email field is filled out, check for that contact in the api, return json of their info and populate the form).
to build the api you can either use the Kentico rest service or if you need more flexibility use the web part to api coupled with a repeater with custom query, adding the right where condition through macros.
My use case is that I would like customers to log in via a custom Login Form I have created, but not from NetSuite Login which is publicly accessible. How can I achieve that?Any ideas?
One way to do your own branded custom login page (with your own HTML/CSS), is by creating a form that on submit sends a POST request to https://system.netsuite.com/app/webservices/wslogin.nl?c=######
where ##### is your netsuite account number
the form must submit following attributes:
email
password
taskid // see the help topic Task Ids for valid values e.g.: LIST_MYROLES
role // not required if has a default role specified on the View All Roles page
I don't think that there is a way to block the normal UI login so, that only custom login is allowed.
In addition to what Prasun wrote there are a couple of different approaches to custom login/reg forms.
One is to just hack the login form so that it looks and behaves like you want it to. See the login/registration at http://www.lablearning.com/
The other is to create your own login page using an SSP page and install it to override the built-in login/registration.
We have a document library that contains a list of proposals (InfoPath Forms). Users log in through SharePoint using Claims (Forms Auth, via an Extranet) who are from various organizations. The forms open in InfoPath on the client. The InfoPath form contains a field for what organization the proposal belongs to (a select list) that the user then selects when filling the form.
We have written a custom claims provider that augments each user's login with an organization claim.
When the user opens a proposal from SharePoint in the InfoPath form filler, we'd like to:
Pre-populate the organization select list with the organization
matching the user's claim
Restrict the saving of the form (inserting and updating) if the
user's claim value for organization does not match the selected
organization on the form
I'm wondering how to get the claims information in InfoPath. Or, for ideas on how to do this server-side using a custom workflow/event receiver/web service (or something else).
Here is a basic tutorial for getting claims from SharePoint 2010. Place this in the code behind of your InfoPath form. http://msdn.microsoft.com/en-us/library/ee535731.aspx
Ideally you want to call the code from the FormEvents_Loading method of your InfoPath form and if the user's organization is invalid, create a bool, that if false, will prevent the form from submitting. This would be done in the FormEvents_Submit method.
I'm not sure if this works for your specific implementation however, you can set the data source for input controls (drop down lists, list boxes, etc) to be retreived from a web service.
You can then use hidden fields on the eForm which are populated with the metadata you need such as the user Id. These values are subsequently passed to the webservice and the return (List or whatever) are bound to the desired controls within the eForm.