Module : Script
Issue |
Type |
TrialGrid Version |
Description |
|---|---|---|---|
5547 |
Feature |
A script can now create Forms as well as records of the object types you define. The attributes are the Form's own columns, named as the ALS workbook names them, together with any custom properties your URL has added to Forms. A Form has to be given an OID and a name, and the Draft cannot already hold a Form with either of them. The other built-in object types cannot be created from a script yet, and the command says so by name. |
|
5548 |
Feature |
A script can now create records of an object type, not just the object type itself. One command creates one record with the values it holds, naming the attributes as the object type names them. A record of an object type that sits inside another names its parent by identifier, and an attribute that points at another record names it the same way. |
|
5536 |
Feature |
The help now lists every command a script can issue, with what each one does, the arguments it takes and the values each argument allows. |
|
5482 |
Feature |
Applying the commands from an Import Script run happens in the background and reports progress as it works, so a run which asks for many commands is not limited by how long a page can wait. |
|
5434 |
Feature |
Import Scripts can create a draft, link it to a standard library, copy named forms from that library and then import every other library object those forms make applicable. Objects which need a visit folder the new draft does not have are not imported. |
|
5513 |
Feature |
Script capabilities are now documented under their own Script module in the validation documentation, with a page describing what a script can do and the controls on it. Entries previously listed under Study build now appear under Script. |
|
5481 |
Feature |
An Import Script command can now say which URL, Project or Draft it acts on, so one script can build the same objects in several of them. |
|
5425 |
Feature |
An Import Script can now apply commands that act on a URL, not only on the Organization. |
|
5390 |
Feature |
An Import Script can now read a spreadsheet cell by cell, for files that hold a value at a known address such as D7 or key and value pairs down two columns, instead of only a table under a header row. |
|
5370 |
Feature |
An Import Script test run can now apply the commands it built, after you have reviewed them. A script can also walk a file whose shape it does not know in advance - taking a row's column names and values together in the order the sheet declares them, or asking a document what keys it holds - and asking a file for something the other kind of file offers now says which kind was uploaded instead of naming an internal type. |
|
5323 |
Feature |
A test run of an Import Script can now be pointed at a Draft, Project or URL, and the script can read from it. Settings that name a Draft, Project or URL are chosen from the same searchable list, with Projects that hold Standard libraries marked. |
|
5262 |
Feature |
Import Scripts can now be tested against a real file, showing what the script would do without changing anything. |
|
5246 |
Feature |
Import Scripts can now declare the settings they need. |
|
5237 |
Feature |
Organizations can now register Import Scripts, ready for importing data from Excel, JSON and YAML files. |