| || |
ClearQuest - technical problem
First, I'm sorry for my English (I'm from Russia)
I found one critical impossibility in ClearQuest ideology, and I need to resolve it.
During submit action, in dependence of user-choosen value in one of the record fields, we want to transfer stated-record in database into 2 different state.
For example we have entity REQUEST. It has a field TYPE.
When SUBMIT and user choose TYPE=BUG, record must go into ANALYSIS state, but
When SUBMIT and user choose TYPE=IMPROVEMENT, record must go into DISCUSSING state.
I tried to use many different ways to resolve problem: from standard ClearQuest API to SQL-programming.
No decision I found. When I use sql-updates functions ClearQuest suppress this ("only SELECT allowed"). Field "State" is read-only. And so on.
May be anyone had resolved this problem earlier? I will wait for answer.
Big thanks for answers.
Re: ClearQuest - technical problem
Dobryi dien Alexis,
When you are in the process of submitting a record or changing its state (action type = CHANGE_STATE), it is not possible to use a hook to trigger another CHANGE_STATE action. It is not even possible to do it in the notification hook.
So you have to find another way.