DOCUMENTS_BY_SEARCH_FT Strategy

You have two possibilities here:

DOCUMENTS_BY_SEARCH_FT or DOCUMENTS_BY_SEARCH_FT_PAGED

Route DOCUMENTS_BY_SEARCH_FT
router.GET('search') {
	strategy(DOCUMENTS_BY_SEARCH_FT) {
			databaseName('names.nsf')
			runAsSigner(true)
	}
	description '<b>Executing a full text search</b>'
	mapJson 'UNID', json:'unid', type:'STRING', isformula:true, formula:'@Text(@DocumentUniqueID)'
	mapJson 'Created', json:'Created', type:'DATETIME', isformula:true, formula:'@Created'
	mapJson 'Modified', json:'Modified', type:'DATETIME', isformula:true, formula:'@Modified'
}

URL to call

http://localhost/rest/myfirst.nsf/xsp/.xrest/search?search=entwicklungsserver

Testing with postman


Depending on the amount of search results there is a chance you run into a timeout. Then you can ask for a paged JSON response. To do so, add _PAGED to the strategy name:

strategy(DOCUMENTS_BY_SEARCH_FT_PAGED)

The postman test changes to:



When using the _PAGED strategy option, you can define the next slice using:

http://localhost/rest/myfirst.nsf/xsp/.xrest/search?search=entwicklungsserver&start=10&count=10