Executing Objects

Objects can be executed either manually or automatically because they are inserted in other objects (Workflows, Schedules, Groups) that automate their processing. As a developer and object designer, you execute objects in the Process Assembly perspective after defining them to check if they behave as expected. For this purpose, you have three options: Execute them immediately, once or recurrently. As an operator, you execute objects from the My Catalog or Dashboard perspectives and you only have the option to execute them immediately. Whether you can execute objects or not depends on the rights that have been granted to your user definition.

Considerations

• Tasks are objects that are being or have been executed. Whereas objects are available in the Process Assembly perspective, tasks are visible in the Process Monitoring, Dashboards and My Catalog perspectives, provided you have the necessary rights and your Dashboard or My Catalog is configured accordingly.
• When you define an object you must decide when it will be executed, whether at activation or at runtime. For more information about the implications of this setting, see Generating at Activation or at Runtime.
• The terms Parent and Child are commonly used with objects and tasks. Child objects are activated by a superordinate object such as a Schedule or a Workflow.
• When you execute a Workflow, its children are not affected by the Time Zone defined for the Workflow. They have their own Time Zone definition, which you can specify on the Time & Dependencies tab that is displayed when you select a particular task in the Workflow and click the Properties button on the toolbar.
• In the case of Job objects, the status ENDED_OK is set as soon as the execution has ended. Post Processing options do not result in the status of the task changing to ACTIVE.

This chapter provides information on the following: