Anonymous user access rights to view for filling a combobox - xpages

I'm building a form that will be used by anonymous users. On the form is a combo box that I want to pre-fill so they can pick one of the items. The items that would fill the combo box are in a database view that is not available to anonymous users.
My initial attempt at doing this was to use a basic Notes form and an agent in the WebQueryOpen event to fill the combo box. Since that agent ran under my name the combo box got filled in.
When I moved it to xpages, the combo box was empty. I realized it was because the javascript is running under a non-authenticated user (when I authenticate with my username/password it works correctly).
How do people typically address this issue?
thanks
clem

sessionAsSigner is designed to access documents the current user doesn't have access to.

Related

If I type an address in a dialog box, is the website owner notified of the text?

If a type in a dialog box on a website, is the owner of the website able to access the text? Note I have not submitted the page or draft in any way.
Furthermore if the dialog box is a address bar and comes up with address suggestions and I pick one is the owner of the website able to access this information? Note I have also not submitted the page or draft here.
Many Thanks
If you mean by dialog box input fields inside an HTML page, then the frontend code can listen to changes on the input fields, while you are typing and send that information to the backend. Nothing stops the frontend code from doing that, so it is possible.

unable to forward form created in notes designer 9 to notes 9 to share with clients

I have create a form in Notes Designer version 9.0 and i am unable to forward this form to any users, as i do not find Forward Button under Create Menu.
Not sure if am looking at right options to forward the form, please help.
Thank You
Venu
There are two classic approaches to publishing a form for users to fill out.
Set the Store Form in Document property on the form (see here), and add mail fields (SendTo, Subject, etc.) to it. Add a button that is only visible to you and use #MailSend code in that button to send a document to the people you want to fill out the form. Add another button that is visible to the recipients, and use #MailSend code in that button to send the document back to you, or to a mail-in database. The form will accompany the document wherever it goes. (It will be stored in a field called $Form.)
Just put the form in a database on your server, and set the ACL so that your users can create documents in that database. Send an email message to all the users containing a button with code that executes #Command([Compose]...) with the options set to point to the correct server, database, and form.
Note that both of the above techniques assume that the people you want to fill out the form have Notes clients. If that's not the case, then what you'll want to do is this:
Just put the form in a database on a server that is running the Domino http task, and set the ACL so that your users can create documents in that database. Send an email message to all the users containing a link in the form http://server/path/databasename.nsf/formname?OpenForm

MS CRM Block all entity forms from user

I am an admin for MS CRM 2011 and I have this demand that certain users - although they have READ access to an entity - should NOT have access to any of this entity's forms.
Meaning, they should only view the records via sub grids, on related records.
Is there a way to have such control over user view?
You could make all the tabs on the form invisible unless the user had certain roles(s) through JavaScript.
This seems like a very strange request. Any chance you could elaborate?
Put these users in a role. Create a new form for each entity and assign that form to that role. Make sure these users do not have access to the other forms by role. Don't put any fields on this new form and maybe even add a javascript pop-up error message and some code that closes the form immediately.
This way your other forms aren't slowed down by a javascript request that always checks role membership plus everything is contained in that special form instead of spread through your other "real" forms.
if this entity just hold relationships like a N:N entity would do, you can also make sure that the relationship (reference to it) is not shown on the navigation area of the related entity forms. This way its there but no one can 'use' it.

Default selected Item in Connected web part

I have a web part connected to another (provide a row to).
It shows the radio button that when clicked correctly provides the data to the second web part.
Can I have this radio button selected by default so that it automatically provides the filter data as soon as the page is loaded?
Thanks in advance
Sachin
You can do this by XSTL web part connection. You can user sharepoint designer for it.
Pleaes ref the following link
http://sachinvkatkar.blogspot.com/

How to allow Users to request access to a particular document in SharePoint?

I would like to create something in SharePoint that allows users to request access to particular documents and then for me to be able assign access for a period. Would this be possible in SharePoint? If so, how would i go about doing this? What must i use?
Thanks in advance!
Set up a SharePoint Group for those documents and then allow users to request membership to the group.
This is how I would do it:
Add a hyperlink column to the Document Library
Add a 'New Item' event handler to the DL which adds the url to the hyperlink column, and point the hyperlink to your own ASP.Net page (or even the DL itself), with details of the document required (ID et al) in the GET string. Call this hyperlink 'Request Access' or something similar.
Create a webpart which checks the GET string for the right variables, identifies the user (currently logged in user viewing the page the webpart is on) and sends you an email informing you of the request. Add this webpart to the target ASP.Net page in step 2.
When a document is added, the event handler will update the hyperlink column with the required hyperlink. When a user requires access, they will click on the properly formed hyperlink, which will take you to a page with the receiver webpart on it. The receiver webpart will get the required information from the GET string, inform you via email, and also inform the user that the request has been received.
Although I'm sure theres a better way to do this...
You can modify the "popup" menu that's shown while hovering over the document. Add a link to that menu, here's an example of how to change the hover menu:
www.articlestreet.com/computers/send-a-sharepoint-document-library-file-as-email.html

Resources