Processing order for AppEngines

By default, all objects deployed on an AppEngine are processed (scheduled) in the following order.

Note: You configure the process order of an ApplicationObject or an Area object using the Process Order option on the Object Information tab. For more information, click Attributes Help in the Help file header.

1. All DeviceIntegration Objects are processed first.

   Individual DeviceIntegration Objects are processed in alphabetical order, based on the tagname.

2. All Area objects (plus any hosted ApplicationObjects) are processed second.

   Individual Area objects are processed in alphabetical order based on the tagname, unless a valid process order configuration is specified. The process order for an Area object is ignored if it refers to another object that has any of the following characteristics:

   • The object is not an Area object.

   • The object is deployed to a different AppEngine.

   • The object is not yet deployed. (The process order configuration will become valid as soon as the referenced object is deployed to the AppEngine.)

     The process order configuration is also ignored if it results in conflicts or circular references.

     Individual ApplicationObjects hosted by an Area object are processed just before the host Area object. Individual ApplicationObjects within an Area are processed in alphabetical order based on the tagname, unless a valid process order configuration is specified. The process order configuration of an ApplicationObject is ignored if it refers to another object that has any of the following characteristics:

   • The object not an ApplicationObject.

   • The object is deployed to a different AppEngine or Area.

   • The object is not yet deployed. (The process order configuration will become valid as soon as the referenced object is deployed to the AppEngine.)

     The process order configuration is also ignored if it results in conflicts or circular references.

3. The AppEngine object is processed last.

The process order cannot be specified for WinPlatform objects, AppEngine objects, or DeviceIntegration Objects.

The process order configuration is not validated until the object is deployed. When the object is deployed, invalid settings are ignored, but no error is reported.