It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×10,961

question asked: Mar 21 '12, 9:45 a.m.
question was seen: 4,016 times
last updated: Mar 21 '12, 9:45 a.m.

Related questions

Tasks artifact "message" element.

0
Aaron Shepherd (37●1●6●7) | asked Mar 21 '12, 9:45 a.m.
Hi,

I have been playing around with reading and updating artifact data via the REST API and discovered that the tasks artifact has an optional "message" element. According to the tasks.xsd schema, the message element can be defined to provide "information about a task." This was very exciting for me as I have been looking for a way to provide contextual information as I dynamically update the task's progress during execution. Unfortunately, I either am doing something wrong, or the element is not supported in the RQM interface.

For my testing I am executing RFT tasks. By default, the message element is not included in the task sent to the RFT adapter. I do not see any way of specifying a message in the RQM interface, nor do I see any place holder text in the execution status page where the message may appear. I have manually created the message element and updated the executing task, but the message does not appear anywhere on the execution status page, nor does it appear anywhere in the execution result.

I have verified that the task artifact is being updated by also updating the progress and verifying the update on the status page, and by performing a GET on the task during execution and verifying that the message element is included in the response. Has anyone had experience with this element and can provide feedback on whether or not the behavior I am seeing is expected? What is the intended use for this element?

2 answers

Most liked answers ↑|Newest answers|Oldest answers

0
permanent link
Robert Rassmann (992●3) | answered Mar 27 '12, 2:42 p.m.
FORUM MODERATOR / JAZZ DEVELOPER
Hi,

I have been playing around with reading and updating artifact data via the REST API and discovered that the tasks artifact has an optional "message" element. According to the tasks.xsd schema, the message element can be defined to provide "information about a task." This was very exciting for me as I have been looking for a way to provide contextual information as I dynamically update the task's progress during execution. Unfortunately, I either am doing something wrong, or the element is not supported in the RQM interface.

For my testing I am executing RFT tasks. By default, the message element is not included in the task sent to the RFT adapter. I do not see any way of specifying a message in the RQM interface, nor do I see any place holder text in the execution status page where the message may appear. I have manually created the message element and updated the executing task, but the message does not appear anywhere on the execution status page, nor does it appear anywhere in the execution result.

I have verified that the task artifact is being updated by also updating the progress and verifying the update on the status page, and by performing a GET on the task during execution and verifying that the message element is included in the response. Has anyone had experience with this element and can provide feedback on whether or not the behavior I am seeing is expected? What is the intended use for this element?


Hi Aaron,

I think you've hit upon one of the elements that was put in early on but was never used. You may want to create an enhancement workitem that explains what you are trying to accomplish. That way we can review it for a future release.
0
permanent link
Aaron Shepherd (37●1●6●7) | answered Mar 28 '12, 2:16 p.m.
Hi,

I have been playing around with reading and updating artifact data via the REST API and discovered that the tasks artifact has an optional "message" element. According to the tasks.xsd schema, the message element can be defined to provide "information about a task." This was very exciting for me as I have been looking for a way to provide contextual information as I dynamically update the task's progress during execution. Unfortunately, I either am doing something wrong, or the element is not supported in the RQM interface.

For my testing I am executing RFT tasks. By default, the message element is not included in the task sent to the RFT adapter. I do not see any way of specifying a message in the RQM interface, nor do I see any place holder text in the execution status page where the message may appear. I have manually created the message element and updated the executing task, but the message does not appear anywhere on the execution status page, nor does it appear anywhere in the execution result.

I have verified that the task artifact is being updated by also updating the progress and verifying the update on the status page, and by performing a GET on the task during execution and verifying that the message element is included in the response. Has anyone had experience with this element and can provide feedback on whether or not the behavior I am seeing is expected? What is the intended use for this element?


Hi Aaron,

I think you've hit upon one of the elements that was put in early on but was never used. You may want to create an enhancement workitem that explains what you are trying to accomplish. That way we can review it for a future release.

Robert.

I was afraid of that. I'll look into adding an enhancement. Thanks

Your answer

Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.