Date: Fri, 29 Mar 2024 00:56:18 +0000 (UTC) Message-ID: <81124775.10841.1711673778502@911f0a1bad02> Subject: Exported From Confluence MIME-Version: 1.0 Content-Type: multipart/related; boundary="----=_Part_10840_2138451486.1711673778501" ------=_Part_10840_2138451486.1711673778501 Content-Type: text/html; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Content-Location: file:///C:/exported.html
With the release of Servoy 7.3 the upgrade path for the 6.1.x branch wil= l be the Servoy 7.x branch, as Servoy 7.x can be considered Servoy 6.1.x + = Servoy Mobile. This means that Servoy 6.1.6 is the last update in the Servo= y 6.1 branch and that installations that run Servoy 6.1.x can upgrade to Se= rvoy 7.3, skipping 7.0.0 - 7.2.
The auto-update mechanism in Servoy Developer and the command-line upgra= de mechanism in the Servoy Application Server will start offering the Servo= y 7.3 version as update on Servoy 6.1.x releases as of November 8 2013.
For more information on all supported version, see Supported Versions
See the following links for the Release Notes of previous 7.x.x releases= :
application.get/setS=
erverURL()
to specify the URL of the Application Server to which the=
Mobile Client will connect to access it's Service Solution.security.authentic=
ate
is called from custom login form. This way, the URL is set befor=
e any calls to server are done application.getApplic=
ationType()
JSFoundSet.getRecord=
Index(JSRecord)
plugins.mobile.getUU=
IDPKValueAsString
plugins.mobile.getUUIDPKValueAsStr=
ing
method allows to get the UUID PK value for a specific JSRecord. =
This is needed in case callbacks are made from the Mobile Client to the Ser=
vice Solution outside the the built-in sync mechanism and information about=
specific records needs to be communicated.@designtime
new/removeValueList(=
)
to solutionModel
application.get/setU=
serProperties
support to the Service Solutionapplication.getUserProperty()=
, the properties and their values will be send back to the Mobile Cl=
ient where they are persisted. With each subsequent request to the service =
solution the properties and their values will be send back to the service s=
olution, where they can be accessed through application.getUserProperty. No=
te that the sending of the properties and their values back to the service =
solution with each request is only applicable to requests made by the Servo=
y API. In custom AJAX calls done through JQuery for example, the special HT=
TP Request Headers that take care of sending the properties and their value=
s to the service solution are not set and thus the properties and their val=
ues are not available in the service solution.@typedef
(https://developers.google.com/closure/compiler/docs=
/js-for-compiler) where one can have a variable that is then an alias f=
or a more complex type. The variable name can then be used in @param =
{varname}
or @type {varname}
@protecte=
d
annotation on members of constructor functionsapplication.output()<=
/code> statements with WARNING and ERROR level appear in red in the Console=
in Servoy Developer, so they stand out more
Behavior Changes
Due to the implementation of SVY-5036: 'Added application.get/setUserProperties support =
to the Service Solution', the behavior of get/setUserProperty
=
in the Headless & Batch Processor clients has changed.
APPLICATION_TYPES.MOB=
ILE
datab=
aseManager.saveData(JSRecord/JSFoundSet)
from within table events on=
related recordsJSDataSet.getColumnNa=
mes()
JSComponent.getD=
esigntimePropertyNames()