Deploy Logics

When you have finished editing the logics, you can deploy them, even to multiple partitions, at once.

  1. Go to the Deploy panel. (If you do not see it, enable it in View > Tools Windows.) 

  2. Select the target environment, target partitions and objects to be deployed. There are some useful options to help you with the selection – see below. 

  3. Click Deploy
    If there are Groovy syntax errors detected in the code, you get a notification and cannot proceed with the deployment. In the notification, there is a link which takes you directly to the incorrect element.

Note that Deploy works with uniqueName of the logic; the folder of the logic is irrelevant.

Working with PfxDeploy Panel

You can switch projects and partitions:

For the list of entities you can:

  • Expand/collapse the entities list in a single click.

  • Select/unselect all visible entities.

  • Select objects in actual commit – Selects files which were last committed to Git.

  • Select objects from selected commit – Allows you to compare what has changed between a particular commit and the last one and these files are selected.

  • Select objects modified on the disk.

For a list of fetched items you can:

  • Select/unselect all visible items.

  • Reload calculation logics.

  • Show also Inactive and Simulation Only statuses (only for logics and Company Parameters) – By default, only objects with status Active are shown. This button allows you to show also objects with status Inactive or Simulation Only.

It can also be handy to compare an object with its version on the partition (this can be done in the Fetch window).

At the bottom of the panel you have additional options:

  • Test Input Generation – Turns on and off the input generation mode. It is disabled by default to make the deployment quicker.
    It is recommended to run this mode once in while to ensure the parameters are generated correctly (e.g. when you modify parameters or you want to use the logic in Price Lists or Dashboards).

  • Keep Labels Intact – Sets that the element labels should not be overwritten during deploy.

  • Keep User Groups – If checked, the user group setting (which user group can view/edit individual objects) at the partition is kept, it is not overwritten by your local settings. This is handy in cases when it is after Go Live, the security setup was handed over to the customer and you do not want to interfere with that.

 

 

Found an issue in documentation? Write to us.