Making run-time changes in FactoryTalk applications

Changes made to the development environment that can be transferred to the application while it is running are referred to as 'runtime edits'. These fall into four groups:

Edits that take effect immediately.

Edits that require a non-disruptive action, such as reopening a graphic display, before they take effect.

Edits that require a disruptive action, such as restarting a server or a run-time client, before they take effect.

Edits that cause adverse effects immediately.

Warnings have been added to

FactoryTalk

to tell users if making an edit in the development environment will adversely affect the run-time system. If the change is made through a dialog box, this warning icon ico_warning

appears next to the component where the edit can be made.

Hovering the mouse cursor over the ico_warning

icon displays the following warning:

Modifying this data at run time could cause unexpected results. See 'Making run-time changes in
FactoryTalk
applications' in the online help.

If the edit is made through a menu item, a warning message is displayed when the user clicks the menu item.

When this icon or warning message displays, it indicates that if the change is made while the application is running, it will have one or more of the following adverse effects:

One or more of the run-time clients (for example, the

FactoryTalk View SE

Display Client) might become unresponsive (for example, does not respond to mouse input).

One or more of the run-time clients might stop displaying correct data (for example, a changing tag value is not reflected in the client).

One or more of the

FactoryTalk View

processes might crash or stop responding.

Edits that cause adverse effects

Editing the name of a computer hosting a

FactoryTalk Linx

server,

OPC