Limitations :

• Haley cannot insert a record.
• Haley cannot delete a record.
• Haley cannot replace browser script that interacts with the user or desktop.
• Haley cannot interact with the user to get information or answer questions.
• There is no way to make dynamic search specifications for business components. (Haley would have to be part of workflow.)
• Haley cannot interrogate the application for things like LoginName, PositionId, PositionName etc. (Haley would have to be part of workflow.)
• One cannot set values or get values from an entity that is not related to the current record. So, for example, if I want to update a record in a business component that is not related to the current business component, I cannot do it. (Haley would have to be part of workflow.)
• Haley cannot disallow duplicate child records. In order to “see” all the records for a particular parent, a runtime event would have to be configured on the parent record. It is only then that Haley can iterate over the records. It does iterate by the way. This fires the BusComp_ChangeRecord event for each record in the child business component.

What it can do:

• Get/set profile attributes
• Get/set field values
• Get the active view name
• Can be invoked from script/workflow/runtime event