collective-pcng

[Collective-pcng] Changing The Default Workflow

[<to...@to...>]

Version Info
============
Plone version: 2.0.5
Zope version: (Zope 2.7.6-final, python 2.4.1, cygwin)
Apache version:
CMF version (if known): CMF-1.4.7
Browser(s) and version(s): Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
Operating system: cygwin
Python version: 2.4.1 (#1, May 27 2005, 18:02:40)
[GCC 3.3.3 (cygwin special)]
Debug mode: Yes

Installed Products
==================
Archetypes 1.3.3-final installed
...
CMFPlone 2.0.5
...
DCWorkflow CMF-1.4.7
...
PloneCollectorNG 1.2.7 installed
...

Issue
=====
I'm trying to add to the pcng_issue_workflow workflow, and I'm running
into a couple of problems.  Any help at all would be greatly appreciated.

Basically, I've completed the following steps:

1.  I created a pending_defect state with the following properties:
 - Title: Pending Defect
 - Possible Transitions:
  - reaccept
  - resolve
  - wont_fix

2. I then created the pending_defect transition with the following
properties:
 - Destination state: pending_defect
 - Trigger: User action
 - Script (after): send_notifications
 - Requires role: TrackerAdmin ; Supporter or Owner
 - Adds to actions box: pending defect
 - Variables
	assigned_to = python: list(state_change.kwargs['assignees'])

3. Finally, I opened the "accepted" state and added pending_defect as a
possible transition.

4. I then opened a new issue, assinged it to myself, and saved it.  After
that, I created a followup, and tried to choose the pending_defect radio
button.  Here's the tracebac:

Traceback (innermost last):
  Module ZPublisher.Publish, line 101, in publish
  Module ZPublisher.mapply, line 88, in mapply
  Module ZPublisher.Publish, line 39, in call_object
  Module Products.PloneCollectorNG.Issue, line 238, in issue_followup
  Module Products.CMFCore.WorkflowTool, line 299, in doActionFor
WorkflowException: No workflow provides the "pending defect" action.

I then saw on the Zopyx web site that I "must re-create the workflow and
catalog tool through the corresponding option under Configuration ->
Maintenance".  I therefore clicked on the "Recreate catalog and workflow
tool" link.

After doing that, I went back to my workflow and tried to tranisition it
to the pending_defect state via a followup.  However, my pending_defect
action is no longer a choice.

Is there something that I'm doing wrong?  There seems to be a step that
I'm missing?  Any help at all would be greatly apprecaited.

Thanks!

Tom Purl

Re: [Collective-pcng] Changing The Default Workflow

[Andreas J. <an...@an...>]

--On 6. Juni 2005 17:05:34 -0500 to...@to... wrote:

> Version Info
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Plone version: 2.0.5
> Zope version: (Zope 2.7.6-final, python 2.4.1, cygwin)
> Apache version:
> CMF version (if known): CMF-1.4.7
> Browser(s) and version(s): Mozilla/4.0 (compatible; MSIE 6.0; Windows NT
> 5.1) Operating system: cygwin
> Python version: 2.4.1 (#1, May 27 2005, 18:02:40)
> [GCC 3.3.3 (cygwin special)]
> Debug mode: Yes
>
> Installed Products
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Archetypes 1.3.3-final installed
> ...
> CMFPlone 2.0.5
> ...
> DCWorkflow CMF-1.4.7
> ...
> PloneCollectorNG 1.2.7 installed
> ...
>
> Issue
> =3D=3D=3D=3D=3D
> I'm trying to add to the pcng_issue_workflow workflow, and I'm running
> into a couple of problems.  Any help at all would be greatly appreciated.
>
> Basically, I've completed the following steps:
>
> 1.  I created a pending_defect state with the following properties:
>  - Title: Pending Defect
>  - Possible Transitions:
>   - reaccept
>   - resolve
>   - wont_fix
>
> 2. I then created the pending_defect transition with the following
> properties:
>  - Destination state: pending_defect
>  - Trigger: User action
>  - Script (after): send_notifications
>  - Requires role: TrackerAdmin ; Supporter or Owner
>  - Adds to actions box: pending defect
>  - Variables
> 	assigned_to =3D python: list(state_change.kwargs['assignees'])
>
> 3. Finally, I opened the "accepted" state and added pending_defect as a
> possible transition.
>
> 4. I then opened a new issue, assinged it to myself, and saved it.  After
> that, I created a followup, and tried to choose the pending_defect radio
> button.  Here's the tracebac:
>
> Traceback (innermost last):
>   Module ZPublisher.Publish, line 101, in publish
>   Module ZPublisher.mapply, line 88, in mapply
>   Module ZPublisher.Publish, line 39, in call_object
>   Module Products.PloneCollectorNG.Issue, line 238, in issue_followup
>   Module Products.CMFCore.WorkflowTool, line 299, in doActionFor
> WorkflowException: No workflow provides the "pending defect" action.
>
> I then saw on the Zopyx web site that I "must re-create the workflow and
> catalog tool through the corresponding option under Configuration ->
> Maintenance".  I therefore clicked on the "Recreate catalog and workflow
> tool" link.
>
> After doing that, I went back to my workflow and tried to tranisition it
> to the pending_defect state via a followup.  However, my pending_defect
> action is no longer a choice.
>
> Is there something that I'm doing wrong?  There seems to be a step that
> I'm missing?  Any help at all would be greatly apprecaited.
>

Likely a problem of the workflow definition...but no idea to dig into your=20
code to figure out problems on your side...at least for free..

-aj

Re: [Collective-pcng] Changing The Default Workflow

[Tim C. <tw...@sh...>]

Tom,

I went through this a couple of months ago and finally found the
solution by creating another workflow definition on the filesystem.=20
There were also some hoops to jump through but I can't recall them at
this point.  I intended then to write a HOWTO, but you know how that
goes........

We were implementing some change management features into the workflow
and (as you did) found that working inside the ZMI did not make the
workflow changes visible in the product. =20

You can see the result here if you like, though from the UI it doesn't
tell you a whole lot:
http://coruscant.chime.ucl.ac.uk:8200/openEHR_Collector/projects/specificat=
ions/CR/

It does require (free) membership to the site.

I will gather this info (I have to extract it from email discussions I
had with a colleague) and write something up but it will likely be the
end of the week.  If you haven't heard anything by Friday feel free to
harass me via email.

Cheers,
Tim



On Mon, 2005-06-06 at 15:05, to...@to... wrote:
> Version Info
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Plone version: 2.0.5
> Zope version: (Zope 2.7.6-final, python 2.4.1, cygwin)
> Apache version:
> CMF version (if known): CMF-1.4.7
> Browser(s) and version(s): Mozilla/4.0 (compatible; MSIE 6.0; Windows NT =
5.1)
> Operating system: cygwin
> Python version: 2.4.1 (#1, May 27 2005, 18:02:40)
> [GCC 3.3.3 (cygwin special)]
> Debug mode: Yes
>=20
> Installed Products
> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D
> Archetypes 1.3.3-final installed
> ...
> CMFPlone 2.0.5
> ...
> DCWorkflow CMF-1.4.7
> ...
> PloneCollectorNG 1.2.7 installed
> ...
>=20
> Issue
> =3D=3D=3D=3D=3D
> I'm trying to add to the pcng_issue_workflow workflow, and I'm running
> into a couple of problems.  Any help at all would be greatly appreciated.
>=20
> Basically, I've completed the following steps:
>=20
> 1.  I created a pending_defect state with the following properties:
>  - Title: Pending Defect
>  - Possible Transitions:
>   - reaccept
>   - resolve
>   - wont_fix
>=20
> 2. I then created the pending_defect transition with the following
> properties:
>  - Destination state: pending_defect
>  - Trigger: User action
>  - Script (after): send_notifications
>  - Requires role: TrackerAdmin ; Supporter or Owner
>  - Adds to actions box: pending defect
>  - Variables
> 	assigned_to =3D python: list(state_change.kwargs['assignees'])
>=20
> 3. Finally, I opened the "accepted" state and added pending_defect as a
> possible transition.
>=20
> 4. I then opened a new issue, assinged it to myself, and saved it.  After
> that, I created a followup, and tried to choose the pending_defect radio
> button.  Here's the tracebac:
>=20
> Traceback (innermost last):
>   Module ZPublisher.Publish, line 101, in publish
>   Module ZPublisher.mapply, line 88, in mapply
>   Module ZPublisher.Publish, line 39, in call_object
>   Module Products.PloneCollectorNG.Issue, line 238, in issue_followup
>   Module Products.CMFCore.WorkflowTool, line 299, in doActionFor
> WorkflowException: No workflow provides the "pending defect" action.
>=20
> I then saw on the Zopyx web site that I "must re-create the workflow and
> catalog tool through the corresponding option under Configuration ->
> Maintenance".  I therefore clicked on the "Recreate catalog and workflow
> tool" link.
>=20
> After doing that, I went back to my workflow and tried to tranisition it
> to the pending_defect state via a followup.  However, my pending_defect
> action is no longer a choice.
>=20
> Is there something that I'm doing wrong?  There seems to be a step that
> I'm missing?  Any help at all would be greatly apprecaited.
>=20
> Thanks!
>=20
> Tom Purl
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you sho=
tput
> a projector? How fast can you ride your desk chair down the office luge t=
rack?
> If you want to score the big prize, get to know the little guy. =20
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20
> _______________________________________________
> Collective-pcng mailing list
> Col...@li...
> https://lists.sourceforge.net/lists/listinfo/collective-pcng
--=20
Tim Cook
Key ID 0203DEEC @ http://www.keyserver.net & http://keyserver.mine.nu
Get the key from: http://24.85.34.168:28080/Nikki_and_Tim/twcook_publickey.=
txt/file_view

Re: [Collective-pcng] Changing The Default Workflow

[<to...@to...>]

Thanks for the help Tim & Andreas.  I'll try creating the workflow on the
filesystem to see if that helps.

> Tom,
>
> I went through this a couple of months ago and finally found the
> solution by creating another workflow definition on the filesystem.
> There were also some hoops to jump through but I can't recall them at
> this point.  I intended then to write a HOWTO, but you know how that
> goes........
>
> We were implementing some change management features into the workflow
> and (as you did) found that working inside the ZMI did not make the
> workflow changes visible in the product.
>
> You can see the result here if you like, though from the UI it doesn't
> tell you a whole lot:
> http://coruscant.chime.ucl.ac.uk:8200/openEHR_Collector/projects/specifications/CR/
>
> It does require (free) membership to the site.
>
> I will gather this info (I have to extract it from email discussions I
> had with a colleague) and write something up but it will likely be the
> end of the week.  If you haven't heard anything by Friday feel free to
> harass me via email.
>
> Cheers,
> Tim
>
>
>
> On Mon, 2005-06-06 at 15:05, to...@to... wrote:
>> Version Info
>> ===========> Plone version: 2.0.5
>> Zope version: (Zope 2.7.6-final, python 2.4.1, cygwin)
>> Apache version:
>> CMF version (if known): CMF-1.4.7
>> Browser(s) and version(s): Mozilla/4.0 (compatible; MSIE 6.0; Windows NT
>> 5.1)
>> Operating system: cygwin
>> Python version: 2.4.1 (#1, May 27 2005, 18:02:40)
>> [GCC 3.3.3 (cygwin special)]
>> Debug mode: Yes
>>
>> Installed Products
>> =================> Archetypes 1.3.3-final installed
>> ...
>> CMFPlone 2.0.5
>> ...
>> DCWorkflow CMF-1.4.7
>> ...
>> PloneCollectorNG 1.2.7 installed
>> ...
>>
>> Issue
>> ====> I'm trying to add to the pcng_issue_workflow workflow, and I'm
>> running
>> into a couple of problems.  Any help at all would be greatly
>> appreciated.
>>
>> Basically, I've completed the following steps:
>>
>> 1.  I created a pending_defect state with the following properties:
>>  - Title: Pending Defect
>>  - Possible Transitions:
>>   - reaccept
>>   - resolve
>>   - wont_fix
>>
>> 2. I then created the pending_defect transition with the following
>> properties:
>>  - Destination state: pending_defect
>>  - Trigger: User action
>>  - Script (after): send_notifications
>>  - Requires role: TrackerAdmin ; Supporter or Owner
>>  - Adds to actions box: pending defect
>>  - Variables
>> 	assigned_to = python: list(state_change.kwargs['assignees'])
>>
>> 3. Finally, I opened the "accepted" state and added pending_defect as a
>> possible transition.
>>
>> 4. I then opened a new issue, assinged it to myself, and saved it.
>> After
>> that, I created a followup, and tried to choose the pending_defect radio
>> button.  Here's the tracebac:
>>
>> Traceback (innermost last):
>>   Module ZPublisher.Publish, line 101, in publish
>>   Module ZPublisher.mapply, line 88, in mapply
>>   Module ZPublisher.Publish, line 39, in call_object
>>   Module Products.PloneCollectorNG.Issue, line 238, in issue_followup
>>   Module Products.CMFCore.WorkflowTool, line 299, in doActionFor
>> WorkflowException: No workflow provides the "pending defect" action.
>>
>> I then saw on the Zopyx web site that I "must re-create the workflow and
>> catalog tool through the corresponding option under Configuration ->
>> Maintenance".  I therefore clicked on the "Recreate catalog and workflow
>> tool" link.
>>
>> After doing that, I went back to my workflow and tried to tranisition it
>> to the pending_defect state via a followup.  However, my pending_defect
>> action is no longer a choice.
>>
>> Is there something that I'm doing wrong?  There seems to be a step that
>> I'm missing?  Any help at all would be greatly apprecaited.
>>
>> Thanks!
>>
>> Tom Purl
>>
>>
>>
>> -------------------------------------------------------
>> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you
>> shotput
>> a projector? How fast can you ride your desk chair down the office luge
>> track?
>> If you want to score the big prize, get to know the little guy.
>> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=20
>> _______________________________________________
>> Collective-pcng mailing list
>> Col...@li...
>> https://lists.sourceforge.net/lists/listinfo/collective-pcng
> --
> Tim Cook
> Key ID 0203DEEC @ http://www.keyserver.net & http://keyserver.mine.nu
> Get the key from:
> http://24.85.34.168:28080/Nikki_and_Tim/twcook_publickey.txt/file_view
>
>

Re: [Collective-pcng] Changing The Default Workflow

[Bryan S. <bry...@gm...>]

I'm not entirely sure that changing the workflow on the filesystem
will give you anything at all.
Is it possible to alter the workflow and reinstall it without having
PCNG lose its mind?
I suppose if you were able to reinstall the workflow in Zope,
performing the recreate action in PCNG will solve it.  However, would
the action scripts still be tied to the reinstalled workflow or would
they too need to be reinstalled?

On 6/7/05, to...@to... <to...@to...> wrote:
> Thanks for the help Tim & Andreas.  I'll try creating the workflow on the
> filesystem to see if that helps.
>=20
> > Tom,
> >
> > I went through this a couple of months ago and finally found the
> > solution by creating another workflow definition on the filesystem.
> > There were also some hoops to jump through but I can't recall them at
> > this point.  I intended then to write a HOWTO, but you know how that
> > goes........
> >
> > We were implementing some change management features into the workflow
> > and (as you did) found that working inside the ZMI did not make the
> > workflow changes visible in the product.
> >
> > You can see the result here if you like, though from the UI it doesn't
> > tell you a whole lot:
> > http://coruscant.chime.ucl.ac.uk:8200/openEHR_Collector/projects/specif=
ications/CR/
> >
> > It does require (free) membership to the site.
> >
> > I will gather this info (I have to extract it from email discussions I
> > had with a colleague) and write something up but it will likely be the
> > end of the week.  If you haven't heard anything by Friday feel free to
> > harass me via email.
> >
> > Cheers,
> > Tim
> >
> >
> >
> > On Mon, 2005-06-06 at 15:05, to...@to... wrote:
> >> Version Info
> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> Plone version: 2.0.5
> >> Zope version: (Zope 2.7.6-final, python 2.4.1, cygwin)
> >> Apache version:
> >> CMF version (if known): CMF-1.4.7
> >> Browser(s) and version(s): Mozilla/4.0 (compatible; MSIE 6.0; Windows =
NT
> >> 5.1)
> >> Operating system: cygwin
> >> Python version: 2.4.1 (#1, May 27 2005, 18:02:40)
> >> [GCC 3.3.3 (cygwin special)]
> >> Debug mode: Yes
> >>
> >> Installed Products
> >> =3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D> Archetypes 1.3.3-=
final installed
> >> ...
> >> CMFPlone 2.0.5
> >> ...
> >> DCWorkflow CMF-1.4.7
> >> ...
> >> PloneCollectorNG 1.2.7 installed
> >> ...
> >>
> >> Issue
> >> =3D=3D=3D=3D> I'm trying to add to the pcng_issue_workflow workflow, a=
nd I'm
> >> running
> >> into a couple of problems.  Any help at all would be greatly
> >> appreciated.
> >>
> >> Basically, I've completed the following steps:
> >>
> >> 1.  I created a pending_defect state with the following properties:
> >>  - Title: Pending Defect
> >>  - Possible Transitions:
> >>   - reaccept
> >>   - resolve
> >>   - wont_fix
> >>
> >> 2. I then created the pending_defect transition with the following
> >> properties:
> >>  - Destination state: pending_defect
> >>  - Trigger: User action
> >>  - Script (after): send_notifications
> >>  - Requires role: TrackerAdmin ; Supporter or Owner
> >>  - Adds to actions box: pending defect
> >>  - Variables
> >>      assigned_to =3D python: list(state_change.kwargs['assignees'])
> >>
> >> 3. Finally, I opened the "accepted" state and added pending_defect as =
a
> >> possible transition.
> >>
> >> 4. I then opened a new issue, assinged it to myself, and saved it.
> >> After
> >> that, I created a followup, and tried to choose the pending_defect rad=
io
> >> button.  Here's the tracebac:
> >>
> >> Traceback (innermost last):
> >>   Module ZPublisher.Publish, line 101, in publish
> >>   Module ZPublisher.mapply, line 88, in mapply
> >>   Module ZPublisher.Publish, line 39, in call_object
> >>   Module Products.PloneCollectorNG.Issue, line 238, in issue_followup
> >>   Module Products.CMFCore.WorkflowTool, line 299, in doActionFor
> >> WorkflowException: No workflow provides the "pending defect" action.
> >>
> >> I then saw on the Zopyx web site that I "must re-create the workflow a=
nd
> >> catalog tool through the corresponding option under Configuration ->
> >> Maintenance".  I therefore clicked on the "Recreate catalog and workfl=
ow
> >> tool" link.
> >>
> >> After doing that, I went back to my workflow and tried to tranisition =
it
> >> to the pending_defect state via a followup.  However, my pending_defec=
t
> >> action is no longer a choice.
> >>
> >> Is there something that I'm doing wrong?  There seems to be a step tha=
t
> >> I'm missing?  Any help at all would be greatly apprecaited.
> >>
> >> Thanks!
> >>
> >> Tom Purl
> >>
> >>
> >>
> >> -------------------------------------------------------
> >> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you
> >> shotput
> >> a projector? How fast can you ride your desk chair down the office lug=
e
> >> track?
> >> If you want to score the big prize, get to know the little guy.
> >> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20
> >> _______________________________________________
> >> Collective-pcng mailing list
> >> Col...@li...
> >> https://lists.sourceforge.net/lists/listinfo/collective-pcng
> > --
> > Tim Cook
> > Key ID 0203DEEC @ http://www.keyserver.net & http://keyserver.mine.nu
> > Get the key from:
> > http://24.85.34.168:28080/Nikki_and_Tim/twcook_publickey.txt/file_view
> >
> >
>=20
>=20
>=20
> -------------------------------------------------------
> This SF.Net email is sponsored by: NEC IT Guy Games.  How far can you sho=
tput
> a projector? How fast can you ride your desk chair down the office luge t=
rack?
> If you want to score the big prize, get to know the little guy.
> Play to win an NEC 61" plasma display: http://www.necitguy.com/?r=3D20
> _______________________________________________
> Collective-pcng mailing list
> Col...@li...
> https://lists.sourceforge.net/lists/listinfo/collective-pcng
>=20


--=20

Regards,

Bryan Simmons

  "All parts should go together without forcing. You must remember
that the parts you are reassembling were disassembled by you.
Therefore, if you can't get them together again, there must be a
reason. By all means, do not use a hammer."
  -- IBM maintenance manual, 1925

Re: [Collective-pcng] Changing The Default Workflow

[Tim C. <tw...@sh...>]

On Thu, 2005-06-09 at 19:01, Bryan Simmons wrote:
> I'm not entirely sure that changing the workflow on the filesystem
> will give you anything at all.

Though I think changing the existing workflow should work.  Note I said
I created a new one so that I have an additional selection for new
instances of PCNG.  Using the recreate workflow/catalog function in
maintenance, I was able to apply the new workflow to an existing PCNG.

> Is it possible to alter the workflow and reinstall it without having
> PCNG lose its mind?

There is probably a caveat here as to what you do to the workflow. If
you're not careful you could leave instances in a state that would be
inescapable. :-)

> I suppose if you were able to reinstall the workflow in Zope,
> performing the recreate action in PCNG will solve it.  However, would
> the action scripts still be tied to the reinstalled workflow or would
> they too need to be reinstalled?

Again, you would have to be careful what you changed. This is (a major
reason) why I felt creating an entirely new WF on the filesystem was
better.  I just used the existing ones as a models.

Cheers,
--=20
Tim Cook
Key ID 0203DEEC @ http://www.keyserver.net & http://keyserver.mine.nu
Get the key from: http://24.85.34.168:28080/Nikki_and_Tim/twcook_publickey.=
txt/file_view