nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Workflow Transition Comment

Faizi

Hi All,

I am using TS 6.7.1 SP1, WFM 1.0.0.1, Windows 2003 Server.
I wanted to trim the Task Transition Comment in the Workflow created in WFM 1.0.0.1. Can anybody help how can we do this?

Thanks

Find more posts tagged with

Comments

Sailesh

Hi All,

I am using TS 6.7.1 SP1, WFM 1.0.0.1, Windows 2003 Server.
I wanted to trim the Task Transition Comment in the Workflow created in WFM 1.0.0.1. Can anybody help how can we do this?

Thanks

What do you mean by Trim the comments? You mean you have put in long comments but want to display just bit of it?

Faizi

Actually, In the workflow there is Deploy Task which is a normal deployment. When this task perform either on success/failure, it gives a long transition comment (default). That's shown in Job Details.

Question is how to trim/short this comment?

Thanks

kaalraa

Actually, In the workflow there is Deploy Task which is a normal deployment. When this task perform either on success/failure, it gives a long transition comment (default). That's shown in Job Details.

Question is how to trim/short this comment?

Thanks

Could you please share an example of the specific transition comment?

Faizi

Here is the example attached and marked.........

Sailesh

Here is the example attached and marked.........

How are you doing your deployment? Is it an external task (ipl) which is calling a deployment? If so you can control the comments rather then displaying what been returned.

Faizi

It is a Deploy Task of WFM not WFT.
Internally it calls a java class "DeployURLExternalTask". We have to pass a parameter of deployment config file (deploy.xml etc).

kaalraa

It is a Deploy Task of WFM not WFT.
Internally it calls a java class "DeployURLExternalTask". We have to pass a parameter of deployment config file (deploy.xml etc).

While returning to the workflow engine, you have provided the complete return code being provided by the script.

Instead of catching the exception, put custom message while returning.

Adam Stoller

It is a Deploy Task of WFM not WFT.
Internally it calls a java class "DeployURLExternalTask". We have to pass a parameter of deployment config file (deploy.xml etc).

Then you need to modify (or create your own copy in place of) the java class and find the point in the code where it performs a callback to the workflow engine. It is in the callback that the transition comment is being passed and then showing up within the GUI.

If you do that, however, make sure you also ensure that the full diagnostic information gets output into a log file - otherwise you're shooting yourself and/or your TeamSite administrators in the foot when it comes to trying to track down and resolve deployment issues.