Other than the automation documentation indicates, the HierarchyHeaderWidth and ColumnOrder properties of the SAPTree class are write only and cannot be read.
Ensure that your scripts use write rather than read with these properties.
GetColumnIndexFromName() of the SapTree class may fail with an "unspecified error". This is a known issue in SAP automation.
Check the SAP web site to see if the issue has been resolved.
Calling the Select() method of the SAPTree class on a Context menu item may fail.
Call SelectContextMenuItem on the parent control instead. This problem is a known issue in the SAP automation.
The position property for a horizontal scrollbar always returns 1. This is a known issue in SAP automation.
Check the SAP web site to see if the issue has been resolved.
This issue will be resolved in a future release.
In certain cases, if you record an SAP test and then replay it, the following error might occur: The data necessary to complete this operation is not yet available. This means that Silk4J is executing the recorded actions too fast.
To solve this issue, you can add sleeps to your test script or you can increase the post replay delay to increase the time that Silk4J waits after invoking a function or setting a property. For additional information about this option, see Agent Options. You could also change the script to use SAP automation to replay the problematic action instead of using the xBrowser technology domain. For example, you could change the action DomLink.Select to SapHTMLViewer.SapEvent.
If you use SAPGUI client 7.30 and you call the method getCurrentRow, the method might falsely return -1 instead of the row number.
If you use SAPGUI client 7.30 and you call the method resizeWorkingPaneEx, the method will not resize the workingPane and calling getSapWindow().getWidth() will return a wrong value for the window width.