Databases
StackOverflow2013
Postsdbo
POPlone 4 - History for second workflow won't show in @@historyview
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POPlone 4 - History for second workflow won't show in @@historyview
    primarykey
    data
    text
    <p>I have a dexterity content type in Plone 4.2.4. The versioning works fine with the <code>default workflow</code> for this content type, although it is not a workflow shipped with plone, but a custom made.</p> <p>However, when I enable a second workflow for the same type, everything but the versioning works fine. </p> <ul> <li>additional permissions managed by the second workflow are working</li> <li>The state changes are working</li> </ul> <p>The difference:</p> <ul> <li>I used different <code>state_variable</code> names for the workflows, which seems to make sense, to have a catalogable field for the state of the second workflow.</li> </ul> <p>I've tried to use the same state variable name, but that didn't help. I have the workflow variable <code>review_history</code> also set in the 2nd workflow and sufficient permissions in the context. I am (mostly) shure, that I got the permission concept, but I have no clou, how permissions get calculated, when multiple workflows are involved.</p> <p>Any idea, why the second workflow does not leave a trace in my content types history?</p> <p>Thanks very much in advance.</p> <p><strong>Udate</strong></p> <p>I've reordered the workflows as Ida Ebkes suggested and did see, that all transitions from the 2nd workflow get stored properly. So it seems to be an issue with the historyview. </p> <p>Since these workflows indeed describe concurrent behaviors of a content type, I really would like to stick with separate workflows and ideally different workflow state variables and catalog indexes.</p> <p>What I now think needs to be done, is to tweak the historyview. </p>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USansi_lumen
    1. USansi_lumen
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POPlone 4 - History for second workflow won't show in @@historyview
      1. This table or related slice is empty.
      1. VTUpMod
    2. VO
      singulars
      1. POPlone 4 - History for second workflow won't show in @@historyview
      1. This table or related slice is empty.
      1. VTUpMod
    1. COI can confirm your observations, only the transitions of the first assigned wf are tracked in the history. But this appears to concern only the history-form. The modifications seem to be stored completely, because if you switch the order of the wf's, older modifications of the new first wf are visible, also. Would you like to give some more insights of your use-case? Maybe there are other ways to solve your requirements.
      singulars
      1. POPlone 4 - History for second workflow won't show in @@historyview
      1. USIda Ebkes
    2. COThank you very much for this hint. I had the feeling, that it gets stored, but not displayed, but found no way to confirm my feeling about this. The reordering of the workflows, assigned to my type shows that theese transitions get stored.
      singulars
      1. POPlone 4 - History for second workflow won't show in @@historyview
      1. USansi_lumen
    3. COEven more oddly, if you change the order of wf's and the current state is one of the now 2nd-wf, the state cannot be displayed, instead one of the new wf-states is displayed!? Anyway, you write your workflows 'describe concurrent behaviours', hard to guess, what that means exactly, but any chance, placeful-wf can help you here?
      singulars
      1. POPlone 4 - History for second workflow won't show in @@historyview
      1. USIda Ebkes
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload