Today Notes URLs can be used to open forms and compose new documents.
For example, this URL composes a new person document in the local address book:
Notes:///names.nsf/person?openform
It would be great to get support for URL arguments (on all Notes Client platforms and via the address bar), so that fields in the new document can get populated (text fields would be enough):
Notes:///names.nsf/person?openform&lastname=Lehmann&firstname=Karsten
This would be a great enhancement for the Nomad mobile clients.
We could add code in the form's QueryOpen/PostOpen methods to read these parameters and run application code, e.g. to do further data lookups, close the form, open a frameset to display the lookup result etc.
Another use case would a an integration with the Shortcuts.app, e.g. to select text in a mail and pass it to a CRM Notes application via the iOS share sheet. The CRM application looks up contact data and uses @UrlOpen with a tel: URL to start a phone call.
Karsten Lehmann, Mindoo GmbH
Perhaps add a new checkbox form property "Formulas inherit values from URL arguments" which if set, will (when composed) have Notes / Nomad / Domino default each field value to the argument with the same name (if one exists). Similar to the property "Formulas inherit values from selected document".
Make it work with XPiNC as well.
It should be possible to use non Domino URL commands without getting the error message "Unknown URL Exception"
This would allow many many new things !
I misinterpreted. You want the CGI variables and @URLQueryString to work in the Notes Client as well as on the web.
Fair question. I’ll promote it.
I don't think that you can do this today with a Notes URL in the Notes Client, but maybe I am missing something.
I just created a new form with computed text.
Tried the following as formula:
Query_String
Query_String_Decoded
@UrlQueryString("lastname")
lastname
@DocFields
All returned no result when I opened the form with this URL in the Notes Client's address bar:
notes:///test/urlargtest.nsf/person?openform&lastname=Lehmann
Karsten
Dear guest: yes you miss something. The use case Karsten has in mind covers situations where you don’t own the form or can’t touch it. In these situations you can’t alter your @Formula. Also it makes things simpler since you don’t need to add @if conditions to check if there is a parameter and otherwise use a default. Makes sense in integration scenarios
Not sure I understand. Using and @ function, you can read those parameters now, and use them as defaults for your fields. I must be missing something here.