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; } } }

Finish / Next button transition in DCR with tt_data

yuvpurush

Win 2003 / TS 672 SP2

We have enabled tt_data for a workflow and accessing via CC STD.
When we edit the DCR, typically the transition button would display "Next" and upon clicking that, it will take to the workflow selection screen.

But weirdly, many times, instead of "next" button, "Finish" button is appearing and upon clicking that, the DCR is saved and the window closes without invoking the workflow (which is the behavior of Finish). The question is, why sometimes, it displays "Finish" button. If we logout and login again, then the "Next" button is appearing. This is happening on all DCRs, in Firefox and IE 7.

Can anyone shed some light on this?

Alternatively, can we configure that, workflow to be invoked upon clicking the "Finish" button as well?

Find more posts tagged with

Comments

nipper

Finish is *supposed* to start a WF if there is an appropriate tt_data setting for that scenario.

In 6.7.2 there was a bug that tt_data did not start a WFM unless there were WFT's defined as well.

Faizi

Win 2003 / TS 672 SP2

We have enabled tt_data for a workflow and accessing via CC STD.
When we edit the DCR, typically the transition button would display "Next" and upon clicking that, it will take to the workflow selection screen.

But weirdly, many times, instead of "next" button, "Finish" button is appearing and upon clicking that, the DCR is saved and the window closes without invoking the workflow (which is the behavior of Finish). The question is, why sometimes, it displays "Finish" button. If we logout and login again, then the "Next" button is appearing. This is happening on all DCRs, in Firefox and IE 7.

Can anyone shed some light on this?

Alternatively, can we configure that, workflow to be invoked upon clicking the "Finish" button as well?

There are lots of posting related to this topic. You just need to search on the forum.
You can instantiate a workflow using FormAPI after saving a DCR. You can also go through pdf (SitePublisher) document. You will find "Faq Entry" DCT code that has the workflow instantiation code through FormAPI.

HTH!

yuvpurush

I should have been more clear and i did search the entire forum before posting my first thread and it seems that my scenario is unique.

We are not using WFM but using WFT only. The tt_data is configured and it does work properly almost everytime.

The problem is when you open a DCR from the CCSTD window, it is supposed to display the "Next" button only as long as a tt_data is configured for that. However at times, it is displaying "Finish" button instead of "Next". My question is why the system is behaving that way.

As long as the user logout and login, the same DCR displays "Next" button.

@nipper
I tried the tt_data setting for the "finish" button, but it is not working in our environment. If you have the working setting for that, can you share the snippet for the same?

Faizi

Alternatively, can we configure that, workflow to be invoked upon clicking the "Finish" button as well?

My reply was for your above query. You can instantiate a workflow using FormAPI also. You do not need to configure tt_data command for that. In DCT just add FormAPI code to instantiate a workflow.
If you are using WFT then your task is more easy. Just explore these things.

yuvpurush

@Faizi
Thanks for your reply, and i want to use that option as the last resort.

The business was using tt_data for the past few yrs and once we migrated to the win 672 sp2, they are seeing this inconsistent behavior.

I am still trying to figure out if this is a known bug in win 672 sp2 and is there any configuration to fix this. If not, i am planning the form API route only.