Hi ,

Received error message after clicking on create new test script button in test plan.
This issue started only after ALM 12.21 Patch 6 upgrade to Patch 7.
In the common script module, below is the code associated with TS_Version field.

Dim TS_Version
TS_Version = userfield("Version","TEST")

Function userfield(label,tablename)
sql = "Select SF_COLUMN_NAME as thecolumn FROM SYSTEM_FIELD WHERE SF_USER_LABEL="’ & label & "’ "
sql = sql & "AND SF_TABLE_NAME="’ & tablename & ""’

set req = requestRecordset(sql)
if req.Recordcount > 0 then
result = req.FieldValue("thecolumn")
else
msgbox "Error for the field " & label
result=""
end if

userfield = result
end Function

After this code is executed, string value "TS_USER_TEMPLATE_03" is stored in TS_Version variable.

For Version Labeled UDF , in ALM customization project entity’s list, type is NUMBER and length is 255. But when we describe TEST table and see the datatype for this same column in TEST table it is VARCHAR2(255). Not sure, why it got created as datatype varchar2(255) when it is declared as NUMBER in ALM , also not sure how code "Test_Fields(TS_Version).Value = 0" is working in Patch 6 and why it is failing in Patch 7.

In the Test_New module, we have below code:

Sub Template_Test_New
Test_Fields(TS_Version).Value = 0
End Sub

Error message is triggered at the line `Test_Fields(TS_Version).Value = 0`

Below is the screenshot of workflow error message:

![alt text][1]

Same line of code is executing from Visual Studio Debugger without any issues ,but from IE it is failing:

? Test_fields(TS_Version).Value = 0
True

Below is the clue i found but could not convert into a acceptable solution:

Looks like issue is definitely with "OTAClient.Core.dll" and might not be with the workflow script.
In patch 6 its size is 773 KB , where as in Patch 7 its size is 765 KB.As part of my trouble shooting steps, I replaced the problematic Patch 7 "OTAClient.Core.dll" with Patch 6 "OTAClient.Core.dll" in ALM userprofile location i.e. "C:\\Users\\<<>>\\AppData\\Local\\HP\\ALM-Client\\<<>>.Post that, issue did not occur in Patch 7, test script creation is not leading to "Specified Cast not valid" error message.

But, since it is not a acceptable solution, I could not rollout to user machines.

Could some one help on the below questions:

1. What is the cause of this issue, and how this issue can be fixed?

2. If there is no other option other than modifying workflow script, what is the change that has to be made in workflow?

Regards, Srihari

[1]: /storage/temp/964-ts-version-workflow-error-message.jpg