Manual: In this mode, you can do a File > Save to update the Staging version, and then a File > Publish to update the Published version.By default the project is set to Auto, which means both the staging and published version of the project will always be synchronized. Here you specify how project publishing is handled. The audit profile stores the audit events when auditing is enabled. If auditing is enabled, audit events that relate to this project will be stored in the chosen audit profile. To define the roles, go to the Gateway's Configure section under the Security > User, Roles page, click the manage users link, and then go to the Roles tab. If no roles are specified, the user only needs to correctly authenticate with the User Source in order to log in. Users must have at least one of the roles in order to log in. You can optionally specify a list of roles that are required for a user to log into this project. This property is for Client logins, and determines what role(s) a user must have before they can log into the Client. To use the default database connection, use the special connection, or in scripting, the empty-string connection "".Ĭhoose the User Source that governs this project's security: specifically, which group of users ( User Sources) is allowed to log into the client. The User Sources are all defined in Gateway's Configure section under the Security > User, Roles page. This is the default database connection to use for this project. The Client poll rate (in milliseconds) is the rate at which a Vision Client or Ignition Designer polls the Gateway for updates to its subscribed Tags. To use the default provider, simply omit the source section of a Tag path, or leave it blank, for example: Path/To/MyTag or Path/To/MyTag. The Tag provider chosen here will act as the project's default tag provider. However, if you used the explicit Production_DB connection in your groups and screens, you will need to laboriously switch the bindings over to New_DB. If your project consistently used its default database connection, the switchover will be as simple as changing the copied project's default database. You copy the project and create a new database connection, named New_DB. Now you want to adapt the project to a new, similar plant, while leaving the existing project intact. By consistently using the default option, you make your project more resilient to change.įor example, suppose you have a project, and it has a database connection named Production_DB. If your project is like most typical projects, it primarily uses a single database and a single Tag provider. Wherever you use a database connection or a Tag in a project, you are always given the option to use the project's default, or an explicitly named connection or provider.
It is important to understand how to use defaults effectively for proper project design. Under Project > General is where you set the project's Default Database and its Default Tag Provider.