I'm not usually using Agent in Lotus Notes because I always Lotusscript button only. But recently I need to do a function in Lotus Notes using using an Agent. So in some of an Agent, I found this:
Option Public
Option Declare
Use "ParametersMaster"
Use "CommonFunctions"
Use "Class.QueryString"
Some Lotusscript code...
I don't really understand what are the functions of these "Use" and where to find them. I know this is kinda simple question and I would like somebody help me on this to understand what it is. Thanks!
The "Use" commands loads external script libraries. Usually these script libraries are found in the same database under the Script Libraries design elements.
Refer to the Help in Designer for a much better answer 😀
Related
I would like to modify the Field Help of NetSuite's Standard / Native field. How to do?
Thanks for reading this question.
Any type of related information will definitely help me to move a step ahead towards solution.
I have tried without success UserEvent Script on BeforeLoad event this (SS2.0):
scriptContext.form.getField('tranid').setHelpText({help:'Test'});
The example above is working only with fields created by scriptContext.form.addField.
There is no way to do it with ClientScript (no access to setHelpText method there).
And of course, there is no customization tool.
The only way is to use DOM, which is not recomended by Netsuite, and for sure is not a good practice.
As I have asked questions in this form - thanks for your many helpful answers - i have found many really neat things that one can do using ExtLibUtil.???? however, other than a bit here and a bit there I have not found anything that gives a listing on the various functions. I one post I read that it is all in the source of the extension Library, and it might be if you really understand where in the source to look. Sure would appreciate a pointer and starting point.
I've been unable to find a JavaDoc for it. The library slipped passed us when we wrote the book - certainly I was not as au fait with Java to be aware of it and all the strength within it. So the best option currently is to look at the source code in Eclipse. Many of the methods are helper methods to easily access things like viewScope etc, which is easy from SSJS but less easy from Java. Most are pretty self-explanatory.
Content assist doesn't seem to work from SSJS, but will from any Java class or, alternatively, open up one of the Java classes created for XPages / Custom Controls under the "local" package in Package Explorer, type "ExtLibUtil." in any method and you'll see the list.
I noticed that sitecore has the option of exporting users in an Excel format.
I need to have similar functionality for exporting 'participations', (a users can enlist to take part in an 'event', and if their entry is approved via a sitecore workflow, a 'participation' item is created in the content tree)
Since mostly everything in Sitecore is in essence based on items, and I want to export items to Excel, my question is - what are some of the best ways of doing this?
Questions:
Is there a way to re-use this functionality for regular items?
Would it be a good idea to create a custom admin page (any tips on doing this?) which has some custom code that reads the items from the database using the API?
are there sitecore plugins/shared source projects that can help me achieve this?
Or does anyone have a better idea? - would it be better to just store the participations in SQL? I'm mostly doing it this way because I want to make use of the 'free' functionality offers, for example workflow, but if that leads to me using anti-patterns please shoot me ;)
Link is different now: https://marketplace.sitecore.net/en/Modules/Advanced_System_Reporter.aspx
P.S. Couldn't leave a comment to original answer as I don't have enough reputation. Oh well :)
Found a most excellent shared source module which does exactly this (and much more)!
Basically it allows you to configure (and easily extend, if you need to) any kind of table based report on 'items'.
The report module shows up as an application in the sitecore menu (like the user manager tool) and comes with features such as xml,csv, xls export. It's also really easy to set up, once you get the hang of it.
http://trac.sitecore.net/AdvancedSystemReporter
I'm in the process of adding some much needed client side form validation to a website I'm working on. We're currently using YUI. YUI doesn't have any form validation built in as I can see(prove me wrong).
I googled it
http://code.google.com/p/yui-form-validator/
It's not important that it's a YUI-extension as long as it plays along with YUI in a civilized manner.
What should I go for? Anyone out there with experience and an opinion?
There's a module in the gallery: http://yuilibrary.com/gallery/show/form
I haven't used it, but it looks pretty good to me.
Looks like we'll go for http://validatious.org/
Lightweight and standalone. Will not interfere with YUI.
I want to add a calendar control to a page that already includes Prototype and Scriptaculous. Not happy with any of the Prototype ones I could find, I'm considring using the YUI Calendar widget.
I this likely to cause any problems?
We have worked hard to make sure that YUI is safe to use with any other library. We namespace everything, as HermanD says, under only one required global (YAHOO) and one optional one (YAHOO_config). We don't modify native objects. And even though Protoype does modify native prototypes, we code defensively so that this doesn't break YUI functionality.
If you find any bugs in using the two together, please let us know.
Regards,
Eric
YUI Team
By default everything in YUI is within the YAHOO namespace, so as long as you sensibly apply namespaces to anything you use from YUI, I would have thought you should be ok.
See: http://developer.yahoo.com/yui/yahoo/
I successfully used the YUI tab control in an app I was already using Prototype and Scriptaculous in and had no problem. The weight of all that is a bit much though if you're looking at a publicly available app. I wouldn't care so much about an internal app, say for a company, but you might want to think about how much JavaScript you're making end users download and the number of separate files they're having to download for the page.