Check also: How can I set up a new application?
You can find an order you have sent from composer in “Open orders” or in “Instancies” > search for your app.
Also you can use the globalsearch in deployment to find your application (with ctrl-F or clicking it) > so for instances it will look through the application url and the application description.
Presentation Layer: should be Kendo;
Checkboxes: for a standard workflow, check the first two boxes to automatically start integration and generation. Make sure that the third one is NOT checked, so it is still possible to add dataconversion before installation;
Checkbox extra: the fourth check mark is nice to have, but optional. It automatically starts the installation workflow once the order is sent to the Installer;
Model: if you are making a new model, you need to select “New model” and specify the name of your model;
Source: Specify the complete svn url: https://svn.novulo.com/novulo/projects/mXXXXX/trunk where XXXX is your modelnumber.
Instance:
- the name of your instance (or name of your application) could be the same as the name of your model, but you usually want to specify whether this application is used for testing your model or not; this name will also be displayed in the browser when using the application instance;
- the server can either be Lokaal uitrollen (local hosting) to test your application on your own computer, Staging01 to test your application online or a server specified by a customer;
- the directory depends on whether you’re hosting locally or not. If you’re hosting locally, the directory needs to be the same as the directory on your pc in C:\inetpub\wwwroot (more on this in the chapter Component development, as local hosting is mostly interesting for developers). If you’re not hosting locally, Deployment will generate a directory based on the name you specify here, meaning that for instance the name can’t use spaces. Use all lower case characters, no whitspaces or special characters! This name is also used as database name, etc. Disk quota can be left blank. (Initial default quota assigned is 1 GB).
More > Release log
Here you can see on what step you are in the deployment.
Update scripts
If there is any data conversion you need to approve updatescripts. Tip! DO NOT APPROVE IF you don’t fully understand the changes. Ask the Project Owner first.
Check also What is wrong with my update script?
Installation workflow
During the deployment the installation workflow informs you where you are in the deployment flow and whether there are any errors or concers.
For example, the deployment will stop if there are TODO items you need to process before installation. Go to the “installation concers” > TODO items > read every item carefully and check what must be done or taken into account > mark an item as skipped, irrelevant or done.
Other possible error - if there is a blocking (unfinished) installation. Click on the link “Blocking installation” and finish it:
To finish deployment > click on the Installer link as soon as the message tells you so:
Click on Yes to accept changes. Tip! Before clicking on the “Yes” button you can open your app and test changes. After you can decide if you want to keep them or no. If you click no, any changes will be applied:
