Example User Requests¶
See also
If you’ve arrived at this page directly it may be worth briefly taking in some of the general configuration notes.
Similarly, if you’re receiving requests which are likely to require updating
AP-Portal
to the latest public version additional, general notes are
available in the Updating – Remote AP-Portal/ApPredict changes section of this documentation.
Please change the values of ion channel variability.¶
client
The variability values are defined in thesite-business
appCtx.config.assays.site.xml
file as per the extensibility instructions.client-direct
The visible default values of spread variability are defined in theclient-direct
appCtx.config.site.xml
file as per the installation instructions.
Please change the default CellML model.¶
This is set by having only one of the available models assigned a
defaultModel
value of true
in the following :
client
Thesite-business
appCtx.config.cellModels.site.xml
file as per the extensibility instructions.client-direct
Theclient-direct
appCtx.config.cellModels.site.xml
file as per the installation instructions.
Note
See [3] regarding the change deployment technique.
Please change the values of credible interval percentiles.¶
The variability percentile values are defined in the following :
client
Thesite-business
appCtx.config.actionPotential.site.xml
file as per the extensibility instructions.client-direct
Theclient-direct
appCtx.config.site.xml
file as per the installation instructions.
Please modify information displayed by the information icons.¶
Currently the information displayed by is not configurable. [2]
Information icons appear in various places throughout the client
and
client-direct
UIs. Modification of the information they display is
generally not possible as they are designed to enable the provision of an
internationalised AP-Portal
. It is of course possible to directly
change the AP-Portal
code base, rebuild and redeploy, but if tempted to do so
please be careful regarding
version control conflicts).
Having said that, parts of the values they display may be flexible, e.g. the
sample below is taken from a middle.jsp
file in client-direct
.
1 2 3 4 5 6 | <td colspan="4" class="input_division cs_rounded_5">
<spring:message code="general.notes" />
<img src="${info_location}" class="info"
title="<spring:message code="input.notes_max_chars"
arguments="${notes_length}" />" />
</td>
|
In the above we can see the use of the <spring:message code="general.notes" />
which, when the UI is to display the corresponding web page, will read in
and display the general.notes
property value derived from
the src/main/resources/bundle/general[<_locale>].properties
files [1].
What is also visible is the use of the <spring:message code=".." arguments="<args>" />
option which allows dynamic replacement of values which may be derived from,
for example, values defined in configuration settings and so could be a technique
for future (non-i18n!) information display.
Please add the new CellML models the ApPredict
developer has released.¶
Please see ApPredict updating.
Please modify the warning/error messages.¶
As is the case with Please modify information displayed by the information icons.
the warning messages are general not modifiable except by request to the
AP-Portal
developers. Whilst some error messages are internationalised
some are also derived from hard-coded messages in back-end components.
Please update AP-Portal
to incorporate the new development in the public version.¶
There are unfortunately no one-size-fits-all step-by-step guides to doing this
unless it’s known what the modifications to the AP-Portal
have been between the
currently installed version and the latest available public version.
Some general updating notes are available which may provide guidance.
Footnotes
[1] | The “locale” is considered to be the browser’s current preferred display language. |
[2] | Any suggestions for change or queries would be welcomed by the portal developers! |
[3] | (1, 2, 3) Modification of the configuration files should ideally be done prior
to rebuilding and redeploying the relevant component (as opposed to directly
modifying the content of an expanded .war file in the servlet
container and restarting the component). |
[4] | (1, 2) See also Variability Configuration. |