Question on using CQ hook to create RTC WI, with bridge
In RTC 3.0 bridge integration with CQ, users can create new WI from CQ web. We are thinking about automating this step, by adding a CQ hook to automatically create a WI when a record is transitioned to Assigned. In the WI, we could put the CQ record URL into the link. However, we would not know the WI URL to be put back into the CQ record.
Is there a utility that can go through RTC WIs and update their related CQ records with the link to the WI? Any advice and recommendation?
Thanks a lot!
Rachel
Is there a utility that can go through RTC WIs and update their related CQ records with the link to the WI? Any advice and recommendation?
Thanks a lot!
Rachel
2 answers
When you issues a Work Item creation using the REST API, namely doing a POST to the factory URL of the initial Work Item contents, it should return with 2 main pieces of information:
1. a 201-Created response, stating it has been created.
2. in the Location HTTP response header, the URI of the Work Item created.
Your utility (hook) can extra this Location value to get the URI, then update the CQ record with this information.
Another option to consider, is whether the CQ synchronizor may meet some of your needs.
1. a 201-Created response, stating it has been created.
2. in the Location HTTP response header, the URI of the Work Item created.
Your utility (hook) can extra this Location value to get the URI, then update the CQ record with this information.
Another option to consider, is whether the CQ synchronizor may meet some of your needs.
Note that in general, we recommend that folks push the CQ Bridge to its
limits before using the CQ Synchronizer (which is a relatively big hammer).
Cheers,
Geoff
On 12/6/2010 3:38 PM, sspeiche wrote:
limits before using the CQ Synchronizer (which is a relatively big hammer).
Cheers,
Geoff
On 12/6/2010 3:38 PM, sspeiche wrote:
When you issues a Work Item creation using the REST API, namely doing
a POST to the factory URL of the initial Work Item contents, it
should return with 2 main pieces of information:
1. a 201-Created response, stating it has been created.
2. in the Location HTTP response header, the URI of the Work Item
created.
Your utility (hook) can extra this Location value to get the URI, then
update the CQ record with this information.
Another option to consider, is whether the CQ synchronizor may meet
some of your needs.