Whenever there is a need to implement any functionality on based of some trigger,
we usually use Run time vent where we invoke some workflow or business service or Data validation If the Workflow is also based on the active business object, system will automatically set the "Object Id" process property with the Row Id of the primary business component on UI. Moreover, the complete context of the UI handed over to the workflow. RTE will not get invoked if the business object, on which workflow is based on, is different from the UI context BO. For example, assume the user drills down on a Contact, clicks the Service Requests view tab, updates the Status field, then steps off the record. In this case, the service request record is being written in the context of the Contact Business Object, and the run-time event does not fire. So scenarios where workflow is not based on any BO then In the RTE action set, we can set the profile attibutes as the first step and in the next step call the desired workflow. Then inside the workflow, we can read the profile attribute values.