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

Start workflow from Edit button

GregOrf

Is it possible to override or clone the edit button on the file explorer view of teamsite, so a user can start editing a dcr, and when the edit is complete start a workflow on the modified dcr. Could the save button from the edit window be overridden to run a workflow, but be smart enough to check to make sure the dcr wasn't launched from a workflow cgi?

My users think that having to select New Job from the drop down is to cumbersome.

We are running Teamsite 5.5.2 on solaris.

Thanks

Find more posts tagged with

Comments

nipper

Not quite

but do they need ot have a new job ? My users just click
close on the DCR and it starts the WF. The WF will find the
the associated file and include it (we keep consistant names
so we can do that).

You can restrict the WF only be started from tt_data

HTH

Andy

GregOrf

There isn't a job in the system for the dcr yet.

So I'm thinking that you added to the close functioanlity to tie it into the workflow, is that right? If so could I have the close start a workflow?

nipper

Yes. available_templates.cfg

<command value="tt_deletedcr" include="yes">
</command>
<command value="tt_data" include="yes">
</command>

in the command list. When you close a DCR it will ask you if you want to submit it.

iwovGraduate

Note: The "tt_data" is tied to the "close" button of the DCT. The workflow starts if and only if you hit the "close" button. (would be glad to find if its otherwise)

GregOrf

OK I read through the workflow pdf and am getting up to speed on the tt_data. Is tt_data tied to the "save and close" button as well as the "close" button?

Let me go through a scenario to see if this is possible.

Obviously we don't want anyone to be able to edit something outside of workflow (or in the case of using tt_data destined to be in workflow shortly).

User clicks edit.
edit dcr opens and user can change stuff.
Then the user clicks close. Is it possible somehow to get cgi window to popup, ask the user if they want to save changes and submit into workflow and capture some metadata here (or another cgi screen), like who to asign to and other variables needed for workflow, then send it off on it's way through the wonderful world of workflow. If they would select that they didn't wan't to save changes it would discard them, unlock the dcr and no workflow would be created.

nipper

>User clicks edit.
>edit dcr opens and user can change stuff.
>Then the user clicks close. Is it possible somehow to get cgi window to popup, ask the user if they want to save changes and submit into workflow and >capture some metadata here (or another cgi screen), like who to asign to and other variables needed for workflow, then send it off on it's way through >the wonderful world of workflow.

That part is not too tough.

> If they would select that they didn't wan't to save changes it would discard them, unlock the dcr and no workflow would be created.

Save & workflow are 2 atomic operations. So you can save without sending to WF. IMHO, that is the correct move, what if I make some changes
but not all the changes ? That allows work-in-progress saves. I wish cancel edit had an unlock option (query). You should file this as an
enhancement request. They ignore mine.

HTH

Andy

GregOrf

Thanks Andy,

Is it as simple as making the first workflow step a cgi task? Then I could verify that the dcr isn't in WF already, and decide if they want to start workflow and collect task data to populate the workflow. If the user wants to cancel then just unlock the file and revert the saved changes to the previous version.

I agree about the work-in-progress changes. In our normal workflow we handle that from cgi tasks.

I've been watching the dev forumn for a while now but haven't started posting until now. For the most part have been relying on the support site and tickets opened there. Get frustrated from there answers and all the reps want to do is sell us more products instead of helping overcome issues.

Greg

nipper

>Is it as simple as making the first workflow step a cgi task? Then I could verify that the dcr isn't in WF already, and decide if they want to start workflow >and collect task data to populate the workflow. If the user wants to cancel then just unlock the file and revert the saved changes to the previous version.
THere is a "pre-invocation" step where you collect information (get comments, can specify reviewers, etc).

I make the first step of a WF a root owned lock (& verify it is not locked already by root)

That prevents the file being in 2 WFs at once & prevents someone from editing or unlocking the file mid workflow
(except me of course, but rules are for mere mortals)

>I've been watching the dev forumn for a while now but haven't started posting until now. For the most part have been relying on the support site and
>tickets opened there. Get frustrated from there answers and all the reps want to do is sell us more products instead of helping overcome issues.

Good place to post questions. Depends on our mood. You will get RTFM a lot but you will also get some help.

One point, specific questions are a big plus. Too many people post My WF broke, what is wrong.....

sucking up is also helpful, but then I digress.

Andy