There is a lot of sample code in the API documentation, though probably nothing that exactly matches what you want to do.
First you need to determine which of the objects you need. If you compare the descriptions for the database Tables with the descriptions for the Objects, you'll find matches; i.e. the RUN table and the RunObject. To get a pointer to a specific entity, like a Run, usually you used a Factory with a filter identifying the specific record you want. To get a specific Run, you would use a RunFactory.
Some objects have Properties that point directly to their parent object. For instance if you look at the Step object (which corresponds to the STEP table and the executed test steps) you will see that it has a Run property. This is a pointer to the Run of which the specified Step is a member.
Are you well versed in the entities and their relationships? If not you may want to spend some time studying the Database Reference doc. It includes entity relationship diagrams that show how objects in the various functional areas link to each other. Once you understand your starting point, you can use the ERDs to figure out the links to get to what you want, Then you can look at the API objects to find the corresponding objects, and review their properties to see if they provide direct pointers or just an ID for the related object.
You can find out which workflow to customize by using a MsgBox in the ActionCanExecute workflow to display the name of the Actions run when you click various buttons. This is described in the Administrator Guide in the section on Workflow Customization.
Do some studying and experimenting. Then come back with some specific questions about the code you write.
First you need to determine which of the objects you need. If you compare the descriptions for the database Tables with the descriptions for the Objects, you'll find matches; i.e. the RUN table and the RunObject. To get a pointer to a specific entity, like a Run, usually you used a Factory with a filter identifying the specific record you want. To get a specific Run, you would use a RunFactory.
Some objects have Properties that point directly to their parent object. For instance if you look at the Step object (which corresponds to the STEP table and the executed test steps) you will see that it has a Run property. This is a pointer to the Run of which the specified Step is a member.
Are you well versed in the entities and their relationships? If not you may want to spend some time studying the Database Reference doc. It includes entity relationship diagrams that show how objects in the various functional areas link to each other. Once you understand your starting point, you can use the ERDs to figure out the links to get to what you want, Then you can look at the API objects to find the corresponding objects, and review their properties to see if they provide direct pointers or just an ID for the related object.
You can find out which workflow to customize by using a MsgBox in the ActionCanExecute workflow to display the name of the Actions run when you click various buttons. This is described in the Administrator Guide in the section on Workflow Customization.
Do some studying and experimenting. Then come back with some specific questions about the code you write.
